Terminal, wireless communication method, base station and system

Abstract

A terminal according to one aspect of the present disclosure includes: a reception unit that receives a first downlink control channel used to trigger a random access procedure with respect to a non-serving cell; and a control unit that controls the reception of a second downlink control channel used in the reception of a response signal in the random access procedure, on the basis of a first QCL assumption using a first quasi-colocation (QCL) corresponding to the first downlink control channel, and / or a second QCL assumption using a second QCL corresponding to a particular control resource set.

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 using multiple transmission / reception points (e.g., Multi-TRP (MTRP)) in a serving cell, or communications will be controlled based on inter-cell mobility including non-serving cells.

[0006] In this case, it is also assumed that UL transmission control (for example, implementation of a random access procedure (or setting of timing advance)) is performed for each transmission / reception point, or for each serving cell and non-serving cell. However, the problem arises as to how a terminal (user terminal, User Equipment (UE)) controls UL transmission (for example, timing advance control) for multiple transmission / reception points (or non-serving cells). If UL transmission to each transmission / reception point (or TRP of a serving cell / non-serving cell) is not appropriately controlled, the quality of communication using multiple transmission / reception points 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 communicating appropriately even when communication is performed using multiple transmission and reception points.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a first downlink control channel used to trigger a random access procedure for a non-serving cell, and a control unit that controls reception of a second downlink control channel used to receive a response signal in the random access procedure based on at least one of a first quasi-co-location (QCL) assumption that uses a first QCL corresponding to the first downlink control channel and a second QCL assumption that uses a second QCL corresponding to a specific control resource set.

[0009] According to one aspect of the present disclosure, communication can be performed appropriately even when communication is performed using multiple transmission points.

[0010] 1A to 1D are diagrams illustrating an example of multi-TRP. FIGS. 2A and 2B are diagrams illustrating an example of inter-cell mobility. FIGS. 3A and 3B are diagrams illustrating an example of switching between a serving cell and an additional cell by L1 / L2 signaling. FIG. 4 is a diagram illustrating an example of configuration example 1-3 when a candidate cell is supported. FIGS. 5A to 5C are diagrams illustrating an example of switching between a candidate cell and a candidate cell group by L1 / L2 signaling in configuration example 1-3 when a candidate cell is supported. FIG. 6 is a diagram illustrating an example of a timing advance group (TAG) to which cells included in a cell group belong. FIG. 7 is a diagram illustrating an example of a MAC CE for a timing advance command. FIGS. 8A and 8B are diagrams illustrating an example of QCL assumptions for a RACH procedure in a first embodiment. FIGS. 9A and 9B are diagrams illustrating an example of QCL assumptions for a RACH procedure in a second embodiment. FIG. 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 11 is a diagram illustrating an example of the configuration of a base station according to an embodiment. Fig. 12 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. Fig. 13 is a diagram illustrating an example of a hardware configuration of a base station and a user terminal according to an embodiment. Fig. 14 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] (Multi-TRP) In NR, one or more transmission / reception points (Transmission / Reception Points (TRP)) (multi-TRP) are considered to perform DL transmission to a UE using one or more panels (multi-panels). Also, it is considered that a UE performs UL transmission to one or more TRPs.

[0026] Note that multiple TRPs may correspond to the same cell identifier (ID), or different cell IDs, which may be physical cell IDs (e.g., PCIs) or virtual cell IDs.

[0027] 1A-1D illustrate an example of a multi-TRP scenario, assuming, but not limited to, that each TRP is capable of transmitting four different beams.

[0028] 1A shows an example of a case where only one TRP (TRP1 in this example) of multiple TRPs transmits to the UE (this may be referred to as single mode, single TRP, etc.). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

[0029] In this disclosure, single-TRP mode may refer to a mode in which multi-TRP (mode) is not set.

[0030] 1B shows an example of a case where only one TRP (TRP1 in this example) transmits control signals to the UE, and the multi-TRP transmits data signals (also called single master mode). The UE receives each PDSCH transmitted from the multi-TRP based on a single Downlink Control Information (DCI).

[0031] Figure 1C shows an example of a case where each of the multi-TRPs transmits a part of the control signal to the UE, and the multi-TRPs transmit data signals (this may be called a master-slave mode). Part 1 of the control signal (DCI) may be transmitted in TRP1, and Part 2 of the control signal (DCI) may be transmitted in TRP2. Part 2 of the control signal may depend on Part 1. The UE receives each PDSCH transmitted from the multi-TRP based on these parts of the DCI.

[0032] 1D shows an example of a multi-TRP mode in which each TRP transmits a separate control signal to the UE, and the multi-TRP transmits a data signal (also referred to as a multi-master mode). A first control signal (DCI) may be transmitted on TRP1, and a second control signal (DCI) may be transmitted on TRP2. The UE receives each PDSCH transmitted from the multi-TRP based on these DCIs.

[0033] When multiple PDSCHs from multiple TRPs as shown in Figure 1B (which may also be referred to as multiple PDSCHs) are scheduled using one DCI, the DCI may be referred to as a single DCI (S-DCI, single PDCCH). Also, when multiple PDSCHs from multiple TRPs as shown in Figure 1D are scheduled using multiple DCIs, these multiple DCIs may be referred to as multiple DCIs (M-DCI, multiple PDCCHs).

[0034] Each TRP in a multi-TRP may transmit a different transport block (TB) / code word (CW) / different layer, or each TRP in a multi-TRP may transmit the same TB / CW / layer.

[0035] Non-Coherent Joint Transmission (NCJT) is being considered as one form of multi-TRP transmission. In NCJT, for example, TRP1 modulates and layer-maps a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding. TRP2 modulates and layer-maps a second codeword to transmit a second PDSCH using a second number of layers (e.g., two layers) with a second precoding.

[0036] Note that multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in time and / or frequency domains, i.e., a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in time and / or frequency resources.

