Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a receiving unit that receives a first downlink control channel that is used in triggering a random access procedure for a non-serving cell; and a control unit that, on the basis of at least one of a first quasi-co-location (QCL) assumption using a first QCL corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set, controls the reception of a second downlink control channel that is used in the reception of an acknowledgement signal in the random access procedure.

Description

Technical Field

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

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

[0003] The successor systems of LTE (also known as the fifth generation mobile communication system (5G), 5G+(plus), the sixth generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) are also being studied.

[0004] Prior art literature

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the invention

[0007] Problems to be solved by the invention

[0008] In future wireless communication systems (for example, wireless communication systems after Rel.17 / 5G), it is envisaged to control communications utilizing multiple transmitting and receiving points (for example, Multi-TRP (MTRP)) in a serving cell, or to control communications based on inter-cell mobility including non-serving cells.

[0009] In this case, it is also envisaged to control UL transmission for each transmission and reception point, or for each service cell and non-service cell (for example, implementation of a random access procedure (or setting of a timing advance)). However, the problem is how a terminal (user terminal, user equipment (UE)) controls UL transmission for multiple transmission and reception points (or non-service cells) (for example, control of timing advance, etc.). If UL transmission to each transmission and reception point (or TRP of a service cell / non-service cell) is not properly controlled, there is a concern that the quality of communication utilizing multiple transmission and reception points may deteriorate.

[0010] The present disclosure has been made in view of the above, and one of its objectives is to provide a terminal, a wireless communication method, and a base station that can appropriately perform communication even when communication is performed using a plurality of transmission and reception points.

[0011] Means for solving problems

[0012] A terminal involved in one embodiment of the present invention comprises: a receiving unit, which receives a first downlink control channel used in triggering a random access process for a non-service cell; and a control unit, which controls reception of a second downlink control channel used in receiving a response signal in the random access process based on at least one of a first QCL assumption using a first quasi-co-location (QCL) corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set.

[0013] Effects of the Invention

[0014] According to one aspect of the present disclosure, even when communication is performed using a plurality of transmission points, communication can be performed appropriately. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1A-Figure 1D This is a diagram showing an example of multi-TRP.

[0016] Figure 2A and Figure 2B This is a diagram showing an example of inter-cell mobility.

[0017] Figure 3A and Figure 3B This is a diagram showing an example of switching between a serving cell and an additional cell based on L1 / L2 signaling.

[0018] Figure 4 This is a diagram showing an example of setting example 1-3 when supporting candidate cells.

[0019] Figure 5A-5C This is a diagram showing an example of switching of candidate cells / candidate cell groups based on L1 / L2 signaling in setting example 1-3 in the case of supporting candidate cells.

[0020] Figure 6 This is a diagram showing an example of a timing advance group (TAG) to which cells included in a cell group belong.

[0021] Figure 7 This is a diagram showing an example of a MAC CE for a timing advance command.

[0022] Fig. 8A and Figure 8B This is a diagram showing an example of QCL assumption of the RACH procedure in the first embodiment.

[0023] Fig. 9A and Fig. 9B This is a diagram showing an example of QCL assumption of the RACH procedure in the second embodiment.

[0024] Fig.10 This is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.

[0025] Fig.11 This is a diagram showing an example of the configuration of a base station according to an embodiment.

[0026] Fig.12 This is a diagram showing an example of a configuration of a user terminal according to an embodiment.

[0027] Fig.13 This is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment.

[0028] Fig.14 This is a diagram showing an example of a vehicle according to an embodiment. DETAILED DESCRIPTION

[0029] (TCI, spatial relationship, QCL)

[0030] In NR, research is being conducted on controlling the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and coding) of at least one of a signal and a channel (expressed as signal / channel) in the UE based on the transmission configuration indication state (Transmission Configuration Indication state (TCI state)).

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

[0032] The TCI state is information related to Quasi-Co-Location (QCL) of signals / channels, and may also be referred to as spatial reception parameters, spatial relationship information, etc. The TCI state may be set for each channel or each signal to the UE.

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

[0034] In addition, the spatial reception parameter may also correspond to a reception beam of the UE (eg, a reception analog beam), and the beam may also be determined based on the spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may also be rewritten as sQCL (spatial QCL).

[0035] QCL may also be specified in multiple types (QCL types). For example, four QCL types AD may be set, in which the same parameters (or parameter sets) may be assumed to be different, and the parameters (also referred to as QCL parameters) are expressed as follows:

[0036] QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread;

[0037] QCL type B (QCL-B): Doppler shift and Doppler spread;

[0038] QCL type C (QCL-C): Doppler shift and average delay;

[0039] QCL type D (QCL-D): spatial reception parameters.

[0040] The UE assumes that a certain control resource set (CORESET), channel or reference signal is in a specific QCL (e.g., QCL type D) relationship with other CORESETs, channels or reference signals. This situation can also be called QCL assumption.

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

[0042] The TCI state may be, for example, information related to the QCL of the target channel (in other words, the reference signal (RS) used for the channel) and other signals (for example, other RS). The TCI state may also be set (indicated) by high-layer signaling, physical layer signaling, or a combination thereof.

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

[0044] The channel for which the TCI state or spatial relationship is set (specified) may also be, for example, at least one of a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and an uplink control channel (Physical Uplink Control Channel (PUCCH)).

[0045] In addition, the RS that is in a QCL relationship with the channel may be, for example, a synchronization signal block (SynchronizationSignal Block (SSB)), a channel state information reference signal (CSI-RS)), a measurement reference signal (Sounding Reference Signal (SRS)), a tracking CSI-RS (also called a tracking reference signal (TRS))), a QCL detection reference signal (also called QRS), a demodulation reference signal (DeModulation Reference Signal (DMRS)), etc., at least one of the following.

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

[0047] The RS of QCL type X in the TCI state may also mean an RS that is in a QCL type X relationship with a certain channel / signal (DMRS), and the RS may also be referred to as a QCL source of QCL type X in the TCI state.

[0048] (Multiple TRP)

[0049] In NR, one or more transmission / reception points (Transmission / Reception Point (TRP)) (multi-TRP) are being studied to use one or more panels (multi-panels) to perform DL transmission to the UE. In addition, the UE is being studied to perform UL transmission to one or more TRPs.

[0050] In addition, multiple TRPs can correspond to the same cell identifier (cell identifier (ID)) or different cell IDs. The cell ID can be a physical cell ID (for example, PCI)) or a virtual cell ID.

[0051] Figure 1A-Figure 1D The following are diagrams showing an example of a multi-TRP scenario. In these examples, it is assumed that each TRP is capable of sending 4 different beams, but this is not limited to this.

[0052] Figure 1A This is an example of a situation where only one TRP (TRP1 in this example) among multiple TRPs transmits to the UE (may also be referred to as single mode, single TRP, etc.) In this case, TRP1 transmits both the control signal (PDCCH) and the data signal (PDSCH) to the UE.

[0053] In the present disclosure, the single TRP mode may also mean a mode in which the multi-TRP (mode) is not set.

[0054] Figure 1B This is an example of a situation in which only one TRP (TRP1 in this example) among multiple TRPs sends a control signal to the UE and the multiple TRPs send data signals (also known as single-master mode). The UE receives each PDSCH sent from the multiple TRPs based on one downlink control information (Downlink Control Information (DCI)).

[0055] Figure 1C An example of a situation in which each of multiple TRPs sends a part of a control signal to the UE and the multiple TRPs send data signals (also referred to as master-slave mode). Alternatively, part 1 of the control signal (DCI) may be sent in TRP1, and part 2 of the control signal (DCI) may be sent in TRP2. Part 2 of the control signal may also depend on part 1. The UE receives each PDSCH sent from the multiple TRPs based on these parts of the DCI.

[0056] Figure 1DAn example of a situation in which each of the multiple TRPs sends a different control signal to the UE and the multiple TRPs send data signals (also referred to as a multi-master mode). Alternatively, the first control signal (DCI) may be sent in TRP1 and the second control signal (DCI) may be sent in TRP2. Based on these DCIs, the UE receives each PDSCH sent from the multiple TRPs.

[0057] exist Figure 1B In the case where one DCI is used to schedule multiple PDSCHs from multiple TRPs (also referred to as multiple PDSCHs), the DCI may also be referred to as a single DCI (S-DCI, single PDCCH). Figure 1D In the case where multiple DCIs are used to schedule multiple PDSCHs from multiple TRPs, these multiple DCIs may also be referred to as multi-DCIs (M-DCI, multiple PDCCH).

[0058] Different transport blocks (Transport Block (TB)) / codewords (CodeWord (CW)) / different layers can be sent from each TRP of multiple TRPs. Alternatively, the same TB / CW / layer can be sent from each TRP of multiple TRPs.

[0059] As a method of multi-TRP transmission, non-coherent joint transmission (NCJT) is being studied. In NCJT, for example, TRP1 performs modulation mapping on a first codeword, and performs layer mapping to transmit a first PDSCH using a first precoding for a first number of layers (e.g., 2 layers). In addition, TRP2 performs modulation mapping on a second codeword, and performs layer mapping to transmit a second PDSCH using a second precoding for a second number of layers (e.g., 2 layers).

[0060] In addition, multiple PDSCHs (multi-PDSCHs) that are NCJTed may also be defined to partially or completely overlap with respect to at least one of the time domain and the frequency domain. That is, at least one of the time and frequency resources of the first PDSCH from the first TRP and the second PDSCH from the second TRP may also overlap.

[0061] It can also be assumed that the first PDSCH and the second PDSCH are not quasi-co-located. The reception of multiple PDSCHs can also be rewritten as the simultaneous reception of PDSCHs of a non-certain QCL type (eg, QCL type D).

