Terminals, wireless communication methods, base stations and systems

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

Technical Field

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

Background Art

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

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] Future wireless communication systems (e.g., wireless communication systems beyond Rel.17 / 5G) are expected to control communication using multiple transmit / receive points (e.g., Multi-TRP (MTRP)) in a serving cell, or to control communication based on inter-cell mobility including non-serving cells.

[0006] In this case, it is conceivable that UL transmission control (e.g., implementation of random access procedures (or setting of timing advances)) may be performed for each transmit / receive point, or for each serving cell and non-serving cell. However, the problem lies in how a terminal (user terminal, User Equipment (UE)) controls UL transmission (e.g., timing advance control) for multiple transmit / receive points (or non-serving cells). If UL transmission to each transmit / receive point (or TRP of a serving / non-serving cell) is not properly controlled, the quality of communication using multiple transmit / receive points may deteriorate.

[0007] This disclosure is made in view of the above, and describes a terminal and wireless communication method that can properly perform communication even when using multiple transmission and reception points. 、 base station and system One of the objectives is to provide it. [Means for solving the problem]

[0008] A terminal relating to one aspect of this disclosure is ,sa Moving Cell Additional PCI which is different from the Physical Cell Identity (PCI) against A first downlink control channel, Used to trigger random access procedures. The aforementioned First descent link A receiving unit that receives the control channel, SpecialSupports a fixed set of control resources Pseudo-collocation (QCL) Use ruQ CL thoughts In Based on this, a second descending sequence is used to receive the response signal in the random access procedure. link It includes a control unit that controls the reception of a control channel. [Effects of the Invention]

[0009] According to one aspect of this disclosure, communication can be performed appropriately even when using multiple transmission points. [Brief explanation of the drawing]

[0010] [Figure 1] Figures 1A-1D show an example of a multi-TRP. [Figure 2] Figures 2A and 2B show an example of inter-cell mobility. [Figure 3] Figures 3A and 3B show an example of switching between a serving cell and an additional cell using L1 / L2 signaling. [Figure 4] Figure 4 shows an example of settings 1-3 when candidate cells are supported. [Figure 5] Figures 5A-5C illustrate an example of how candidate cells / candidate cell groups are switched using L1 / L2 signaling in setting example 1-3 when candidate cells are supported. [Figure 6] Figure 6 shows an example of a Timing Advance Group (TAG) to which a cell group belongs. [Figure 7] Figure 7 shows an example of a MAC CE for timing advance commands. [Figure 8] Figures 8A and 8B show an example of the QCL assumption for the RACH procedure in the first embodiment. [Figure 9] Figures 9A and 9B show an example of the QCL assumption for the RACH procedure in the second embodiment. [Figure 10]FIG. 10 is a diagram showing an example of the schematic configuration of a wireless communication system according to an embodiment. [Figure 11] FIG. 11 is a diagram showing an example of the configuration of a base station according to an embodiment. [Figure 12] FIG. 12 is a diagram showing an example of the configuration of a user terminal according to an embodiment. [Figure 13] FIG. 13 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 14] FIG. 14 is a diagram showing an example of a vehicle according to an embodiment.

Embodiments for Carrying Out the Invention

[0011] (TCI, Spatial Relationship, QCL) In NR, it is considered to control at least one of signal and channel (expressed as signal / channel) in a UE, such as reception processing (e.g., at least one of reception, demapping, demodulation, decoding), transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, encoding) based on the Transmission Configuration Indication state (TCI state).

[0012] The TCI state may represent what is applied to the downlink signal / channel. What corresponds to the TCI state applied to the uplink signal / channel may be expressed as a spatial relation.

[0013] The TCI state is information regarding the Quasi-Co-Location (QCL) of the signal / channel, and may be called a spatial reception parameter, Spatial Relation Information, etc. The TCI state may be set for each UE for each channel or each signal.

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

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

[0016] QCL may have multiple types (QCL types). For example, there may be four QCL types A and D that differ in the parameters (or parameter sets) that can be assumed to be the same, and these parameters (which may also be called QCL parameters) are shown below: • 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 assumption by the UE that one control resource set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be called a QCL assumption.

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

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

[0020] The channel / signal to which the TCI status applies may also be called the target channel / reference signal (target channel / RS), or simply the target, while the other signal mentioned above may be called the reference signal (reference RS), source RS, or simply the reference.

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

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

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

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

[0025] (Multi-TRP) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs) will use one or more panels (multi-panels) to perform DL transmissions to the UE. Furthermore, it is being considered that the UE will perform UL transmissions to one or more TRPs.

[0026] Multiple TRPs may correspond to the same cell identifier (Cell Identifier (ID)) or to different cell IDs. This cell ID may be a physical cell ID (e.g., PCI) or a virtual cell ID.

[0027] Figures 1A-1D show examples of multi-TRP scenarios. In these examples, it is assumed, but not limited to, that each TRP can transmit four different beams.

[0028] Figure 1A shows an example of a case where only one TRP (TRP1 in this example) among the multi-TRPs transmits to the UE (this may also be called single-mode or single-TRP). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

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

[0030] Figure 1B shows an example of a case where only one of the multi-TRPs (TRP1 in this example) transmits control signals to the UE, and that multi-TRP transmits data signals (this may also be 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 portion of the control signal to the UE, and the multi-TRP transmits the data signal (this may be called master-slave mode). Part 1 of the control signal (DCI) may be transmitted by TRP1, and part 2 of the control signal (DCI) may be transmitted by 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] Figure 1D shows an example of a multi-TRP where each of the multi-TRPs transmits a separate control signal to the UE, and the multi-TRP transmits data signals (this may also be called multi-master mode). TRP1 may transmit a first control signal (DCI), and TRP2 may transmit a second control signal (DCI). The UE receives each PDSCH transmitted from the multi-TRP based on these DCIs.