[0037] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located (QCL). Reception of multiple PDSCHs may be interpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0038] In URLLC for multi-TRP, it is considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multi-TRP is supported. Repetition schemes (URLLC schemes, e.g., Schemes 1, 2a, 2b, 3, and 4) across multi-TRP in the frequency domain, layer (spatial) domain, or time domain are supported. In Scheme 1, multiple PDSCHs from multi-TRP are space division multiplexed (SDM). In Schemes 2a and 2b, PDSCHs from multi-TRP are frequency division multiplexed (FDM). In Scheme 2a, the redundancy version (RV) is the same for multi-TRP. In Scheme 2b, the RVs for multi-TRP may be the same or different. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexed (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted in one slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different slots.

[0039] Such a multi-TRP scenario allows for more flexible transmission control using good quality channels.

[0040] NCJT using multiple TRPs / panels may use high rank. To support ideal and non-ideal backhaul between multiple TRPs, both single DCI (single PDCCH, e.g., FIG. 1B) and multiple DCI (multiple PDCCH, e.g., FIG. 1D) may be supported. For both single DCI and multiple DCI, the maximum number of TRPs may be two.

[0041] For single PDCCH design (mainly for ideal backhaul), TCI extension is being considered. Each TCI codepoint in the DCI may correspond to one or two TCI states. The TCI field size may be the same as that of Rel. 15.

[0042] For PDCCH / CORESET specified in Rel. 15, one TCI state without CORESETPoolIndex (also referred to as TRP Info) is set to one CORESET.

[0043] Regarding the PDCCH / CORESET enhancements specified in Rel. 16, in multi-TRP based on multi-DCI, a CORESET pool index is configured for each CORESET.

[0044] (Inter-cell mobility) In NR, one or more transmission / reception points (Transmission / Reception Points (TRPs)) (multi-TRPs (MTRPs)) are considered to perform DL transmission to a UE. Also, it is considered that a UE performs UL transmission to one or more TRPs.

[0045] During inter-cell mobility (e.g., L1 / L2 inter cell mobility), a UE may receive channels / signals from multiple cells / TRPs (see Figures 2A and 2B).

[0046] FIG. 2A illustrates an example of inter-cell mobility (e.g., single-TRP inter-cell mobility) including a non-serving cell. A UE may be configured with one TRP (or a single TRP) in each cell. Here, the UE receives channels / signals from the base station / TRP of cell #1, which is the serving cell, and the base station / TRP of cell #3, which is not the serving cell (non-serving cell). For example, this corresponds to a case where the UE switches / switches from cell #1 to cell #3 (e.g., a fast cell switch).

[0047] In this case, the selection of the port (e.g., antenna port) / TRP may be performed dynamically or based on the TCI status indicated or updated by the DCI / MAC CE. Here, it is shown that different physical cell ID (e.g., PCI) configurations are supported for cell #1 and cell #3.

[0048] FIG. 2B illustrates an example of a multi-TRP scenario (e.g., multi-TRP inter-cell mobility). A UE may be configured with multiple (e.g., two) TRPs (or different CORESET pool indices) in each cell. Here, the UE receives channels / signals from TRP #1 and TRP #2. Also, here, TRP #1 corresponds to physical cell ID (PCI) #1, and TRP #2 corresponds to PCI #2.

[0049] The multi-TRPs (TRPs #1 and #2) may be connected via an ideal / non-ideal backhaul to exchange information, data, etc. The same or different code words (CWs) and the same or different layers may be transmitted from each TRP of the multi-TRP. As shown in FIG. 2B, non-coherent joint transmission (NCJT) may be used as one form of multi-TRP transmission. This example illustrates the case where NCJT is performed between TPRs corresponding to different PCIs. The same serving cell configuration may be applied / configured for TRPs #1 and #2.

[0050] Multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in time and / or frequency domains. That is, the first PDSCH from TRP #1 and the second PDSCH from TRP #2 may overlap in time and / or frequency resources. The first PDSCH and the second PDSCH may be used for transmission of the same TB or for transmission of different TBs.

[0051] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located (QCL). Reception of multiple PDSCHs may be interpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0052] Multiple PDSCHs from multiple TRPs (which may be referred to as multiple PDSCHs) may be scheduled using one DCI (single DCI (S-DCI), single PDCCH) (single master mode). One DCI may be transmitted from one TRP of a multi-TRP. A configuration using one DCI in a multi-TRP may be referred to as single DCI-based multi-TRP (mTRP / MTRP).

[0053] Multiple PDSCHs from a multi-TRP may be scheduled using multiple DCIs (multiple DCI (M-DCI), multiple PDCCHs (multiple PDCCHs)), respectively (multiple master mode). Multiple DCIs may be transmitted from multiple TRPs, respectively. A configuration that utilizes multiple DCIs in a multi-TRP may be referred to as a multi-DCI-based multi-TRP (mTRP / MTRP).

[0054] It may be assumed that the UE transmits separate CSI reports (CSI reports) for different TRPs. Such CSI feedback may be referred to as separate feedback, separate CSI feedback, etc. In the present disclosure, "separate" may be interchangeably read as "independent."

[0055] In inter-cell mobility, the following scenario 1 or scenario 2 is possible. In the present disclosure, the serving cell may be interpreted as a TRP in the serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as 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." A non-serving cell, a cell having a different PCI, and an additional cell may be interpreted as interchangeable.

[0056] <Scenario 1> Scenario 1 corresponds to, for example, multi-TRP inter-cell mobility. Note that scenario 1 may not correspond to multi-TRP inter-cell mobility. In scenario 1, for example, the following procedure is performed.

[0057] (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).

[0058] 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 assumed by the UE) is not changed. That is, serving cell switching via L1 / L2 is not supported. 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.

[0059] Figure 3A 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.

[0060] 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).

[0061] <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 (or without performing an L3 mobility procedure). 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. In scenario 2, for example, the following procedure is performed.