[0062] Research is underway to support repetition of PDSCH (transport block (TB) or codeword (CW)) across multiple TRPs in URLLC for multiple TRPs. Research is underway to support repetition across multiple TRPs in the frequency domain or layer (space) domain or time domain (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4). In scheme 1, multiple PDSCHs from multiple TRPs are space division multiplexing (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are frequency division multiplexing (FDM). In scheme 2a, the redundancy version (RV) is the same for multiple TRPs. In scheme 2b, the RVs can be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexing (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are sent in one time slot. In Scheme 4, multiple PDSCHs from multiple TRPs are sent in different time slots.

[0063] Based on such a multi-TRP scenario, more flexible transmission control can be performed by utilizing channels with good quality.

[0064] NCJT using multiple TRPs / panels may use high rank. In order to support ideal and non-ideal backhaul between multiple TRPs, single DCI (single PDCCH, for example, Figure 1B ) and multi-DCI (multi-PDCCH, e.g. Figure 1D ) For both single DCI and multiple DCI, the maximum number of TRPs can also be 2.

[0065] For single PDCCH design (mainly for ideal backhaul), the extension of TCI is being studied. Each TCI code point in DCI can also correspond to one or two TCI states. The TCI field size can also be the same as the TCI field size of Rel.15.

[0066] For PDCCH / CORESET specified in Rel.15, a TCI state without a CORESET pool index (CORESETPoolIndex) (which may also be referred to as TRP information (TRP Info)) may also be set for a CORESET.

[0067] For the enhancement of PDCCH / CORESET specified in Rel.16, in the multi-TRP based on multi-DCI, a CORESET pool index is set for each CORESET.

[0068] (Inter-cell mobility)

[0069] In NR, one or more transmission / reception points (Transmission / Reception Point (TRP)) (Multi-TRP (MTRP)) are being studied for DL ​​transmission to the UE. In addition, the UE is studying for UL transmission to one or more TRPs.

[0070] Consider that a UE receives channels / signals from multiple cells / TRPs in inter-cell mobility (e.g., L1 / L2 inter-cell mobility) (refer to Figure 2A , B).

[0071] Figure 2A An example of inter-cell mobility including non-serving cells (e.g., Single-TRP inter-cell mobility). The UE may also be configured with one TRP (or, Single TRP) in each cell. Here, it indicates a situation where the UE receives channels / signals from the base station / TRP of cell #1, which is a serving cell, and the base station / TRP of cell #3, which is not a serving cell (a non-serving cell). For example, it is equivalent to a situation where the UE switches from cell #1 to cell #3 (e.g., fast cell switch).

[0072] In this case, the selection of the port (e.g., antenna port) / TRP may also be performed dynamically. The selection of the port (e.g., antenna port) / TRP may also be performed based on the TCI state indicated or updated by the DCI / MAC CE. Here, it is indicated that different physical cell IDs (e.g., PCIs) are set for cell #1 and cell #3.

[0073] Figure 2BAn example of a multi-TRP scenario (for example, inter-cell mobility using multiple TRPs). Multiple (for example, two) TRPs (or different CORESET pool indexes) may be set for the UE in each cell. Here, the case where the UE receives channels / signals from TRP#1 and TRP2 is shown. In addition, here, the case where TRP#1 corresponds to physical cell ID (PCI)#1 and TRP#2 corresponds to PCI#2 is shown.

[0074] Multiple TRPs (TRP#1, #2) are connected through an ideal / non-ideal backhaul, and information, data, etc. can be exchanged. The same or different codewords (CodeWord (CW)) or the same or different layers can be sent from each TRP of the multiple TRPs. As one method of sending multiple TRPs, Figure 2B As shown, non-coherent joint transmission (NCJT) can also be used. Here, NCJT is performed between TPRs corresponding to different PCIs. In addition, the same service cell setting can also be applied / set for TRP#1 and TRP#2.

[0075] Multiple PDSCHs (multi-PDSCHs) that are NCJTed may also be defined to partially or completely overlap with respect to at least one of the time domain and the frequency domain. That is, at least one of the time and frequency resources of the first PDSCH from TRP#1 and the second PDSCH from TRP#2 may also overlap. The first PDSCH and the second PDSCH may be used for transmission of the same TB or for transmission of different TBs.

[0076] It can also be assumed that the first PDSCH and the second PDSCH are not quasi-co-located. The reception of multiple PDSCHs can also be rewritten as the simultaneous reception of PDSCHs that are not of a certain QCL type (eg, QCL type D).

[0077] Multiple PDSCHs from multiple TRPs (also referred to as multiple PDSCHs) can also be scheduled using one DCI (single DCI (S-DCI), single PDCCH) (single master mode). One DCI can also be sent from one TRP in multiple TRPs. The structure of using one DCI in multiple TRPs can also be called multiple TRPs (mTRP / MTRP) based on a single DCI.

[0078] Multiple PDSCHs from multiple TRPs can also be scheduled separately (multiple master mode) using multiple DCIs (multiple DCI (M-DCI), multiple PDCCH (multiplePDCCH)). Multiple DCIs can also be sent separately from multiple TRPs. The structure of using multiple DCIs in multiple TRPs can also be called multi-TRP (mTRP / MTRP) based on multiple DCIs.

[0079] The UE may also be considered to send separate CSI reports (CSI reports) related to different TRPs. Such CSI feedback may also be referred to as separate feedback, separate CSI feedback, etc. In the present disclosure, "separate" may also be interchanged with "independent".

[0080] In inter-cell mobility, consider the following scenario 1 or scenario 2. In addition, in the present disclosure, the service cell can also be rewritten as the TRP within the service cell. Layer 1 / layer 2 (layer1 / layer2 (L1 / L2)), DCI / Medium Access Control Control Element (MAC CE)) can also be rewritten with each other. In the present disclosure, a PCI that is different from the Physical Cell Identity (PCI) of the current service cell is sometimes referred to as a "different PCI". Non-service cells, cells with different PCIs, and additional cells can also be rewritten with each other.

[0081] <Scene 1>

[0082] Scenario 1 corresponds to, for example, inter-cell mobility of multiple TRPs. In addition, scenario 1 may also be a scenario that does not correspond to inter-cell mobility of multiple TRPs. In scenario 1, for example, the following process is performed.

[0083] (1) The UE receives from the serving cell the settings of the SSB for beam measurement of the TRP corresponding to the PCI different from that of the serving cell, and the settings necessary for using wireless resources in data transmission and reception, including resources of the different PCI.

[0084] (2) The UE performs beam measurement of TRPs corresponding to different PCIs and reports the beam measurement results to the serving cell.

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

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

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

[0088] In scenario 1, when the UE sends or receives signals to the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the assumption of the serving cell in the UE) is not changed. That is, switching of the serving cell based on L1 / L2 is not supported. The UE is set with high-layer parameters associated with the PCI of the non-serving cell from the serving cell. Scenario 1 can also be applied in Rel.17, for example.

[0089] Figure 3A This is a diagram showing an example of UE movement in Rel. 17. Assume that the UE moves from a cell (serving cell) of PCI#1 to a cell (additional cell) of PCI#3 (overlapping with the serving cell). In this case, in Rel. 17, switching of serving cells based on L1 / L2 is not supported.

[0090] An additional cell is a cell with an additional PCI different from the PCI of the serving cell. The UE can receive / send UE-dedicated channels from the additional cell. In order to receive UE common channels (e.g., system information / paging / short messages), the UE needs to be within the coverage of the serving cell. When the UE moves out of the coverage of the serving cell, it is necessary to switch cells through handover (also known as L3 mobility).

[0091] <Scenario 2>

[0092] In scenario 2, L1 / L2 inter-cell mobility is applied. In L1 / L2 inter-cell mobility, it is possible to change the serving cell by using functions such as beam control without resetting RRC. In other words, it is possible to perform transmission and reception with the additional cell without handover (or without performing the L3 mobility process). Since handover requires RRC reconnection, etc., there will be a period during which data communication is impossible, so by applying L1 / L2 inter-cell mobility that does not require handover, data communication can continue even when the serving cell is changed. In scenario 2, for example, the following steps are performed.

[0093] (1) The UE receives the SSB configuration of a cell (additional cell) having a different PCI from the serving cell for beam measurement / changing the serving cell.

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

[0095] (3) The UE may also receive the configuration of a cell with a different PCI (serving cell configuration) through higher layer signaling (e.g., RRC). In other words, the UE may be pre-configured for serving cell changes. This configuration may be performed together with the configuration in (1) or separately.

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

[0097] (5) The UE changes the serving cell (the assumption of the serving cell) and starts receiving / transmitting using the pre-set UE-dedicated channel and TCI state.

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

[0099] Figure 3B This is a diagram showing an example of UE movement in Rel. 18. In Rel. 18, the serving cell is switched through L1 / L2. The UE can receive / transmit UE-specific channels / common channels with the new serving cell. The UE can also move out of the coverage of the previous serving cell.

[0100] (Setting of candidate cells)

[0101] In L1 / L2 inter-cell mobility, candidate cells may be set in addition to the service cell. In the present disclosure, the candidate cell may also be rewritten as a target cell, an additional cell, or an additional PCI. One or more candidate cells (or candidate cell groups) may be associated with each service cell respectively, or one or more candidate cells (or candidate cell groups) may be associated with multiple service cells in common.

[0102] The setting of candidate cells (or candidate cell groups) can also be set in the same way as the inter-cell beam management (inter-cell BM) of existing systems (e.g., before Rel. 17) using specific high-level parameters (e.g., ServingCellConfig). Alternatively, regarding the setting of candidate cells (or candidate cell groups), the framework for carrier aggregation settings (e.g., CA configuration framework) or the framework for CHO (Conditional Handover) / CPC (Conditional PSCell Change) settings can also be reused.

[0103] Regarding the candidate cells (or candidate cell groups) configured by higher-layer parameters, the activation / deactivation may be instructed to the UE via MAC CE / DCI.

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

[0105] [Setting Example 1]

[0106] Setting example 1 is: for each serving cell (or the frequency domain corresponding to each serving cell), one or more candidate cells are associated / set (refer to Figure 4 ). Here, the following situation is shown: 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- are associated with SCell#2 (or the frequency domain corresponding to SpCell#2). Information related to the association can also be set / indicated to the UE from the base station via RRC / MAC CE / DCI.

[0107] [Setting Example 2]

[0108] Example 2: For MAC entity / MCG / SCG, associate / set candidate cells (reference Figure 4). Here, the case where candidate cells #3-#8 are associated with the MAC entity / MCG / SCG is shown. In this case, the candidate cells are not associated with each service cell, but the candidate cells are set to the MAC entity or cell group (for example, MCG / SCG). Information related to the candidate cells set to each cell can also be set / indicated to the UE from the base station via RRC / MAC CE / DCI.

[0109] [Setting Example 3]

[0110] In setting example 3, one or more candidate cell groups are set (refer to Figure 4 ). The candidate cell group has more than one candidate cell. Here, a case is shown where a candidate cell group #1 having candidate cells #0-#2, a candidate cell group #2 having candidate cells #0 and #1, and a candidate cell group #3 having candidate cell #0 are set. At least one of the information related to the set candidate cell group and the information related to the candidate cells included in each candidate cell group can also be set / indicated to the UE from the base station through RRC / MACCE / DCI.

[0111] [Serving cell switching]

[0112] In the existing system (eg, Rel. 17), L1 beam indication related to the TCI status of an additional PCI (or an additional cell) is supported (eg, indication based on the TCI status field of the DCI).

[0113] After Rel.18, it is envisaged to support a new L1 / L2 signal (e.g., DCI / MAC CE) for indicating the switching of a serving cell (e.g., serving cell switch). As the indication, it is also envisaged to support at least one of an implicit indication and an explicit indication. An implicit indication may also mean, for example, that a certain CORESET is updated to a TCI state associated with an additional PCI through a MAC CE. An explicit indication may also mean that the switching of a cell is directly indicated through a DCI / MAC CE.

[0114] For example, in the example 1 of the candidate cell setting, a specific candidate cell may be designated as a serving cell (or instructed to switch to a serving cell) via L1 / L2 signaling. Figure 5A In FIG. 1 , candidate cell #0-2 is shown to become the SpCell of MCG / SCG (SpCell #0 and candidate cell #0-2 are switched) through L1 / L2 signaling. In addition, candidate cell #2-1 is shown to become the SCell of MCG / SCG (SCell #2 and candidate cell #2-1 are switched) through L1 / L2 signaling.

[0115] Alternatively, in the example 2 of setting the candidate cell, a specific candidate cell may be designated as a serving cell (or instructed to switch to a serving cell) via L1 / L2 signaling. Figure 5B , a situation is shown in which the candidate cell #4 becomes the SpCell of the MCG / SCG through L1 / L2 signaling (SpCell #0 and the candidate cell #4 are switched).

[0116] Alternatively, in the candidate cell setting example 3, a specific candidate cell group (or one or more candidate cells included in the specific candidate cell group) may also be changed / updated to a serving cell group via L1 / L2 signaling. Figure 5C , it is shown that candidate cell group #1 (or candidate cells #0-#2 included in candidate cell group #1) becomes a service cell group (the service cell group and candidate cell group #1 are switched) through 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) can also be set as a new SpCell. Alternatively, a candidate cell that becomes a SpCell can also be indicated through L1 / L2 signaling.

[0117] (Timing Advance Group)

[0118] When using multiple TRPs, there is also a situation where the distance between the UE and each TRP is different. Multiple TRPs can also be included in the same cell (for example, a service cell). Alternatively, it can be that one of the multiple TRPs is equivalent to a service cell, and the other TRPs are equivalent to non-service cells. In this case, it is also assumed that the distance between each TRP and the UE is different.

[0119] 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 (UE) is adjusted on the wireless base station (also called TRP: Transmission and Reception Point, gNB: gNodeB, etc.) side.

[0120] The UE may apply the timing advance (multiple timing advance) for each preset timing advance group (TAG: Timing Advance Group) to perform timing control of UL transmission.

[0121] In the case of applying multiple timing advances, it is supported to send timing advance groups classified by timing

[0122] (TAG: Timing Advance Group). The UE is supposed to apply the same TA offset (or, TA value) for each TAG to control the UL transmission timing in each TAG. That is, the TA offset can also be set independently for each TAG.

[0123] In the case of applying multiple timing advances, the UE can align the uplink signal reception timing at the radio base station even when using multiple cells by independently adjusting the transmission timing of the cells belonging to each TAG.

[0124] TAGs (e.g., serving cells belonging to the same TAG) can also be set by higher layer parameters. For serving cells belonging to the same TAG, the same timing advance value can also be applied. It can also be that the timing advance group of the SpCell containing the MAC entity is called the primary timing advance group (PTAG), and other TAGs are called secondary timing advance groups (STAGs).

[0125] In the existing system (e.g., Rel.16 NR), each cell group (e.g., MCG / SCG) supports setting a maximum of 4 TAGs (refer to Figure 6 ). In Figure 6 , it shows the case where 3 TAGs are set for a cell group including the SpCell and SCell#1 to #4. Here, it shows the following case: the SpCell and SCell#1 belong to the first TAG (PTAG or TAG#0), SCell#2 and SCell#3 belong to the second TAG (TAG#1), and SCell#4 belongs to the third TAG (TAG#2).

[0126] The timing advance command (TA command) can also be notified to the UE through a MAC control element (e.g., MAC CE). The TA command is a command indicating the transmission timing value of the uplink channel and is included in the MAC control element. The TA command is signaled from the radio base station to the UE at the MAC layer. The UE controls a specific timer (e.g., TA timer) based on the reception of the TA command.

[0127] The MAC CE for the timing advance command (TAC MAC CE) can also be a structure including a field for the timing advance group index (e.g., TAGID) and a field for the timing advance command (refer to Figure 7 ).

[0128] On the other hand, it is envisioned that in future wireless communication systems, different TAGs (or TAG-IDs) are set for more than one TRP corresponding to a certain cell (or CC). For example, regarding multi-TRP operation using multiple DCIs, it is envisioned that two TAs (or TAGs) are supported in UL transmission.

[0129] Alternatively, it is also conceivable that different TRPs corresponding to a certain cell share a common TAG. Alternatively, it is also conceivable that the MAC CE for TA command is applied to only one TRP, or that the MAC CE for TA command is applied to multiple TRPs.

[0130] Alternatively, it is also envisioned that the TRPs corresponding to different cells use different TAGs / share a common TAG. For example, in inter-cell mobility, it is also envisioned that the UL transmission is controlled based on a common / different timing advance for the serving cell (or the TRP of the serving cell) and the non-serving cell (or the TRP of the non-serving cell).

[0131] In this way, in MIMO after Rel.18, in multi-TRP operation using multiple DCIs, it is also envisaged to support two timing advances (TA) for two TRPs.

[0132] In the case where the TAG is set / controlled in units of TRP, a time alignment timer (e.g., timeAlignmentTimer) may also be set per TRP. The time alignment timer may also control the time at which the MAC entity considers the serving cell to which the associated TAG belongs to be uplink time aligned (e.g., uplink time aligned). For example, in order to maintain (e.g., maintenance) UL time alignment, the time alignment timer may also be set by RRC.

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

[0134] The MAC entity receives the TAC MAC CE and maintains a specific value (N) between the indicated TAG TA), apply the timing advance command for the indicated TAG, or start or restart the time alignment timer associated with the indicated TAG. TA ) can also be the timing advance between DL and UL.