[0033] When scheduling multiple PDSCHs from a multi-TRP (which may also be called multiple PDSCHs) as shown in Figure 1B using a single DCI, that DCI may be called a single DCI (S-DCI, single PDCCH). Similarly, when scheduling multiple PDSCHs from a multi-TRP (as shown in Figure 1D) using multiple DCIs, these multiple DCIs may be called multiple DCIs (M-DCI, multi-PDCCH (multiple PDCCH)).

[0034] Each TRP in a multi-TRP system may transmit different transport blocks (TBs), code words (CWs), and layers. Alternatively, each TRP in a multi-TRP system may transmit the same TB, CW, and layer.

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

[0036] Furthermore, multiple PDSCHs (Multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. In other words, a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in at least one of the time and frequency resources.

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

[0038] In URLLC for multiple TRPs, support for PDSCH (Transport Block (TB) or Codeword (CW)) repetition spanning multiple TRPs is being considered. Support for repetition schemes (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4) spanning multiple TRPs on the frequency domain, layer (spatial) domain, or time domain is being considered. In scheme 1, multiple PDSCHs from multiple TRPs are performed using space division multiplexing (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are performed using frequency division multiplexing (FDM). In scheme 2a, the redundant version (RV) is the same for multiple TRPs. In scheme 2b, the RV may be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are performed using time division multiplexing (TDM). In Scheme 3, multi-PDSCH signals from multi-TRPs are transmitted within a single slot. In Scheme 4, multi-PDSCH signals from multi-TRPs are transmitted within different slots.

[0039] Such multi-TRP scenarios allow for more flexible transmission control using high-quality channels.

[0040] NCJT using multiple TRPs / panels may utilize high ranks. To support ideal and non-ideal backhauls between multiple TRPs, both single DCI (single PDCCH, e.g., Figure 1B) and multi-DCI (multi-PDCCH, e.g., Figure 1D) may be supported. For both single and multi-DCI, the maximum number of TRPs may be 2.

[0041] An extension of the TCI is being considered for single PDCCH designs (primarily for ideal backhaul). Each TCI code point within 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 as defined in Rel.15, one TCI state without a CORESET Pool Index (CORESETPoolIndex) (also known as TRP Info) is set for one CORESET.

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

[0044] (Inter-cell mobility) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs (MTRPs)) will perform DL transmissions to the UE. It is also being considered that the UE will perform UL transmissions to one or more TRPs.

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

[0046] Figure 2A shows an example of inter-cell mobility including non-serving cells (e.g., Single-TRP inter-cell mobility). The UE may configure one TRP (or 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 from the base station / TRP of cell #3, which is not the serving cell (it becomes a non-serving cell). This corresponds, for example, to the UE switching from cell #1 to cell #3 (e.g., a fast cell switch).

[0047] In this case, the selection of a port (e.g., an antenna port) / TRP may be performed dynamically. The selection of a port (e.g., an antenna port) / TRP may be performed based on the TCI status indicated or updated by the DCI / MAC CE. Here, we show a case where different physical cell IDs (e.g., PCI) are supported for cell #1 and cell #3.

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

[0049] Multiple TRPs (TRP#1, #2) may be connected by an ideal / non-ideal backhaul, and information, data, etc., may be exchanged. Each TRP in a multi-TRP may transmit the same or different codewords (CW) and the same or different layers. As one form of multi-TRP transmission, Non-Coherent Joint Transmission (NCJT) may be used, as shown in Figure 2B. Here, we show the case where NCJT is performed between TPRs corresponding to different PCIs. Note that the same serving cell settings may be applied / configured for TRP#1 and TRP#2.

[0050] Multiple PDSCHs (Multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. That is, a first PDSCH from TRP#1 and a second PDSCH from TRP#2 may overlap in at least one of the time and frequency resources. The first and second PDSCHs may be used for transmitting the same TB or for transmitting different TBs.

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

[0052] Multiple PDSCHs from a multi-TRP (which may also be called multiple PDSCHs) may be scheduled using a single DCI (single DCI (S-DCI), single PDCCH) (single master mode). A single DCI may be transmitted from one TRP in the multi-TRP. A configuration using a single DCI in a multi-TRP may be called a single-DCI-based multi-TRP (mTRP / MTRP).

[0053] Multiple PDSCHs from a multi-TRP may be scheduled using multiple DCIs (multi-DCI (M-DCI), multi-PDCCH (multiple PDCCH)) (multi-master mode). Multiple DCIs may be transmitted from each of the multi-TRPs. A configuration that utilizes multiple DCIs in a multi-TRP may be called a multi-DCI-based multi-TRP (mTRP / MTRP).

[0054] A UE may assume that it sends separate CSI reports (CSI reports) for different TRPs, each for each TRP. Such CSI feedback may be called separate feedback, separate CSI feedback, etc. In this disclosure, “separate” may be interpreted as “independent.”

[0055] In inter-cell mobility, the following Scenario 1 or Scenario 2 is possible. In this disclosure, "serving cell" may be interpreted as "TRP within a serving cell." Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as mutually interchangeable. In this disclosure, a PCI different from the Physical Cell Identity (PCI) of the current serving cell may simply be referred to as "different PCI." Non-serving cells, cells with different PCIs, and additional cells may be interpreted as mutually interchangeable.

[0056] <Scenario 1> Scenario 1 corresponds to, for example, inter-cell mobility in a multi-TRP. However, Scenario 1 may also be a scenario that does not correspond to inter-cell mobility in a multi-TRP. In Scenario 1, for example, the following steps are taken.

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

[0058] In Scenario 1, when the UE sends and receives signals with the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the UE's assumption of the serving cell) does not change. In other words, L1 / L2 switching of the serving cell is not supported. The UE sets higher-layer parameters related to the PCI of the non-serving cell 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. It assumes that the UE moves from a PCI#1 cell (serving cell) to a PCI#3 cell (additional cell) (overlapping with the serving cell). In this case, Rel.17 does not support L1 / L2 switching of serving cells.

[0060] An additional cell is a cell with an additional PCI that is different from the PCI of the serving cell. UEs can receive / transmit UE-specific channels from the additional cell. UEs need to be within the serving cell's coverage to receive UE-common channels (e.g., system information / paging / short messages). If a UE moves outside the serving cell's coverage, a cell switch is required, such as through a handover (also called L3 mobility).

[0061] <Scenario 2> In Scenario 2, L1 / L2 cell mobility is applied. With L1 / L2 cell mobility, serving cells can be changed using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with additional cells are possible without handover (or without performing the L3 mobility procedure). Since handover requires RRC reconnection and other factors, resulting in a period of no data communication, applying L1 / L2 cell mobility, which does not require handover, allows data communication to continue even when the serving cell is changed. In Scenario 2, for example, the following procedure is performed.

[0062] (1) The UE receives the SSB settings for a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell changes. (2) The UE performs beam measurements of the cell using different PCIs and reports the measurement results to the serving cell. (3) The UE may receive the configuration of cells with different PCIs (serving cell configuration) through upper-layer signaling (e.g., RRC). In other words, pre-configuration regarding serving cell changes may be performed. This configuration may be performed together with the configuration in (1) or separately. (4) Based on the above report, the TCI status of cells with different PCIs may be activated by L1 / L2 signaling in accordance with the change in the serving cell. The activation of the TCI status and the change in the serving cell may be performed separately. (5) The UE changes the serving cell (assumed to be the serving cell) and starts receiving / transmitting using the pre-configured individual UE channel and TCI state.

[0063] In other words, 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 migration in Rel.18. In Rel.18, serving cells are switched via L1 / L2. UEs can receive / transmit UE-dedicated / common channels to and from the new serving cell. UEs may be outside the coverage of the previous serving cell.

[0065] (Setting candidate cells) In L1 / L2 inter-cell mobility, candidate cells may be set in addition to serving cells. In this disclosure, candidate cells may be read as target cells, additional cells, or additional PCIs. One or more candidate cells (or groups of candidate cells) may be associated separately with each serving cell, or one or more candidate cells (or groups of candidate cells) may be commonly associated with multiple serving cells.

[0066] The configuration of candidate cells (or candidate cell groups) may be set using predetermined higher-layer parameters (e.g., ServingCellConfig) in the same way as the inter-cell beam management (inter-cell BM) of existing systems (e.g., Rel.17 and earlier). Alternatively, the configuration of candidate cells (or candidate cell groups) may reuse the framework for carrier aggregation configuration (e.g., CA configuration framework) or the framework for CHO (Conditional Handover) / CPC (Conditional PSCell Change) configuration.

[0067] Candidate cells (or groups of candidate cells) defined by higher-level layer parameters may be activated / deactivated by MAC CE / DCI instructing the UE.

[0068] For setting candidate cells (or associating them with serving cells), at least one of the following setting examples 1 to 3 may be applied. Here, SpCell#0, SCell#1, and SCell#2 are set as serving cells, and an example of candidate cells / candidate cell groups set separately from the serving cells is shown. Setting examples 1 to 3 below are just examples, and the number of serving cells / candidate cells / candidate cell groups, the association between serving cells and candidate cells, etc., are not limited to these and may be changed as appropriate. Alternatively, other setting examples may be supported / applied in addition to / instead of setting examples 1 to 3.

[0069] [Example Configuration 1] Configuration Example 1 shows that one or more candidate cells are associated with / configured for each serving cell (or the frequency domain corresponding to each serving cell) (see Figure 4). Here, candidate cells #0-1, #0-2, and #0-3 are associated with SpCell#0 (or the frequency domain corresponding to SpCell#0), candidate cell #1-1 is associated with SCell#1 (or the frequency domain corresponding to SCell#1), and candidate cells #2-1 and #2-2 are associated with SCell#2 (or the frequency domain corresponding to SpCell#2). Information regarding these associations may be set / instructed by the base station to the UE via RRC / MAC CE / DCI.

[0070] [Example Configuration 2] Configuration Example 2 shows that candidate cells are associated with / configured for MAC entities / MCG / SCG (see Figure 4). This example shows the case where candidate cells #3-#8 are associated with MAC entities / MCG / SCG. In this case, candidate cells are configured for MAC entities or cell groups (e.g., MCG / SCG), rather than being associated with each individual serving cell. Information regarding the candidate cells to be configured for each cell may be configured / instructed by the base station to the UE via RRC / MAC CE / DCI.

[0071] [Example 3] In Configuration Example 3, one or more candidate cell groups are configured (see Figure 4). Each candidate cell group has one or more candidate cells. This example shows the configuration of 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. At least one piece of information regarding the configured candidate cell groups and information regarding the candidate cells included in each candidate cell group may be set / instructed by the base station to the UE via RRC / MAC CE / DCI.

[0072] [Switching serving cells] Existing systems (e.g., Rel.17) support L1 beam indication for the TCI status of additional PCIs (or additional cells) (e.g., indication by the TCI status field of the DCI).

[0073] From Rel.18 onward, it is expected that new L1 / L2 signals (e.g., DCI / MAC CE) will be supported to instruct serving cell switching (e.g., serving cell switch). It is also expected that at least one of implicit and explicit instructions will be supported for such instructions. An implicit instruction may mean, for example, that a CORESET is updated to a TCI state associated with an additional PCI by MAC CE. An explicit instruction may mean that the cell switching is directly instructed by DCI / MAC CE.

[0074] For example, in candidate cell setting example 1, a predetermined candidate cell may be designated as a serving cell (or instructed to switch to a serving cell) via L1 / L2 signaling. Figure 5A shows a case where candidate cells #0-2 become MCG / SCG SpCells via L1 / L2 signaling (SpCell #0 and candidate cells #0-2 are switched). It also shows a case where candidate cell #2-1 becomes MCG / SCG SCell (SCell #2 and candidate cell #2-1 are switched) via L1 / L2 signaling.

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

[0076] Alternatively, in candidate cell setting 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 shows a case where 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 domain as SpCell #0 (here, candidate cell #0) may be set as a new SpCell. Alternatively, the candidate cell that becomes an SpCell may be indicated by L1 / L2 signaling.

[0077] (Timing Advance Group) When using multiple TRPs, the distance between the UE and each TRP may differ. Multiple TRPs may be contained within the same cell (e.g., a serving cell). Alternatively, some TRPs may correspond to a serving cell, while others correspond to non-serving cells. In this case, it is conceivable that the distance between each TRP and the UE will differ.

[0078] In existing systems, the transmission timing of UL (Uplink) channels and / or UL signals (UL channels / signals) is adjusted by Timing Advance (TA). The reception timing of UL channels / signals from different user terminals (UEs) is adjusted at the base station (TRP: Transmission and Reception Point, also known as gNB: gNodeB, etc.).

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

[0080] When applying multiple timing advances, Timing Advance Groups (TAGs) are supported, categorized by transmission timing. 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 applying Multiple Timing Advance, the UE can independently adjust the transmission timing of the cells belonging to each TAG, allowing the radio base station to synchronize the uplink signal reception timing from the UE, even when using multiple cells.

[0082] TAGs (for example, serving cells belonging to the same TAG) may be defined by higher-level parameters. The same timing advance value may be applied to serving cells belonging to the same TAG. The timing advance group containing a MAC entity's SpCell may be called the primary timing advance group (PTAG), and the other TAGs may be called secondary timing advance groups (STAG).

[0083] In existing systems (e.g., Rel.16 NR), the setting of up to four TAGs is supported per cell group (e.g., MCG / SCG) (see Figure 6). Figure 6 shows a case where three TAGs are set for a cell group containing SpCell and SCell#1~#4. Here, 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 belong to the third TAG (TAG#2).

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

[0085] A MAC CE for timing advance commands (TAC MAC CE) may be configured to include a field for the timing advance group index (e.g., TAG ID) and a field for the timing advance command (see Figure 7).

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

[0087] Alternatively, different TRPs corresponding to a given cell may share a common TAG. Furthermore, a MAC CE for TA commands may apply to only one TRP, or to multiple TRPs.

[0088] Alternatively, different TRPs (Traffic Rate Programs) may use different TAGs for different cells, or they may share a common TAG. For example, in intercell mobility, it is conceivable that UL transmissions could be controlled based on common / different timing advances for serving cells (or serving cell TRPs) and non-serving cells (or non-serving cell TRPs).

[0089] Thus, MIMO versions Rel.18 and later are expected to support two timing advances (TAs) for two TRPs in multi-TRP operation using multi-DCI.

[0090] If TAGs are set / controlled on a TRP basis, a time alignment timer (e.g., timeAlignmentTimer) may be set for each TRP. The time alignment timer may control the time at which a MAC entity considers a serving cell belonging to an associated TAG to be uplink time aligned. For example, a time alignment timer may be set by the RRC to maintain UL time alignment.

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

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

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

[0094] For example, in Rel.17, it is supported that when the timing advance timer corresponding to PTAG expires, a predetermined operation for PTAG is applied, and when the timing advance timer corresponding to STAG expires, a predetermined operation for STAG is applied.

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

[0096] [Operation for specified PTAGs] If the time alignment timer is associated with the PTAG, • Flushes (discards) all HARQ buffers in all serving cells. • If configured, notify RRC to release PUCCH for all serving cells. • If configured, notify RRC to release the SRS. • Clear all configured DL (Download) and UL (Ultimate Load) allocations. Clear the PUSCH resources for semi-persistent CSI reporting. • Complete all time alignment timers during your run. • All TAGs N TA Maintain.

[0097] [Operation for specified STAG] If a time alignment timer is associated with a STAG, then for all serving cells belonging to that TAG, • Flushes (discards) all HARQ buffers. • If configured, notify RRC to release PUCCH. • If configured, notify RRC to release the SRS. • Clear all configured DL and UL assignments. Clear the PUSCH resources for semi-persistent CSI reporting. • N of the relevant TAG TA Maintain.

[0098] (TA control per TRP / panel) As mentioned above, when using multiple transmission / reception points (e.g., TRPs) / panels for communication, it is also conceivable that timing advance (TA) may be controlled for each TRP / panel.

[0099] In NRs Rel.18 and later, for RACH triggered by PDCCH orders and RACH triggered by UEs, it is conceivable that contention-based random access (CBRA) and contention-free random access (CFRA) will be considered / determined on a TRP basis or a TRP TA (TA per TRP) basis.

[0100] If timing advances can be applied / configured for each TRP (or on a per-TRP basis), the UE controls UL transmissions (e.g., RACH transmissions, 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 regarding the TRP corresponding to each serving cell (e.g., TRP index / TRP ID) may be set / instructed to the UE by the base station using RRC / MAC CE / downlink control information. The UE may also receive relevant information regarding the timing advance corresponding to each TRP (e.g., information regarding TA value / timing advance command / time alignment timer, etc.) from the base station.

[0102] Each embodiment of this disclosure may be applied to / supported in at least one of intra-cell multi-TRPs and inter-cell multi-TRPs.

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

[0104] In inter-cell multi-TRP, multiple TRPs (or the 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 each associated with two PCIs.

[0105] If the application / setting of timing advance is supported for each TRP (or per TRP), each TRP may belong to a different TAG. Multiple TRPs in a serving cell (e.g., two TRPs) may each belong to two TAGs. 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 this disclosure, a TAG may contain one or more sub-TAGs. For example, two TRPs of a serving cell may each belong to two sub-TAGs and also to one TAG. A sub-TAG may contain multiple TRPs from multiple serving cells. All TRPs / serving cells within a sub-TAG apply / maintain the same timing advance (TA) / same time alignment timer.

[0107] For example, a TA may be applied to each TRP (or instructions may be given on a TRP TA basis). 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 TA commands 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. A MAC CE for a TA command may be applied to only one TRP. The UE applies 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, only one time alignment timer may exist for the UL time alignment of multiple TRPs. This may mean that the UL time alignment of multiple TRPs may be maintained or lost simultaneously.

[0111] [Option 3] There may be only one TAG. The MAC CE for the TA command may be applied to multiple serving TRPs for the UE.

[0112] [Option 4] There may be only one TAG. MAC CEs for TA commands received on a TRP / CW / PDSCH / DMRS port group may be applied 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 anticipated that multiple timing advances will be supported in multi-TRP (e.g., multi-TRP using multi-DCI). For example, multiple (e.g., two) timing advances may be supported for multi-TRP using multi-DCI (e.g., two TRPs). Furthermore, the 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] By the way, in the multi-TRP scenario described above, there has been insufficient consideration given to how to perform the RACH procedure for each TRP (or TRP TA).

[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. The PDCCH for RAR may be a PDCCH transmitted by the base station in response to a PRACH triggered to (or transmitted by) the UE by the PDCCH order. The PDSCH scheduled by the RAR PDCCH may include RAR. The QCL characteristics may be interpreted as DMRS QCL characteristics.

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

[0117] Furthermore, in existing systems (e.g., Rel.17 and earlier), there are no restrictions on RACH procedures for other cells (e.g., SCell) as there are for specific cells, and the UE is supported to use the QCL of a given CORESET for receiving PDCCH for RAR. The given CORESET may be a CORESET associated with a type 1 CSS set (e.g., type 1-PDCCH CSS set).

[0118] Specifically, if a UE performs detection of DCI format 1_0 scrambled with CRC by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for a SCell, the UE may assume a pseudo-collocation characteristic of the DMRS antenna port of the CORESET associated with a type 1-PDCCH CSS set for receiving PDCCHs containing DCI format 1_0.

[0119] By the way, in order to obtain TA for each TRP (or TA for serving and non-serving cells), a RACH may be triggered for each TRP (or for each serving / non-serving cell). For PDCCH orders that trigger a RACH procedure to a TRP (or serving / non-serving cell), there may be cases where the PDCCH order and the PDCCH for RAR are sent from different TRPs. In such cases, it is necessary to relax / change the restriction that the PDCCH order and the PDCCH for RAR must 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 a RAR is sent from TRP#2. In this case, it becomes possible to trigger a RACH to any TRP via a PDCCH order from any TRP, 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 a RAR is sent from TRP#1. This example may occur in inter-cell multi-TRP (e.g., inter-cell M-TRP) cases when the UE is unable to receive a type 1CSS set from a non-serving cell's TRP.

[0122] Therefore, the present inventors focused on the case in which RACH is triggered for each TRP, and considered the RACH procedure in such a case (for example, the QCL in the RACH procedure (for example, the DMRS QCL characteristics)) and conceived one aspect of this embodiment.

[0123] Alternatively, the inventors focused on cases where RACH is triggered for non-serving cells and considered the RACH procedure in such cases (e.g., QCL in the RACH procedure (e.g., DMRS QCL characteristics)) to conceive of other embodiments of this model.

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

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

[0126] In this disclosure, terms such as notice, activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.

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

[0128] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

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

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

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

[0132] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, 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 relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) groups, PUCCH resource groups, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pools, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumptions, etc., may be interpreted interchangeably.

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

[0134] In this disclosure, TRP, CORESETPoolIndex, TRP ID, ID related to TRP, TAG ID, TCI status group, spatial relationship group, QCL source RS group, DL RS group, path loss RS group, and PCI (for inter-cell multi-TRP) may be interpreted as one another.

[0135] In this disclosure, being associated with different TRPs, being associated with different CORESET pool indexes (CORESETPoolIndex), being associated with different TRP IDs, being associated with different TRP 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 path loss RS groups, and being associated with different PCIs (for inter-cell multi-TRPs) may be interpreted as being associated with each other.

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

[0137] In this 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 this 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 this disclosure, in the case of inter-cell multi-TRPs, multiple (e.g., two) TRPs may mean multiple (e.g., two) TRPs associated with multiple (e.g., two) PCIs.

[0140] In this disclosure, non-serving cell, additional cell, candidate cell, and target cell may be interpreted as interchangeable.

[0141] The following embodiments may apply when a RACH procedure is configured / supported for each TRP (or for each serving cell / additional cell / non-serving cell). Alternatively, the following embodiments may apply when a timing advance / timing advance group is configured / supported for each TRP (or for each serving cell / additional cell / non-serving cell).

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

[0143] For a specific cell where a multi-DCI-based multi-TRP is configured, if a RACH procedure (or PRACH / RACH) is triggered by a PDCCH order, the UE may assume the QCL (e.g., DMRS QCL) characteristics 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 received in the RACH procedure have the same DMRS QCL characteristics.

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

[0146] The UE may assume a DMRS QCL characteristic to use for receiving the PDCCH order when receiving a PRACH for RAR transmitted from the base station in response to a PRACH triggered by the PDCCH order (see Figure 8A). Alt.1-0 may apply the same mechanism as the QCL characteristic of the RACH procedure for a particular cell in existing systems (e.g., Rel.17 or earlier).

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

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

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

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

[0151] [QCL assumptions for each scenario] Different QCL assumptions (e.g., Alt.1-0 / Alt.1-1) may be applied to each scenario in which the RACH procedure is performed. In this disclosure, scenario may be interpreted as condition, application condition, or 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. For instance, Alt.1-0 (see, for example, Figure 8A) may be applied to the first scenario, and Alt.1-1 (see, for example, Figure 8B) may be applied to the second scenario.

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

[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 also be a scenario in which intra-cell multi-TRP (e.g., Intra-cell M-TRP) is configured / supported.

[0156] Scenario #1-2 Scenarios #1-2 may also be scenarios in which inter-cell multi-TRP (e.g., Inter-cell M-TRP) is configured / supported.

[0157] 《Scenario #1-3》 Scenarios #1-3 may also be scenarios 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 indexes.

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

[0159] In scenario #1-3, for example, Alt.1-1 may be applied. Of course, it is not limited to this, and other QCL assumptions (for example, Alt.1-0) may also be applied.

[0160] 《Scenario #1-4》 Scenarios #1-4 may also be scenarios 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 be sent in the CORESET corresponding to the first CORESET pool index, respectively.

[0162] In scenario #1-4, for example, Alt.1-0 may be applied. Of course, it is not limited to this, and other QCL assumptions (for example, Alt.1-1) may also be applied.

[0163] 《Scenario #1-5》 Scenarios #1-5 may also be scenarios in which, in intra-cell multi-TRP / inter-cell multi-TRP, the PDCCH order is associated with a first CORESET pool index (e.g., #0), and the PDCCH 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. Of course, it is not limited to this, and other QCL assumptions (for example, Alt.1-0) may also be applied.

[0165] 《Scenario #1-6》 Scenarios #1-6 may also be scenarios in which, in intra-cell multi-TRP / inter-cell multi-TRP, the PDCCH order is associated with a second CORESET pool index (e.g., #1), and the PDCCH for RAR is associated with a first CORESET pool index (e.g., #0).

[0166] In scenario #1-6, for example, Alt.1-1 may be applied. Of course, it is not limited to this, and other QCL assumptions (for example, Alt.1-0) may also be applied.

[0167] 《Scenario #1-7》 Scenarios #1-7 may be scenarios 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, scenarios #1-7 may be scenarios 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. Of course, it is not limited to this, and other QCL assumptions (for example, Alt.1-1) may also be applied.

[0169] 《Scenario #1-8》 Scenarios #1-8 may be scenarios in which, in an inter-cell multi-TRP (e.g., Inter-cell M-TRP), the PDCCH order is associated with an additional PCI (e.g., additional PCI), and the PDCCH for RAR is associated with a serving cell PCI. In this disclosure, the additional PCI (e.g., additional PCI) may be interpreted 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. Of course, it is not limited to this, and other QCL assumptions (for example, Alt.1-0) may also be applied.

[0171] 《Scenario #1-9》 Scenarios #1-9 may also be scenarios in which, in an inter-cell multi-TRP (e.g., Inter-cell M-TRP), 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).

[0172] In scenario #1-9, for example, Alt.1-1 may be applied. Of course, it is not limited to this, and other QCL assumptions (for example, Alt.1-0) may also be applied.

[0173] 《Scenario #1-10》 Scenarios #1-10 may be scenarios 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 the serving cell PCI. Alternatively, scenarios #1-10 may be scenarios 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. Of course, it is not limited to this, and other QCL assumptions (for example, Alt.1-1) may also be applied.

[0175] [Variations] Not all of scenarios #1-1 to #1-10 may be supported, and some may be supported. For example, the scenarios that each UE supports may be determined based on its capabilities. In this case, the UE does not need to anticipate 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 specification, or it may be set by the base station to the UE via higher-layer parameters / DCI, etc.

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

[0178] Furthermore, while scenarios #1-1 to #1-10 were given as examples in the first embodiment, the applicable scenarios are not limited to these. Other scenarios may be additionally applied / supported, or two or more scenarios from scenarios #1-1 to #1-10 may be combined into a single scenario.

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

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

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

[0182] The second embodiment may apply to QCL assumptions between PDCCH orders and PDCCHs for RAR when RACH procedures (e.g., PRACH transmissions) for non-serving cells are supported in inter-cell mobility. The non-serving cell (or candidate cell) may correspond to a different frequency than the current serving cell.

[0183] With respect to inter-cell mobility, if a RACH procedure is triggered for a non-serving cell (or candidate cell) by a PDCCH order, the UE may assume the QCL (e.g., DMRS QCL) characteristics in 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 received in the RACH procedure have the same DMRS QCL characteristics.

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

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

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

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

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

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

[0191] The specified CSS set (e.g., Type 1-PDCCH CSS) may be either option 2a or option 2b below. Whether option 2a or option 2b is applied may be defined in the specification, set by the base station to the UE via upper-layer parameters, or selected depending on the scenario.

[0192] 《Option 2a》 The specified CSS set (e.g., type1-PDCCH CSS) may be the type1-PDCCH CSS set from the non-serving cell from which RACH was triggered. In this case, the type1-PDCCH CSS set may be provided / configured separately for each non-serving cell.

[0193] 《Option 2b》 The specified CSS (e.g., Type 1-PDCCH CSS) set may be the Type 1-PDCCH CSS set from the serving cell. Option 2b may apply if the 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 the first scenario and the RACH procedure in the second scenario. As an example, Alt.2-0 may be applied to the first scenario and Alt.2-1 to the second scenario.

[0195] Scenarios may be classified based on the cell / PCI type corresponding to the PDCCH order and the PDCCH for RAR, respectively (e.g., serving cell (or serving cell PCI) / additional cell (or additional cell PCI)). Alternatively, scenarios may be classified based on the frequency corresponding to the non-serving cell / frequency corresponding to the 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 also be a scenario in which the PDCCH order is associated with an additional PCI (e.g., an additional PCI), and the PDCCH for RAR is associated with a serving cell PCI.

[0198] In Scenario #2-1, for example, option 2a of Alt.2-1 may be applied. Of course, this is not the only option, and 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 also 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. Of course, this is not the only option, and 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. Alternatively, 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., an additional PCI).

[0202] In scenario #2-3, for example, Alt.2-0 may be applied. Of course, it is not limited to this, and other QCL assumptions (for example, options 2a / 2b of Alt.2-1) may also be applied.

[0203] Scenario #2-4 Scenario #2-4 may also be a scenario where the 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. Of course, it is not limited to this, and other QCL assumptions (for example, option 2a of Alt.2-1) may also be applied.

[0205] Scenario #2-5 Scenario #2-5 may also be a scenario where the non-serving cell corresponds to a different frequency than the serving cell.

[0206] In scenario #2-5, for example, option 2a of Alt.2-1 may be applied. Of course, this is not the only option, and 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 in at least one of the following conditions 2-1 and 2-2.

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

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

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

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

[0212] Not all of scenarios #2-1 to #2-5 may be supported, while some may be. For example, the scenarios each UE supports may be determined based on its capabilities. In this case, the UE does not need to anticipate some 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 specification, or it may be set by the base station to the UE via higher-layer parameters / DCI, etc.

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

[0215] Furthermore, while scenarios #2-1 to #2-5 were given as examples in the second embodiment, the applicable scenarios are not limited to these. Other scenarios may be additionally applied / supported, or two or more scenarios from scenarios #2-1 to #2-5 may be combined into a single scenario.

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

[0217] <Supplement> [Notification of information to UE] In the embodiments described above, notification of any information from a Network (NW) (e.g., a Base Station (BS)) to a UE (in other words, reception of any information from a BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0218] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

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

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

[0221] [Notification of information from UE] In the embodiments described above, notification of any information from the UE (to the NW) (in other words, transmission / reporting 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), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

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

[0223] If the above notice is issued by the UCI, the notice may be sent using PUCCH or PUSCH.

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

[0225] [Regarding the application of each embodiment] At least one of the embodiments described above may be applied if certain conditions are met. These conditions may be specified in a standard or notified to the UE / BS using upper-layer signaling / physical layer signaling.

[0226] At least one of the embodiments described above may apply only to a UE that has reported or supports a particular UE capability.

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

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

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

[0230] Furthermore, at least one of the embodiments described above may be applied when the UE is configured / activated / triggered by upper layer signaling / physical layer signaling to configure / activate specific information (or perform the actions of the embodiments described above) related to the embodiments described above. For example, such 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, or any RRC parameters for a particular release (e.g., Rel.18 / 19).

[0231] If the UE does not support at least one of the above-mentioned specific UE capabilities or does not have the above-mentioned specific information configured, the behavior of, for example, Rel.15 / 16 / 17 may be applied.

[0232] (Note) The following invention is added with respect to one embodiment of this disclosure. [Note 1-1] A terminal having: a receiving unit that receives a first downlink control channel used to trigger a random access procedure; and a control unit that controls the 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 pseudo-collocation (QCL) corresponding to the first downlink control channel and a second QCL assumption that uses a second QCL corresponding to a specific set of control resources, when a random access procedure is supported for each transmit / receive point. [Appendix 1-2] The control unit is the terminal described in Appendix 1-1, which determines the QCL assumption to be used for the second downlink control channel based on the scenario to which the random access procedure is applied. [Appendix 1-3] The terminal as described in Appendix 1-1 or Appendix 1-2, wherein the control unit determines whether to apply the first QCL assumption or the second QCL assumption to reception on the second downlink control channel based on at least one of the control resource set pool index to which the first downlink control channel corresponds and the control resource set pool index to which the second downlink control channel corresponds. [Appendix 1-4] The terminal according to any of the appendices 1-1 to 1-3, wherein the control unit determines whether to apply the first QCL assumption or the second QCL assumption to the reception of the second downlink control channel based on at least one of the cell type to which the first downlink control channel corresponds and the cell type to which the second downlink control channel corresponds.

[0233] [Note 2-1] A terminal having: a receiving unit that receives a first downlink control channel used to trigger a random access procedure to a non-serving cell; and a control unit that controls the 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 pseudo-collocation (QCL) corresponding to the first downlink control channel and a second QCL assumption that uses a second QCL corresponding to a specific set of control resources. [Note 2-2] The control unit is the terminal described in Appendix 2-1, which determines the QCL assumption to be used for the second downlink control channel based on the scenario to which the random access procedure is applied. [Appendix 2-3] The terminal according to Appendix 2-1 or Appendix 2-2, wherein the control unit determines whether to apply the first QCL assumption or the second QCL assumption to the reception of the second downlink control channel based on at least one of the cell type to which the first downlink control channel corresponds and the cell type to which the second downlink control channel corresponds. [Appendix 2-4] The control unit determines, based on at least one of the frequencies corresponding to the non-serving cell and the serving cell, which of the first QCL assumption and the second QCL assumption to apply to the reception of the second downlink control channel, as described in any of the appendices 2-1 to 2-3.

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

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

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

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

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

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

[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 (CC) and Dual Connectivity (DC).

[0241] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 may be included in FR1, and 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, definitions, etc. of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.

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

[0243] The plurality of base stations 10 may be connected by wire (for example, an optical fiber compliant with Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, the base station 11 corresponding to the upper-level 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 via another base station 10 or directly. The core network 30 may include at least one of, for example, Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0245] The core network 30 may include network functions (NFs) such as, for example, User Plane Function (UPF), Access and Mobility management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Note that a single network node may provide multiple functions. Also, communication with an external network (e.g., the Internet) may be performed via the DN.

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

[0247] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access method may be used. For example, in at least one of the downlink (DL) and the uplink (UL), 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), etc. may be used.

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

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

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

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

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

[0253] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

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

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

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

[0257] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

[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 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

[0260] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0261] (base station) Figure 11 shows an example of the configuration of a base station according to one 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 one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

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

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

[0264] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission, reception, measurement, etc. using the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140. The control unit 110 may generate data, control information, a sequence, etc. to be transmitted as signals and transfer them to the transmission / reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of communication channels, state management of the base station 10, management of radio resources, etc.

[0265] The transmission / reception 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 transmission / reception unit 120 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc. described based on the common knowledge in the technical field related to the present disclosure.

[0266] The transmission / reception unit 120 may be configured as an integrated transmission / reception unit or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of the transmission processing unit 1211 and the RF unit 122. The reception unit may be composed of the reception processing unit 1212, the RF unit 122, and the measurement unit 123.

[0267] The transmission / reception antenna 130 may be composed of an antenna described based on the common knowledge in the technical field related to the present disclosure, such as an array antenna.

[0268] The transmission / reception unit 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmission / reception unit 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

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

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

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

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

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

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

[0276] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes providing 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] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0278] The transmitting / receiving unit 120 may transmit a first downlink control channel used to trigger a random access procedure. If a random access procedure is supported for each transmitting / receiving point, the control unit 110 may control the 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 QCL assumption that uses a first pseudo-collocation (QCL) corresponding to the first downlink control channel and a second QCL assumption that uses a second QCL corresponding to a specific set of control resources. If a random access procedure is supported for each transmitting / receiving point, setting a TA for each transmitting / receiving point may also be supported.

[0279] The transmitting / receiving unit 120 may transmit a first downlink control channel used to trigger a random access procedure for a non-serving cell. The control unit 110 may control the transmission of a second downlink control channel used to receive a response signal in a random access procedure, based on at least one of a first QCL assumption that uses a first pseudo-collocation (QCL) corresponding to the first downlink control channel and a second QCL assumption that uses a second QCL corresponding to a specific set of control resources.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0297] The transmitting / receiving unit 220 may receive a first downlink control channel used to trigger a random access procedure. If a random access procedure is supported for each transmitting / receiving point, the control unit 210 may control the 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 pseudo-collocation (QCL) corresponding to the first downlink control channel and a second QCL assumption that uses a second QCL corresponding to a specific set of control resources. If a random access procedure is supported for each transmitting / receiving point, setting a TA for each transmitting / receiving point may also be supported.

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

[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 the reception of a second downlink control channel used to receive a response signal in a random access procedure, based on at least one of a first QCL assumption that uses a first pseudo-collocation (QCL) corresponding to the first downlink control channel and a second QCL assumption that uses a second QCL corresponding to a specific set of control resources.

[0300] The control unit 210 may determine which QCL assumption to use for the second downlink control channel based on the scenario to which the random access procedure is applied. For example, the control unit 210 may determine whether to apply the first or second QCL assumption to the reception of the second downlink control channel based on at least one of the cell type to which the first downlink control channel corresponds and the cell type to which the second downlink control channel corresponds. Alternatively, the control unit 210 may determine whether to apply the first or second QCL assumption to the reception of the second downlink control channel based on at least one of the frequencies to which non-serving cells correspond and the frequencies to which serving cells correspond.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0325] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0348] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

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

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

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

[0352] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

[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. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

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

[0355] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

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

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

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

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

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

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

[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 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[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 external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

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

[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, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

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

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

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

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

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

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

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

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

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

[0377] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0378] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

[0379] The term "maximum transmit power" as used in this disclosure may mean the maximum value of the 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,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

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

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

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

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

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

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

[0387] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

[0388] This application is based on Japanese Patent Application No. 2022-163516, filed on October 11, 2022. All of its contents are included here.

Claims

1. A first downlink control channel for an additional PCI different from the Physical Cell Identity (PCI) of a serving cell, comprising a receiving unit that receives the first downlink control channel used to trigger a random access procedure, A terminal having a control unit that controls the reception of a second downlink control channel used for receiving response signals in the random access procedure, based on a QCL assumption that utilizes pseudo-collocation (QCL) corresponding to a specific set of control resources.

2. The terminal according to claim 1, wherein the specific control resource set is a control resource set associated with a type 1-PDCCH CSS set.

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

4. The terminal according to claim 1, further comprising a transmitting unit that transmits at least one capability information indicating support for two timing advances for an inter-cell multi-transmit / receive point (TRP) using multi-downlink control information (DCI), and capability information indicating support for two timing advances for an intra-cell multi-TRP using multi-DCI.

5. A first downlink control channel to an additional PCI different from the Physical Cell Identity (PCI) of a serving cell, comprising the step of receiving the first downlink control channel which is used to trigger a random access procedure, A wireless communication method for a terminal, comprising the step of controlling the reception of a second downlink control channel used for receiving response signals in the random access procedure, based on a QCL assumption that utilizes a pseudo-collocation (QCL) corresponding to a specific set of control resources.

6. A first downlink control channel for an additional PCI different from the Physical Cell Identity (PCI) of a serving cell, comprising a transmitting unit that transmits the first downlink control channel used to trigger a random access procedure, A base station having a second downlink control channel, which is received by a terminal based on a QCL assumption that utilizes pseudo-collocation (QCL) corresponding to a specific set of control resources, and a control unit that controls the transmission of the second downlink control channel used for transmitting response signals in the random access procedure.

7. A system including a terminal and a base station, The aforementioned terminal is A first downlink control channel for an additional PCI that is different from the Physical Cell Identity (PCI) of the serving cell, and a receiving unit that receives the first downlink control channel which is used to trigger a random access procedure, The system includes a control unit that controls the reception of a second downlink control channel used for receiving response signals in the random access procedure, based on a QCL assumption that utilizes pseudo-collocation (QCL) corresponding to a specific set of control resources, The aforementioned base station is A system having a transmitting unit that transmits the first downlink control channel.

Images