[0062] (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.

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

[0064] Figure 3B shows an example of UE mobility in Rel. 18. In Rel. 18, the serving cell is switched via L1 / L2. The UE can receive / transmit UE-dedicated channels / common channels to / from the new serving cell. The UE may move out of the coverage of the previous serving cell.

[0065] (Configuration of Candidate Cells) In L1 / L2 inter-cell mobility, candidate cells may be configured in addition to the serving cell. In the present disclosure, the candidate cell may be read as a target cell, an additional cell, or an additional PCI. One or more candidate cells (or candidate cell groups) may be associated separately with each serving cell, or one or more candidate cells (or candidate cell groups) may be commonly associated with multiple serving cells.

[0066] The configuration of the candidate cell (or the candidate cell group) may be configured in the same manner as the inter-cell beam management (inter-cell BM) of an existing system (e.g., Rel. 17 or earlier) by using a predetermined higher layer parameter (e.g., ServingCellConfig). Alternatively, the configuration of the candidate cell (or the candidate cell group) may reuse a carrier aggregation configuration framework (e.g., CA configuration framework) or a CHO (Conditional Handover) / CPC (Conditional PSCell Change) configuration framework.

[0067] The activation / deactivation of a candidate cell (or a candidate cell group) configured by higher layer parameters may be instructed to the UE by MAC CE / DCI.

[0068] As the configuration of the candidate cell (or the association with the serving cell), for example, at least one of the following configuration examples 1 to 3 may be applied. Here, SpCell #0, SCell #1, and SCell #2 are configured as serving cells, and an example of a candidate cell / candidate cell group configured separately from the serving cell is shown. The following configuration examples 1 to 3 are merely examples, and the number of serving cells / number of candidate cells / number of candidate cell groups, the association between the serving cell and the candidate cell, etc. are not limited to these and may be changed as appropriate. Alternatively, other configuration examples may be supported / applied in addition to / instead of configuration examples 1 to 3.

[0069] [Configuration Example 1] In configuration example 1, one or more candidate cells are associated / configured with each serving cell (or frequency regions corresponding to each serving cell) (see FIG. 4). Here, a case is shown in which candidate cells #0-1, #0-2, and #0-3 are associated with SpCell #0 (or the frequency region corresponding to SpCell #0), candidate cell #1-1 is associated with SCell #1 (or the frequency region corresponding to SCell #1), and candidate cells #2-1 and #2-2 are associated with SCell #2 (or the frequency region corresponding to SpCell #2). Information regarding the association may be configured / instructed to the UE by the base station using RRC / MAC CE / DCI.

[0070] [Configuration Example 2] In configuration example 2, candidate cells are associated / configured with a MAC entity / MCG / SCG (see FIG. 4). Here, a case is shown in which candidate cells #3-#8 are associated with a MAC entity / MCG / SCG. In this case, candidate cells are not associated with each serving cell, but are configured with a MAC entity or a cell group (e.g., MCG / SCG). Information about the candidate cell configured for each cell may be configured / instructed to the UE by the base station via RRC / MAC CE / DCI.

[0071] [Configuration Example 3] In configuration example 3, one or more candidate cell groups are configured (see FIG. 4). Each candidate cell group has one or more candidate cells. Here, a case is shown in which candidate cell group #1 having candidate cells #0-#2, candidate cell group #2 having candidate cells #0 and #1, and candidate cell group #3 having candidate cell #0 are configured. At least one of information about the candidate cell group to be configured and information about the candidate cells included in each candidate cell group may be configured / instructed to the UE by the base station via RRC / MAC CE / DCI.

[0072] [Serving Cell Switching] Existing systems (eg, Rel. 17) support L1 beam indication (eg, indication by the TCI status field of the DCI) regarding the TCI status of an additional PCI (or additional cell).

[0073] It is assumed that new L1 / L2 signals (e.g., DCI / MAC CE) that indicate a serving cell switch will be supported in Rel. 18 and later. At least one of implicit and explicit indications may be supported. An implicit indication may mean, for example, that a CORESET is updated by a MAC CE to a TCI state associated with an additional PCI. An explicit indication may mean that a cell switch is directly indicated by a DCI / MAC CE.

[0074] For example, in candidate cell configuration example 1, a predetermined candidate cell may be designated as a serving cell (or switching to the serving cell may be instructed) via L1 / L2 signaling. Figure 5A shows a case where candidate cell #0-2 becomes an SpCell of the MCG / SCG through L1 / L2 signaling (SpCell #0 and candidate cell #0-2 are switched). Also, a case where candidate cell #2-1 becomes an SCell of the MCG / SCG through L1 / L2 signaling (SCell #2 and candidate cell #2-1 are switched) is shown.

[0075] Alternatively, in candidate cell configuration example 2, a predetermined candidate cell may be designated as a serving cell (or a switch to the serving cell may be instructed) via L1 / L2 signaling. Fig. 5B shows a case where candidate cell #4 becomes an SpCell of the MCG / SCG (SpCell #0 and candidate cell #4 are switched) via L1 / L2 signaling.

[0076] Alternatively, in candidate cell configuration example 3, a predetermined candidate cell group (or one or more candidate cells included in the predetermined candidate cell group) may be changed / updated to a serving cell group via L1 / L2 signaling. Figure 5C illustrates a case in which candidate cell group #1 (or candidate cells #0-#2 included in candidate cell group #1) becomes a serving cell group (the serving cell group and candidate cell group #1 are switched) via L1 / L2 signaling. Among the candidate cells included in candidate cell group #1 (here, candidate cells #0-#2), a candidate cell associated with SpCell #0 or a candidate cell set in the same frequency region as SpCell #0 (here, candidate cell #0) may be set as a new SpCell. Alternatively, the candidate cell to be the SpCell may be indicated by L1 / L2 signaling.

[0077] (Timing Advance Group) When multiple TRPs are used, the distances between the UE and each TRP may be different. The multiple TRPs may be included in the same cell (e.g., serving cell). Alternatively, one TRP may correspond to the serving cell and the other TRPs may correspond to non-serving cells. In this case, the distances between each TRP and the UE may be different.

[0078] In existing systems, the transmission timing of an uplink (UL) channel and / or an UL signal (UL channel / signal) is adjusted by a timing advance (TA). The reception timing of the UL channel / signal from different user terminals (UE) is adjusted by a radio base station (TRP: Transmission and Reception Point, also referred to as gNodeB: gNB) side.

[0079] The UE may control the timing of UL transmission by applying timing advance (multiple timing advances) for each pre-configured timing advance group (TAG).

[0080] When multiple timing advances are applied, Timing Advance Groups (TAGs) classified by transmission timing are supported. The UE may control the UL transmission timing for each TAG assuming that the same TA offset (or TA value) is applied to each TAG. In other words, the TA offset may be set independently for each TAG.

[0081] When multiple timing advance is applied, the UE independently adjusts the transmission timing of cells belonging to each TAG, so that even when multiple cells are used, the radio base station can synchronize the reception timing of uplink signals from the UE.

[0082] TAGs (e.g., serving cells belonging to the same TAG) may be configured by higher layer parameters. The same timing advance value may be applied to serving cells belonging to the same TAG. The timing advance group including the SpCell of a MAC entity may be called a Primary Timing Advance Group (PTAG), and the other TAGs may be called Secondary Timing Advance Groups (STAGs).

[0083] In existing systems (e.g., Rel. 16 NR), the configuration of up to four TAGs per cell group (e.g., MCG / SCG) is supported (see Figure 6). Figure 6 shows a case where three TAGs are configured for a cell group including SpCell and SCell #1 to #4. Here, the SpCell and SCell #1 belong to the first TAG (PTAG or TAG #0), SCell #2 and SCell #3 belong to the second TAG (TAG #1), and SCell #4 belongs to the third TAG (TAG #2).

[0084] A timing advance command (TA command) may be notified to the UE using a MAC control element (e.g., MAC CE). The TA command indicates a transmission timing value of an uplink channel and is included in the MAC control element. The TA command is signaled from the radio base station to the UE at the MAC layer. The UE controls a predetermined timer (e.g., a TA timer) based on the reception of the TA command.

[0085] The MAC CE for the timing advance command (TAC MAC CE) may include a field for a timing advance group index (for example, TAG ID) and a field for the timing advance command (see FIG. 7).

[0086] On the other hand, in future wireless communication systems, it is expected that different TAGs (or TAG-IDs) will be configured for one or more TRPs corresponding to a cell (or CC). For example, for multi-TRP operation using multi-DCI, it is expected that two TAs (or TAGs) will be supported for UL transmission.

[0087] Alternatively, different TRPs corresponding to a cell may share a common TAG, or a MAC CE for a TA command may be applied to only one TRP, or a MAC CE for a TA command may be applied to multiple TRPs.

[0088] Alternatively, cases where TRPs corresponding to different cells use different TAGs or share a common TAG are also assumed. For example, in inter-cell mobility, it is also assumed that UL transmissions for a serving cell (or a TRP of a serving cell) and a non-serving cell (or a TRP of a non-serving cell) are controlled based on common / different timing advances.

[0089] Thus, in MIMO Rel. 18 and later, it is expected that two timing advances (TAs) for two TRPs will be supported in multi-TRP operation using multi-DCI.

[0090] When TAGs are configured / controlled on a per-TRP basis, a time alignment timer (e.g., timeAlignmentTimer) may be configured for each TRP. The time alignment timer may control when the MAC entity considers a serving cell belonging to the associated TAG to be uplink time aligned. For example, the time alignment timer may be configured by RRC for UL time alignment maintenance.

[0091] A time alignment timer (e.g., timeAlignmentTimer) may be maintained for UL time alignment. In Rel. 17, the time alignment timer (e.g., timeAlignmentTimer) corresponds to each TAG. When the UE receives a MAC CE (e.g., TAC MAC CE) for a timing advance command, it starts or restarts the time alignment timer associated with the indicated timing advance group (e.g., TAG), respectively.

[0092] The MAC entity receives the TAC MAC CE and performs a predetermined value (N ＴＡ) is maintained, apply a timing advance command for the indicated TAG or start or restart the time alignment timer associated with the indicated TAG. ＴＡ ) may be the timing advance between DL and UL.

[0093] The behavior when the time alignment timer expires may be defined separately for the PTAG and the STAG. Note that the timing advance group (TAG) including the SpCell of the MAC entity may be called the primary timing advance group (PTAG), and the other TAGs may be called secondary timing advance groups (STAGs).

[0094] For example, Rel. 17 supports that when a timing advance timer corresponding to a PTAG expires, a predetermined PTAG action is applied, and when a timing advance timer corresponding to a STAG expires, a predetermined STAG action is applied.

[0095] For example, when the time alignment timer expires, the following actions (e.g., predetermined PTAG action / predetermined STAG action) may be performed.