[0135] The operation when the time alignment timer expires (expire) can also be defined separately in PTAG and STAG. In addition, the timing advance group (TAG) of the SpCell including the MAC entity can also be called the primary timing advance group (PTAG), and the other TAGs can be called secondary timing advance groups (STAG).

[0136] For example, Rel.17 may also support: when the timing advance timer corresponding to PTAG expires, applying a specific operation for PTAG; and when the timing advance timer corresponding to STAG expires, applying a specific operation for STAG.

[0137] For example, when the time alignment timer expires, the following operations (eg, operations for a specific PTAG / operations for a specific STAG) may be performed.

[0138] [Specific PTAG operation]

[0139] In case the time alignment timer is associated with PTAG,

[0140] • Flush (discard) all HARQ buffers of all serving cells.

[0141] When set, the RRC is notified to release the PUCCH to all serving cells.

[0142] If set, notify RRC to release SRS.

[0143] · Clear all configured DL allocations and configured UL allocations.

[0144] Clear PUSCH resources used for semi-persistent CSI reporting.

[0145] · Expire all running time alignment timers.

[0146] Maintain N of all tags TA .

[0147] [Specific STAG operation]

[0148] When the time alignment timer is associated with a STAG, for all serving cells belonging to the TAG,

[0149] · Flush (discard) all HARQ buffers.

[0150] If set, notify RRC to release PUCCH.

[0151] If set, notify RRC to release SRS.

[0152] Clear all the configured DL allocation and UL allocation.

[0153] Clear PUSCH resources used for semi-persistent CSI reporting.

[0154] Maintain the N of this TAG TA .

[0155] TA control in TRP / panel)

[0156] As described above, in the case of communicating using multiple transmission and reception points (e.g., TRPs) / panels, it is also conceivable to control the timing advance (TA) for each TRP / each panel.

[0157] In NRs after Rel.18, for RACH triggered by PDCCH order and RACH triggered by UE, contention based random access (CBRA) and non-contention free random access (CFRA) are considered / determined in TRP units or TRP TA (TA per TRP) units.

[0158] In the case of supporting the application / setting of timing advance per TRP (or in TRP units), the UE controls the UL transmission (e.g., RACH transmission, etc.) in each TRP based on the timing advance corresponding to each TRP (or the timing advance group to which each TRP belongs).

[0159] Information related to the TRP corresponding to each service cell (e.g., TRP index / TRP ID) can also be set / indicated to the UE from the base station using RRC / MAC CE / downlink control information. The UE can also receive associated information related to the timing advance corresponding to each TRP from the base station (e.g., information related to the TA value / timing advance command / time alignment timer, etc.).

[0160] The various embodiments of the present disclosure may also be applied / supported in at least one of intra-cell multi-TRP (Intra-cell M-TRP) and inter-cell multi-TRP (Inter-cell M-TRP).

[0161] In multiple TRPs within a cell, multiple TRPs (or activated TCI states of multiple TRPs) can also be associated with the same cell ID. The cell ID can also be a physical cell ID (PCI).

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

[0163] In the case of supporting the application / setting of timing advance per TRP (or, in TRP units), each TRP may also belong to a different TAG. Multiple TRPs (for example, two TRPs) of a serving cell may also belong to two TAGs respectively. A TAG may also contain multiple TRPs from multiple serving cells. All TRPs / serving cells within a TAG apply / maintain the same timing advance (TA) / the same time alignment timer.

[0164] In the present disclosure, a TAG may also contain more than one sub-TAG. For example, two TRPs of a serving cell belong to two sub-TAGs respectively and also belong to one TAG. A sub-TAG may also 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.

[0165] For example, TA may be applied to each TRP (or may be indicated in TRP TA units). For example, at least one of the following options may be applied.

[0166] [Option 1]

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

[0168] [Option 2]

[0169] Different TRPs may also share a TAG. The MAC CE for the TA command may also be applied to only one TRP. The UE may also apply different TAs to other TRPs. For example, the UE may also 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).

[0170] In this case, there may also be only one time alignment timer for UL time alignment of multiple TRPs. This means that UL time alignment of multiple TRPs is maintained or lost at the same time.

[0171] [Option 3]

[0172] The TAG may also be set to one. The TA command MAC CE may also be applied to multiple service TRPs for the UE.

[0173] [Option 4]

[0174] TAG can also be set to one. The MAC CE for TA command received through the TRP / CW / PDSCH / DMRS port group can also be applied to the TRP / CW / PDSCH / DMRS port group with the same TAG. Each TRP / CW / PDSCH / DMRS port group of TAG can also maintain a time alignment timer for UL time alignment.

[0175] Thus, after Rel.18, it is also envisioned to support multiple timing advances in multiple TRPs (e.g., multiple TRPs utilizing multiple DCIs). For example, for multiple TRPs utilizing multiple DCIs (e.g., two TRPs), multiple (e.g., two) timing advances may also be supported. In addition, the application of multiple timing advances for multiple TRPs may be supported in intra-cell / inter-cell multi-DCI multi-TRP scenarios, and may also be supported in multiple frequency ranges (e.g., FR1 and FR2).

[0176] However, how to perform the RACH process in the RACH process of each TRP (or, TRP TA) in multiple TRPs as described above has not been fully studied.

[0177] In an existing system (e.g., before Rel. 17), regarding a RACH process for a specific cell (e.g., SpCell), for a RACH commanded by a PDCCH, the UE assumes that the PDCCH command and the PDCCH for RAR have the same QCL characteristics, thereby performing the RACH process. The PDCCH for RAR may also be a PDCCH sent by the base station in response to a PRACH triggered by a PDCCH command to the UE (or sent from the UE). The PDSCH scheduled by the PDCCH for RAR may also include RAR. The QCL characteristics may also be rewritten as DMRS QCL characteristics.

[0178] Specifically, when the UE detects DCI format 1_0 scrambled by CRC via the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH instruction for triggering a CFRA process for the SpCell, the UE may also assume that the PDCCH containing DCI format 1_0 and the PDCCH instruction have the same quasi-co-location characteristics of the DMRS antenna port.

[0179] In addition, in existing systems (e.g., before Rel. 17), RACH procedures for other cells (e.g., SCells) are supported without restrictions such as specific cells, and the UE receives the PDCCH for RAR using the QCL of a specific CORESET. The specific CORESET may also be a CORESET associated with a type 1 CSS set (e.g., type 1-PDCCH CSS set).

[0180] Specifically, when the UE detects DCI format 1_0 encrypted by CRC through the corresponding RA-RNTI in response to a PRACH transmission started by a PDCCH instruction for triggering a CFRA process for the SCell, the UE can also envision the quasi-co-location characteristics of the DMRS antenna ports of the CORESET associated with the type 1-PDCCH CSS set for receiving the PDCCH containing DCI format 1_0.