[0096] Actions for a given PTAG If a time alignment timer is associated with a PTAG: Flush (discard) all HARQ buffers for all serving cells. Inform RRC to release PUCCH for all serving cells, if configured. Inform RRC to release SRS, if configured. Clear all configured DL allocations and configured UL allocations. Clear PUSCH resources for semi-persistent CSI reporting. Allow all running time alignment timers to expire. Clear N for all TAGs. ＴＡ Maintain.

[0097] Actions for a given STAG: If a time alignment timer is associated with a STAG, then for all serving cells belonging to that TAG: Flush (discard) all HARQ buffers. Inform RRC to release PUCCH, if configured. Inform RRC to release SRS, if configured. Clear all configured DL and UL allocations. Clear PUSCH resources for semi-persistent CSI reporting. Clear N for that TAG. ＴＡ Maintain.

[0098] (TA control on a TRP / panel basis) As described above, when communication is performed using multiple transmission / reception points (e.g., TRPs) / panels, it is also possible to control the timing advance (TA) for each TRP / panel.

[0099] In NR Rel. 18 and later, for RACHs triggered by PDCCH orders and RACHs triggered by UEs, contention-based random access (CBRA) / contention-free random access (CFRA) is considered / determined on a TRP basis or a TRP TA (TA for each TRP).

[0100] If application / setting of timing advance is supported for each TRP (or on a TRP-by-TRP basis), the UE controls UL transmission (e.g., RACH transmission, etc.) in each TRP based on the timing advance corresponding to each TRP (or the timing advance group to which each TRP belongs).

[0101] Information about the TRP corresponding to each serving cell (e.g., TRP index / TRP ID) may be configured / instructed to the UE from the base station using RRC / MAC CE / downlink control information. The UE may receive related information about the timing advance corresponding to each TRP (e.g., information about the TA value / timing advance command / time alignment timer, etc.) from the base station.

[0102] Each embodiment of the present disclosure may be applied / supported in at least one of intra-cell multi-TRP (Intra-cell M-TRP) and inter-cell multi-TRP (Inter-cell M-TRP).

[0103] In intra-cell multi-TRP, multiple TRPs (or activated TCI states of multiple TRPs) may be associated with the same cell ID, which may be a physical cell ID (PCI).

[0104] In inter-cell multi-TRP, multiple TRPs (or activated TCI states of multiple TRPs) may be associated with different cell IDs (e.g., PCIs). For example, in inter-cell multi-TRP, two TRPs may be interpreted as two TRPs associated with two PCIs, respectively.

[0105] If per-TRP (or per-TRP) timing advance application / configuration is supported, each TRP may belong to a different TAG. Multiple TRPs (e.g., two TRPs) of a serving cell may belong to two TAGs each. A TAG may contain multiple TRPs from multiple serving cells. All TRPs / serving cells within a TAG apply / maintain the same timing advance (TA) / same time alignment timer.

[0106] In the present disclosure, a TAG may include one or more sub-TAGs. For example, two TRPs of a serving cell may belong to two sub-TAGs each and belong to one TAG. A sub-TAG may include multiple TRPs from multiple serving cells. All TRPs / serving cells in a sub-TAG apply / maintain the same timing advance (TA) / same time alignment timer.

[0107] For example, TA may be applied for each TRP (or TRP TA unit indication may be performed). For example, at least one of the following options may be applied:

[0108] [Option 1] A different TAG-ID may be set for each TRP, and a different MAC CE for the TA command may be set for each TRP. Each TAG may maintain a time alignment timer for UL time alignment.

[0109] [Option 2] Different TRPs may share a TAG. The MAC CE for the TA command may apply to only one TRP. The UE may apply different TAs to other TRPs. For example, the UE may adjust the TA value for other TRPs (e.g., TRP#1) by a TA offset (TA_TRP_offset) based on the TA for TRP#0 (TA_TRP#0).

[0110] In this case, there may be only one time alignment timer for UL time alignment of multiple TRPs, which may mean that UL time alignment of multiple TRPs is maintained or lost simultaneously.

[0111] [Option 3] There may be one TAG, and the MAC CE for the TA command may apply to multiple serving TRPs for the UE.

[0112] [Option 4] There may be a single TAG. MAC CEs for TA commands received on a TRP / CW / PDSCH / DMRS port group may apply to the same TRP / CW / PDSCH / DMRS port group of the TAG. Each TRP / CW / PDSCH / DMRS port group of the TAG maintains a time alignment timer for UL time alignment.

[0113] Thus, in Rel. 18 and later, it is assumed that multiple timing advances will be supported for multi-TRP (e.g., multi-TRP using multiple DCIs). For example, multiple (e.g., two) timing advances may be supported for multi-TRP (e.g., two TRPs) using multi-DCI. Furthermore, application of multiple timing advances to multi-TRP may be supported in intra-cell / inter-cell multi-DCI multi-TRP scenarios or in multiple frequency ranges (e.g., FR1 and FR2).

[0114] However, in the RACH procedure for each TRP (or TRP TA) in the multi-TRP system as described above, sufficient consideration has not been given to how to perform the RACH procedure.

[0115] In existing systems (e.g., Rel. 17 and earlier), for a RACH procedure for a specific cell (e.g., SpCell), the UE performs the RACH procedure assuming that the PDCCH order and the PDCCH for RAR have the same QCL characteristics for the RACH of a PDCCH order. The PDCCH for RAR may be a PDCCH transmitted by the base station in response to a PRACH triggered to the UE by the PDCCH order (or transmitted from the UE). The RAR may be included in the PDSCH scheduled by the PDCCH for RAR. The QCL characteristics may be interpreted as DMRS QCL characteristics.

[0116] Specifically, when a UE detects a CRC-scrambled DCI format 1_0 with a corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for an SpCell, the UE may assume that the PDCCH containing DCI format 1_0 and the PDCCH order have the same DMRS antenna port quasi-co-location property.

[0117] In addition, in existing systems (e.g., Rel. 17 and earlier), there is no restriction such as a specific cell for the RACH procedure for other cells (e.g., SCell), and the UE is supported to use the QCL of a predetermined CORESET for receiving the PDCCH for RAR. The predetermined CORESET may be a CORESET associated with a Type 1 CSS set (e.g., Type 1-PDCCH CSS set).

[0118] Specifically, if the UE performs detection of CRC-scrambled DCI format 1_0 with the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for the SCell, the UE may assume the DMRS antenna port quasi-co-location property of the CORESET associated with the Type 1-PDCCH CSS set for reception of the PDCCH including DCI format 1_0.

[0119] Incidentally, to obtain the TA for each TRP (or the TA for the serving cell and the non-serving cell), a RACH may be triggered for each TRP (or for each serving cell / non-serving cell). Regarding a PDCCH order that triggers a RACH procedure for a TRP (or a serving cell / non-serving cell), a case may be considered in which the PDCCH order and the PDCCH for RAR are transmitted from different TRPs. In such a case, it is necessary to relax / modify the restriction that the PDCCH order and the PDCCH for RAR have the same DMRS QCL characteristics.

[0120] For example, it may be supported that a PDCCH order from TRP #1 triggers a RACH to TRP #2, and an RAR is transmitted from TRP #2. In this case, it becomes possible to trigger a RACH to any TRP via a PDCCH order from any TRP, thereby increasing the flexibility of the RACH procedure.

[0121] As another example, it may be supported that a PDCCH order from TRP #2 triggers a RACH to TRP #2 and an RAR is transmitted from TRP #1. This example may occur in an inter-cell multi-TRP (e.g., inter-cell M-TRP) case when the UE cannot receive a Type 1 CSS set from the TRP of a non-serving cell.

[0122] Therefore, the inventors focused on the case where RACH is triggered for each TRP, and studied the RACH procedure in such a case (e.g., the QCL in the RACH procedure (e.g., DMRS QCL characteristics)), and came up with one aspect of this embodiment.

[0123] Alternatively, the inventors have focused on a case where a RACH for a non-serving cell is triggered, and have considered the RACH procedure in such a case (e.g., QCL (e.g., DMRS QCL characteristics) in the RACH procedure) to come up with another aspect of the present embodiment.

[0124] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0125] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

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

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