[0181] However, in order to obtain the TA of each TRP (or the TA of the serving cell and the non-serving cell), the RACH of each TRP (or each serving cell / non-serving cell) may also be triggered. Regarding the PDCCH command that triggers the RACH process to the TRP (or the serving cell / non-serving cell), the situation where the PDCCH command and the PDCCH for RAR are sent from different TRPs is also considered. In such a situation, it is necessary to alleviate / change the limitation that the PDCCH command and the PDCCH for RAR have the same DMRS QCL characteristics.

[0182] For example, it is also possible to support: a PDCCH command from TRP#1 triggers a RACH to TRP#2, and RAR is sent from TRP#2. In this case, a RACH to any TRP can be triggered via a PDCCH command from any TRP, which can improve the flexibility of the RACH process.

[0183] As another example, it can also support: PDCCH command from TRP#2 triggers RACH to TRP#2, and RAR is sent from TRP#1. This example may occur in the case of inter-cell multi-TRP (e.g., inter-cell M-TRP) when the UE cannot receive the type 1 CSS set from the TRP of the non-serving cell.

[0184] Therefore, the inventors of the present invention focused on the situation where RACH is triggered per TRP, studied the RACH process in the relevant case (for example, the QCL in the RACH process (for example, DMRS QCL characteristics)), and came up with one method of the present embodiment.

[0185] Alternatively, the inventors of the present invention focused on the situation where RACH is triggered for a non-serving cell, studied the RACH process in the relevant situation (eg, QCL in the RACH process (eg, DMRS QCL characteristics)), and came up with other aspects of the present embodiment.

[0186] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods according to the embodiments may be applied individually or in combination.

[0187] In the present disclosure, "A / B" and "at least one of A and B" may also be replaced with each other. In addition, in the present disclosure, "A / B / C" may also mean "at least one of A, B, and C".

[0188] In the present disclosure, notification, activation, deactivation, indication (or indication), selection, configuration, update, determination, etc. may also be mutually replaced. In the present disclosure, support, control, controllable, operation, and operation may also be mutually replaced.

[0189] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, high-layer parameters, fields, Information Element (IE), settings, etc. may also be overwritten with each other. In the present disclosure, Medium Access Control (MAC Control Element (CE)), update commands, activation / deactivation commands, etc. may also be overwritten with each other.

[0190] In the present disclosure, the high-layer signaling may also be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

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

[0192] In the present disclosure, the physical layer signaling may also be, for example, downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI)), etc.

[0193] In the present disclosure, index, identifier (ID), indicator, resource ID, etc. may also be replaced by each other. In the present disclosure, sequence, list, set, group, group, cluster, subset, etc. may also be replaced by each other.

[0194] In the present disclosure, panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmission entity, transmission / reception point (TRP)), base station, spatial relation information (SpatialRelation Information (SRI)), spatial relation, SRS resource indicator (SRS Resource Indicator (SRI)), control resource set (COntrol REsource SET (CORESET)), physical downlink shared channel (Physical Downlink Shared Channel (PDSCH)), codeword (Codeword (CW)), transport block (TransportBlock (TB)), reference signal (Reference Signal (RS)), antenna port (e.g., demodulation reference signal (DeModulation Reference Signal (DMRS)) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, code division multiplexing (Code Division Multiplexing (CDM)) group, reference signal group, CORESET group, physical uplink control channel (Physical Uplink Control Channel (PUCCH)) group, PUCCH resource group), resources (for example, reference signal resources, SRS resources), resource sets (for example, reference signal resource sets), CORESET pool, downlink transmission configuration indication state (Transmission Configuration Indication state) (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state (unified TCI state), common TCI state (common TCI state), Quasi-Co-Location (Quasi-Co-Location (QCL)), QCL assumptions, etc. can also be rewritten with each other.

[0195] In addition, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) can also be overwritten with each other. "Spatial relationship information" can also be overwritten with "a set of spatial relationship information", "one or more spatial relationship information", etc. TCI state and TCI can also be overwritten with each other.

[0196] In the present disclosure, TRP, CORESET pool index (CORESETPoolIndex), TRP ID, ID related to TRP, TAG ID, TCI state group, spatial relationship group, QCL source RS group, DL RS group, path loss RS group, PCI (for multiple TRPs between cells) can also be rewritten with each other.

[0197] In the present disclosure, associations with different TRPs, associations with different CORESET pool indexes (CORESETPoolIndex), associations with different TRP IDs, associations with IDs related to different TRPs, associations with different TAG IDs, associations with groups of different TCI states, associations with groups of different spatial relationships, associations with groups of different QCL source RSs, associations with groups of different DLRSs, associations with groups of different path loss RSs, and associations with different PCIs (for multiple TRPs between cells) can also rewrite each other.

[0198] The various embodiments of the present disclosure may also be applied to at least one of intra-cell multi-TRP and inter-cell multi-TRP.

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

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

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

[0202] In the present disclosure, non-serving cells, additional cells, candidate cells, and target cells may be replaced with each other.

[0203] The following embodiments may also be applied to the case of setting / supporting the RACH process for each TRP (or, each serving cell / supplementary cell / non-serving cell). Alternatively, the following embodiments may also be applied to the case of setting / supporting the timing advance / timing advance group for each TRP (or, each serving cell / supplementary cell / non-serving cell).

[0204] (Wireless Communication Method)

[0205] <First Embodiment>

[0206] In the first embodiment, an example of QCL assumption applied in the following case is described: multi-TRP based on multi-DCI is supported / configured / activated for a specific cell (e.g., SpCell), and a PDCCH instruction triggers a RACH process of the specific cell.

[0207] For a specific cell configured with multiple TRPs based on multiple DCIs, when the RACH process (or, PRACH / RACH) is triggered by a PDCCH instruction, the UE may also assume the QCL (e.g., DMRS QCL) characteristics in the RACH process based on at least one of the following Alt.1-0 and Alt.1-1.

[0208] [Alt.1-0]

[0209] The UE may also assume that the first PDCCH and the second PDCCH received in the RACH process have the same DMRS QCL characteristics.

[0210] The first PDCCH may also be a PDCCH instruction that triggers a RACH process (or a PDCCH corresponding to a PDCCH instruction). The second PDCCH may also be a PDCCH for RAR (or a PDCCH that schedules a PDSCH used in RAR transmission). In the present disclosure, the PDCCH for RAR may also be rewritten as a DCI format (e.g., DCI format 1_0) that is scrambled by a CRC in response to RACH transmission and by a corresponding RA-RNTI.

[0211] The UE may also assume the DMRS QCL characteristics used in the reception of the PDCCH command, when receiving the PDCCH for RAR transmitted from the base station in response to the PRACH triggered by the PDCCH command (see Fig. 8A ). Alt.1-0 may also be applied with the same mechanism as the QCL characteristic of the RACH process for a specific cell in the existing system (eg, before Rel.17).

[0212] [Alt.1-1]

[0213] The UE may also be considered to support a situation where the first PDCCH and the second PDCCH received in the RACH process have different DMRS QCL characteristics.

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

[0215] For example, the UE may also receive the PDCCH command assuming the first QCL, and in receiving the PDCCH for RAR transmitted from the base station in response to the PRACH triggered by the PDCCH command, assume the second QCL obtained (or provided) separately from the first QCL (refer to Figure 8B ).

[0216] The UE may also assume the DMRS QCL characteristics of a specific CORESET for reception of the PDCCH for RAR. The specific CORESET may also be, for example, a CORESET associated with a specific CSS (eg, Type 1-PDCCH CSS) set.

[0217] [QCL assumptions for each scenario]

[0218] Different QCL assumptions (eg, Alt. 1-0 / Alt. 1-1) may be applied to each scenario of performing the RACH process. In the present disclosure, the scenario may also be rewritten as a condition, an application condition, or a setting condition.

[0219] For example, different QCL assumptions may be applied to the RACH process in the first scenario and the RACH process in the second scenario. As an example, it may also be that Alt.1-0 (for example, refer to Fig. 8A ), in the second scenario, apply Alt.1-1 (e.g., refer to Figure 8B ).

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

[0221] For example, the multiple scenarios for performing the RACH process may be at least one of the following scenarios #1-1 to #1-10. Alternatively, the first scenario may include one or more scenarios, and the second scenario may include one or more other scenarios.

[0222] 《Scenario #1-1》

[0223] Scenario #1-1 may also be a scenario in which multiple TRPs within a cell (e.g., Intra-cell M-TRP) are configured / supported.

[0224] Scenario #1-2

[0225] Scenario #1-2 may also be a scenario where inter-cell multi-TRP (eg, Inter-cell M-TRP) is set / supported.

[0226] Scenario #1-3

[0227] Scenario #1-3 may also be a scenario in which, in multiple TRPs within a cell / multiple TRPs between cells, the PDCCH command and the PDCCH for RAR are associated with different CORESET pool indices.

[0228] For example, the PDCCH command may be transmitted through the first CORESET corresponding to the first CORESET pool index, and the PDCCH for RAR may be transmitted through the second CORESET corresponding to the second CORESET pool index.

[0229] In scenario #1-3, for example, Alt.1-1 may also be applied. Of course, the present invention is not limited thereto, and other QCL concepts (for example, Alt.1-0) may also be applied.

[0230] Scenario #1-4

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

[0232] For example, the PDCCH command and the PDCCH for RAR may be transmitted separately through the CORESET corresponding to the first CORESET pool index.

[0233] In scenario #1-4, for example, Alt.1-0 may also be applied. Of course, the present invention is not limited thereto, and other QCL concepts (for example, Alt.1-1) may also be applied.

[0234] Scenario #1-5

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

[0236] In scenario #1-5, for example, Alt.1-1 may also be applied. Of course, the present invention is not limited thereto, and other QCL concepts (for example, Alt.1-0) may also be applied.

[0237] Scenario #1-6

[0238] Scenario #1-6 may also be a scenario in which, in intra-cell multi-TRP / inter-cell multi-TRP, the PDCCH instruction is associated with the second CORESET pool index (e.g., #1), and the PDCCH used for RAR is associated with the first CORESET pool index (e.g., #0).

[0239] For example, Alt.1-1 can also be applied in scenario #1-6. Of course, the present invention is not limited thereto, and other QCL concepts (for example, Alt.1-0) can also be applied.

[0240] Scenario #1-7

[0241] Scenario #1-7 may also be a scenario where both the PDCCH command and the PDCCH for RAR are associated with the first CORESET pool index (e.g., #0) in intra-cell multiple TRPs / inter-cell multiple TRPs. Alternatively, scenario #1-7 may also be a scenario where both the PDCCH command and the PDCCH for RAR are associated with the second CORESET pool index (e.g., #1) in intra-cell multiple TRPs / inter-cell multiple TRPs.

[0242] In scenario #1-7, for example, Alt.1-0 may also be applied. Of course, the present invention is not limited thereto, and other QCL concepts (for example, Alt.1-1) may also be applied.

[0243] Scenario #1-8

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

[0245] In scenario #1-8, for example, Alt.1-1 may also be applied. Of course, the present invention is not limited thereto, and other QCL concepts (for example, Alt.1-0) may also be applied.

[0246] Scenario #1-9

[0247] Scenario #1-9 may be a scenario in which, in an inter-cell multi-TRP (eg, Inter-cell M-TRP), the PDCCH instruction is associated with the serving cell PCI, and the PDCCH for RAR is associated with an additional PCI (eg, additional PCI).