[0128] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, or a combination thereof.

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

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

[0131] In the present disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In the present disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0132] In the present disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

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

[0134] In the present disclosure, TRP, CORESET pool index (CORESETPoolIndex), TRP ID, ID related to TRP, TAG ID, group of TCI states, group of spatial relationships, group of QCL source RSs, group of DL RSs, group of path loss RSs, and PCI (for inter-cell multi-TRP) may be read as interchangeable.

[0135] In the present disclosure, being associated with different TRPs, being associated with different CORESET pool indices (CORESETPoolIndex), being associated with different TRP IDs, being associated with different TRP-related IDs, being associated with different TAG IDs, being associated with different TCI state groups, being associated with different spatial relationship groups, being associated with different QCL source RS groups, being associated with different DL RS groups, being associated with different pathloss RS groups, and being associated with different PCIs (for inter-cell multi-TRP) may be read as interchangeable.

[0136] Each embodiment of the present disclosure may be applied to at least one of intra-cell multi-TRP and inter-cell multi-TRP.

[0137] In the present disclosure, intra-cell multi-TRP may mean that the activated TCI states of multiple (e.g., two) TRPs are associated with the same PCI.

[0138] In the present disclosure, inter-cell multi-TRP may mean that the activated TCI states of multiple (e.g., two) TRPs are associated with different PCIs.

[0139] In the present disclosure, in the case of inter-cell multi-TRP, multiple (e.g., two) TRPs may mean multiple (e.g., two) TRPs associated with multiple (e.g., two) PCIs.

[0140] In the present disclosure, the terms non-serving cell, additional cell, candidate cell, and target cell may be interpreted interchangeably.

[0141] The following embodiments may be applied when a per-TRP (or per-serving / additional / non-serving cell) RACH procedure is configured / supported, or when a per-TRP (or per-serving / additional / non-serving cell) timing advance / timing advance group is configured / supported.

[0142] (Wireless Communication Method) <First Embodiment> In the first embodiment, an example of a QCL assumption that is applied when multi-DCI-based multi-TRP is supported / configured / enabled for a specific cell (e.g., SpCell) and a PDCCH order triggers a RACH procedure for the specific cell will be described.

[0143] When a RACH procedure (or PRACH / RACH) is triggered by a PDCCH order for a specific cell in which multiple DCI-based multiple TRP is configured, the UE may assume a QCL (e.g., DMRS QCL) characteristic in the RACH procedure based on at least one of Alt. 1-0 and Alt. 1-1 below.

[0144] [Alt. 1-0] The UE may assume that the first and second PDCCHs it receives in the RACH procedure have the same DMRS QCL characteristics.

[0145] The first PDCCH may be a PDCCH order (or a PDCCH corresponding to the PDCCH order) that triggers the RACH procedure. The second PDCCH may be a PDCCH for RAR (or a PDCCH that schedules a PDSCH used for transmitting the RAR). In the present disclosure, the PDCCH for RAR may be interpreted as a DCI format (e.g., DCI format 1_0) in which the CRC is scrambled by the corresponding RA-RNTI in response to the RACH transmission.

[0146] When receiving a PDCCH for RAR transmitted from a base station in response to a PRACH triggered by a PDCCH order, the UE may assume the DMRS QCL characteristics to be used for receiving the PDCCH order (see FIG. 8A). Alt. 1-0 may be applied with the same mechanism as the QCL characteristics of the RACH procedure for a specific cell in existing systems (e.g., Rel. 17 and earlier).

[0147] [Alt. 1-1] The UE may assume that a case is supported in which the first and second PDCCHs received in the RACH procedure have different DMRS QCL characteristics.

[0148] The first PDCCH may be a PDCCH order (or a PDCCH corresponding to a PDCCH order) that triggers a RACH procedure, and the second PDCCH may be a PDCCH for RAR (or a PDCCH that schedules a PDSCH used to transmit the RAR).

[0149] For example, the UE may receive a PDCCH order assuming a first QCL, and may assume a second QCL obtained (or provided) separately from the first QCL when receiving a PDCCH for an RAR transmitted from a base station in response to a PRACH triggered by the PDCCH order (see Figure 8B).

[0150] The UE may assume the DMRS QCL characteristics of a predetermined CORESET for receiving PDCCH for RAR, which may be, for example, a CORESET associated with a predetermined CSS (e.g., Type 1-PDCCH CSS) set.

[0151] [QCL assumptions for each scenario] A different QCL assumption (e.g., Alt. 1-0 / Alt. 1-1) may be applied to each scenario in which the RACH procedure is performed. In the present disclosure, a scenario may be interpreted as a condition, an application condition, or a setting condition.

[0152] For example, different QCL assumptions may be applied to the RACH procedure in the first scenario and the RACH procedure in the second scenario. As an example, Alt. 1-0 (see, for example, FIG. 8A) may be applied to the first scenario, and Alt. 1-1 (see, for example, FIG. 8B) may be applied to the second scenario.

[0153] The scenarios may be classified based on the CORESET pool indexes corresponding to the PDCCH order and the PDCCH for RAR, respectively. Alternatively, the scenarios may be classified based on the type of cell / PCI (e.g., serving cell (or serving cell PCI) / additional cell (or additional cell PCI)) corresponding to the PDCCH order and the PDCCH for RAR, respectively.

[0154] For example, the multiple scenarios in which the RACH procedure is performed may be at least one of the following scenarios #1-1 to #1-10. The first scenario may include one or more scenarios, and the second scenario may include one or more other scenarios.

[0155] <Scenario #1-1> Scenario #1-1 may be a scenario in which intra-cell multi-TRP (e.g., intra-cell M-TRP) is configured / supported.

[0156] <Scenario #1-2> Scenario #1-2 may be a scenario in which inter-cell multi-TRP (e.g., inter-cell M-TRP) is configured / supported.

[0157] <Scenario #1-3> Scenario #1-3 may be a scenario in which, in intra-cell multi-TRP / inter-cell multi-TRP, the PDCCH order and the PDCCH for RAR are associated with different CORESET pool indices.

[0158] For example, a PDCCH order may be transmitted in a first CORESET corresponding to a first CORESET pool index, and a PDCCH for RAR may be transmitted in a second CORESET corresponding to a second CORESET pool index.

[0159] In scenario #1-3, for example, Alt. 1-1 may be applied, but of course, other QCL assumptions (for example, Alt. 1-0) may also be applied.

[0160] <Scenario #1-4> Scenario #1-4 may be a scenario in which, in intra-cell multi-TRP / inter-cell multi-TRP, the PDCCH order and the PDCCH for RAR are associated with the same CORESET pool index.

[0161] For example, the PDCCH order and the PDCCH for RAR may each be transmitted in a CORESET corresponding to a first CORESET pool index.

[0162] In scenario #1-4, for example, Alt. 1-0 may be applied, but of course, other QCL assumptions (for example, Alt. 1-1) may also be applied.

[0163] <Scenario #1-5> Scenario #1-5 may be a scenario in which, in intra-cell multi-TRP / inter-cell multi-TRP, the PDCCCH order is associated with a first CORESET pool index (e.g., #0) and the PDCCCH for RAR is associated with a second CORESET pool index (e.g., #1).

[0164] In scenario #1-5, for example, Alt. 1-1 may be applied, but of course, other QCL assumptions (for example, Alt. 1-0) may also be applied.

[0165] <Scenario #1-6> Scenario #1-6 may be a scenario in which, in intra-cell multi-TRP / inter-cell multi-TRP, the PDCCCH order is associated with the second CORESET pool index (e.g., #1) and the PDCCCH for RAR is associated with the first CORESET pool index (e.g., #0).

[0166] In scenario #1-6, for example, Alt. 1-1 may be applied, but of course, other QCL assumptions (for example, Alt. 1-0) may also be applied.

[0167] Scenario #1-7 Scenario #1-7 may be a scenario in which, in intra-cell multi-TRP / inter-cell multi-TRP, both the PDCCH order and the PDCCH for RAR are associated with a first CORESET pool index (e.g., #0). Alternatively, scenario #1-7 may be a scenario in which, in intra-cell multi-TRP / inter-cell multi-TRP, both the PDCCH order and the PDCCH for RAR are associated with a second CORESET pool index (e.g., #1).

[0168] In scenario #1-7, for example, Alt. 1-0 may be applied, but of course, other QCL assumptions (for example, Alt. 1-1) may also be applied.

[0169] Scenario #1-8 Scenario #1-8 may be a scenario in which, in an inter-cell multi-TRP (e.g., inter-cell M-TRP), a PDCCH order is associated with an additional PCI (e.g., additional PCI), and a PDCCH for RAR is associated with a serving cell PCI. In the present disclosure, the additional PCI (e.g., additional PCI) may be read as a non-serving cell PCI, a candidate cell PCI, or a target cell PCI.

[0170] In scenario #1-8, for example, Alt. 1-1 may be applied, but of course, other QCL assumptions (for example, Alt. 1-0) may also be applied.

[0171] <Scenario #1-9> Scenario #1-9 may be a scenario in which, in an inter-cell multi-TRP (e.g., Inter-cell M-TRP), the PDCCCH order is associated with the serving cell PCI and the PDCCCH for RAR is associated with an additional PCI (e.g., additional PCI).

[0172] In scenario #1-9, for example, Alt. 1-1 may be applied, but of course, other QCL assumptions (for example, Alt. 1-0) may also be applied.

[0173] Scenario #1-10 may be a scenario in which, in an inter-cell multi-TRP (e.g., inter-cell M-TRP), both the PDCCH order and the PDCCH for RAR are associated with a serving cell PCI. Alternatively, scenario #1-10 may be a scenario in which, in an inter-cell multi-TRP (e.g., inter-cell M-TRP), both the PDCCH order and the PDCCH for RAR are associated with an additional PCI (e.g., additional PCI).

[0174] In scenario #1-10, for example, Alt. 1-0 may be applied, but of course, other QCL assumptions (for example, Alt. 1-1) may also be applied.

[0175] [Variation] Not all of scenarios #1-1 to #1-10 may be supported, but some of the scenarios may be supported. For example, the scenarios supported by each UE may be determined based on the UE capabilities. In this case, the UE may not assume some scenarios (for example, scenarios that the UE does not support).

[0176] Furthermore, which QCL assumption (e.g., Alt. 1-0 / Alt. 1-1) applies to which scenario may be defined in the specifications, or may be set by the base station to the UE using higher layer parameters / DCI, etc.

[0177] In the first embodiment, two cases of the first QCL assumption (e.g., Alt. 1-0) and the second QCL assumption (e.g., Alt. 1-1) are shown as QCL assumptions, but applicable / supportable QCL assumptions are not limited to these. For example, other QCL assumptions (e.g., third QCL assumptions) may be applied / supported.

[0178] In addition, although the first embodiment uses scenarios #1-1 to #1-10 as examples, applicable scenarios are not limited to these. Other scenarios may be additionally applied / supported, or two or more of scenarios #1-1 to #1-10 may be combined into one scenario.

[0179] The first embodiment may be applied to a specific cell (for example, an SpCell) or to other cells (for example, an SCell).

[0180] According to the first embodiment, even when the RACH procedure is supported for each TRP, it is possible to appropriately control the QCL assumption applied in the RACH procedure.

[0181] Second Embodiment In a second embodiment, an example of a QCL assumption applied in the case of a RACH procedure (e.g., PRACH transmission) for a non-serving cell will be described. The second embodiment may be applied in combination with the first embodiment.

[0182] The second embodiment may be applied to the QCL assumption between the PDCCH order and the PDCCH for RAR when a RACH procedure (e.g., PRACH transmission) for a non-serving cell is supported in inter-cell mobility. The non-serving cell (or candidate cell) may correspond to a different frequency than the current serving cell.

[0183] For inter-cell mobility, if a PDCCH order triggers a RACH procedure for a non-serving cell (or a candidate cell), the UE may assume a QCL (e.g., DMRS QCL) characteristic for the RACH procedure based on at least one of Alt. 2-0 and Alt. 2-1 below.

[0184] [Alt. 2-0] The UE may assume that the first and second PDCCHs it receives in the RACH procedure have the same DMRS QCL characteristics.

[0185] The first PDCCH may be a PDCCH order (or a PDCCH corresponding to the PDCCH order) that triggers the RACH procedure. The second PDCCH may be a PDCCH for RAR (or a PDCCH that schedules a PDSCH used for transmitting the RAR). In the present disclosure, the PDCCH for RAR may be interpreted as a DCI format (e.g., DCI format 1_0) in which the CRC is scrambled by the corresponding RA-RNTI in response to the RACH transmission.

[0186] When receiving a PDCCH for RAR transmitted from a base station in response to a PRACH triggered by a PDCCH order, the UE may assume the DMRS QCL characteristics to be used for receiving the PDCCH order (see FIG. 9A). Alt. 2-0 may apply the same mechanism as the QCL characteristics of the RACH procedure for a specific cell (e.g., SpCell) in existing systems (e.g., Rel. 17 and earlier).

[0187] [Alt. 2-1] The UE may assume that a case is supported in which the first and second PDCCHs received in the RACH procedure have different DMRS QCL characteristics.

[0188] The first PDCCH may be a PDCCH order (or a PDCCH corresponding to a PDCCH order) that triggers a RACH procedure, and the second PDCCH may be a PDCCH for RAR (or a PDCCH that schedules a PDSCH used to transmit the RAR).

[0189] For example, the UE may receive a PDCCH order assuming a first QCL, and may assume a second QCL obtained (or provided) separately from the first QCL when receiving a PDCCH for RAR transmitted from the base station in response to a PRACH triggered by the PDCCH order (see Figure 9B).

[0190] The UE may assume the DMRS QCL characteristics of a predetermined CORESET for receiving PDCCH for RAR, which may be, for example, a CORESET associated with a predetermined CSS (e.g., Type 1-PDCCH CSS) set.

[0191] The predetermined CSS (e.g., Type 1-PDCCH CSS) set may be Option 2a or Option 2b below. Whether Option 2a or Option 2b is applied may be defined in the specifications, may be configured in the UE by a higher layer parameter from the base station, or may be selected depending on the scenario.

[0192] Option 2a: The predetermined CSS (e.g., Type 1-PDCCH CSS) set may be the Type 1-PDCCH CSS set from the non-serving cell for which the RACH is triggered. In this case, the Type 1-PDCCH CSS set may be provided / configured separately for each non-serving cell.