[0248] In scenario #1-9, for example, Alt.1-1 may also be applied. Of course, the present invention is not limited thereto, and other QCL concepts (for example, Alt.1-0) may also be applied.

[0249] Scenario #1-10

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

[0251] For example, Alt. 1-0 can also be applied in scenario #1-10. Of course, the present invention is not limited thereto, and other QCL concepts (for example, Alt. 1-1) can also be applied.

[0252] [change]

[0253] It is also possible that all scenarios #1-1 to #1-10 are not supported, and only some scenarios are supported. For example, the scenarios supported by each UE may also be determined based on the UE capability. In this case, the UE may not assume some scenarios (for example, scenarios that the UE does not support).

[0254] In addition, which QCL assumption (for example, Alt.1-0 / Alt.1-1) is applied in which scenario can be defined through the specification or set from the base station to the UE through higher layer parameters / DCI, etc.

[0255] In addition, in the first embodiment, two cases of the first QCL concept (for example, Alt. 1-0) and the second QCL concept (for example, Alt. 1-1) are shown as QCL concepts, but the applicable / supportable QCL concepts are not limited thereto. For example, other QCL concepts (for example, the third QCL concept) may also be applied / supported.

[0256] In the first embodiment, scenarios #1-1 to #1-10 are exemplified, but applicable scenarios are not limited thereto. Other scenarios may be additionally applied / supported, or two or more scenarios among scenarios #1-1 to #1-10 may be integrated into one scenario.

[0257] The first embodiment can be applied to a specific cell (eg, SpCell) or to other cells (eg, SCell).

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

[0259] <Second Embodiment>

[0260] In the second embodiment, an example of QCL assumption applied in the case of a RACH procedure (for example, PRACH transmission) for a non-serving cell is described. The second embodiment can also be applied in combination with the first embodiment.

[0261] The second embodiment may also be applied to the QCL concept between PDCCH commands and PDCCHs for RAR in inter-cell mobility (e.g., inter-cell mobility) when supporting a RACH procedure (e.g., PRACH transmission) for a non-serving cell. The non-serving cell (or candidate cell) may also correspond to a frequency different from that of the current serving cell.

[0262] For inter-cell mobility, when the RACH process for a non-serving cell (or candidate cell) is triggered by a PDCCH instruction, the UE may also assume the QCL (eg, DMRS QCL) characteristics in the RACH process based on at least one of the following Alt.2-0 and Alt.2-1.

[0263] [Alt.2-0]

[0264] The UE may also assume that the first PDCCH and the second PDCCH received in the RACH process have the same DMRS QCL characteristics.

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

[0266] When receiving the PDCCH for RAR transmitted from the base station in response to the PRACH triggered by the PDCCH command, the UE may also assume the DMRS QCL characteristics used in the reception of the PDCCH command (see Fig. 9A ). Alt.2-0 may also be applied with the same mechanism as the QCL characteristic of the RACH process for a specific cell (eg, SpCell) in the existing system (eg, before Rel.17).

[0267] [Alt.2-1]

[0268] The UE may also be considered to support a situation where the first PDCCH and the second PDCCH received in the RACH process have different DMRS QCL characteristics.

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

[0270] For example, the UE may also assume the first QCL and receive the PDCCH command, and assume the following second QCL: in the reception of the PDCCH for RAR transmitted from the base station in response to the PRACH triggered by the PDCCH command, the second QCL (reference Fig. 9B ).

[0271] The UE may also assume the DMRS QCL characteristics of a specific CORESET regarding the reception of the PDCCH for RAR. The specific CORESET may also be, for example, a CORESET associated with a specific CSS (eg, Type 1-PDCCH CSS) set.

[0272] A specific CSS (eg, type 1-PDCCH CSS) set may also be option 2a or option 2b below. Which of option 2a and option 2b is applied may be defined by the specification, set from the base station to the UE via a higher layer parameter, or selected according to the scenario.

[0273] Option 2a

[0274] The specific CSS (eg, Type 1-PDCCH CSS) set may be a Type 1-PDCCH CSS set from the non-serving cell in which the RACH is triggered. In this case, the Type 1-PDCCH CSS set may be separately provided / configured for each non-serving cell.

[0275] Option 2b

[0276] The specific CSS (eg, Type 1-PDCCH CSS) set may also be the Type 1-PDCCH CSS set from the serving cell. Option 2b may also be applied in the case where the non-serving cell corresponds to the same frequency as the serving cell.

[0277] [QCL assumptions for each scenario]

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

[0279] The scenarios may also be classified based on the types of cells / PCIs corresponding to the PDCCH command and the PDCCH for RAR, respectively (e.g., serving cell (or serving cell PCI) / additional cell (or additional cell PCI)). Alternatively, the scenarios may also be classified based on the frequency corresponding to the non-serving cell / the 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).

[0280] For example, the multiple scenarios for performing the RACH process 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 another one or more scenarios.

[0281] Scenario #2-1

[0282] Scenario #2-1 may be a scenario in which a PDCCH command is associated with an additional PCI (eg, additional PCI), and a PDCCH for RAR is associated with a serving cell PCI.

[0283] In scenario #2-1, option 2a of Alt.2-1 may also be applied, for example. Of course, the present invention is not limited thereto, and other QCL concepts (for example, option 2b of Alt.2-0 / Alt.2-1) may also be applied.

[0284] Scenario #2-2

[0285] Scenario #2-2 may be a scenario in which the PDCCH command is associated with the serving cell PCI, and the PDCCH for RAR is associated with an additional PCI (eg, additional PCI).

[0286] In scenario #2-2, option 2b of Alt. 2-1 may also be applied, for example. Of course, the present invention is not limited thereto, and other QCL concepts (for example, option 2a of Alt. 2-0 / Alt. 2-1) may also be applied.

[0287] Scenario #2-3

[0288] Scenario #2-3 may be a scenario where both the PDCCH command and the PDCCH for RAR are associated with the serving cell PCI. Alternatively, scenario #2-3 may be a scenario where both the PDCCH command and the PDCCH for RAR are associated with an additional PCI (eg, additionalPCI).

[0289] In scenario #2-3, for example, Alt. 2-0 may also be applied. Of course, the present invention is not limited thereto, and other QCL concepts (for example, option 2a / 2b of Alt. 2-1) may also be applied.

[0290] Scenario #2-4

[0291] Scenario #2-4 may also be a scenario where the non-serving cell corresponds to the same frequency as the serving cell.

[0292] In scenario #2-4, option 2b of Alt.2-0 / Alt.2-1 may also be applied, but the present invention is not limited thereto and other QCL concepts (eg, option 2a of Alt.2-1) may also be applied.

[0293] Scenario #2-5

[0294] Scenario #2-5 may also be a scenario where the non-serving cell corresponds to a frequency different from that of the serving cell.

[0295] In scenario #2-5, option 2a of Alt.2-1 may also be applied, for example. Of course, the present invention is not limited thereto, and other QCL concepts (for example, option 2b of Alt.2-0 / Alt.2-1) may also be applied.

[0296] [change]

[0297] The second embodiment can also be applied to at least one of the following conditions 2-1 and 2-2.

[0298] 《Condition 2-1》

[0299] The PDCCH (PDCCH command) that triggers the PRACH can also be received through the PCI corresponding to the serving cell PCI.

[0300] Alternatively, the PDCCH (PDCCH command) that triggers the PRACH may be received via the PCI corresponding to the additional PCI.

[0301] 《Condition 2-2》

[0302] The PDCCH (PDCCH command) that triggers the PRACH may also be received in a cell corresponding to the SpCell (eg, PCell / PSCell) or a cell corresponding to the same frequency as the SpCell.

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

[0304] Alternatively, all scenarios #2-1 to #2-5 may not be supported, but some scenarios may be supported. For example, the scenarios supported by each UE may be determined based on the UE capability. In this case, the UE may not assume some scenarios (for example, scenarios not supported by the UE).

[0305] In addition, which QCL assumption (for example, Alt.2-0 / Alt.2-1) is applied to which scenario can be defined through specifications or set from the base station to the UE through higher layer parameters / DCI, etc.

[0306] In the second embodiment, two cases of the first QCL concept (e.g., Alt. 2-0) and the second QCL concept (e.g., Alt. 2-1) are shown as QCL concepts, but the QCL concepts that can be applied / supported are not limited thereto. For example, other QCL concepts (e.g., the third QCL concept) may also be applied / supported.

[0307] In the second embodiment, scenarios #2-1 to #2-5 are exemplified, but applicable scenarios are not limited thereto. Other scenarios may be additionally applied / supported, or two or more scenarios among scenarios #2-1 to #2-5 may be integrated into one scenario.

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

[0309] <Supplement>

[0310] [Notification of information to UE]

[0311] The notification of arbitrary information from the network (Network (NW)) (for example, from the base station (Base Station (BS))) to the UE (in other words, the reception of arbitrary information from the BS in the UE) in the above-mentioned embodiment can also be carried out using physical layer signaling (for example, DCI), high-layer signaling (for example, RRC signaling, MAC CE), specific signals / channels (for example, PDCCH, PDSCH, reference signals), or a combination thereof.

[0312] When the above notification is performed through MAC CE, the MAC CE can also be identified by including a new logical channel ID (Logical Channel ID (LCID)) that is not specified in the existing specifications in the MAC subheader.

[0313] In the case where the above-mentioned notification is performed through DCI, the above-mentioned notification may also be performed through a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used in scrambling of a cyclic redundancy check (CRC) bit assigned to the DCI, the format of the DCI, etc.

[0314] In addition, notification of any information in the above-mentioned embodiments to the UE may be performed periodically, semi-continuously, or aperiodically.

[0315] [Notification of information from UE]

[0316] The notification of arbitrary information from the UE (to the NW) in the above-mentioned embodiment (in other words, the sending / reporting of arbitrary information from the UE to the BS) can also be carried out using physical layer signaling (e.g., UCI), high-layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0317] In the case where the above notification is performed through MAC CE, the MAC CE can also be identified by including a new LCID that is not specified in the existing specifications in the MAC subheader.

[0318] In the case where the notification is performed through UCI, the notification may be transmitted using PUCCH or PUSCH.

[0319] In addition, the notification of arbitrary information from the UE in the above-mentioned embodiments may be performed periodically, semi-continuously, or aperiodically.

[0320] [About application of each embodiment]

[0321] At least one of the above-mentioned embodiments may also be applied when a specific condition is met. The specific condition may be specified in the specification or notified to the UE / BS using high-layer signaling / physical layer signaling.

[0322] At least one of the above-mentioned embodiments may also be applied only to a UE that reports a specific UE capability (UE capability) or supports the specific UE capability.

[0323] The specific UE capability may also represent at least one of the following:

[0324] Support two TAs for multiple TRPs;

[0325] Support for two TAs for intra-cell multiple TRPs (e.g., intra-cell M-TRP);

[0326] Support for two TAs for inter-cell multi-TRP (e.g., inter-cell M-TRP);

[0327] Support L1 / L2 inter-cell mobility.