[0193] Option 2b: The predetermined CSS (e.g., Type 1-PDCCH CSS) set may be the Type 1-PDCCH CSS set from the serving cell. Option 2b may be applied when a non-serving cell corresponds to the same frequency as the serving cell.

[0194] [QCL Assumptions for Each Scenario] Different QCL assumptions (e.g., Alt. 2-0 / Alt. 2-1) may be applied to each scenario in which the RACH procedure is performed. For example, different QCL assumptions may be applied to the RACH procedure in a first scenario and the RACH procedure in a second scenario. As an example, Alt. 2-0 may be applied to the first scenario, and Alt. 2-1 may be applied to the second scenario.

[0195] The scenarios may be classified based on the type of cell / PCI (e.g., serving cell (or serving cell PCI) / additional cell (or additional cell PCI)) corresponding to the PDCCH order and the PDCCH for RAR, respectively. Alternatively, the scenarios may be classified based on the frequency corresponding to a non-serving cell / the frequency corresponding to a serving cell (e.g., whether the frequency of the non-serving cell is the same as the frequency of the serving cell).

[0196] For example, the multiple scenarios in which the RACH procedure is performed may be at least one of the following scenarios #2-1 to #2-5. The first scenario may include one or more scenarios, and the second scenario may include one or more other scenarios.

[0197] <Scenario #2-1> Scenario #2-1 may be a scenario in which the PDCCH order is associated with an additional PCI (for example, an additional PCI) and the PDCCH for RAR is associated with the serving cell PCI.

[0198] In Scenario #2-1, for example, Option 2a of Alt. 2-1 may be applied, but of course, other QCL assumptions (for example, Option 2b of Alt. 2-0 / Alt. 2-1) may also be applied.

[0199] <Scenario #2-2> Scenario #2-2 may be a scenario in which the PDCCH order is associated with the serving cell PCI, and the PDCCH for RAR is associated with an additional PCI (e.g., additional PCI).

[0200] In Scenario #2-2, for example, Option 2b of Alt. 2-1 may be applied, but of course, other QCL assumptions (for example, Option 2a of Alt. 2-0 / Alt. 2-1) may also be applied.

[0201] Scenario #2-3: Scenario #2-3 may be a scenario in which both the PDCCH order and the PDCCH for RAR are associated with the serving cell PCI, or scenario #2-3 may be a scenario in which both the PDCCH order and the PDCCH for RAR are associated with an additional PCI (e.g., additional PCI).

[0202] In Scenario #2-3, for example, Alt. 2-0 may be applied, but other QCL assumptions (for example, options 2a / 2b of Alt. 2-1) may also be applied.

[0203] <Scenario #2-4> Scenario #2-4 may be a scenario in which a non-serving cell corresponds to the same frequency as the serving cell.

[0204] In Scenario #2-4, for example, Option 2b of Alt. 2-0 / Alt. 2-1 may be applied, but of course, other QCL assumptions (for example, Option 2a of Alt. 2-1) may also be applied.

[0205] <Scenario #2-5> Scenario #2-5 may be a scenario in which a non-serving cell corresponds to a frequency different from that of the serving cell.

[0206] In Scenario #2-5, for example, Option 2a of Alt. 2-1 may be applied, but of course, other QCL assumptions (for example, Option 2b of Alt. 2-0 / Alt. 2-1) may also be applied.

[0207] [Variations] The second embodiment may be applied under at least one of the following conditions 2-1 and 2-2.

[0208] Condition 2-1: The PDCCH (PDCCH order) that triggers the PRACH may be received on a PCI corresponding to the serving cell PCI.

[0209] Alternatively, the PDCCH (PDCCH order) that triggers the PRACH may be received on a PCI that corresponds to the additional PCI.

[0210] Condition 2-2: The PDCCH (PDCCH order) that triggers the PRACH may be received in a cell corresponding to the SpCell (for example, PCell / PSCell) or a cell corresponding to the same frequency as the SpCell.

[0211] Alternatively, the PDCCH (PDCCH order) that triggers the PRACH may be received in the SCell or a cell corresponding to the same frequency as the SCell.

[0212] It is also possible that some of the scenarios from scenario #2-1 to scenario #2-5 are not supported, and that only some of the scenarios are supported. For example, the scenarios supported by each UE may be determined based on the UE capabilities. In this case, the UE may not assume some of the scenarios (for example, scenarios that the UE does not support).

[0213] Furthermore, which QCL assumption (e.g., Alt. 2-0 / Alt. 2-1) applies to which scenario may be defined in the specifications, or may be set by the base station to the UE using higher layer parameters / DCI, etc.

[0214] In the second embodiment, two cases of the first QCL assumption (e.g., Alt. 2-0) and the second QCL assumption (e.g., Alt. 2-1) are shown as QCL assumptions, but applicable / supportable QCL assumptions are not limited to these. For example, other QCL assumptions (e.g., third QCL assumptions) may be applied / supported.

[0215] In addition, although the second embodiment uses scenarios #2-1 to #2-5 as examples, applicable scenarios are not limited to these. Other scenarios may be additionally applied / supported, or two or more of scenarios #2-1 to #2-5 may be combined into one scenario.

[0216] According to the second embodiment, even when a RACH procedure for a non-serving cell is triggered, it is possible to appropriately control the QCL assumption to be applied in the RACH procedure.

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

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

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

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

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

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

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

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

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

[0226] At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0227] The specific UE capability may indicate at least one of the following: - Supporting two TAs for multi-TRP; - Supporting two TAs for intra-cell multi-TRP (e.g., intra-cell M-TRP); - Supporting two TAs for inter-cell multi-TRP (e.g., inter-cell M-TRP); - Supporting L1 / L2 inter-cell mobility (e.g., L1 / L2 inter-cell mobility).

[0228] 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).

[0229] 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)).

[0230] 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 the activation of multiple TAs for multi-TRP, information indicating the activation of multiple TAs for intra-cell multi-TRP, information indicating the activation of multiple TAs for inter-cell multi-TRP, information indicating the activation of L1 / L2 inter-cell mobility, any RRC parameter for a specific release (e.g., Rel. 18 / 19), etc.

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

[0232] (Supplementary Note) The following inventions are supplementary notes regarding one embodiment of the present disclosure. [Supplementary Note 1-1] A terminal including: a receiver that receives a first downlink control channel used to trigger a random access procedure; and a controller that, when a random access procedure for each transmitting / receiving point is supported, controls reception of a second downlink control channel that is used to receive a response signal in the random access procedure, based on at least one of a first quasi-co-location (QCL) assumption that uses a first QCL corresponding to the first downlink control channel and a second QCL assumption that uses a second QCL corresponding to a specific control resource set. [Supplementary Note 1-2] The terminal according to Supplementary Note 1-1, in which the controller determines the QCL assumption to be used for the second downlink control channel based on a scenario in which the random access procedure is applied. [Supplementary Note 1-3] The terminal according to Supplementary Note 1-1 or Supplementary Note 1-2, wherein the control unit determines whether to apply the first QCL assumption or the second QCL assumption to reception of the second downlink control channel, based on at least one of a control resource set pool index to which the first downlink control channel corresponds and a control resource set pool index to which the second downlink control channel corresponds. [Supplementary Note 1-4] The terminal according to any of Supplementary Notes 1-1 to 1-3, wherein the control unit determines whether to apply the first QCL assumption or the second QCL assumption to reception of the second downlink control channel, based on at least one of a type of cell to which the first downlink control channel corresponds and a type of cell to which the second downlink control channel corresponds.