[0328] In addition, the above-mentioned specific UE capabilities can be capabilities that are applied across all frequencies (commonly regardless of frequency), or capabilities for each frequency (for example, one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), or capabilities for each frequency range (for example, Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or capabilities for each subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities for each feature set (Feature Set (FS)) or each feature set (Feature Set Per Component-carrier (FSPC)) of each component carrier.

[0329] In addition, the above-mentioned specific UE capabilities can be capabilities applied across all full-duplex modes (commonly regardless of the duplex mode) or capabilities of each duplex mode (for example, time division duplex (TDD) and frequency division duplex (FDD)).

[0330] In addition, at least one of the above-mentioned embodiments may also be applied when the UE is set / activated / triggered with specific information associated with the above-mentioned embodiments (or the operation of the above-mentioned embodiments is implemented) through high-layer signaling / physical layer signaling. For example, the specific information may also be information indicating activation of multiple TAs for multiple TRPs, information indicating activation of multiple TAs for multiple TRPs within a cell, information indicating activation of multiple TAs for multiple TRPs between cells, information indicating activation of L1 / L2 inter-cell mobility, any RRC parameter for a specific version (e.g., Rel.18 / 19), etc.

[0331] Even if the UE does not support at least one of the above-mentioned specific UE capabilities or is not configured with the above-mentioned specific information, the UE may also apply operations such as Rel.15 / 16 / 17.

[0332] (Note)

[0333] The following inventions are added to one embodiment of the present disclosure.

[0334] [Additional Note 1-1]

[0335] A terminal having:

[0336] A receiving unit receives a first downlink control channel used in triggering a random access process; a control unit controls reception of a second downlink control channel used in receiving a response signal in the random access process based on at least one of a first QCL assumption using a first quasi-co-location (QCL) corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set, when the random access process of each transmitting and receiving point is supported.

[0337] [Additional Notes 1-2]

[0338] A terminal as described in Appendix 1-1, wherein:

[0339] The control unit determines a QCL assumption to be used in the second downlink control channel based on a scenario in which the random access procedure is applied.

[0340] [Notes 1-3]

[0341] A terminal as described in Supplement 1-1 or Supplement 1-2, wherein:

[0342] The control unit determines which of the first QCL concept and the second QCL concept to apply in receiving the second downlink control channel based on at least one of the control resource pool index corresponding to the first downlink control channel and the control resource pool index corresponding to the second downlink control channel.

[0343] [Addendum 1-4]

[0344] A terminal as described in any one of Supplement 1-1 to Supplement 1-3, wherein:

[0345] The control unit determines which of the first QCL assumption and the second QCL assumption to apply in receiving the second downlink control channel based on at least one of a type of a cell corresponding to the first downlink control channel and a type of a cell corresponding to the second downlink control channel.

[0346] [Additional Note 2-1]

[0347] A terminal having:

[0348] a receiving unit, receiving a first downlink control channel used in triggering a random access process for a non-serving cell; and

[0349] A control unit controls the reception of a second downlink control channel used in the reception of a response signal in the random access process based on at least one of a first QCL assumption utilizing a first quasi-co-location (QCL) corresponding to the first downlink control channel and a second QCL assumption utilizing a second QCL corresponding to a specific control resource set.

[0350] [Additional Note 2-2]

[0351] A terminal as described in Appendix 2-1, wherein:

[0352] The control unit determines a QCL assumption to be used in the second downlink control channel based on a scenario in which the random access procedure is applied.

[0353] [Additional Notes 2-3]

[0354] A terminal as described in Note 2-1 or Note 2-2, wherein:

[0355] The control unit determines which of the first QCL assumption and the second QCL assumption to apply in receiving the second downlink control channel based on at least one of a type of a cell corresponding to the first downlink control channel and a type of a cell corresponding to the second downlink control channel.

[0356] [Additional Notes 2-4]

[0357] A terminal as described in any one of Notes 2-1 to 2-3, wherein:

[0358] The control unit determines which of the first QCL assumption and the second QCL assumption to apply in reception of the second downlink control channel based on at least one of a frequency corresponding to the non-serving cell and a frequency corresponding to the serving cell.

[0359] (Wireless Communication System)

[0360] Hereinafter, a configuration of a wireless communication system according to an embodiment of the present disclosure will be described. In the wireless communication system, communication is performed using any one of the wireless communication methods according to the above-mentioned embodiments of the present disclosure or a combination thereof.

[0361] Fig.10 1 is a diagram showing an example of a schematic structure of a wireless communication system involved in one embodiment. The wireless communication system 1 (may also be simply referred to as system 1) may also be a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP), the fifth generation mobile communication system New Radio (5G NR), and the like.

[0362] In addition, the wireless communication system 1 can also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple radio access technologies (Radio Access Technology (RAT)). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA))) and NR (E-UTRA-NR Dual Connectivity (E-UTRA-NR Dual Connectivity (EN-DC))), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NR-E-UTRA Dual Connectivity (NE-DC))), etc.

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

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

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

[0366] The user terminal 20 may be connected to at least one of the plurality of base stations 10. The user terminal 20 may use at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).

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

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

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

[0370] The base station 10 may also be connected to the core network 30 via other base stations 10 or directly. The core network 30 may also include, for example, at least one of an evolved packet core (EPC), a 5G core network (5G Core Network (5GCN)), a next generation core (NGC), and the like.

[0371] The core network 30 may also include network functions (NF), such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), Operation, Administration and Maintenance (Management) (OAM), etc. In addition, multiple functions may be provided by one network node. In addition, communication with an external network (e.g., network) may also be performed via DN.

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

[0373] In the wireless communication system 1, a wireless access method based on orthogonal frequency division multiplexing (OFDM) 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.

[0374] The radio access scheme may also be referred to as a waveform. In addition, in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the radio access schemes for UL and DL.

[0375] As downlink channels, the wireless communication system 1 may use a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH))), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc.

[0376] In addition, as uplink channels, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20), an uplink control channel (Physical Uplink Control Channel (PUCCH))), a random access channel (Physical Random Access Channel (PRACH)) and the like can also be used in the wireless communication system 1.

[0377] User data, high-layer control information, system information block (SIB), etc. are transmitted through PDSCH. User data, high-layer control information, etc. can also be transmitted through PUSCH. In addition, master information block (MIB) can also be transmitted through PBCH.

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

[0379] In addition, the DCI for scheduling the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI for scheduling the PUSCH may also be referred to as UL grant, UL DCI, etc. In addition, the PDSCH may also be rewritten as DL data, and the PUSCH may also be rewritten as UL data.

[0380] In the detection of PDCCH, the control resource set (CORESET) and the search space (search space) can also be used. CORESET corresponds to the resources for searching DCI. The search space corresponds to the search area and search method of PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor the CORESET associated with a certain search space based on the search space setting.

[0381] A search space may also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space set. In addition, the "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" and the like in the present disclosure may also be rewritten mutually.

[0382] Through PUCCH, uplink control information (uplink control information (UCI)) including at least one of channel state information (CSI), delivery confirmation information (e.g., also called hybrid automatic repeat request confirmation (HARQ-ACK), ACK / NACK, etc.) and scheduling request (SR) can also be transmitted. Through PRACH, random access preambles for establishing a connection with a cell can also be transmitted.

[0383] In addition, in the present disclosure, downlink, uplink, etc. may be expressed without "link". In addition, various channels may be expressed without "Physical" at the beginning.

[0384] In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. can also be transmitted. As DL-RS, in the wireless communication system 1, a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), etc. can also be transmitted.

[0385] 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 also be referred to as SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. may also be referred to as reference signals.

[0386] In addition, in the wireless communication system 1, as an uplink reference signal (Uplink Reference Signal (UL-RS)), a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. can also be transmitted. In addition, DMRS can also be called a user terminal specific reference signal (UE-specific Reference Signal).

[0387] (Base Station)

[0388] Fig.111 is a diagram showing an example of a structure of a base station involved in one embodiment. The base station 10 includes a control unit 110, a transmitting and receiving unit 120, a transmitting and receiving antenna 130, and a transmission path interface (transmission line interface) 140. In addition, the control unit 110, the transmitting and receiving unit 120, the transmitting and receiving antenna 130, and the transmission path interface 140 may each be provided with more than one.

[0389] In addition, in this example, the functional blocks of the characteristic parts in this embodiment are mainly shown, and it is also conceivable that the base station 10 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0390] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which the present disclosure relates.

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

[0392] The transmitting and receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measuring unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting and receiving unit 120 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter (phase shifter), a measuring circuit, a transmitting and receiving circuit, etc., which are described based on the common knowledge in the technical field involved in the present disclosure.

[0393] The transmitting and receiving unit 120 may be configured as an integrated transmitting and receiving unit, or may be configured as a transmitting unit and a receiving unit. The transmitting unit may also be configured as a transmitting processing unit 1211 and an RF unit 122. The receiving unit may also be configured as a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

[0394] The transmitting / receiving antenna 130 can be constituted by an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

[0395] The transmitting and receiving unit 120 may also transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may also receive the above-mentioned uplink channel, uplink reference signal, etc.

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

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

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

[0399] The transmitting and receiving unit 120 (RF unit 122 ) may also perform modulation, filter processing, amplification, etc. on the baseband signal to a radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 130 .

[0400] On the other hand, the transmitting and receiving unit 120 (RF unit 122) may also perform amplification, filter processing (filter processing), demodulation into a baseband signal, etc. on the signal in the radio frequency band received by the transmitting and receiving antenna 130.

[0401] The sending and receiving unit 120 (receiving processing unit 1212) can also apply analog-to-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (as needed), filter processing (filtering processing), demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal, and obtain user data, etc.

[0402] The transmitting and receiving unit 120 (measuring unit 123) may also implement measurements related to the received signal. For example, the measuring unit 123 may also perform radio resource management (Radio Resource Management (RRM)) measurement, channel state information (CSI) measurement, etc. based on the received signal. The measuring unit 123 may also measure the received power (e.g., reference signal received power (Reference Signal Received Power (RSRP))), received quality (e.g., reference signal received quality (Reference Signal Received Quality (RSRQ)), signal to interference plus noise ratio (Signal to Interference plus Noise Ratio (SINR)), signal to noise ratio (Signal to Noise Ratio (SNR))), signal strength (e.g., received signal strength indicator (Received Signal Strength Indicator (RSSI))), propagation path information (e.g., CSI), etc. The measurement result may also be output to the control unit 110.

[0403] The transmission path interface 140 can also send and receive signals (return signaling) between devices included in the core network 30 (for example, a network node providing NF), other base stations 10, etc., and obtain and transmit user data (user plane data) and control plane data for the user terminal 20.

[0404] In addition, the transmission unit and the reception unit of the base station 10 in the present disclosure may also be constituted by at least one of the transmission and reception unit 120 , the transmission and reception antenna 130 , and the transmission path interface 140 .

[0405] The transmitting and receiving unit 120 may also transmit a first downlink control channel used in triggering a random access procedure. The control unit 110 may also control the transmission of a second downlink control channel used in receiving a response signal in a random access procedure based on at least one of a first QCL assumption using a first quasi-co-location (QCL) corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set, while supporting a random access procedure for each transmitting and receiving point. The case of supporting a random access procedure for each transmitting and receiving point may also be a case of supporting the setting of a TA for each transmitting and receiving point.

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

[0407] (User Terminal)

[0408] Fig.12 2 is a diagram showing an example of a configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230. In addition, the control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may each be provided in one or more pieces.

[0409] In addition, in this example, the functional blocks of the characteristic parts in this embodiment are mainly shown, and it is also conceivable that the user terminal 20 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may be omitted.

[0410] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which the present disclosure relates.

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

[0412] The transmitting and receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measuring unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting and receiving unit 220 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting and receiving circuit, etc., which are described based on the common knowledge in the technical field involved in the present disclosure.

[0413] The transmitting and receiving unit 220 may be configured as an integrated transmitting and receiving unit, or may be configured as a transmitting unit and a receiving unit. The transmitting unit may also be configured as a transmitting processing unit 2211 and an RF unit 222. The receiving unit may also be configured as a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.

[0414] The transmitting / receiving antenna 230 can be constituted by an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

[0415] The transmitting and receiving unit 220 may also receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 220 may also transmit the above-mentioned uplink channel, uplink reference signal, etc.

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

[0417] The sending and receiving unit 220 (sending processing unit 2211), for example, can also perform PDCP layer processing, RLC layer processing (for example, RLC retransmission control), MAC layer processing (for example, HARQ retransmission control), etc. on the data, control information, etc. obtained from the control unit 210, and generate a bit string to be sent.

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

[0419] In addition, whether to apply DFT processing may also be based on the setting of transform precoding. Regarding a certain channel (e.g., PUSCH), when transform precoding is valid (enabled), the transmitting and receiving unit 220 (transmitting processing unit 2211) may also perform DFT processing as the above-mentioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform. Otherwise, the transmitting and receiving unit 220 (transmitting processing unit 2211) may also perform DFT processing as the above-mentioned transmission processing without performing DFT processing.

[0420] The transmitting and receiving unit 220 (RF unit 222 ) may also perform modulation, filter processing (filtering processing), amplification, etc. on the baseband signal to a radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 230 .

[0421] On the other hand, the transmitting and receiving unit 220 (RF unit 222) may also perform amplification, filter processing (filter processing), demodulation into a baseband signal, etc. on the signal in the radio frequency band received by the transmitting and receiving antenna 230.

[0422] The sending and receiving unit 220 (receiving processing unit 2212) can also apply analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing (filtering processing), demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal, and obtain user data, etc.

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

[0424] In addition, the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 220 and the transmitting and receiving antenna 230 .

[0425] The transmitting and receiving unit 220 may also receive a first downlink control channel used in triggering a random access procedure. The control unit 210 may also control reception of a second downlink control channel used in receiving a response signal in a random access procedure based on at least one of a first QCL assumption using a first quasi-co-location (QCL) corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set, while supporting a random access procedure for each transmitting and receiving point. The case of supporting a random access procedure for each transmitting and receiving point may also be a case of supporting the setting of a TA for each transmitting and receiving point.

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

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

[0428] The control unit 210 may also determine the QCL assumption to be used for the second downlink control channel based on the scenario in which the random access process is applied. For example, the control unit 210 may also determine which of the first QCL assumption and the second QCL assumption to be applied in the reception of the second downlink control channel based on at least one of the type of the cell corresponding to the first downlink control channel and the type of the cell corresponding to the second downlink control channel. Alternatively, the control unit 210 may also determine which of the first QCL assumption and the second QCL assumption to be applied in the reception of the second downlink control channel based on at least one of the frequency corresponding to the non-service cell and the frequency corresponding to the service cell.

[0429] (Hardware Structure)

[0430] In addition, the block diagram used in the description of the above-mentioned embodiment shows a block of a functional unit. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented by a device that is physically or logically combined, or two or more devices that are physically or logically separated can be directly or indirectly (for example, by wired, wireless, etc.) connected and implemented by these multiple devices. The functional block can also be implemented by combining the above-mentioned one device or the above-mentioned multiple devices with software.

[0431] Here, the functions include judging, deciding, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, solving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but are not limited to these. For example, a functional block (structural unit) that implements a sending function may also be referred to as a transmitting unit, a transmitter, etc. Any one of them is as described above, and the implementation method thereof is not particularly limited.

[0432] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Fig.13 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0433] In addition, in the present disclosure, the terms such as device, circuit, equipment, section, and unit can be interchanged. 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 may exclude some of the devices.

[0434] For example, only one processor 1001 is shown, but there may be multiple processors. In addition, the processing may be performed by one processor, or may be performed by two or more processors simultaneously, sequentially, or in other ways. In addition, the processor 1001 may also be implemented by one or more chips.

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

[0436] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may also be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), the sending and receiving unit 120 (220), etc. may also be implemented by the processor 1001.

[0437] In addition, the processor 1001 reads the program (program code), software module, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and performs various processes based on them. As a program, a program that causes a computer to perform at least a part of the operations described in the above-mentioned embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001, and the same can be implemented for other functional blocks.

[0438] The memory 1002 may also be a computer-readable recording medium, for example, composed of at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), or other appropriate storage media. The memory 1002 may also be referred to as a register, a cache, a main memory (main storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing the wireless communication method involved in one embodiment of the present disclosure.

[0439] The storage 1003 may also be a computer-readable recording medium, such as a flexible disk, a floppy disk, an optical disk (such as a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray (Blu-ray) (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (such as a card, a stick, a key drive), a magnetic stripe, a database, a server, or at least one of other suitable storage media. The storage 1003 may also be referred to as an auxiliary storage device.

[0440] The communication device 1004 is hardware (transmitting and 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, a network controller, a network card, a communication module, etc. In order to realize at least one of frequency division duplex (Frequency Division Duplex (FDD)) and time division duplex (Time Division Duplex (TDD)), the communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the above-mentioned transmitting and receiving unit 120 (220), the transmitting and receiving antenna 130 (230), etc. may also be realized by the communication device 1004. The transmitting and receiving unit 120 (220) may also be physically or logically separated by the transmitting unit 120a (220a) and the receiving unit 120b (220b).

[0441] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that implements output to the outside (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.). In addition, the input device 1005 and the output device 1006 may also be an integrated structure (e.g., a touch panel).

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

[0443] In addition, the base station 10 and the user terminal 20 may also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA), and the hardware may be used to implement a part or all of each functional block. For example, the processor 1001 may also be implemented using at least one of these hardware.

[0444] (Variation Example)

[0445] In addition, the terms described in the present disclosure and the terms required for understanding the present disclosure may also be replaced with terms having the same or similar meanings. For example, channels, symbols, and signals (signals or signaling) may also be rewritten with each other. In addition, a signal may also be a message. A reference signal may also be referred to as RS, and may also be referred to as a pilot, a pilot signal, etc. depending on the standard applied. In addition, a component carrier (CC) may also be referred to as a cell, a frequency carrier, a carrier frequency, etc.

[0446] A wireless frame may also be composed of one or more periods (frames) in the time domain. Each period (frame) of the one or more periods (frames) constituting a wireless frame may also be referred to as a subframe. Further, a subframe may also be composed of one or more time slots in the time domain. A subframe may also be a fixed time length (e.g., 1 ms) that is not dependent on a parameter set (numerology).

[0447] Here, the parameter set may also be a communication parameter applied in at least one of the transmission and reception of a certain signal or channel. For example, the parameter set may also represent at least one of a subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), the number of symbols per TTI, a wireless frame structure, a specific filtering process performed by a transmitter and receiver in the frequency domain, a specific windowing process performed by a transmitter and receiver in the time domain, and the like.

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

[0449] A time slot may also include multiple mini-slots. Each mini-slot may also be composed of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may also be composed of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may also be referred to as a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may also be referred to as a PDSCH (PUSCH) mapping type B.

[0450] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols may also be referred to by their respective names. In addition, time units such as frames, subframes, time slots, mini-time slots, and symbols in the present disclosure may also be replaced with each other.

[0451] For example, a subframe may be referred to as a TTI, a plurality of consecutive subframes may be referred to as a TTI, and a time slot or a mini time slot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. In addition, the unit representing a TTI may be referred to as a time slot, a mini time slot, etc. instead of a subframe.

[0452] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station schedules each user terminal to allocate wireless resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) in TTI units. In addition, the definition of TTI is not limited to this.

[0453] TTI may also be a transmission time unit for a data packet (transport block), a code block, a code word, etc. that has been channel-coded, and may also be a processing unit for scheduling, link adaptation, etc. In addition, when TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0454] In addition, when a time slot or a mini time slot is called TTI, more than one TTI (i.e., more than one time slot or more than one mini time slot) can also be the minimum time unit of scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit of scheduling can also be controlled.

[0455] A TTI having a time length of 1 ms may also be referred to as a normal TTI (TTI in 3GPP Rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub time slot, a time slot, etc.

[0456] In addition, a long TTI (e.g., normal TTI, subframe, etc.) can also be rewritten as a TTI with a time length exceeding 1 ms, and a short TTI (e.g., shortened TTI, etc.) can also be rewritten as a TTI with a TTI length shorter than that of the long TTI and longer than 1 ms.

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

[0458] In addition, an RB may also include one or more symbols in the time domain, and may also be the length of a slot, a mini-slot, a subframe, or a TTI. A TTI, a subframe, etc. may also be composed of one or more resource blocks, respectively.

[0459] In addition, one or more RBs may also be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, etc.

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

[0461] Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) may also represent a subset of contiguous common RBs (common resource blocks) for a parameter set in a carrier. Here, common RBs may also be identified by the index of the RB relative to the common reference point of the carrier. PRBs may also be defined in a BWP and numbered within the BWP.

[0462] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). For a UE, one or more BWPs may be configured in one carrier.

[0463] At least one of the configured BWPs may be activated, and the UE may not assume that a specific signal / channel is transmitted or received except in the activated BWP. In addition, "cell", "carrier", etc. in the present disclosure may be rewritten as "BWP".

[0464] In addition, the above-mentioned structures of radio frames, subframes, time slots, mini-time slots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of time slots per subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and the like can be changed in various ways.

[0465] In addition, the information, parameters, etc. described in the present disclosure may be represented by absolute values, relative values ​​relative to a specific value, or other corresponding information. For example, wireless resources may also be indicated by a specific index.

[0466] In the present disclosure, the names used for parameters, etc. are not limiting in all respects. Furthermore, the mathematical formulas, etc. using these parameters may be different from those explicitly disclosed in the present disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and therefore, the various names assigned to these various channels and information elements are not limiting in all respects.

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

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

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

[0470] The notification of information is not limited to the methods / implementations described in the present disclosure, and may also be performed by other methods. For example, the notification of information in the present disclosure may also be implemented through physical layer signaling (e.g., downlink control information (Downlink Control Information (DCI))), uplink control information (Uplink Control Information (UCI))), high-layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB)), System Information Block (SIB)), etc.), Medium Access Control (MAC) signaling), other signals or a combination thereof.

[0471] In addition, physical layer signaling may also be referred to as layer 1 / layer 2 (Layer 1 / Layer 2 (L1 / L2)) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. In addition, RRC signaling may also be referred to as an RRC message, such as an RRC connection establishment (RRC Connection Setup) message, an RRC connection reconstruction (RRC Connection Reconfiguration) message, etc. In addition, MAC signaling may also be notified using, for example, a MAC control element (MACControl Element (CE)).

[0472] Furthermore, notification of specific information (eg, notification of “it is X”) is not limited to explicit notification, but may be performed implicitly (eg, by not notifying the specific information or by notifying other information).

[0473] The determination can be made by a value represented by a bit (0 or 1), by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a specific value).