[0233] [Supplementary Note 2-1] A terminal comprising: a receiving unit that receives a first downlink control channel used to trigger a random access procedure for a non-serving cell; and a control unit that controls reception of a second downlink control channel used to receive a response signal in the random access procedure, based on at least one of a first QCL assumption that uses a first quasi-co-location (QCL) corresponding to the first downlink control channel and a second QCL assumption that uses a second QCL corresponding to a specific control resource set. [Supplementary Note 2-2] The terminal according to Supplementary Note 2-1, in which the control unit determines the QCL assumption to use for the second downlink control channel based on a scenario in which the random access procedure is applied. [Supplementary Note 2-3] The terminal according to Supplementary Note 2-1 or Supplementary Note 2-2, in which the control unit determines which of the first QCL assumption and the second QCL assumption to apply to reception of the second downlink control channel, based on at least one of a type of cell to which the first downlink control channel corresponds and a type of cell to which the second downlink control channel corresponds. [Supplementary Note 2-4] The terminal according to any one of Supplementary Note 2-1 to Supplementary Note 2-3, wherein the control unit determines whether to apply the first QCL assumption or the second QCL assumption to reception of the second downlink control channel based on at least one of a frequency corresponding to the non-serving cell and a frequency corresponding to a serving cell.

[0234] (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.

[0235] 10 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).

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

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

[0238] 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))).

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

[0240] 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).

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

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

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

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

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

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

[0247] 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).

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

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

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

[0251] 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).

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

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

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

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

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

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

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

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

[0260] 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).

[0261] 11 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.

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

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

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

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

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

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

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

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

[0270] The transceiver 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.

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

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

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

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

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

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

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

[0278] The transceiver 120 may transmit a first downlink control channel used to trigger a random access procedure. When a random access procedure for each transmitting / receiving point is supported, the control unit 110 may control transmission of a second downlink control channel used to receive a response signal in the random access procedure based on at least one of a first quasi-co-location (QCL) assumption using a first QCL corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set. When a random access procedure for each transmitting / receiving point is supported, setting of a TA for each transmitting / receiving point may be supported.

[0279] The transceiver 120 may transmit a first downlink control channel used to trigger a random access procedure for a non-serving cell. The controller 110 may control transmission of a second downlink control channel used to receive a response signal in the random access procedure based on at least one of a first quasi-co-location (QCL) assumption using a first QCL corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set.

[0280] (User Terminal) Fig. 12 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 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0297] The transceiver unit 220 may receive a first downlink control channel used to trigger a random access procedure. When a random access procedure per transmitting / receiving point is supported, the control unit 210 may control reception of a second downlink control channel used to receive a response signal in the random access procedure based on at least one of a first quasi-co-location (QCL) assumption using a first QCL corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set. When a random access procedure per transmitting / receiving point is supported, setting of a TA per transmitting / receiving point may be supported.

[0298] The control unit 210 may determine a QCL assumption to be used for the second downlink control channel based on a scenario in which the random access procedure is applied. For example, the control unit 210 may determine whether the first QCL assumption or the second QCL assumption is to be applied to reception of the second downlink control channel based on at least one of a control resource set pool index corresponding to the first downlink control channel and a control resource set pool index corresponding to the second downlink control channel. Alternatively, the control unit 210 may determine whether the first QCL assumption or the second QCL assumption is to be applied to reception of the second downlink control channel based on at least one of a cell type corresponding to the first downlink control channel and a cell type corresponding to the second downlink control channel.

[0299] The control unit 210 may receive a first downlink control channel used to trigger a random access procedure for a non-serving cell. The control unit 210 may control reception of a second downlink control channel used to receive a response signal in the random access procedure based on at least one of a first quasi-co-location (QCL) assumption using a first QCL corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set.

[0300] The control unit 210 may determine a QCL assumption to be used for the second downlink control channel based on a scenario in which a random access procedure is applied. For example, the control unit 210 may determine whether the first QCL assumption or the second QCL assumption should be applied to reception of the second downlink control channel based on at least one of the type of cell to which the first downlink control channel corresponds and the type of cell to which the second downlink control channel corresponds. Alternatively, the control unit 210 may determine whether the first QCL assumption or the second QCL assumption should be applied to reception of the second downlink control channel based on at least one of the frequency corresponding to a non-serving cell and the frequency corresponding to a serving cell.

[0301] (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.

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

[0303] For example, a base station, a user terminal, or the like 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. 13 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, and the like.

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

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

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

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

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

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

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

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

[0312] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (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).

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

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

[0315] (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0333] 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."

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

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

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

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

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

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

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

[0341] 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).

[0342] 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).

[0343] 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).

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

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

[0346] 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).

[0347] In the present 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," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

[0348] In this 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.

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

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

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

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

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

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

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

[0356] 14 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.

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

[0358] 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).

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

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

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

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

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

[0364] 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).

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

[0366] 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)).

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

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

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

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

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

[0372] 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).

[0373] 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."

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

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

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

[0377] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "deciding" some action.

[0378] Furthermore, "judgment (decision)" may be read as "assuming," "expecting," "considering," or the like.

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

[0380] 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."

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

[0382] 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."

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

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

[0385] 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").

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

[0387] 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 invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

[0388] This application is based on Japanese Patent Application No. 2022-163516, filed on October 11, 2022, the contents of which are incorporated herein in their entirety.

Claims

1. A receiver for receiving a first downlink control channel for an additional PCI different from a physical cell identity (PCI) of a serving cell, the first downlink control channel being used to trigger a random access procedure; a control unit that controls reception of a second downlink control channel used to receive a response signal in the random access procedure based on a quasi-co-location (QCL) assumption that uses a QCL corresponding to a specific control resource set.

2. The terminal described in claim 1, wherein the specific control resource set is a control resource set associated with a Type 1-PDCCH CSS set.

3. The terminal described in claim 1, wherein the first downlink control channel is received when a timing advance group is set for each TRP in a multi-transmission / reception point (TRP) based on multi-downlink control information (DCI).

4. A terminal as described in claim 1, further comprising a transmitting unit that transmits at least one of capability information indicating support for two timing advances for inter-cell multi-transmission / reception points (TRPs) using multi-downlink control information (DCI), and capability information indicating support for two timing advances for intra-cell multi-TRPs using multi-DCI.

5. receiving a first downlink control channel for an additional Physical Cell Identity (PCI) different from the serving cell's Physical Cell Identity (PCI), the first downlink control channel being used to trigger a random access procedure; and controlling reception of a second downlink control channel used to receive a response signal in the random access procedure based on a quasi-co-location (QCL) assumption that uses a QCL corresponding to a specific control resource set.

6. A transmitter that transmits a first downlink control channel for an additional PCI different from a physical cell identity (PCI) of a serving cell, the first downlink control channel being used to trigger a random access procedure; a control unit that controls transmission of a second downlink control channel that is received by a terminal based on a quasi-co-location (QCL) assumption that uses a QCL corresponding to a specific control resource set, and that is used to transmit a response signal in the random access procedure.

7. A system including a terminal and a base station, The terminal a receiver configured to receive a first downlink control channel for an additional PCI different from a physical cell identity (PCI) of a serving cell, the first downlink control channel being used to trigger a random access procedure; a control unit that controls reception of a second downlink control channel used to receive a response signal in the random access procedure based on a quasi-co-location (QCL) assumption that uses a QCL corresponding to a specific control resource set; The base station a transmitter for transmitting the first downlink control channel.