[0474] Whether software is called software, firmware, middle-ware, microcode, hardware description language, or other names, it should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, program, sub-program, software modules, applications, software applications, software packages, routines, sub-routines, objects, executable files, execution threads, procedures, functions, etc.

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

[0476] The terms "system" and "network" used in the present disclosure can be used interchangeably. "Network" may also refer to a device (eg, a base station) included in the network.

[0477] In the present disclosure, terms such as "precoding", "precoder", "weight (precoding weight)", "Quasi-Co-Location (QCL)", "Transmission Configuration Indication state (TCI state)", "spatial relation", "spatial domain filter", "transmission 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" can be used interchangeably.

[0478] In the present 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" can be used interchangeably. There are also cases where base stations are referred to by terms such as macro cell, small cell, micro-micro cell, and micro-micro cell.

[0479] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services through a base station subsystem (for example, a small base station for indoor use (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a part or the entirety of the coverage area of ​​at least one of a base station and a base station subsystem that provides communication services within the coverage area.

[0480] In the present disclosure, the base station sends information to the terminal, and this situation can also be rewritten mutually with the base station instructing the terminal to control / operate based on the information.

[0481] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user device (User Equipment (UE))”, and “terminal” can be used interchangeably.

[0482] There are also cases where a mobile station is referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, hand set, user agent, mobile client, client or several other appropriate terms.

[0483] At least one of the base station and the mobile station may also be referred to as a transmission device, a reception device, a wireless communication device, etc. In addition, at least one of the base station and the mobile station may also be a device mounted on a moving object, a moving object body, etc.

[0484] The mobile body refers to a movable object, and the moving speed is arbitrary, including the situation where the mobile body stops. The mobile body includes, for example, vehicles, transport vehicles, cars, automatic two-wheeled vehicles (motorcycles), bicycles, connected cars, loading shovels, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trolleys, rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, hot air balloons and objects carried on them, but are not limited to these. In addition, the mobile body can also be a mobile body that drives autonomously based on operating instructions.

[0485] The mobile body may be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile body that moves unmanned (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). In addition, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may also be an Internet of Things (IoT) device such as a sensor.

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

[0487] The driving unit 41 is composed of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is composed of at least a steering wheel (also called a handle), and steers at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by a user.

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

[0489] As signals from various sensors 50-58, there are current signals from the current sensor 50 for sensing the current of the motor, speed signals of the front wheels 46 / rear wheels 47 obtained by the speed sensor 51, air pressure signals of the front wheels 46 / rear wheels 47 obtained by the air pressure sensor 52, vehicle speed signals obtained by the vehicle speed sensor 53, acceleration signals obtained by the acceleration sensor 54, depression amount signals of the accelerator pedal 43 obtained by the accelerator pedal sensor 55, depression amount signals of the brake pedal 44 obtained by the brake pedal sensor 56, operation signals of the shift lever 45 obtained by the shift lever sensor 57, detection signals for detecting obstacles, vehicles, pedestrians, etc. obtained by the object detection sensor 58, and the like.

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

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

[0492] The driving assistance system unit 64 is composed of various devices that provide functions for preventing accidents before they happen or reducing the driver's driving burden, such as millimeter wave radar, light detection and ranging (LiDAR), camera, positioning device (for example, Global Navigation Satellite System (GNSS)), map information (for example, High Definition (HD) map, Autonomous Vehicle (AV) map, etc.), gyroscope system (for example, inertial measurement unit (Inertial Measurement Unit (IMU))), inertial navigation unit (Inertial Navigation System (INS))), artificial intelligence (Artificial Intelligence (AI)) chip, AI processor, and one or more ECUs that control these devices. In addition, the driving assistance system unit 64 sends and receives various information via the communication module 60 to realize the driving assistance function or the automatic driving function.

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

[0494] The communication module 60 can be controlled by the microprocessor 61 of the electronic control unit 49, and is a communication device that can communicate with an external device. For example, various information is sent and received with the external device via wireless communication. The communication module 60 can be inside or outside the electronic control unit 49. The external device can also be, for example, the above-mentioned base station 10, user terminal 20, etc. In addition, the communication module 60 can also be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (it can also function as at least one of the base station 10 and user terminal 20).

[0495] The communication module 60 may also transmit at least one of the following to an external device via wireless communication: a signal from the various sensors 50-58 input to the electronic control unit 49, information obtained based on the signal, and information based on input from the outside (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 referred to as an input unit that receives input. For example, the PUSCH transmitted through the communication module 60 may also include information based on the above input.

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

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

[0498] In addition, the base station in the present disclosure may also be rewritten as a user terminal. For example, the various methods / implementations of the present disclosure may also be applied to a structure in which the communication between a base station and a user terminal is replaced by the communication between multiple user terminals (for example, it may also be referred to as device-to-device (D2D)), vehicle-to-everything (V2X), etc.). In this case, it may also be set as a structure in which the user terminal 20 has the functions possessed by the above-mentioned base station 10. In addition, terms such as "uplink", "downlink", etc. may also be rewritten as terms corresponding to communication between terminals (for example, "sidelink"). For example, uplink channels, downlink channels, etc. may also be rewritten as sidelink channels.

[0499] Likewise, the user terminal in the present disclosure may be rewritten as a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

[0500] In the present disclosure, the actions set to be performed by the base station are sometimes also performed by its upper node according to the circumstances. Obviously, in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (for example, considering a Mobility Management Entity (MME)), a Serving-Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0501] Each method / implementation method described in this disclosure may be used alone or in combination, and may be used in a switched manner as the method is executed. In addition, the processing procedures, timings, flow charts, etc. of each method / implementation method described in this disclosure may be reversed in order as long as they are not contradictory. For example, with respect to the method described in this disclosure, the elements of various steps are presented in an illustrative order, but are not limited to the specific order presented.

[0502] The various modes / implementations described in the present disclosure may also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), systems using other appropriate wireless communication methods, and next-generation systems that are expanded, modified, generated, or specified based on them. In addition, multiple systems can also be applied in combination (for example, LTE or LTE-A, combination with 5G, etc.).

[0503] The phrase “based on” used in the present disclosure does not mean “based only on” unless otherwise specified. In other words, the phrase “based on” means both “based only on” and “based at least on”.

[0504] Any reference to an element using the terms "first", "second", etc. used in this disclosure does not fully define the amount or order of these elements. These terms can be used in this disclosure as a convenient method to distinguish between two or more elements. Therefore, reference to the first and second elements does not mean that only two elements can be used or that the first element must take precedence over the second element in some form.

[0505] The term "determining" used in the present disclosure may include a variety of actions. For example, "determining" may also refer to situations where judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching in a table, database or other data structure), ascertaining, etc. are considered to be "determining".

[0506] In addition, "judgment (decision)" may also be a situation where receiving (for example, receiving information), sending (for example, sending information), input (input), output (output), accessing (for example, accessing data in a memory), etc. are regarded as making a "judgment (decision)".

[0507] In addition, "judgment (decision)" can also be regarded as a situation where resolving, selecting, choosing, establishing, comparing, etc. are regarded as a situation where "judgment (decision)" is performed. That is, "judgment (decision)" can also be regarded as a situation where some actions are regarded as a situation where "judgment (decision)" is performed.

[0508] In addition, "judge (decide)" can also be rewritten as "assuming (assuming)", "expecting (expecting)", "considering (considering)" and so on.

[0509] The “maximum transmit power” recorded in the present disclosure may refer to the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0510] The terms "connected", "coupled", or all their variations used in this disclosure refer to all direct or indirect connections or combinations between two or more elements, and can include the situation where one or more intermediate elements exist between the two elements that are "connected" or "coupled" to each other. The combination or connection between the elements can be physical, logical, or a combination thereof. For example, "connection" can also be rewritten as "access".

[0511] In the present disclosure, when two elements are connected, it is possible to consider being "connected" or "combined" to each other using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, light (both visible and invisible) region, etc. as several non-limiting and non-inclusive examples, thereby being "connected" or "combined" to each other.

[0512] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other". In addition, the term may also mean "A and B are different from C, respectively". The terms "separate" and "combined" may also be interpreted in the same manner as "different".

[0513] When the terms “include,” “including,” and variations thereof are used in the present disclosure, these terms have an inclusive meaning, similar to the term “comprising.” Furthermore, the term “or” used in the present disclosure does not have an exclusive OR meaning.

[0514] In the present disclosure, when an article is added by translation like a, an, and the in English, for example, the present disclosure may also include a case where the noun following the article is in plural form.

[0515] In the present disclosure, "below", "less than", "above", "more than", "equal to", etc. may be rephrased with each other. Furthermore, in the present disclosure, terms meaning "good", "bad", "big", "small", "high", "low", "early", "late", "wide", "narrow", etc. are not limited to the original degree, comparative degree and superlative degree, but may be rephrased with each other. Furthermore, in the present disclosure, expressions with "ith" (i is an arbitrary integer) added to terms meaning "good", "bad", "big", "small", "high", "low", "early", "late", "wide", "narrow", etc. are not limited to the original degree, comparative degree and superlative degree, but may be rephrased with each other (for example, "highest" and "i-th highest" may be rephrased with each other).

[0516] In the present disclosure, “of,” “for,” “regarding,” “related to,” “associated with,” etc. may also be replaced by each other.

[0517] The invention involved in the present disclosure has been described in detail above, but it is obvious to those skilled in the art that the invention involved in the present disclosure is not limited to the embodiments described in the present disclosure. The invention involved in the present disclosure can be implemented as a modified and altered method without departing from the gist and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for the purpose of illustrative description and does not bring any restrictive meaning to the invention involved in the present disclosure.

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

Claims

1. A terminal having: a receiving unit, receiving a first downlink control channel used in triggering a random access process for a non-serving cell; and A control unit controls the reception of a second downlink control channel used in the reception of a response signal in the random access process based on at least one of a first QCL assumption using a first quasi-co-located QCL corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set.

2. The terminal according to claim 1, in, The control unit determines a QCL assumption to be used for the second downlink control channel based on a scenario in which the random access procedure is applied.

3. The terminal according to claim 1, in, The control unit determines which of the first QCL assumption and the second QCL assumption to apply in receiving the second downlink control channel based on at least one of a type of a cell corresponding to the first downlink control channel and a type of a cell corresponding to the second downlink control channel.

4. The terminal according to claim 1, in, The control unit determines which of the first QCL assumption and the second QCL assumption to apply in reception of the second downlink control channel based on at least one of a frequency corresponding to the non-serving cell and a frequency corresponding to the serving cell.

5. A wireless communication method of a terminal, comprising: The step of receiving a first downlink control channel used in triggering a random access procedure for a non-serving cell; and Based on at least one of a first QCL assumption utilizing a first quasi-co-located QCL corresponding to the first downlink control channel and a second QCL assumption utilizing a second QCL corresponding to a specific control resource set, a step of controlling the reception of a second downlink control channel utilized in the reception of a response signal in the random access process.

6. A base station, comprising: a sending unit, configured to send a first downlink control channel used in triggering a random access procedure for a non-serving cell; and A control unit controls the sending of a second downlink control channel used in the reception of a response signal in the random access process based on at least one of a first QCL assumption using a first quasi-co-located QCL corresponding to the first downlink control channel and a second QCL assumption using a second QCL corresponding to a specific control resource set.

Images