Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit for receiving a physical downlink control channel (PDCCH) order that includes identification information indicating one or more synchronization signal blocks among a plurality of synchronization signal blocks and triggers a random access procedure; and a control unit for controlling transmission of a physical random access channel (PRACH) in one or more occasions associated with the identification information.

Description

Terminal, wireless communication method, and base station 【0001】 This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems. 【0002】 In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified with the aim of achieving even higher data rates and lower latency (Non-Patent Literature 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP®) Release (Rel.) 8, 9). 【0003】 Successor systems to LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later) are also being considered. 【0004】 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 【0005】 In future wireless communication systems (e.g., NR, 6G, etc.), it is being considered that terminals (user terminals, User Equipment (UE)) will communicate using different unit areas (e.g., more transmit / receive points (TRPs) / access points (APs)) than existing cells. 【0006】However, detailed considerations regarding such communications have not been sufficient. If these considerations are insufficient, improvements in communication quality and throughput may be hindered. 【0007】 Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that perform appropriate communication using a unit area different from existing cells. 【0008】 A terminal according to one aspect of the present disclosure includes a receiving unit that receives a physical downlink control channel (PDCCH) order that triggers a random access procedure, which includes identification information that indicates one or more synchronization signal blocks from a plurality of synchronization signal blocks, and a control unit that controls the transmission of a physical random access channel (PRACH) on one or more occasions associated with the identification information. 【0009】 According to one aspect of this disclosure, appropriate communication can be performed using a different unit area than existing cells. 【0010】Figures 1A-1C show an example of a hypothetical cell-free configuration. Figure 2 shows an example of common RACH settings. Figures 3A and 3B show an example of the association between SSB and RO. Figure 4 shows an example of multiple SSBs detected by UE in a cell-free system based on Hypothesis 1. Figure 5 shows another example of multiple SSBs detected by UE in a cell-free system based on Hypothesis 1. Figures 6A and 6B show an example of the association between an SSB set and RO. Figure 7 shows an example of an SSB set. Figure 8 shows an example of the association between SSBs and SSB sets and RO. Figures 9A and 9B show an example of a RAR window. Figure 10 shows an example of an SSB set related to option 1 of embodiment B0. Figure 11 shows an example of multiple parallel RA procedures related to option 1 of embodiment B0. Figure 12 shows an example of an SSB set related to embodiment B1. Figure 13 shows an example of constraints related to embodiment B1. Figure 14 shows an example of option 1 of embodiment B2-1. Figure 15 shows an example of option 2 of embodiment B2-1. Figure 16 shows an example of option 3 of embodiment B2-1. Figure 17 shows another example of option 3 of embodiment B2-1. Figure 18 shows an example of multiple RAR windows according to embodiment B3. Figure 19 shows an example of one RAR window according to embodiment B3. Figure 20 shows an example of option 2 of embodiment B4. Figure 21 shows an example of an SSB index field in a PDCCH order according to embodiment C1. Figure 22 shows an example of an SSB set index field in a PDCCH order according to embodiment C1. Figure 23 is a diagram showing an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 24 is a diagram showing an example of a base station configuration according to one embodiment. Figure 25 is a diagram showing an example of a user terminal configuration according to one embodiment. Figure 26 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 27 is a diagram showing an example of a vehicle according to one embodiment. 【0011】 (Cell-free) Existing wireless communication systems (e.g., 5G NR) employ a cellular system in which, in principle, one antenna / TRP forms one cell. The area formed by such a cell is fixed / static. 【0012】 Also, in existing wireless communication systems (e.g., after Rel. 16), Distributed Multi Input Multi Output (Distributed MIMO, e.g., multi-TRP using multiple transmission and reception points (TRP)) that forms a communication area by the coverage of multiple antennas / TRP has been introduced. In Distributed MIMO, simultaneous communication using multiple antennas / TRP and communication using one antenna / TRP can be performed. 【0013】 By adopting Distributed MIMO, a more suitable line-of-sight environment can be prepared, and the performance improvement regarding MIMO can be achieved. 【0014】 In Co-located MIMO, one UE communicates with one antenna / TRP. 【0015】 On the other hand, in Distributed MIMO, one UE communicates with a plurality of coordinated antennas / TRP. 【0016】 In future wireless communication systems (e.g., after Rel. 20), the introduction of cell-free communication is being considered for further performance improvement and energy consumption efficiency through reduction of interference between multiple antennas / TRP, preparation of a line-of-sight environment corresponding to the use of high frequencies, improvement of the overall system frequency utilization efficiency, and application of equal and high-quality communication to each user. 【0017】Self-free may also be referred to as self-free massive MIMO (mMIMO), large-scale distributed MIMO (D-MIMO). Self-free uses the coherent cooperation of a large number of access points. Self-free may include at least one of ultra-dense deployment, scalable cooperation, user-centric clustering, supercarrier aggregation, and analog fronthaul. The user plane for self-free may perform scheduling that is more flexible than existing scheduling. The control plane for self-free may maintain some forms of cells to facilitate signaling. 【0018】 In self-free, different from the conventional cellular system, one area (which may also be called a cell / subcell, etc.) may be formed by multiple antennas / TRPs. That is, the area may mean a cell that does not depend on the position of the antenna. 【0019】 In self-free, the set of antennas / TRPs used for area formation may be changed according to the needs of the UE. For example, the set of antennas / TRPs may be changed based on, for example, the number of UEs / traffic volume / communication usage (such as initial access / data communication / measurement / reporting, etc.) rather than the coverage of the antennas / TRPs. 【0020】 In other words, in self-free, the coverage between multiple antennas / TRPs may overlap. 【0021】 In self-free, at each antenna / TRP, the direction of transmitting a synchronization signal (which may also be called, for example, a synchronization signal block (SSB), a synchronization signal / physical broadcast channel (SS / PBCH) block, etc.) may be controlled. 【0022】Furthermore, in a self-free system, the central unit (CU) and distributed unit (DU) may be virtualized for each antenna / TRP. Alternatively, each antenna / TRP may be managed by the CU alone. 【0023】 In existing cellular systems, each antenna / TRP forms a cell, and the UE communicates based on that cell. 【0024】 On the other hand, in a cell-free system, the installed antennas / TRPs do not form fixed / static cells in a cellular system. For example, in a cell-free system, one or more antennas / TRPs form areas depending on the conditions. Therefore, in a cell-free system, each antenna / TRP does not have to correspond to the same physical cell ID, and areas between multiple antennas / TRPs may overlap. 【0025】 Self-reliance may be achieved, for example, by adjusting a set of antennas / TRPs controlled by a central control unit (e.g., a CU). 【0026】 In a cell-free system, a first cell (which may be called a cell / supercell / macrocell / large cell, etc.) with a fixed physical range, similar to a cell in a 5G NR system, and a second cell (which may be called a subcell / area / microcell / cell / small cell / second cell within a first cell, etc.) whose physical range changes quasi-statically / dynamically based on conditions, may be formed. For example, the first cell may be called a supercell to distinguish it from the second cell. If a supercell consists of multiple second cells, the second cells may have the same definition / operation / coverage as existing cells in NR. For example, the second cells may be called subcells to distinguish them from the first cell. If a supercell or cell consists of multiple subcells, the subcells may have the same definition / operation / coverage as existing cells in NR. 【0027】The first cell may be a cell newly defined in a future wireless communication system, or a cell definition from an existing wireless communication system may be reused. 【0028】 The configurations of the first and second cells can be assumed to be as follows: Assumption 1: The first cell is composed of multiple TRPs, each having a single cell ID (physical cell ID (PCI)). Multiple TRPs can cooperate in sending and receiving data. Assumption 2: The first cell is composed of multiple TRPs (or subcells) with different cell IDs. Multiple TRPs / subcells can cooperate in sending and receiving data. 【0029】 Figure 1A shows an example of a cell-free configuration (Concept 1). In this example, each TRP included in the first cell (supercell / cell) has the same PCI (PCI #0). Multiple TRPs can communicate in cooperation with a single UE. 【0030】 Figure 1B shows an example of hypothetical configuration 2 for cell-free operation. In this example, each TRP in the first cell (supercell / cell) has a different PCI (PCI #0 to #9). Multiple TRPs can communicate in cooperation with a single UE. 【0031】 Figure 1C shows an example of a variation of hypothesis 2 of the cell-free configuration. In this example, a PCI is assigned to each TRP contained in the first cell (supercell / cell). Unlike hypothesis 2, in the variation of hypothesis 2, the same PCI may correspond to multiple TRPs. Multiple TRPs can communicate in cooperation with a single UE. Multiple TRPs associated with the same PCI may be contained within a single cell. 【0032】Transmitting / receiving with TRP / subcell coordination may be based on at least one of the following methods supported in NR: ◇ Single TRP / subcell transmission with dynamic TRP / subcell switching (single TRP transmission). ◇ Joint transmission using multiple TRP / subcells (multi-TRP joint transmission). The joint transmission may be based on single DCI or multi-DCI. The joint transmission may be non-coherent joint transmission (NCJT) or coherent joint transmission (CJT). 【0033】 Assuming an ideal backhaul and close coordination for self-free operation, CJT may be preferred over NCJT in a joint transmission scheme, and single DCI-based joint transmission may be preferred over multi-DCI-based joint transmission. 【0034】 (Inter-cell mobility) It is being considered that a UE may make UL transmissions to one or more cells / TRPs. In this case, the following Scenario 1 or Scenario 2 is possible. In this disclosure, a serving cell may be interpreted as a TRP within a serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as mutually exclusive. In this disclosure, a PCI different from the Physical Cell Identity (PCI) of the current serving cell may be simply referred to as a "different PCI". Non-serving cells, cells with different PCIs, and additional cells may be interpreted as mutually exclusive. 【0035】 <Scenario 1> Scenario 1 is, for example, a scenario that corresponds to inter-cell mobility in a multi-TRP, but it may also be a scenario that does not correspond to inter-cell mobility in a multi-TRP. 【0036】(1) The UE receives from the serving cell the SSB settings for beam measurement of the TRP corresponding to a PCI different from that of the serving cell, and the settings necessary to use wireless resources for data transmission and reception (including resources for the different PCI). (2) The UE performs beam measurement of the TRP corresponding to the different PCI and reports the beam measurement results to the serving cell. (3) Based on the above report, the Transmission Configuration Indication (TCI) status associated with the TRP corresponding to the different PCI is activated by L1 / L2 signaling from the serving cell. (4) The UE transmits and receives using a dedicated channel on the TRP corresponding to the different PCI. (5) The UE must always cover the serving cell, including in the case of multiple TRPs. The UE must use common channels from the serving cell (Broadcast Control Channel (BCCH), Paging Channel (PCH)), etc., as in conventional systems. 【0037】 In Scenario 1, when the UE sends and receives signals with the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the UE's assumption of the serving cell) remains unchanged. The UE sets higher-layer parameters related to the PCI of the non-serving cell from the serving cell. Scenario 1 may be applied, for example, in Rel. 17. 【0038】 In Rel. 17, we consider a scenario where a UE moves from a PCI#1 cell (serving cell) to a PCI#3 cell (additional cell) (overlapping with the serving cell). In this case, Rel. 17 does not support L1 / L2 switching of serving cells. 【0039】An additional cell is a cell that has an additional PCI that is different from the PCI of the serving cell. UEs can receive and transmit UE-dedicated channels (UE-dedicated CH) from additional cells. On the other hand, UEs need to be within the coverage of the serving cell in order to receive UE common channels (e.g., system information / paging / short messages). If a UE moves outside the coverage of the serving cell, a cell switchover (also called L3 mobility) is required (e.g., RRC reconfiguration). 【0040】 <Scenario 2> In Scenario 2, L1 / L2 inter-cell mobility (e.g., L1L2-triggered mobility (LTM)) is applied. With L1 / L2 inter-cell mobility, serving cell changes can be made using functions such as beam control without performing RRC reconfiguration. In other words, transmission and reception with candidate cells / additional cells are possible without handover. Since handover requires RRC reconnection and other factors, resulting in a period of no data communication, applying L1 / L2 inter-cell mobility that does not require handover allows data communication to continue even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel. 18. In Scenario 2, for example, the following procedure is performed. 【0041】(1) The UE receives configuration information (e.g., SSB settings) from the current serving cell regarding cells with different PCIs (additional cells / candidate cells / target serving cells) for beam measurement / serving cell changes. (2) The UE performs beam measurements on cells using different PCIs and reports the measurement results to the serving cell. (3) The UE may receive the configuration of cells with different PCIs (serving cell / candidate cell configurations) via upper-layer signaling (e.g., RRC). In other words, pre-configuration regarding serving cell changes may be performed. This configuration may be performed together with the configuration in (1) or separately. (4) Based on the above report, the TCI status of cells with different PCIs may be activated by L1 / L2 signaling in accordance with the serving cell change. The activation of the TCI status and the serving cell change may be performed separately. (5) The UE changes the serving cell (or assumed serving cell) and starts receiving / transmitting using the pre-configured individual UE channel and TCI state. 【0042】 In other words, in Scenario 2, the serving cell (the assumed serving cell in the UE) is updated by L1 / L2 signaling. Scenario 2 may also be applied in Rel. 18. 【0043】 In Rel. 18, serving cells are switched by L1 / L2 (e.g., DCI / MAC CE). Here, we show a case where L1 / L2 signaling switches from PCI#1, which corresponds to the current serving cell (e.g., Current serving cell), to PCI#3, which corresponds to the candidate cell (e.g., Target serving cell). 【0044】 The UE can receive and transmit common channels (e.g., system information / paging / short messages) and UE-only channels to and from the new serving cell (target serving cell #3). This allows the UE to be excluded from the coverage of the previous serving cell PCI #1. 【0045】(Initial Access Procedure) In the initial access procedure, the UE (RRC_IDLE mode) receives the SS / PBCH block (SSB), sends Msg1 (PRACH / Random Access Preamble / Preamble), receives Msg2 (PDCCH, PDSCH including Random Access Response (RAR)), sends Msg3 (PUSCH scheduled by the RAR UL grant), and receives Msg4 (PDCCH, PDSCH including UE contention resolution identity). Subsequently, when the UE sends an ACK for Msg4 by the base station (network), the RRC connection is established (RRC_CONNECTED mode). 【0046】 SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception. PSS detection involves detecting a portion of the physical cell ID (PCI), detecting (synchronizing) OFDM symbol timing, and (coarse) frequency synchronization. SSS detection includes detecting the physical cell ID. PBCH-DMRS detection includes detecting a portion of the SSB index within a half-radio frame (5ms). PBCH reception includes detecting the system frame number (SFN) and radio frame timing (SSB index), receiving configuration information for receiving remaining minimum system information (RMSI, SIB1), and determining whether a UE can camp in that cell (carrier). 【0047】 SSB has a bandwidth of 20 RB and a duration of 4 symbols. The transmission period for SSB can be set from {5, 10, 20, 40, 80, 160} ms. Within a half frame, multiple symbol positions for SSB are defined based on the frequency range (FR1, FR2). 【0048】 A PBCH has a 56-bit payload. N repetitions of the PBCH are transmitted within an 80ms period. N depends on the SSB transmission period. 【0049】System information consists of MIB (Monitoring Information Box) carried by PBCH, RMSI (SIB1), and other system information (OSI). SIB1 contains information for RACH configuration and RA procedures. The time / frequency resource relationship between the SSB and the PDCCH monitoring resource for SIB1 is set by PBCH. 【0050】 A base station using beam correspondence transmits multiple SSBs using multiple beams for each SSB transmission cycle. Each of the multiple SSBs has multiple SSB indices. When a UE detects one SSB, it transmits a PRACH in the PRACH occasion (RACH occasion, RO) associated with that SSB index and receives a RAR in the RAR window. 【0051】 (PRACH configuration) A ServingCellConfig can contain an UplinkConfig. An UplinkConfig can contain a list of UL BWP configurations (BWP-Uplink). A BWP-Uplink can contain a Common UL BWP configuration (BWP-UplinkCommon). A BWP-UplinkCommon can contain a Common RACH configuration (RACH-ConfigCommon). 【0052】 RACH-ConfigCommon is used to identify cell-specific random access parameters. As shown in Figure 2, RACH-ConfigCommon may include a general RACH configuration (RACH-ConfigGeneric), the total number of RA preambles (totalNumberOfRA-Preambles), the number of SSBs per PRACH occasion (RACH occasion, RO), and the number of contention-based (CB) preambles per SSB (ssb-perRACH-OccasionAndCB-PreamblesPerSSB). 【0053】RACH-ConfigCommon may also include a prach-RootSequenceIndex. prach-RootSequenceIndex indicates the prach root sequence index. Its range of values ​​depends on whether the root sequence length L=839, L=139, L=571, or L=1151. The root sequence length corresponding to the index shown in this IE matches the index shown in prach-ConfigurationIndex within RACH-ConfigDedicated, if such an index exists. If prach-RootSequenceIndex-r16 is advertised, the UE ignores prach-RootSequenceIndex (without the suffix). In FR2-2, the following values ​​are applicable depending on the subcarrier interval used: ◆120 kHz: L=139, L=571, and L=1151 ◆480 kHz: L=139, and L=571 ◆960 kHz: L=139 【0054】 RACH-ConfigGeneric is typically used to identify random access parameters for both random access and beam fault recovery. RACH-ConfigGeneric may include a RACH configuration index (prach-ConfigurationIndex) and message1-FDM counts (msg1-FDM, the number of ROs FDMed within a single time instance). 【0055】 ssb-perRACH-OccasionAndCB-PreamblesPerSSB may include the number of SSBs per RO N (for example, N = 1 / 8, oneEighth, where one SSB is associated with eight ROs) and the number of CB preambles per SSB R. 【0056】A CellGroupConfig can contain a SpCellConfig. A SpCellConfig can contain a ReconfigurationWithSync (e.g., a handover configuration). A ReconfigurationWithSync can contain a RACH-ConfigDedicated (dedicated) configuration. 【0057】 (PDCCH Order) DCI format 1_0 includes a DCI format identifier field, a bit field that is always set to 1, and a frequency domain resource assignment field. When the cyclic redundancy check (CRC) of DCI format 1_0 is scrambled by cell(C)-RNTI and all frequency domain resource assignment fields are 1, then that DCI format 1_0 is for random access procedures initiated by the PDCCH order, and the remaining fields are the random access preamble, UL / supplementary Uplink (SUL) indicator, SS / PBCH index (SSB index), PRACH mask index, and reserved bits (12 bits). 【0058】 For a PRACH transmission triggered by a PDCCH order, the PRACH mask index field indicates the PRACH occasion (RACH occasion, RO) of the PRACH transmission associated with the SS / PBCH block index indicated by the SS / PBCH block index field of the PDCCH order, provided the value of the random access preamble index field is non-zero. 【0059】(Random Access Preamble) For a Type 1 random access procedure (a 4-step RA type, an RA procedure using messages 1 / 2 / 3 / 4), the UE may apply the number of SS / PBCH blocks N associated with a single PRACH occasion (RACH occasion, RO) and the number of CB preambles R per valid PRACH occasion and per SS / PBCH block by ssb-perRACH-OccasionAndCB-PreamblesPerSSB. 【0060】 In a Type 2 random access procedure (a two-step RA type, an RA procedure using messages A / B) with a common PRACH occasion setting with a Type 1 random access procedure, the UE is provided with the number N of SS / PBCH block indices associated with a single PRACH occasion by ssb-perRACH-OccasionAndCB-PreamblesPerSSB, and the number Q of contention-based preambles per SS / PBCH block indices per valid PRACH occasion by msgA-CB-PreamblesPerSSB-PerSharedRO. A PRACH transmission may occur on a subset of PRACH occasions associated with the same SS / PBCH block indices within an SSB-RO mapping cycle, provided the UE is provided with a PRACH mask index by msgA-SSB-SharedRO-MaskIndex. 【0061】In a Type 2 random access procedure involving the setting of a PRACH occasion separate from a Type 1 random access procedure, the UE is provided with the number N of SS / PBCH block indexes associated with one PRACH occasion, and if msgA-CB-PreamblesPerSSB-PerSharedRO is provided, thereby the number R of CB preambles per valid PRACH occasion and per SS / PBCH block index; otherwise, ssb-perRACH-OccasionAndCB-PreamblesPerSSB provides the number R of contention-based preambles per valid PRACH occasion and per SS / PBCH block index. 【0062】 In the random access procedure associated with the feature combinations shown by FeatureCombinationPreambles, the UE is provided with the number of SS / PBCH block indices associated with a single PRACH occasion, if ssb-perRACH-OccasionAndCB-PreamblesPerSSB or msgA-ssb-perRACH-OccasionAndCB-PreamblesPerSSB is provided, by which the UE is provided with the number of SS / PBCH block indices associated with a single PRACH occasion, and the number of CB preambles per SS / PBCH block indices per valid PRACH occasion is provided by startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition. A PRACH transmission may occur on a subset of PRACH occasions associated with the same SS / PBCH block indices within an SSB-RO mapping cycle, for a UE provided with a PRACH mask index by ssb-SharedRO-MaskIndex. 【0063】For a Type 1 random access procedure or a Type 2 random access procedure with a PRACH occasion setting independent of the Type 1 random access procedure, if N < 1, one SS / PBCH block is mapped to 1 / N consecutive valid PRACH occasions, and R CB preambles with consecutive indexes associated with the SS / PBCH block index for each valid PRACH occasion start from preamble index 0. If N >= 1, R CB preambles with consecutive indexes associated with the SS / PBCH block index n (0 <= n <= N - 1) for each valid PRACH occasion start from preamble index n·N preamble total / N. Here, N preamble total is given by totalNumberOfRA-Preambles for a Type 1 random access procedure and by msgA-TotalNumberOfRA-Preambles for a Type 2 random access procedure with a PRACH occasion setting independent of the Type 1 random access procedure. N preamble total is a multiple of N. 【0064】 Starting from frame 0, the association period for mapping the SS / PBCH block to the PRACH occasion is the minimum value within a set determined by the PRACH configuration period according to the relationship (the relationship specified in the specification) between the PRACH configuration period and the association period (the number of PRACH configuration periods) such that at least once within that association period, the value of the ssb-PositionsInBurst within the burst in the SSB position in SIB1 or in the ServingCellConfigCommon is N Tx SSB such that at least one SS / PBCH block index is mapped to the PRACH occasion. Here, the UE obtains N from the value of ssb-PositionsInBurst within the burst in SIB1 or in ServingCellConfigCommon Tx SSBIf, after an integer number of mapping cycles from SS / PBCH block index to PRACH occasion within the relevant period, N Tx SSB If there is a set of PRACH occasions or PRACH preambles that do not map to any SS / PBCH block index, then no SS / PBCH block index maps to that set of PRACH occasions or PRACH preambles. An association pattern period is determined to include one or more association periods such that the pattern between a PRACH occasion and an SS / PBCH block index repeats at most every 160 ms. If, after an integer number of association periods, there is a PRACH occasion that is not associated with an SS / PBCH block index, then that PRACH occasion is not used for PRACH. 【0065】 For PRACH transmissions triggered by higher layers (PRACH transmissions not triggered by PDCCH orders), if an ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex. This ra-ssb-OccasionMaskIndex indicates the PRACH occasion for the PRACH transmission associated with the selected SS / PBCH block index. 【0066】 PRACH occasions are mapped sequentially for each corresponding SS / PBCH block index. The indexing of PRACH occasions, indicated by the mask index value, is reset after each consecutive mapping cycle of PRACH occasions for each SS / PBCH block index. In the first available mapping cycle, the UE selects the PRACH occasion indicated by the PRACH mask index value for the specified SS / PBCH block index for PRACH transmission. 【0067】For a given preamble index, the order of PRACH occasions is as follows: • Firstly, in increasing order of frequency resource index for frequency-multiplexed PRACH occasions (within the same time resource index). • Secondly, in increasing order of time resource index for time-multiplexed PRACH occasions within a PRACH slot. • Thirdly, in ascending order of PRACH slot index. 【0068】 For PRACH transmissions triggered by requests from higher layers, if csirs-ResourceList is provided, the value of ra-OccasionList indicates a list of PRACH occasions for the PRACH transmission, and the PRACH occasions are associated with the CSI-RS index indicated and selected by csi-RS. The indexing of PRACH occasions indicated by ra-OccasionList is reset for each associated pattern period. 【0069】 For PRACH setting periods of 10, 20, 40, 80, and 160 [msec], the associated periods are {1, 2, 4, 8, 16}, {1, 2, 4, 8}, {1, 2, 4}, {1, 2}, and {1}, respectively. 【0070】 The value of the PRACH mask index (msgA-SSB-SharedRO-MaskIndex) is associated with the allowed PRACH occasions for SSB (the value of the PRACH occasion index). 【0071】Figure 3A shows an example of the association between PRACH occasions (RACH occasions, ROs) and beams (SSB / CSI-RS) based on the upper layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB (Mapping 1). When ssb-perRACH-OccasionAndCB-PreamblesPerSSB is [oneHalf,n16] (number of SSBs per RO N=1 / 2, number of preambles per SSB R=16) and msg1-FDM is 4, four ROs are FDM'd in one time instance, one SSB is mapped to two ROs (two ROs are associated with one SSB), and one SSB is associated with 16 preambles. Preamble indices 0 to 15 are associated with SSB0. Thus, when N < 1, one SSB is mapped to multiple ROs. This increases the RO capacity for each beam. 【0072】 Figure 3B shows another example of RO-beam association (mapping 2) based on the upper layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. ssb-perRACH-OccasionAndCB-PreamblesPerSSB is [four,n16] (N=4, R=16), and msg1-FDM is 4, N preamble totalIf the number of preambles is 64, then in one time instance, four ROs are FDM'd, four SSBs are mapped to one RO (one RO is associated with four SSBs), one SSB is associated with 16 preambles, and one RO is associated with 64 preambles. One RO is associated with SSBs #0 through #3. SSB #0 is associated with preamble indices #0 through #15, SSB #1 is associated with preamble indices #16 through #31, SSB #2 is associated with preamble indices #32 through #47, and SSB #3 is associated with preamble indices #48 through #63. In this way, the same RO is associated with different SS / PBCH block indices, and different preambles use different SS / PBCH block indices. The base station can distinguish the associated SS / PBCH block indices by the received PRACH. 【0073】 The random access preamble can only be transmitted over time resources specified in the random access configuration of the specification, and depends on whether it is FR1 or FR2, and the spectrum type (paired spectrum / supplementary uplink (SUL) / unpaired spectrum). The PRACH configuration index is given by the upper layer parameter prach-ConfigurationIndex, or by msgA-PRACH-ConfigurationIndex, if set. In the specification, each value of the PRACH configuration index is associated with at least one of the following: preamble format, n_f (frame number) mod x = y, x and y, subframe number, start symbol, number of PRACH slots in the subframe, number of time domain PRACH occasions N_t^RA,slot in the PRACH slot, and PRACH duration N_dur^RA. 【0074】Whether a PRACH iteration can be applied to a scenario depends on the type of RA procedure triggered by different purposes. The type of RA procedure may be at least one of the following: • Contention-free random access (CFRA), PDCCH ordered RA (RA initiated by a PDCCH order), CFRA for beam failure recovery (BFR), CFRA for system information (SI) requests, CFRA for reconfiguration with sync, etc. • Contention-based random access (CBRA), RA triggered by a MAC entity, RA triggered by an RRC with an event, CBRA for BFR, etc. • 4-step RACH. • 2-step RACH. 【0075】 In this disclosure, the mapping cycle, the SSB-RO mapping cycle, and the mapping cycle from the SS / PBCH block index to the PRACH occasion may be interpreted as mutually exclusive. 【0076】 (SSB / CSI-RS selection: MAC protocol specification / Random Access Resource selection) When the RA type (RA_TYPE) is set to 4-step RA, the MAC entity performs the following actions: 【0077】- If an RA procedure is initiated for SpCell beam fault recovery, and the beamFailureRecoveryTimer is running or not set, and a CFRA resource for a beam fault recovery request associated with at least one SSB / CSI-RS is explicitly provided by the RRC, and at least one of the multiple SSBs in the candidateBeamRSList with an SS-RSRP exceeding the rsrp-ThresholdSSB threshold, and one or more CSI-RSs in the candidateBeamRSList with a CSI-RSRP exceeding the rsrp-ThresholdCSI-RS threshold, then the MAC entity performs the following actions: -- The MAC entity selects one SSB from among the multiple SSBs in candidateBeamRSList that has an SS-RSRP exceeding rsrp-ThresholdSSB, or one CSI-RS from among the multiple CSI-RSs in candidateBeamRSList that has a CSI-RSRP exceeding rsrp-ThresholdCSI-RS. -- If a CSI-RS is selected and there is an RA preamble index (ra-PreambleIndex) associated with the selected CSI-RS, the MAC entity sets the preamble index (PREAMBLE_INDEX) to the ra-PreambleIndex in candidateBeamRSList that corresponds to the SSB that is quasi-colocated with the selected CSI-RS. -- Otherwise, set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the SSB or CSI-RS selected from the set of RA preambles for beam fault recovery requests. 【0078】- If not, and ra-PreambleIndex is explicitly provided by PDCCH and that ra-PreambleIndex is not 0b000000, the MAC entity sets PREAMBLE_INDEX to the notified ra-PreambleIndex and selects the SSB notified by PDCCH. 【0079】 - If not, and a CFRA resource associated with multiple SSBs is explicitly provided within a separate RACH configuration (rach-ConfigDedicated), and at least one SSB with an SS-RSRP exceeding rsrp-ThresholdSSB is available, the MAC entity selects one of its associated SSBs with an SS-RSRP exceeding rsrp-ThresholdSSB and sets PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB. 【0080】 - If not, and a CFRA resource associated with multiple CSI-RSs is explicitly provided within a separate RACH setting (rach-ConfigDedicated), and at least one of the multiple CSI-RSs with a CSI-RSRP exceeding rsrp-ThresholdCSI-RS is available, the MAC entity selects one of its associated multiple CSI-RSs with a CSI-RSRP exceeding rsrp-ThresholdCSI-RS and sets PREAMBLE_INDEX to ra-PreambleIndex corresponding to the selected CSI-RS. 【0081】- If not, and the RA procedure is initiated for an SI request and the RA resources for the SI request are explicitly provided by the RRC, the MAC entity performs the following actions: -- If at least one SSB with an SS-RSRP greater than rsrp-ThresholdSSB is available, the MAC entity selects one SSB with an SS-RSRP greater than rsrp-ThresholdSSB. -- Otherwise, the MAC entity selects any SSB. -- The MAC entity selects the RA preamble corresponding to the selected SSB from the RA preambles, which are checked according to the RA preamble start index (ra-PreambleStartIndex), and sets PREAMBLE_INDEX to the selected RA preamble. 【0082】 - If not (CBRA preamble selection), the MAC entity performs the following actions: -- If at least one SSB with an SS-RSRP exceeding the rsrp-ThresholdSSB is available, the MAC entity selects one SSB with an SS-RSRP exceeding the rsrp-ThresholdSSB. -- Otherwise, the MAC entity selects any SSB. 【0083】- If an RA procedure is initiated for an SI request and ra-AssociationPeriodIndex and si-RequestPeriod are set, the MAC entity determines the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB within the association period given by ra-AssociationPeriodIndex within the si-RequestPeriod, which is permitted by the constraints given by ra-ssb-OccasionMaskIndex (if it is set) (the MAC entity randomly selects a PRACH occasion with equal probability from consecutive PRACH occasions corresponding to the selected SSB). 【0084】- If the above SSB is selected, the MAC entity performs the following steps: -- If a set of RA resources associated with Msg1 repetitions has been selected for this RA procedure, the MAC entity determines the next available set of PRACH occasions for the number of Msg1 repetitions applied to this RA procedure corresponding to the selected SSB, as permitted by the constraints given by ra-ssb-OccasionMaskIndex (if set) or ssb-SharedRO-MaskIndex (if set) (the MAC entity randomly selects PRACH occasions with equal probability from consecutive PRACH occasions, regardless of the FR2 UL gap, corresponding to the selected SSB and the number of Msg1 repetitions for this RA procedure; the MAC entity may consider the possibility of measurement gaps and MUSIM gaps occurring when determining the next available set of PRACH occasions corresponding to the selected SSB). -- Otherwise, the MAC entity determines the next available PRACH occasion from the PRACH occasions corresponding to the selected SSB, as permitted by the constraints given by ra-ssb-OccasionMaskIndex (if set) or ssb-SharedRO-MaskIndex (if set) (the MAC entity randomly selects a PRACH occasion from consecutive PRACH occasions with equal probability, following the procedure corresponding to the selected SSB, regardless of the FR2 UL gap; the MAC entity may consider the possibility of measurement gaps and MUSIM gaps occurring when determining the next available PRACH occasion corresponding to the selected SSB). 【0085】- If the above CSI-RS is selected, the MAC entity performs the following steps: -- If there is no CFRA resource associated with the selected CSI-RS, the MAC entity determines the next available PRACH occasion from the PRACH occasions as permitted by the constraints given by ra-ssb-OccasionMaskIndex (if it is set) (the MAC entity randomly selects a PRACH occasion with equal probability from consecutive PRACH occasions, regardless of the FR2 UL gap, corresponding to the selected CSI-RS and the SSB being QCLed; the MAC entity may consider the possibility of measurement gaps and MUSIM gaps occurring when determining the next available PRACH occasion corresponding to the selected CSI-RS and the SSB being QCLed). -- If not, the MAC entity determines the next available PRACH occasion from the PRACH occasions in ra-OccasionList corresponding to the selected CSI-RS (the MAC entity randomly selects a PRACH occasion with equal probability from among PRACH occasions occurring simultaneously on different subcarriers, regardless of the FR2 UL gap, corresponding to the selected CSI-RS; the MAC entity may consider the possibility of measurement gaps and MUSIM gaps occurring when determining the next available PRACH occasion corresponding to the selected CSI-RS). 【0086】 In other words, in the Msg1 iteration, the MAC entity determines the set of permitted PRACH occasions by the mask index value. 【0087】(PRACH transmit power control: Physical layer procedures for control / Uplink power control / Physical random access channel) The actual PRACH transmit power is determined based on the target preamble reception power, RS path loss, and maximum output power limit. 【0088】 Based on the DL RS for serving cell c within transmission occasion i, the UE determines the (actual) transmit power P of the carrier f of serving cell c on the active UL BWP b. PRACH,b,f,c (i) is determined as follows: P PRACH,b,f,c (i) = min{P CMAX,f,c (i), P PRACH,target,f,c +PL b,f,c} [dBm] 【0089】 P CMAX,f,c (i) is the maximum output power set to UE for the carrier f of serving cell c within transmission occasion i. PRACH,target,f,c This is the PRACH target received power PREAMBLE_RECEIVED_TARGET_POWER provided by the upper layer to the active UL BWP b of the carrier f of serving cell c. b,f,c This is the path loss of carrier f to active UL BWP b based on DL RS associated with PRACH transmission on serving cell c, and is calculated by UE as (reference signal power (ss-PBCH-BlockPower) [dBm] - upper layer filtered RSRP [dBm]) [dB]. If the active DL BWP is the initial DL BWP and is for multiplex pattern 2 or 3 of SS / PBCH block and CORESET, then UE is based on the SS / PBCH block associated with PRACH transmission, and is calculated by PL b,f,c To decide. 【0090】The DL RS used in path loss calculation may also be called pathloss(PL)-RS, path loss reference RS, etc. 【0091】 In an existing RACH process (procedure), if the UE sends a PRACH and does not receive a network RAR or contention / conflict resolution Msg4 within a specific time window, and the random access process does not complete, the UE resends the PRACH after a random backoff period. 【0092】 (Target preamble received power: MAC protocol specification / MAC procedures / Random Access procedure) The UE calculates the transmit power based on the target preamble received power set from the network and the value of the preamble power ramping counter (power lifting / ramping mechanism). 【0093】 `preambleReceivedTargetPower` is the initial random access preamble power for a 4-step RA type. `DELTA_PREAMBLE` relates to the preamble format. `PREAMBLE_POWER_RAMPING_COUNTER` is the number of times the power increases. `PREAMBLE_POWER_RAMPING_STEP` is the step size of the power lifting / ramping. 【0094】For each RA preamble, the MAC entity performs the following actions: - If the selected SSB or CSI-RS has not changed from the selection in the side RA preamble transmission, - Increment PREAMBLE_POWER_RAMPING_COUNTER by 1, - Select the value of DELTA_PREAMBLE, - Set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER-1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA. 【0095】 When a valid downlink assignment for RA-RNTI is received on the PDCCH, the received TB is successfully decoded, the RAR is considered successfully received, and the RAR does not contain a MAC subPDU with only RAPID, the MAC entity applies the following actions to the serving cell from which the RAR preamble was sent: - Process the received timing advance command; - Instruct the lower layer to use preambleReceivedTargetPower and the amount of power ramping applied to the last RA preamble transmission (i.e., PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP); - Ignore the received UL grant if an RA procedure for SCell is performed on an uplink carrier where push-Config is not set. 【0096】 As described above, if the selected SSB / CSI-RS has not changed from the last SSB / CSI-RS selection, the UE increments the power ramping counter (PREAMBLE_POWER_RAMPING_COUNTER). 【0097】PREAMBLE_POWER_RAMPING_STEP is set by the power ramping step {0dB, 2dB, 4dB, 6dB} in RRC IE RACH-ConfigGeneric. 【0098】 (Maximum number of preamble transmissions: MAC protocol specification / MAC procedures / Random Access procedure) preambleTransMax is the maximum number of random access preamble transmissions. 【0099】 If a listen before talk (LBT) failure is received from a lower layer for a random access preamble transmission and lbt-FailureRecoveryConfig is not set, the MAC entity performs the following actions: - The MAC entity increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by 1. - If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1: -- If the random access preamble is transmitted on SpCell, the MAC entity reports the RA problem to the higher layer, and if the RA procedure is triggered for an SI request, the MAC entity considers the RA procedure to have failed to complete. -- If the random access preamble is transmitted on SCell, the MAC entity considers the RA procedure to have failed to complete. -- If the RA procedure has not completed, the MAC entity performs the RA resource selection procedure. 【0100】If the ra-ResponseWindow set in BeamFailureRecoveryConfig expires and no PDCCH transmission on the search space indicated by recoverySearchSpaceId addressed to C-RNTI is received on the serving cell from which the preamble was sent, or if the ra-ResponseWindow set in RACH-ConfigCommon expires and no RAR containing a random access preamble identifier matching the sent PREAMBLE_INDEX is received, the MAC entity performs the following actions: - The MAC entity considers the RAR reception to be a failure, - Increments PREAMBLE_TRANSMISSION_COUNTER by 1, - If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1: If a random access preamble is transmitted on SpCell, the MAC entity will report a RA problem to the higher layer, and if the RA procedure is triggered for an SI request, the MAC entity will consider the completion of the RA procedure to be a failure. -- If a random access preamble is transmitted on SCell, the MAC entity will consider the completion of the RA procedure to be a failure. 【0101】 If contention resolution is deemed to have failed, the MAC entity flushes (clears) the HARQ buffer used to send the MAC PDU in the Msg3 buffer, increments PREAMBLE_TRANSMISSION_COUNTER by 1, reports the RA problem to the higher layer, and if the RA procedure was triggered for an SI request, the MAC entity considers the completion of that RA procedure to have failed. 【0102】(RAR Monitoring) In response to a PRACH transmission, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within a window (RAR window) controlled by the upper layer. The window begins at the first symbol of the earliest CORESET in which the UE is configured to receive a PDCCH for a type 1-PDCCH CSS set, i.e., at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission. The symbol duration corresponds to the SCS for a type 1-PDCCH CSS set. The length of the window is provided as a number of slots by the RAR window length (ra-responseWindow), based on the SCS for a type 1-PDCCH CSS set. 【0103】 If the UE detects its DCI format 1_0, which includes a CRC scrambled by the corresponding RA-RNTI and the same LSBs in the SFN field within the DCI format as the least significant bits (LSBs) of the system frame number (SFN) from which the UE transmitted the PRACH, and the UE receives the transport block in the corresponding PDSCH, the UE may assume the same DMRS antenna port QCL properties with respect to the SS / PBCH block or CSI-RS resource that the UE uses to associate the PRACH, regardless of whether the UE is provided with a TCI-State for the CORESET to receive the PDCCH with the DCI format 1_0. 【0104】If a UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for a SpCell, the UE may assume that the PDCCH containing the DCI format 1_0 and the PDCCH order have the same DMRS antenna port QCL properties. If a UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for a secondary cell, the UE may assume that the DMRS antenna port QCL properties of the CORESET associated with the type 1-PDCCH CSS set for receiving the PDCCH containing the DCI format 1_0 are the same. 【0105】 A RAR UL grant may include at least one of the following: a frequency hopping flag field, a PUSCH frequency resource allocation field, a PUSCH time resource allocation field, a modulation and coding scheme (MCS) field, a TPC command field for PUSCH, a CSI request field, and a channel access-cyclic prefix extension (CPext) field. 【0106】In single-cell operation or operation with carrier aggregation within the same frequency band, if the qcl-Type set in the 'typeD' properties of the DMRS for monitoring a PDCCH in the Type 1-PDCCH CSS set is not set to the same as the qcl-Type set in the 'typeD' properties of the DMRS for monitoring a PDCCH in the Type 0 / 0A / 0B / 2 / 3-PDCCH CSS set or the USS set, and the PDCCH or associated PDSCH overlaps with the PDCCH or associated PDSCH monitored by the UE in the Type 1-PDCCH CSS set by at least one symbol, the UE does not assume to monitor the PDCCH in the Type 0 / 0A / 0B / 2 / 3-PDCCH CSS set or the USS set. 【0107】 If UE is provided with one or more search space sets by PDCCH-Config, which correspond to one or more of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, peiSearchSpace, ra-SearchSpace, and CSS sets, and is provided with SI-RNTI, P-RNTI, PEI-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, then for any of these RNTIs, UE does not assume that it will process information from more than one DCI format with scrambled CRC using that RNTI per slot. 【0108】 (Msg3 PUSCH) The UE sends a transport block in PUSCH, which is scheduled by the RAR UL grant in the corresponding RAR message. The UE is in slot n+k2+Δ+2 μ ・K cell,offset Within the system, it transmits the PUSCH command. cell,offsetThe value inside is provided by CellSpecific_Koffset, and if not provided, K cell,offset = 0 【0109】 k2 is a slot offset, determined based on the row index m+1 of the allocation table provided by the PUSCH time resource allocation field value m of the RAR UL grant, and the PUSCH subcarrier interval μPUSCH. Δ is an additional subcarrier interval specific slot delay time value for the first transmission of PUSCH scheduled by RAR, specific to the PUSCH subcarrier interval μPUSCH, and applied in addition to K2. 【0110】 Within the SIB1 transmitted by the base station, the following is notified: • The priority of each feature (priority, featurePriorities-r17). This priority is used to determine which FeatureCombinationPreamble the UE uses when a feature is mapped to more than one FeatureCombinationPreamble. • Additional RO settings. These settings include available features (which may be associated with multiple features), RA resources (e.g., preamble index), and a mask index to distinguish ROs. 【0111】 The UE determines which RO to use depending on its function. 【0112】 SIB1 contains ServingCellConfigCommonSIB. It contains UplinkConfigCommonSIB. It contains BWP-UplinkCommon (UL BWP common settings). 【0113】BWP-UplinkCommon may include RACH common settings (RACH-ConfigCommon or MsgA-ConfigCommon) and additionalRACH-ConfigList-r17 (additional RACH configuration list). additionalRACH-ConfigList-r17 may also include rsrp-ThresholdMsg3-r17 (threshold). 【0114】 RACH common settings may include FeatureCombinationPreambles. FeatureCombinationPreambles associate one set of preambles (partitions) with one feature combination. FeatureCombinationPreambles may include FeatureCombination (feature combination settings), startPreambleForThisPartition (index of the first preamble), numberOfPreamblesPerSSB-ForThisPartition (number of preambles), and ssb-SharedRO-MaskIndex-r17 (PRACH mask index). FeatureCombination includes at least one of redCap (RedCap), smallData (SDT), sliceGroup (RAN slicing), and msg3-Repetition (Msg3 repetition). Partitions are given by the index of the first preamble and the number of preambles. 【0115】 The available ROs are explicitly set by the PRACH mask index. Using the relationship between the PRACH mask index and the PRACH occasions permitted by the SSB (MAC protocol specification / table of PRACH mask index values), at least one of the PRACH occasion indices 1 to 8 can be set. 【0116】(Contention Resolution) When Msg3 is transmitted, the MAC entity follows the following actions 1 through 4: [Action 1] If Msg3 is transmitted over a non-terrestrial network, the MAC entity starts the ra-ContentionResolutionTimer and restarts it in each HARQ retransmission in the first symbol after the end of Msg3 plus the UE estimation of UE-gNB RTT. [Action 2] Otherwise, if the transmission of Msg3 (initial transmission or HARQ retransmission) is scheduled with a type A PUSCH repetition, the MAC entity starts or restarts the ra-ContentionResolutionTimer in the first symbol after the end of all repetitions of the Msg3 transmission. [Action 3] Otherwise, the MAC entity starts or restarts the ra-ContentionResolutionTimer in the first symbol after the end of the Msg3 transmission. [Action 4] The MAC entity monitors the PDCCH regardless of the possibility of a measurement gap occurring while the ra-ContentionResolutionTimer is running. 【0117】 Step 4 (Msg4) in the RA procedure of Rel. 16 NR follows the following Step 4 operation. 【0118】[Step 4 Operation] If the UE is not provided with C-RNTI, in response to a PUSCH transmission scheduled by the RAR UL grant, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding TCI-RNTI, by scheduling a PDSCH containing the UE contention resolution identity. In response to the reception of the PDSCH containing the UE contention resolution identity, the UE transmits HARQ-ACK information within the PUCCH. The PUCCH transmission is within the same active UL BWP as the PUSCH transmission. The minimum time between the last symbol of the PDSCH reception and the first symbol of the corresponding PUCCH transmission containing HARQ-ACK information is equal to N_T,1 [msec]. N_T,1 is the duration of the N_T,1 symbol, which corresponds to the PDSCH processing time of UE processing capability 1 when additional PDSCH DM-RS is configured. For μ=0, the UE assumes N_T,1=14. 【0119】 When a DCI format is detected in response to a PUSCH transmission scheduled by a RAR UL grant, or in response to a corresponding PUSCH retransmission scheduled by DCI format 0_0 with a CRC scrambled by TC-RNTI provided in the corresponding RAR message, the UE may assume that the PDCCH carrying the DCI format has the same DM-RS antenna port quasi co-location (QCL) properties as the SS / PBCH block used by the UE for PRACH association. 【0120】(PRACH Coverage Extension) PRACH coverage extensions are being considered. For example, multiple PRACH transmissions using the same beam in a 4-step RA procedure (multiple PRACH repetitions) and multiple PRACH transmissions using different beams in a 4-step RA procedure are being considered. This PRACH extension may target frequency range (FR) 2 or be applied to FR 1. This PRACH extension may be applied to short PRACH formats or to other formats. 【0121】 For multiple PRACH transmissions involving the same beam, one RAR window may be used for each PRACH transmission. This RAR window may follow an existing design. Alternatively, for multiple PRACH transmissions involving the same beam, only one RAR window may be used for all of the multiple PRACH transmissions. 【0122】 A UE may use different multiple transmit (Tx) beams to transmit multiple PRACHs across multiple ROs associated with the same SSB / CSI-RS. 【0123】 (Sub-band non-overlapping full duplex (SBFD)) In LTE up to Rel. 14, frequency division duplex (FDD) was the main method used in practical applications, and time division duplex (TDD) was also supported. 【0124】 On the other hand, in the NR from Rel. 15 onwards, TDD was the main focus of consideration, while FDD was also supported at the same time (for example, migration of the LTE band). 【0125】 In an FDD, DL reception and UL transmission can be performed simultaneously, which is preferable from the viewpoint of reducing latency. On the other hand, in an FDD, the resource ratio of DL to UL is fixed (for example, 1:1). 【0126】In TDD, it is possible to change the ratio of DL and UL resources. For example, in a typical environment where DL traffic is relatively high, it is possible to increase the amount of DL resources to improve DL throughput. 【0127】 On the other hand, considering the transmission and reception time ratio using TDD up to Rel. 16, there are cases where the opportunities to transmit UL signals / channels are fewer than the opportunities to receive DL signals / channels. In such cases, the UE may not be able to transmit UL signals / channels frequently, raising concerns about delays in the transmission of important UL signals / channels. Furthermore, because the opportunities to transmit UL signals are fewer than the opportunities to receive DL signals, signal / channel congestion during UL transmission is also a concern. In addition, since the time resources available for transmitting UL signals / channels are limited in TDD, the application of UL coverage extension techniques, such as repeated transmission (which may also be called repetition), becomes limited. 【0128】 In future wireless communication systems (e.g., Rel. 18 and later), the introduction of a division duplex method combining TDD and Frequency Division Duplex (FDD) for UL and DL is being considered. 【0129】 This split-duplex method may also be called sub-band non-overlapping full duplex (SBFD). 【0130】 SBFD may also mean a duplexing method that frequency-division multiplexes DL and UL (allowing DL and UL to be used simultaneously) within a single component carrier (CC) / band of the TDD band, or within multiple CCs (in the same band). 【0131】 When the duplexing method is applied to multiple CCs, it may mean that in the time resources where DL is available in one CC, UL is available in another CC. 【0132】In the existing specifications, the UE is configured with TDD slots / symbols using the bandwidth of one component carrier (CC) (which may also be called a cell or serving cell). 【0133】 The existing TDD slot / symbol settings may not allow for sufficient UL time resources, potentially leading to UL transmission delays and reduced coverage performance. 【0134】 In SBFD, for example, within a single component carrier (CC), the resources used for receiving DL and the resources used for transmitting UL may overlap in time. Such a resource configuration allows for the allocation of UL resources and improves the efficiency of resource utilization. 【0135】 For example, in a 1CC frequency domain, by configuring both ends as DLs and sandwiching the UL resource between the DLs (FDM), it is possible to avoid and mitigate cross-link interference (CLI) with neighboring carriers. In addition, a guard region may be set at the boundary between the DL resource and the UL resource. 【0136】 Considering the complexity of handling self-interference, it is conceivable that only base stations use DL and UL resources simultaneously. In other words, for resources where DL and UL overlap in time, one UE may use the DL resource while another UE uses the UL resource. 【0137】 In SBFD, for example, a portion of the DL resources in the TDD band may be used as UL resources, and DL and UL may overlap in time to some extent. In this case, during periods when only DL is available, each of the multiple UEs may receive the DL channel / signal. 【0138】 Furthermore, during periods when DL and UL overlap in time, one UE receives the DL channel / signal, while another UE transmits the UL channel / signal. During this period, the base station performs simultaneous transmission and reception of DL and UL. 【0139】Furthermore, during UL-only periods, each of the multiple UEs transmits a UL channel / signal. 【0140】 In existing NRs, DL frequency resources and UL frequency resources in a UE carrier are configured as DL Bandwidth Part (BWP) and UL BWP, respectively. Switching between DL / UL frequency resources requires the configuration of multiple BWPs and a BWP adaptation mechanism. 【0141】 Furthermore, in existing NRs, the time resources in the TDD carrier for UE are configured in the TDD settings as at least one of DL, UL, and Flexible (FL). 【0142】 Methods for configuring time-domain and frequency-domain resources when SBFD is used are being considered. For example, for a given UE, the impact on the specification / UE can be minimized by configuring resources for periods in the time domain where DL and UL overlap in the same way as existing DL resources (for example, by avoiding the use of the UL resource portion using frequency domain resource allocation (FDRA)). 【0143】 Furthermore, for example, by configuring resources for a given UE during periods when DL and UL overlap in the time domain in the same way as existing UL resources (for example, by avoiding the use of DL resources using Frequency Domain Resource Allocation (FDRA)), the impact on the specification / UE can be minimized. 【0144】 (Analysis) The concept / scenario / definition of self-free includes MIMO and the evolution of mobility. 【0145】The evolution of MIMO from single-point MIMO to multi-TRP (NCJT / CJT / coordinated scheduling / coordinated beamforming (CSCB) / dynamic point selection (DPS)) and the evolution of mobility from layer 3 (L3) mobility to L2 mobility (LTM) may further evolve to D-MIMO, low-layer mobility, and flexible TRP clustering (high-density TRP, clustering of cells / TRP for mobility, control and data may be decoupled). 【0146】 Selfly may include at least one of the following features: ◆ Higher density TRP arrangement (per cell). This can achieve better SNR for all UEs, including conventional cell edge areas. ◆ Flexible (e.g., UE-centered) TRP clustering for cell construction. This can reduce the number of UEs affected by interference between multiple cells / TRPs. ◆ Low-level mobility. This allows for the consideration of more TRPs within a single clustering and enables seamless mobility through L1 level operation. 【0147】 Selfley may include at least one of the following concepts: 【0148】 ◆Concept 1: Multiple TRP / AP selection / transmission is performed solely for data (physical (PHY) / MAC layer). Cell selection, initial access, and mobility are not significantly affected in the specifications. Existing LTMs may be repurposed or extended. Major impacts on the specifications include extensions to L1 measurement / reporting or SRS transmission for the selection of multiple TRP / APs, and extensions to CSI measurement / reporting or SRS transmission for CSI of clustering of TRP / APs (different from their selection). 【0149】◆Concept 2 Multiple TRP / AP selection / transmission is performed for both control (RRC) and data. In addition to the L1 / CSI for data in Concept 1, there are impacts on the specifications regarding cell selection, initial access, and mobility. For example, a UE may be required to access multiple TRP / APs for initial access, and the SSB / SI / RACH may be redesigned. The clustering of multiple TRP / APs for control and data may be the same or different. There may be impacts on the specifications in the case of clustering of more than one DU / CU that are not geographically located. 【0150】 In another aspect, CCs (CA scenarios) within different frequencies may be considered. Multiple TRPs / APs may be processed separately for each CC, or they may be processed jointly across multiple CCs (for example, clustering and scheduling may jointly consider the dimensions of the TRP and the dimensions of the CC). 【0151】 (Issue) In Concept 2, if the UE requires access to multiple TRP / APs during initial access, how the initial access procedure is redesigned to achieve this has not been sufficiently considered. From a network deployment perspective, each TRP / AP can have one or more SSBs for coverage. 【0152】 Thus, the operation of SSB / initial access in self-free mode has not been adequately considered. If this operation is not adequately considered, there is a risk that communication quality / throughput will deteriorate. 【0153】 Therefore, the inventors considered initial access methods and conceived the following embodiments. 【0154】 The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination. 【0155】(Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above. 【0156】 In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C". 【0157】 In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably. 【0158】 In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably. 【0159】In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages). 【0160】 In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs). 【0161】 In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI). 【0162】 In this disclosure, ceil(x), ceiling function, and ceiling function may be interpreted as interchangeable. In this disclosure, floor(x), floor function, and floor function may be interpreted as interchangeable. In this disclosure, sqrt(x), square root of x, and root x may be interpreted as interchangeable. In this disclosure, x mod y, mod(x, y), mod function, and modulo operation may be interpreted as interchangeable. In this disclosure, Σ i=M M+N-1 f(i), Σ i=MM+N-1 f i f(i) or f over i = M, M+1, ..., M+N-1 i The sum of f(M) + f(M+1) + ... + f(M+N-1), f M +f M+1 +...+f M+N-1 , can be read interchangeably. C(n,k) is the number of combinations of choosing k values ​​from n values ​​(combinatorial coefficient), binomial coefficients, n C k , C n k , may be interpreted as mutually exclusive. In this disclosure, x / / y and floor(x / y) may be interpreted as mutually exclusive. 【0163】 In this disclosure, A b The notations A_b, Ab, and A with a b placed to the lower right may be interpreted as interchangeable. In this disclosure, A c The notation A^c, with a c superscripted above A, may be interpreted as interchangeable. In this disclosure, A b c The notation A_b^c, where b is placed to the lower right of A and c is placed to the upper right of A, may be interpreted as being interchangeable. In this disclosure, x ~ x may be represented by placing a ~ above x, or it may be called x tilde. In this disclosure, x - x may be represented by placing a hyphen above it, or it may be called an x-bar. In this disclosure, x ＾ This can also be represented by placing a caret (^) above x, or it may be called an x-hat. 【0164】In this disclosure, FR may be at least one of, for example, FR1, FR2, FR2-1, FR2-2, FR3, subterahertz, and terahertz. In this disclosure, the frequency range corresponding to FR1 may be 410–7125 MHz. In this disclosure, FR2 may include FR2-1 and FR2-2, the frequency range corresponding to FR2-1 may be 24250–52600 MHz, and the frequency range corresponding to FR2-2 may be 52600–71000 MHz. 【0165】 In this disclosure, the following abbreviations may be used: ◆FDM: frequency division multiplexing ◆TDM: time division multiplexing ◆CDM: code division multiplexing ◆SDM: space division multiplexing ◆SFN: single frequency network 【0166】 In this disclosure, base station (BS), TRP, AP, gNB, and network (NW) may be interpreted as interchangeable. 【0167】 In this disclosure, receiving, detecting, monitoring, and selecting may be interpreted as mutually exclusive. 【0168】 In this disclosure, cell, area, coverage, first cell, and second cell may be interpreted interchangeably. In this disclosure, first cell, supercell, multiple TRP / AP, and set / group of TRP / AP may be interpreted interchangeably. In this disclosure, second cell, subcell, multiple TRP / AP / SSB / QCL assumptions, and set / group / subset / cluster of TRP / AP / SSB / QCL assumptions may be interpreted interchangeably. 【0169】In this disclosure, QCL, QCL assumption, spatial relationship, TCI state, unified TCI state, joint TCI state, DL TCI state, UL TCI state, synchronization signal (index), SSB (index), DL RS (index), SSB corresponding to a specific RSRP, beam, TRP, AP, QCL information (qcl-Info), and QCL type A / B / C / D may be interpreted as mutually interchangeable. 【0170】 In this disclosure, the RA / RACH / PRACH / preamble resources, (PRACH) preamble, occasion, RACH occasion (RO), PRACH occasion, (PRACH) time / frequency resources / instances / start position / number / size / width / index, and PRACH / preamble / mask settings / index may be interpreted as one another. 【0171】 In this disclosure, time instance, time occasion, time domain position, time position, PRACH occasion, PRACH slot, period, period / offset, symbol / slot / subframe / frame / time domain (index) may be interpreted interchangeably. In this disclosure, frequency instance, frequency occasion, frequency domain position, frequency position, subcarrier / RE / RB / CC / time domain (index) may be interpreted interchangeably. 【0172】In this disclosure, Msg1 (Message 1, Msg.1), RACH, PRACH (preamble), and Random Access Preamble may be interpreted as interchangeable. In this disclosure, Msg2 (Message 2, Msg.2), RAR, RAR PDSCH and at least one PDCCH scheduling it, and RAR UL Grant may be interpreted as interchangeable. In this disclosure, Msg3 (Message 3, Msg.3), PUSCH carrying the RRC Setup Request message, and Msg3 PUSCH may be interpreted as interchangeable. In this disclosure, Msg4 (Message 4, Msg.4), PDSCH carrying the RRC Setup message, Msg4 PDSCH, and PDSCH received after sending Msg3 PUSCH may be interpreted as interchangeable. 【0173】 In this disclosure, the terms synchronization signal (SS), PSS, SSS, PBCH, SSB, SS / PBCH block, SSB index, SS / PBCH block index, candidate SS / PBCH block index, CSI-RS, CSI-RS resource, and CSI-RS resource index may be interpreted as interchangeable. 【0174】 In this disclosure, existing RA procedures, RA procedures in existing specifications (e.g., specifications prior to Rel. 18), and RA procedures / PRACH / RACH resources / RO / preambles for selecting one SSB may be interpreted as interchangeable. In this disclosure, new RA procedures, RA procedures for new purposes, and RA procedures / PRACH / RACH resources / RO / preambles for selecting a set of SSBs may be interpreted as interchangeable. In this disclosure, new purposes, selection of a set of SSBs, and (initial) access to self-free may be interpreted as interchangeable. 【0175】 In this disclosure, existing RACH resources and RACH resources / RO / preambles for existing RA procedures may be interpreted as interchangeable. In this disclosure, additional RACH resources, new RACH resources, and RACH resources / RO / preambles for new RA procedures may be interpreted as interchangeable. 【0176】 In this disclosure, the PDCCH order, the PDCCH / DCI that triggers the RA procedure, and the DCI format [1_0] for the RA procedure initiated by the PDCCH order may be interpreted as other terms. 【0177】 (Wireless Communication Method) Figure 4 shows another example of multiple SSBs detected by a UE in a cell-free system based on assumption 1. In this example, one supercell / cell has multiple TRPs / APs. The multiple TRPs / APs (the supercell / cell) have PCI#0. Each TRP / AP transmits at least one SSB. UE#0 receives SSBs #2, #4, and #5 from three surrounding TRPs, respectively. UE#1 receives SSBs #5, #10, #13, and #16 from four surrounding TRPs, respectively. In this example, SSB #5 of PCI#0 belongs to two sets of TRPs / APs (received by two UEs and transmitted in two directions). 【0178】 Figure 5 shows another example of multiple SSBs detected by the UE in a cell-free system based on assumption 1. In this example, one supercell / cell has multiple TRPs / APs. The multiple TRPs / APs (the supercell / cell) have PCI#0. Each TRP / AP transmits at least one SSB. UE#0 receives SSBs #2, #4, and #5 from three surrounding TRPs, respectively. UE#1 receives SSBs #7, #10, #13, and #16 from four surrounding TRPs, respectively. In this example, SSB #5 of PCI#0 and SSB #7 of PCI#0 belong to the same TRP / AP (transmitted from the same TRP / AP, transmitted in different directions). 【0179】 In a cell-free system based on assumption 2, an SSB may be associated with a supercell (supercell ID) instead of a PCI, and multiple SSBs may be associated with multiple different PCIs. 【0180】Each embodiment describes additional conditions / behaviors to be considered for SSB set selection (new RA procedure), and does not mean to remove conditions / behaviors for existing SSB selection (existing RA procedure). For example, Embodiment B3 does not mean to remove the conditions for CORESET for type 1 PDCCH CSS sets described in "RAR Monitoring" above, but rather to mean additional conditions to be considered in addition to the existing timing. 【0181】 In each embodiment, beam, SSB [index], CSI-RS [resource index], TRS [resource index], SRS [resource index], other RS ​​[resource index], DL / UL / joint TCI state [index], QCL assumption, and TRP may be interchangeable. 【0182】 In each embodiment, the TRP [cluster] may be a group / set of beam / SSB / CSI-RS / TRS / SRS / other RS / TCI state / QCL assumptions, or it may be a group of CORESETs (CORESET pool) [in a multi-DCI-based TRP]. In each embodiment, the TRP may be replaced by a TRP cluster. A TRP cluster may have multiple TRPs. 【0183】 In each embodiment, L1-RSRP, L1-SINR, L1-RSRQ, L3-RSRP, L3-SINR, L3-RSRQ, filtered L1 measurement, and extended L1 measurement may be interpreted as one another. 【0184】 In each embodiment, the identification information, one or more SSB indexes, SSB set index, TCI status index, and RS resource index may be interchangeable. 【0185】Multiple TRP / AP / SSB / CSI-RS sets / clusters or supercells may be associated with (applied to) one or more settings based on each embodiment. If multiple TRP / AP / SSB / CSI-RS sets / clusters or supercells change, the UE may need to update one or more of its settings. For example, such updates may be based on one of the following actions: ◆ The UE may send a request for updating one or more of its settings. ◆ The UE may update one or more of its settings based on a definition or setting. ◆ The UE may expect to receive one or more updated settings from the NW. 【0186】 <Embodiment A1> A set of SSB indexes (SSB set) may be associated with one or more PRACH occasions (RACH occasions, ROs). Multiple SSB indexes within each SSB set may be provided by the SIB / RRC IE. The association settings between each SSB set and one or more ROs may be provided by the SIB / RRC IE. 【0187】 A single SSB set may be associated with multiple TRPs / APs within a single supercell / cell / area / coverage. In initial access, an existing UE may detect one SSB, whereas a UE supporting Embodiment A1 may detect multiple SSBs (within a single SSB set). Based on these multiple SSBs, a random access procedure to multiple TRPs / APs may be performed (multiple PRACHs / preambles may be sent to multiple SSBs / TRPs / APs) (clustering of multiple TRPs / APs corresponding to multiple SSBs may be performed). Compared to existing specifications, the number of SSBs detected by a UE and the number of ROs that can be utilized by that UE may be increased. 【0188】 According to Embodiment A1, the UE can connect to multiple TRP / APs during the initial access phase, thereby achieving a self-free effect / gain. 【0189】(As explained in the "Initial Access Procedure" above,) in the existing specification, one SSB is associated with one or more ROs, and the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is used for its configuration. In Embodiment A1, the existing SSB may be replaced with a set of SSB indexes (SSB set). 【0190】 The number of SSB indexes in each SSB set may be based on at least one of the following options: 【0191】 ◆Option 1: The number of SSB indexes in each SSB set is the same. 【0192】 ◆Option 2: The number of SSB indexes in each SSB set is different. The number of SSB indexes in an SSB set may be related to the corresponding coverage or TRP count. 【0193】 Multiple SSB indexes within an SSB set may be determined by the UE, or by coordination between the NW and the UE. 【0194】 The association between an SSB set and one or more PRACH occasions may be determined based on at least one of the following options: 【0195】 ◆Option 3 Similar to the existing parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB, which shows the combination of the number of SSBs N per PRACH occasion and the number of CB preambles R per SSB, the number of SSB sets N per PRACH occasion. Set and the number of CB preambles R per SSB set (per valid PRACH occasion) Set A new parameter indicating a combination with (e.g., ssbSet-perRACH-OccasionAndCB-PreamblesPerSSBSet). 【0196】◆Option 4 A value based on the existing parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB, which indicates the number of SSBs per PRACH occasion and the number of CB preambles per SSB, and a new parameter that indicates the number of SSB indices in an SSB set (e.g., M). For example, the number of SSB sets per PRACH occasion N Set = "Number of SSBs N per PRACH occasion" / M * α. α may be defined in the specification. For example, the number of CB preambles R per SSB set. S = "Number of CB preambles per SSB R" * M * β. β may be defined in the specification. As the number of SSB indices in an SSB set increases, the number of ROs / preambles associated with the SSB set may also increase. 【0197】 If one association between an RO and one SSB, and one association between an RO and one SSB set, can be established, these can be distinguished from existing parameters by defining new parameters. 【0198】 (If the number of SSB sets per PRACH occasion is less than 1,) a subset of one SSB set may be associated with one RO. For example, an SSB set may include SSB #1 through #4, with SSB #1 and #2 (SSB subset #1) associated with RO #1, and SSB #3 and #4 (SSB subset #2) associated with RO #2. 【0199】 The UE may receive existing / new parameters via the SIB / RRC IE. 【0200】 Multiple SSB indexes within different sets of SSBs may be based on at least one of the following options: 【0201】 ◆Option 5: A single SSB index can only exist within a single SSB set. 【0202】◆Option 6 A single SSB index can exist within multiple SSB sets. The constraint is that two different SSB sets can have a maximum of X identical SSB indexes. For example, X may be 1. 【0203】 The association period may ensure that all SSB sets are mapped at least once to a PRACH occasion within a single association period. 【0204】 In option 3 described above, the association between the SSB set and the RO may be represented by at least one of the following examples. 【0205】 ◆Figure 6A shows ssbSet-perRACH-OccasionAndCB-PreamblesPerSSBSet=[oneHalf,n16](N Set =1 / 2,R Set The example of msg1-FDM=4 (=16) is shown. In this example, four ROs are FDM'd in one time instance, one SSB set is mapped to two ROs, and one SSB set is associated with 16 preambles. For example, SSB set #0 is associated with preambles #0 through #15. 【0206】 ◆Figure 6B shows ssbSet-perRACH-OccasionAndCB-PreamblesPerSSBSet=[four,n16](N Set =4,R Set =16), msg1-FDM=4, total number of preambles N preamble total An example of =64 is shown. In this example, four ROs are FDM'd in one time instance, four SSB sets are mapped to one RO, and one SSB set is associated with 16 preambles. For example, SSB set #0 is associated with preambles #0 through #15. SSB set #1 is associated with preambles #16 through #31. SSB set #2 is associated with preambles #32 through #47. SSB set #3 is associated with preambles #48 through #63. 【0207】 Each SSB set in these examples may be an SSB set based on Option 6, as shown in the example in Figure 7. In this example, SSB set #0 may include SSB(index) #0, #2, and #3. SSB set #1 includes SSB(index) #0, #1, and #5. SSB set #2 includes SSB(index) #4 and #7. SSB set #3 includes SSB(index) #5, #6, #7, and #9. Here, SSB #0 is included in both SSB sets #0 and #1. 【0208】 <Embodiment A2> The relationship between SSB and RO may include both an association between SSB and RO (an SSB-RO association similar to the existing specification) and a new association between SSB set and RO (an SSB set-RO association of Embodiment A1). These two associations may be set by SIB / RRC IE. These two associations may be set by the same (common) parameter or by different parameters. 【0209】 According to Embodiment A2, both the SSB-RO association and the SSB set-RO association can be appropriately configured. 【0210】 Multiple ROs may first be mapped to one or more SSBs, and then to one or more SSB sets. 【0211】 For the SSB-RO association case and the SSB set-RO association case, the same or separate parameters may be set for at least one of the following: the number of SSB / SSB sets associated per RO and the number of preambles associated per SSB / SSB set. 【0212】 The related period may ensure that all SSBs and all SSB sets are mapped to a PRACH occasion at least once within a single related period. 【0213】Other RACH-related parameters may be provided in common or separately for the SSB-RO association case and the SSB set-RO association case. These RACH-related parameters may be, for example, parameters indicating at least one of RO resource settings, power, RAR window, and conflict resolution window, or parameters relating to at least one of msg1-FDM, preambleReceivedTargetPower, preambleTransMax, powerRampingStep, ra-ResponseWindow, ra-ContentionResolutionTimer, and prach-RootSequenceIndex. 【0214】 In Embodiment A1, the RACH-related parameters may also be introduced for PRACH settings for SSB set-RO association. 【0215】 Figure 8 shows ssb-perRACH-OccasionAndCB-PreamblesPerSSB=oneHalf,n16 (N=1 / 2,R=16), ssbSet-perRACH-OccasionAndCB-PreamblesPerSSBSet=1,n16 (N Set =1,R SetThe example msg1-FDM=4 (=16) is shown. In this example, four ROs are FDM'd in one time instance. Of the multiple ROs, the first few ROs (first ROs) (in RO index order, or in frequency index order followed by time index order) may be mapped to one or more SSBs (in SSB index order, from SSB #0 to #3), and the next few ROs (second ROs) (in RO index order, or in frequency index order followed by time index order) may be mapped to one or more SSB sets (in SSB set index order, from SSB set #0 to #3). In this example, one SSB is mapped to two ROs, and one SSB is associated with 16 preambles. For example, SSB #0 is associated with preambles #0 to #15. Furthermore, one SSB set is mapped to one RO, and one SSB set is associated with 16 preambles. 【0216】 <Embodiment A3> If the UE receives multiple SSB sets, it may select one SSB set for PRACH transmission (from multiple SSB sets) based on the measurement results for multiple SSB indices for each SSB set. According to Embodiment A3, the UE can select an appropriate SSB set for PRACH transmission. The rules for selecting SSBs (within an SSB set) may be based on the "SSB / CSI-RS selection" described above. 【0217】 The rules for selecting an SSB set may be based on at least one of the following options: 【0218】 ◆Option 1: If all SSBs in a given SSB set have RSRP values ​​that exceed a threshold, that SSB set is selected. This threshold may be set by the RRC IE or defined in the specification. 【0219】 ◆Option 2: If at least Y SSBs in a given SSB set have RSRP values ​​that exceed a threshold, that SSB set is selected. For example, Y may be 2. The threshold may be set by RRC or defined in the specification. 【0220】 ◆Option 3: If the average RSRP of all SSBs within a given SSB set exceeds a threshold, that SSB set is selected. This threshold may be set by RRC or defined in the specification. 【0221】 ◆Option 4 If the RSRP of the best SSB in a given SSB set exceeds threshold 1, and the RSRP of the worst SSB in that SSB set exceeds threshold 2, then that SSB set is selected. Threshold 2 < threshold 1 is also acceptable. Thresholds 1 and 2 may be set by RRC or defined in the specification. 【0222】 The threshold may be set by RRC IEs (e.g., rsrp-ThresholdSSBset, rsrp-ThresholdSSBset1, rsrp-ThresholdSSBset2) that indicate RSRP thresholds for SSB sets. 【0223】 The rules for selecting one SSB and one SSB set (in the case of Embodiment A2) may be based on at least one of the UE capability and the UE RRM measurement results of multiple SSB indices for each SSB set. 【0224】 <Embodiment A4> After PRACH transmission, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding random access (RA)-RNTI within a window controlled by the upper layer for RAR detection. After PRACH transmission, the UE's assumption of the DMRS QCL for PDCCH / PDSCH for RAR detection (received beams for the PDSCH carrying the RAR and the PDCCH scheduling it) may be based on at least one of the following several options. 【0225】 ◆Option 1 The QCL assumption is the same as the QCL assumption for the lowest SSB index in the SSB set for the associated PRACH. The NW may transmit one RAR using the beam of the lowest SSB index in the SSB set. 【0226】◆Option 2 The QCL assumption is the same as the QCL assumption for one or more specific SSB indices in the SSB set for the associated PRACH. The one or more specific SSB indices may be determined based on rules defined in the specification. For example, the one or more specific SSB indices may be the lowest SSB index and the highest SSB index. The NW may transmit multiple RARs using multiple different beams corresponding to multiple specific SSB indices in the SSB set. 【0227】 ◆Option 3 The QCL assumption is the same as the QCL assumption for any SSB index in the SSB set for the associated PRACH. The network may transmit multiple RARs using multiple beams corresponding to all SSB indices in the SSB set. The same RAR may be transmitted by the network using multiple beams in the same time-frequency resource. The same RAR may be transmitted by the network using multiple beams in multiple different time-frequency resources within the RAR window. 【0228】 ◆Option 4 The QCL assumption is the same as the QCL assumption for all SSB indices in the SSB set for the associated PRACH (assuming joint transmission of all SSB indices). The network may transmit multiple RARs using multiple beams corresponding to all SSB indices in that SSB set within the same time-frequency resources. 【0229】◆Option 5 The RAR window [time / length] is divided into N parts based on rules defined in the specification or SIB / RRC IE. The rule may be that each part has the same length, where N is the number of SSB indices in the SSB set. In the N parts of the RAR window, the UE may assume different QCLs for RAR reception. The association between each part and the SSB index may be defined in the specification. The association may associate the N parts with the SSB index in SSB index order. The NW can freely select one part / SSB index for RAR transmission, considering different loads for multiple different beams. 【0230】 The transmit beam of PRACH based on the QCL of the SSB index in the SSB set may correspond to the receive beam (QCL) of RAR. 【0231】 Figure 9A shows an example of one RAR window in options 1 to 4. In this example, the UE assumes one QCL for RAR reception within one RAR window. 【0232】 Figure 9B shows an example of a single RAR window using N=3 in Option 5. In this example, a single RAR window is divided into three parts, and the UE assumes three different QCLs for RAR reception in the three parts. 【0233】 Depending on the assumed QCL type for RAR reception, any of options 1 through 5 may be applied. The same option may be applied to multiple different QCL types, or different options may be applied. For example, one QCL type A may be based on option 1, and all QCL types D may be based on option 4. 【0234】 Multiple RARs to which multiple QCL assumptions are applied may be TDM / FDM / CDM / SDM / SFN. 【0235】According to Embodiment A4, the UE can receive the RAR corresponding to the SSB set using an appropriate QCL. 【0236】 <Embodiment A5> The QCL assumption for the initial transmission of Msg3 PUSCH may be based on at least one of the following options: ◆Option 0: The QCL assumption is dependent on the UE implementation. ◆Option 1: The QCL assumption is the same as the QCL of the transmitted PRACH. ◆Option 2: The QCL assumption is the same as the QCL of the received RAR. 【0237】 The QCL assumption for the retransmission of Msg3 PUSCH may be based on at least one of the following options: ◆Options 0 / 1 / 2 mentioned above. The same option may be applied to the initial and retransmissions, or different options may be applied. ◆Option 3: The QCL assumption is the same as the QCL for the initial transmission. 【0238】 In Option 1, if a UE transmits multiple PRACHs using multiple QCL assumptions, the UE may transmit initial and retransmitted Msg3 PUSCHs using those multiple QCL assumptions. In Option 2, if a UE receives multiple RARs using multiple QCL assumptions, the UE may transmit initial and retransmitted Msg3 PUSCHs using those multiple QCL assumptions. 【0239】 Multiple Msg3 pushes (initial / retransmission) to which multiple QCL assumptions apply may be TDM / FDM / CDM / SDM / SFN. 【0240】 According to Embodiment A5, the UE can transmit Msg3 PUSCH corresponding to the SSB set using an appropriate QCL. 【0241】<Embodiment A6> The UE may detect the DCI format and receive Msg4 PDSCH scheduled by that DCI format in response to a PUSCH transmission scheduled by a RAR UL grant, or to a corresponding PUSCH retransmission scheduled by DCI format 0_0 with a CRC scrambled by a temporary cell (TC)-RNTI provided in the corresponding RAR message. After Msg3, the UE's assumption of the DMRS QCL for the PDCCH carrying that DCI format for Msg4 PDSCH (received beams for Mgg.4 PDSCH and the PDCCH that schedules it) may be based on at least one of several options below: ◆Options 0 / 1 / 2 / 3 / 4 in Embodiment A4. ◆Option 5: The QCL assumption is the same as the QCL of the transmitted PRACH. ◆Option 6: The QCL assumption is the same as the QCL of the received RAR. ◆Option 7: The assumed QCL is the same as the QCL of the transmitted Msg3. 【0242】 In Option 5, if a UE transmits multiple PRACHs using multiple QCL assumptions, the UE may receive multiple Msg4 PDSCHs using those multiple QCL assumptions. In Option 6, if a UE receives multiple RARs using multiple QCL assumptions, the UE may receive multiple Msg4 PDSCHs using those multiple QCL assumptions. In Option 7, if a UE transmits multiple Msg3 PUSCHs using multiple QCL assumptions, the UE may receive multiple Msg4 PDSCHs using those multiple QCL assumptions. 【0243】 Multiple Msg4 PDSCHs, each to which multiple QCL assumptions are applied, may be TDM / FDM / CDM / SDM / SFN. 【0244】 According to Embodiment A6, the UE can receive Msg4 corresponding to the SSB set using an appropriate QCL. 【0245】<Embodiment B0> Multiple Msg1 messages may be sent for the selection of an SSB set. The method of sending these messages may be based on at least one of the following options. 【0246】 ◆Option 1 Multiple RA procedures can be executed in parallel. Some or all of the messages in an RA procedure (e.g., Msg1 / Msg2 / Msg3 / Msg4) may be multiple messages. In the example in Figure 10, SSB set #0 includes SSB (index) #0, #2, and #3, and the gNB / CU sends SSB #0 from TRP #1 and SSB #2 and #3 from TRP #3. In the example in Figure 11, when the UE detects / selects SSB set #0, the UE sends three PRACHs using one or more ROs associated with SSB set #0. The PRACH corresponding to SSB #0 is sent to TRP #1 (using the TCI state corresponding to TRP #1), and the PRACHs corresponding to SSB #2 and #3 are sent to TRP #3 (using the TCI state corresponding to TRP #3). The UE receives three RARs using the RAR window corresponding to SSB set #0. The RAR corresponding to SSB #0 is received from TRP #1 (using the TCI state corresponding to TRP #1), and the RARs corresponding to SSB #2 and #3 are received from TRP #3 (using the TCI state corresponding to TRP #3). The UE sends three Msg3s corresponding to the three RARs. The UE sends three Msg3s corresponding to the three RARs. The Msg3 corresponding to SSB #0 is sent to TRP #1 (using the TCI state corresponding to TRP #1), and the Msg3s corresponding to SSB #2 and #3 are sent to TRP #3 (using the TCI state corresponding to TRP #3). The UE receives three Msg4s corresponding to the three Msg3s. Msg4 corresponding to SSB#0 is received from TRP#1 (using the TCI state corresponding to TRP#1), and Msg4 corresponding to SSB#2 and #3 is received from TRP#3 (using the TCI state corresponding to TRP#3). 【0247】Multiple RA procedures executed in parallel may include one or more RA procedures for existing SSB selection (existing RA procedures), one or more RA procedures for new SSB set selection (new RA procedures), or both existing and new RA procedures. 【0248】 ◆Option 2 A single RA procedure can be redefined. For example, multiple Msg1s and one Msg2 / Msg3 / Msg4 may be considered as a single RA procedure. That RA procedure may be defined as a new type of RA procedure. As with the existing specification, the number of running RA procedures may be limited to one. 【0249】 According to Embodiment B0, the RA procedure can be properly executed even when the UE transmits multiple PRACHs corresponding to the SSB set. 【0250】 <Embodiment B1> The configuration of the SSB sets (showing the SSB index within each SSB set) may be provided by the SIB / RRC IE. 【0251】 The number of SSB indexes within each SSB set may be based on one of the following options: 【0252】 ◆Option 1 (same as Embodiment A1): In multiple SSB sets, the number of SSB indices within each SSB set is the same. 【0253】 ◆Option 2 (same as Embodiment A1) In multiple SSB sets, the number of SSB indexes in each SSB set may be different. 【0254】 Within multiple different SSB sets, the SSB index may be based on one of the following options: 【0255】 ◆Option 5 (same as Embodiment A1): A single SSB index can exist within only one SSB set. 【0256】◆Option 6 (similar to Embodiment A1) A single SSB index can exist in multiple SSB sets. The constraint is that two different SSB sets can have up to X identical SSB indexes. For example, X may be 1. 【0257】 Existing associations between SSB indexes and ROs may be maintained for RACH configuration. 【0258】 (Similar to Embodiment A3,) the UE may select an SSB set based on the measurement results of multiple SSB indices for each SSB set. 【0259】 The UE may send multiple PRACHs in multiple ROs corresponding to multiple SSB indexes within the selected SSB set. For example, if there are three SSB indexes within the selected SSB set, the UE may select / associate one RO for each SSB index and send a PRACH in each RO. 【0260】 Example of constraint: ◆ (At least in FR2,) in multiple ROs associated with multiple SSB indices within the same SSB set, the UE may assume / expect that there are at least multiple ROs that are TDM, or that multiple ROs are TDM. 【0261】 Examples of stricter constraints: ◆ (At least in FR2,) in multiple ROs associated with multiple different SSB indices (whether associated with the same set of SSBs or different sets of SSBs), the UE may assume / expect that there are at least multiple ROs that are TDM, or that multiple ROs are TDM. 【0262】 The constraints on UE behavior may be at least one of the following constraints: 【0263】◆(At least in FR2,) in multiple ROs associated with multiple SSB indices of the same SSB set, the UE selects the TDM-modified ROs associated with those multiple SSB indices for PRACH transmission. In the example in Figure 12, SSB set #0 includes SSBs #0, #2, and #3. In the example in Figure 13, the three TDM-modified ROs are associated with SSBs #0, #2, and #3, respectively. The three Msg1s in the three ROs use the beams (TCI state / spatial relationships) corresponding to SSBs #0, #2, and #3. 【0264】 ◆The same preamble is selected for multiple ROs. The same transmit power may also be applied to multiple ROs. 【0265】 ◆At the start of the RA procedure for SSB set selection, the preamble transmission counter (e.g., PREAMBLE_TRANSMISSION_COUNTER) may be set to 1 and incremented by 1 each time a RAR reception fails. In other words, the preamble transmission counter / random access preamble transmission maximum (e.g., preambleTransMax) may be represented by the number of preamble transmissions. 【0266】 ◆At the start of the RA procedure for SSB set selection, the preamble transmit counter (e.g., PREAMBLE_TRANSMISSION_COUNTER) may be set to the number of SSBs in the SSB set M, and may be incremented by M each time a RAR reception fails. In other words, the preamble transmit counter / random access preamble transmit maximum (e.g., preambleTransMax) may be represented by the number of SSBs. 【0267】 According to Embodiment B1, multiple ROs corresponding to the SSB set can be appropriately set / selected. 【0268】<Embodiment B2> In order to distinguish between the selection of one SSB for one PRACH transmission on one existing RO (SSB selection) and the selection of a set of SSBs for multiple PRACH transmissions on multiple ROs (SSB set selection), at least one of the following embodiments B2-x may be applied. 【0269】 <<Embodiment B2-1>> Separately for a number of ROs for a new SSB set selection and for a number of ROs for an existing SSB selection, RO / preambles may be set via the signaling of a new SIB / RRC or determined based on rules defined in the specification. The new RO / preamble and the existing RO / preamble may be based on at least one of the following several options: 【0270】<<<Option 1>>> A new RO / preamble may be based on an additional RACH setting (second setting) for SSB set selection (in self-free mode). For example, the additional RACH setting may be a new parameter in the UL BWP common setting (BWP-UplinkCommon) (RACH-ConfigCommon-SSBset), or a new parameter in the RACH common setting (RACH-ConfigCommon) (RACH-ConfigGeneric-SSBset). For example, a new RO / preamble setting may include at least one of the following parameters: ◆Parameters for RO time and frequency resources. For example, prach-ConfigurationIndex, Msg1 frequency start position (msg1-FrequencyStart, offset of the minimum PRACH occasion relative to PRB0 in the frequency domain), msg1-FDM, etc. ◆Parameters for mapping from SSB to RO. For example, ssb-perRACH-OccasionAndCB-PreamblesPerSSB, ra-ssb-OccasionMaskIndex, etc. ◆Parameters for PRACH power. For example, preambleReceivedTargetPower, preambleTransMax, powerRampingStep, etc. ◆Parameters for the length of the RAR window or contention resolution window. For example, ra-ResponseWindow, ra-ContentionResolutionTimer, etc. ◆Parameters for SSB set selection. For example, rsrp-ThresholdSSB, RSRP threshold for SSB set (rsrp-ThresholdSSBset), etc. ◆Counter / UE variables. For example, PREAMBLE_TRANSMISSION_COUNTER, PREAMBLE_POWER_RAMPING_COUNTER, etc. ◆For parameters not included in / existing within the additional RACH settings, default values ​​(based on rules defined in the specification) may be applied, or existing RACH settings for SSB selection may be applied.◆Individual RACH resources (additional RACH resources) may be set for SSB set selection. Candidate values ​​for RACH resources for SSB set selection may differ from candidate values ​​for existing RACH resources for SSB selection. For example, candidate values ​​for RAR window length for SSB set selection may be larger than candidate values ​​for RAR window length for existing SSB selection. 【0271】 <<<Option 2>>> Within the existing RACH settings (RACH settings, existing RACH settings, first setting), several new parameters (second setting) for SSB set selection in self-free are additionally set. The new parameters may indicate a distinction between existing RACH resources (RO / preamble) and RACH resources (RO / preamble) for the new purpose. Existing parameters within the existing RACH settings may indicate a RACH resource that includes both existing and new RACH resources, and the new parameters may indicate values ​​(e.g., ratio, resource location, range, entry, index, etc.) to identify at least one of the existing and new RACH resources within that RACH resource. 【0272】 This option means that existing UEs may use all configured RO / preambles based on the RACH settings. 【0273】 <<<Option 3>>> Within the existing RACH settings (RACH settings, existing RACH settings, first settings), several new parameters (second settings) for SSB set selection in self-free mode are additionally set. The new parameters may indicate at least one of the RO offset / resource and preamble for the new purpose. For example, the new parameters may be for at least one of the RO offset / resource to be TDM / FDM, the preamble range, the SSB to RO mapping and the prach-RootSequenceIndex. 【0274】If a new parameter of the same type as an existing parameter for an existing SSB selection is defined, the new parameter name may include a suffix indicating that it is for SSB set selection (i.e., a release that supports SSB set selection), in addition to the existing parameter name. 【0275】 This option allows you to configure individual RACH resources (additional RACH resources) for each SSB set selection. 【0276】 <<Example of Embodiment B2-1>> Figure 14 shows an example of Option 1. In this example, the existing RACH setting indicates multiple ROs (existing RACH resources) for an existing SSB selection, and the additional RACH setting indicates multiple ROs (additional RACH resources) for a new SSB set selection. The existing RACH resources and additional RACH resources may be TDM. The existing RACH setting may associate preambles #0 to #15 with SSB #0, and the additional RACH setting may associate preambles #0 to #31 with SSB #0. 【0277】 Figure 15 shows an example of Option 2. In this example, the existing RACH settings are ssb-perRACH-OccasionAndCB-PreamblesPerSSB=oneHalf,n16 (N=1 / 2, R=16), msg1-FDM (number of PRACH occasions FDMed within one time instance)=4, and the number of ROs for the new objective (PRACH transmission for SSB set selection) is 50% of the total number of ROs, and the number of preambles for the new objective is 50% of the total number of preambles. In this example, two ROs are associated with SSB#0, and one of the ROs is associated with SSB#0 (within the SSB set) for SSB set selection. In this example, preambles #0 to #15 are associated with SSB #0, with preambles #0 to #7 used for PRACH for SSB selection, and preambles #8 to #15 used for PRACH for SSB set selection. 【0278】Figure 16 shows an example of Option 3. In this example, the new parameters are the (frequency domain) offset between the existing RO and the additional RO, and the number of ROs FDM-processed in the additional RACH resource (additional RO). In this example, the number of additional ROs FDM-processed into the existing RO is 1, and one additional RO associated with the same SSB#0 is FDM-processed into two existing ROs associated with SSB#0. The offset may be the difference (RB / RE number) between the lowest frequencies of the two existing ROs and the lowest frequency of the one additional RO. 【0279】 Figure 17 shows another example of Option 3. In this example, the new parameters are the existing RACH resource and the range of the additional preamble. The range of the existing preamble is 0 to 15, and the range of the additional preamble may be 16 to 31. 【0280】 <<Embodiment B2-2>> Additional / individual RACH settings may not be required for a new SSB set selection. For the prach-RootSequenceIndex set for the SSB set selection, the UE may derive an SSB set-specific root sequence based on a function of the SSB set index. That function may be defined in the specification. For example, the root sequence index may be given by a function of the set prach-RootSequenceIndex and the SSB set index. For example, that function may be (set prach-RootSequenceIndex + SSB set index + 1) mod (maximum value of root sequence index + 1). 【0281】 The structure of the RRC IE prach-RootSequenceIndex for existing SSB selections is defined as follows using abstract syntax notation 1 (ASN1): prach-RootSequenceIndex CHOICE { l839 INTEGER (0..837), l139 INTEGER (0..137)} 【0282】 For example, if prach-RootSequenceIndex is set to the index of a root sequence of length 839 = 800 (l839=800), and the UE selects SSB set (index) #5, then the UE derives the root sequence index as (800+5+1) mod 838 = 806. 【0283】 According to Embodiment B2-2, by blind decoding of Msg1, the gNB can distinguish between a PRACH for a new SSB set selection and a PRACH for an existing SSB selection. 【0284】 <<Combination of Embodiment B2-1 and Embodiment B2-2>> A combination of Embodiment B2-1 and Embodiment B2-2 may be supported. 【0285】 <<Constraints on RACH Resources>> (If the RACH resources for the existing SSB selection (existing RACH resources) and the RACH resources for the SSB set selection in Option 1 / 3 (additional RACH resources) are not shared,) constraints between the existing RACH resources and the additional RACH resources may be based on at least one of the following options: ◆Option 1: The existing RACH resources and the additional RACH resources are TDM. The existing RACH resources and the additional RACH resources may overlap in the frequency domain. ◆Option 2: The existing RACH resources and the additional RACH resources are FDM. The existing RACH resources and the additional RACH resources may overlap in the time domain. ◆Option 3: The existing RACH resources and the additional RACH resources are TDM and FDM. The existing RACH resources and the additional RACH resources may not overlap in the time domain and may not overlap in the frequency domain. The time resources and frequency resources may differ between existing RACH resources and additional RACH resources. 【0286】<<Variations>> The signaling architecture for configuring additional RACH resources may be similar to at least one signaling architecture for additional RACH configuration for PRACH repetition and additional RACH configuration for subband non-overlapping full duplex (SBFD), or it may be a repurposed version of at least one of additional RACH configuration for PRACH repetition and additional RACH configuration for SBFD. 【0287】 According to Embodiment B2, the UE can appropriately recognize the RO / preamble for SSB selection and the RO / preamble for SSB set selection. 【0288】 <Embodiment B3> With respect to multiple ROs for SSB set selection, at least one of the following options may be applied to whether one RAR is transmitted / received or multiple RARs are transmitted / received. 【0289】 <<Option 1>> The UE expects / assumes separate RAR reception for each RO. 【0290】 If a UE successfully detects one RAR, it may stop detecting RARs for the corresponding SSB set, or it may continue detecting all RARs for the SSB set. If RAR detection is stopped, even if multiple RARs are transmitted by the NW, only one RAR may be received by the UE. 【0291】 In each RAR for a given RO, the assumption of the QCL for the DMRS of PDCCH / PDSCH by the UE (QCL assumption / TCI state) may be at least one of the following options: ◆ Option 0: The QCL assumption may be the same as the SSB associated with the RO. ◆ Options 1 to 4 in Embodiment A4. 【0292】 If multiple RAR windows overlap for multiple RARs, option 2 or option 4 may be applied. 【0293】A separate RAR window may be maintained / run for each RAR. Multiple RAR windows may be based on one of the following options 1x: 【0294】 ◆Option 1a: Multiple RAR windows overlap. 【0295】 ◆Option 1b: Multiple RAR windows do not need to overlap. Each RAR window may start after the RAR window corresponding to the previous SSB index has stopped / ended. 【0296】 Multiple RAR windows may be sorted in ascending or descending order of their corresponding SSB indexes (starting from the lowest SSB index or starting from the highest SSB index). 【0297】 RAR windows may be set / exist / started for each CC / frequency / carrier / cell group / PCI / SSB / SSB set. Multiple SSBs may be transmitted on multiple CCs / frequencies, and multiple SSB sets may be transmitted on multiple CCs. One SSB set may correspond to one cell group. Multiple cell groups may correspond to multiple different CCs / frequencies. In assumption 2, one SSB may correspond to one PCI. Multiple RA procedures may be executed on multiple CCs / frequencies. Multiple PRACHs may be transmitted on multiple CCs / frequencies. Multiple RAR windows may exist on multiple CCs / frequencies. In option 1a, multiple RAR windows on multiple CCs / frequencies may overlap. 【0298】 The preamble power ramping counter and power ramping procedure may be independent for each SSB / RO, or they may be common to multiple SSBs / ROs within a single SSB set. 【0299】 <<Option 2>> The UE expects / assumes that multiple ROs will receive one RAR. 【0300】 Option 2 may be based on at least one of the following options 2x. 【0301】 ◆Option 2a: The RAR window starts after the end of the last Msg1 associated with multiple SSB indices within the corresponding SSB set. 【0302】 ◆Option 2aa: The RAR window starts after the end of the last RO associated with multiple SSB indexes in the corresponding SSB set. 【0303】 ◆Option 2b: The RAR window starts after the end of the first Msg1 associated with multiple SSB indices in the corresponding SSB set. 【0304】 ◆Option 2ba: The RAR window starts after the completion of the first RO associated with multiple SSB indexes within the corresponding SSB set. 【0305】 In one RAR reception, the assumption of QCL by UE for DMRS of PDCCH / PDSCH (QCL assumption / TCI state) may be at least one of the following options: ◆Options 1 to 5 in Embodiment A4. 【0306】 <<Example of Option 1 / 2>> In the example in Figure 18, three sets of candidate ROs are associated with SSB #0, #2, and #3, respectively. Msg1 is sent using some of the ROs from each set. 【0307】 In the example of option 1a, the three RAR windows corresponding to SSB #0, #2, and #3 start in ascending order of SSB index and overlap. Each RAR window starts after the end of its corresponding RO. 【0308】 In the example of option 1b, the three RAR windows corresponding to SSB #0, #2, and #3 start in ascending order of SSB index and do not overlap. Each RAR window starts after the end of its corresponding RO. 【0309】Similarly, in the example in Figure 19, three sets of candidate ROs are associated with SSB #0, #2, and #3, respectively. Msg1 is sent using some of the ROs from each set. 【0310】 In the example of option 2a, one RAR window corresponding to SSB#0, #2, and #3 starts after the end of the last of the three Msg1s corresponding to SSB#0, #2, and #3. 【0311】 In the example of option 2aa, one RAR window corresponding to SSB #0, #2, and #3 starts after the end of the last of the three ROs corresponding to SSB #0, #2, and #3. 【0312】 In the example of option 2b, one RAR window corresponding to SSB#0, #2, and #3 starts after the end of the first of the three Msg1s corresponding to SSB#0, #2, and #3. 【0313】 In the example of option 2ba, one RAR window corresponding to SSB #0, #2, and #3 starts after the end of the first of the three ROs corresponding to SSB #0, #2, and #3. 【0314】 According to Embodiment B3, the gNB can appropriately transmit one or more RARs corresponding to the SSB set, and the UE can appropriately receive at least one of those one or more RARs. 【0315】 <Embodiment B4> With respect to whether one Msg3 is sent / received or multiple Msg3s are sent / received in response to an SSB set selection, at least one of the following several options may be applied. 【0316】 <<Option 1>> In Embodiment B3, in the case where one RAR is received by the UE, there is one Msg3 scheduled by that RAR. The QCL assumption / TCI state of that Msg3 may follow Embodiment A5. 【0317】<<Option 2>> In Option 1 of Embodiment B3, in the case where multiple RARs are received by the UE, the UE behavior for Msg3 transmission may be based on at least one of the following several Options 2-x. 【0318】 ◆Option 2-1: One Msg3 transmission corresponds to one RAR selected by the UE. This RAR may be selected based on the UE implementation or based on rules defined in the specification. These rules may select the first or last RAR. 【0319】 ◆Option 2-2: The UE sends one Msg3. The UE expects / assumes that all RARs for a single SSB set point to the same Msg3 resource. In this case, the UE does not need to decode multiple RARs. 【0320】 ◆Option 2-3: The UE sends multiple Msg3s. Each Msg3 corresponds to one received RAR. Similar to RAR windows, one or more ra-ContentionResolutionTimers may be maintained / executed by the UE. 【0321】 In cases where multiple Msg3 resources indicated by different RARs overlap, the selection of the Msg3 resource used for actual transmission may depend on the UE implementation or be based on rules defined in the specification. Multiple Msg3s may be transmitted (overlapping or not overlapping) across multiple CCs / frequencies. 【0322】 The QCL assumption / TCI state of Msg3 may follow Embodiment A5. Multiple different QCL assumptions may be applied to multiple options from options 2-1 to 2-3. 【0323】In the example in Figure 20, the UE receives three RARs corresponding to SSB #0, #2, and #3 in that order. In option 2-1, if the rule selects the first RAR, the UE sends one Msg3 scheduled by the first RAR (the RAR corresponding to SSB #0). In option 2-2, the UE sends one Msg3 scheduled by at least one of the three RARs. In option 2-3, the UE sends three Msg3s, each scheduled by one of the three RARs. 【0324】 According to Embodiment B4, the UE can appropriately transmit one or more Msg3s corresponding to the SSB set, and the gNB can appropriately receive at least one of those one or more Msg3s. 【0325】 <Embodiment B5> With respect to whether one Msg4 is transmitted / received or multiple Msg3 are transmitted / received in response to an SSB set selection, at least one of the following several options may be applied. 【0326】 <<Option 1>> In Embodiment B4, when one Msg3 is transmitted by the UE, the UE expects / assumes to receive one Msg4. The QCL assumption / TCI state of Msg4 may follow Embodiment A6. 【0327】 <<Option 2>> In embodiment B4, in the case where multiple Msg3s are transmitted by the UE, the UE behavior for receiving Msg4 may be based on at least one of the following options 2-x. 【0328】 ◆Option 2-1: The UE expects / assumes to receive one Msg4. That Msg4 may correspond to any Msg3. 【0329】◆Option 2-2: The UE expects / anticipates receiving multiple Msg4s. Each Msg4 may correspond to one Msg3. If the UE successfully receives one Msg4, the UE may stop detecting other Msg4s and other RA procedures on the same CC / frequency / CC group (cell group). Multiple Msg4s may be transmitted (overlapping or not overlapping) on ​​multiple CCs / frequencies. 【0330】 The QCL assumption / TCI state of Msg4 may also follow Embodiment A6. Multiple different QCL assumptions may be applied to multiple options from options 2-1 to 2-3. 【0331】 According to Embodiment B5, the gNB can appropriately transmit one or more Msg4 corresponding to the SSB set, and the UE can appropriately receive at least one of the one or more Msg4. 【0332】 <Variations> In each embodiment, examples have been described in which SSB is applied as the RS associated with RO and the RS indicating QCL, but in addition to SSB, CSI-RS may also be applied. 【0333】 In each embodiment, an example in which CBRA is applied as the RA procedure has been described, but in addition to CBRA, CFRA may also be applied. 【0334】 In each embodiment, an example in which a 4-step RACH procedure is applied has been described, but in addition to the 4-step RACH, a 2-step RACH may also be applied. 【0335】 In each embodiment, the operation / parameters related to multiple PRACH iterations using multiple different beams (e.g., RACH setup / RA procedure) may be repurposed for the purpose of SSB set selection. 【0336】 The assumption of QCL in the reception by the UE of a specific channel / RS, which occurs after Msg4 and before subsequent settings / instructions / reports, may be based on at least one of options 1 to 7 in Embodiment A6. 【0337】The assumption of QCL in a UE transmission on a specific channel / RS, which follows Msg4 and precedes subsequent settings / instructions / reports, may be based on at least one of options 1 to 7 in Embodiment A6. 【0338】 A specific channel / RS may be, for example, a DCI format 0_0 (PDCCH) with a CRC scrambled by C-RNTI, a PUSCH (Msg5 PUSCH) scheduled by that DCI format 0_0, or a DMRS of that PDCCH / PUSCH. The PUSCH may carry an RRCSetupComplete confirming from the UE to the NW that the RRC setup is complete. Subsequent setup / instructions / reports may include reporting of UE capability information. 【0339】 In each embodiment, reception using multiple QCL assumptions / TCI states may be multi-TRP reception. In each embodiment, transmission using multiple QCL assumptions / TCI states / spatial relationships may be multi-TRP transmission or simultaneous transmission with multi-panel (STxMP). 【0340】 In this disclosure, at least one of Embodiments A1 to A6 may be referred to as Embodiment Ax. 【0341】 In this disclosure, at least one of Embodiments B0 to B5 may be referred to as Embodiment Bx. 【0342】 <Issue C> For self-free operation, the following are being considered: ◆ The UE selects an SSB set. ◆ Multiple ROs are associated with an SSB set [as in Embodiment Ax], and the UE transmits a PRACH on the RO corresponding to the selected SSB set. ◆ Multiple ROs are associated with an SSB set [as in Embodiment Bx], and the UE transmits multiple PRACHs on multiple ROs corresponding to multiple SSBs within the selected SSB set. 【0343】PRACH can be triggered by a PDCCH order. In the existing specification, a PDCCH order can indicate an SSB index, and the UE sends PRACH on the RO corresponding to the indicated SSB. 【0344】 Depending on whether multiple SSB sets are configured for PRACH transmission, an extension of the PDCCH order may be necessary. 【0345】 <Embodiment C1> This embodiment relates to issue C. 【0346】 In this embodiment, the following may be assumed: ◆ At least one of the following is enabled: ◆ Cell-free and any feature associated with cell-free. ◆ An SSB set configuration is provided for PRACH transmission. 【0347】 Within the PDCCH order that triggers RA, information from any of the following multiple options x may be indicated. 【0348】 ◆Option 1 An index of the SSB (SSB index) is indicated. As shown in the example in Figure 21, the DCI indicating the PDCCH order may include an SSB index field. Multiple indices of the SSB may be indicated. The DCI indicating the PDCCH order may include one or more SSB index fields. Multiple indices indicated by the PDCCH order may indicate multiple SSBs within a single SSB set. 【0349】 ◆Option 2 An SSB set index (SSB set index) is specified. As shown in the example in Figure 22, the DCI indicating the PDCCH order may include an SSB set index field. 【0350】 The size of the SSB set index field may be log2(N_SSBset), where N_SSBset may be the number of SSB sets to be set, or the maximum number of SSB sets that can be supported. 【0351】The SSB set index field may exist only if that PDCCH order triggers CFRA. 【0352】 The UE may determine whether the PDCCH order points to an SSB set index or an SSB index based on at least one of the following multiple options x. 【0353】 ◆Option 0 [By default], whether an SSB set index or an SSB index is specified is defined in the specification. 【0354】 ◆Option 1 Whether an SSB set index or an SSB index is specified is based on the upper layer signaling (configuration). 【0355】 ◆Option 2 Whether an SSB set index or an SSB index is specified is based on the instructions within that PDCCH order. Individual fields within that PDCCH order may also indicate whether an SSB set index or an SSB index is specified. 【0356】 ◆Option 3 Both the SSB set index and the SSB index are specified within the PDCCH order. The SSB index may point to an SSB within the specified SSB set. 【0357】 <<When a PDCCH order indicates an SSB set index>> If an SSB set index is indicated within a PDCCH order, the UE may determine the RO for PRACH transmission based on one of the following multiple options x: 【0358】 ◆Option 1 Based on Embodiment Ax, the UE transmits a PRACH on the RO associated with the specified SSB set index. This option may apply in cases where multiple ROs are associated with the SSB set. 【0359】◆Option 2 Based on Embodiment Bx, the UE sends multiple PRACHs on multiple ROs associated with multiple SSB indices in the specified SSB set index. This option may apply in cases where multiple ROs are associated with an SSB. 【0360】 <<When a PDCCH order indicates an SSB index>> If an SSB index is indicated within a PDCCH order, the UE may determine the RO for PRACH transmission based on one of the following multiple options x: 【0361】 ◆Option 1 The UE sends a PRACH on the RO associated with the specified SSB, [similar to the behavior of existing specifications]. This option may apply in cases where multiple ROs are associated with the SSB. In this option, the PRACH triggered by the PDCCH order may be sent to a single TRP. 【0362】 ◆Option 2 The UE sends a PRACH on the RO associated with the SSB set containing the indicated SSB. This option may apply if multiple ROs are associated with the SSB set. In this option, the indication of the SSB index may be considered an implicit indication of the SSB set; that is, an SSB index is indicated, which may mean an SSB set. 【0363】 ◆Option 3 The UE sends multiple PRACHs on multiple ROs associated with multiple SSB indices within the SSB set containing the indicated SSB. This option may apply when multiple ROs are associated with an SSB. In this option, the indication of an SSB index may be considered an implicit indication of an SSB set; that is, an SSB index is indicated, but that may mean an SSB set. 【0364】 According to Embodiment C1, the PDCCH order can specify the appropriate SSB / SSB set / RO. 【0365】<Variations> In each embodiment, the PDCCH order may include an indicator for non-serving X, where X may be a candidate cell ID, a group / cluster ID of TRP, or a TRP ID. In each embodiment, if the PDCCH order includes such an indicator, the SSB index / SSB set index may be considered an SSB index / SSB set index associated with the indicated non-serving X. 【0366】 In each embodiment, different options may be applied to the case where the PDCCH order triggers the CFRA and the case where the PDCCH order triggers the CBRA. 【0367】 In each embodiment, different options may apply depending on whether at least one of the SSB, the SSB set, and the PRACH is associated with the same TRP or a different TRP that sends the PDCCH order. 【0368】 In each embodiment, the QCL assumption / TCI state / TRP for the PDCCH order may refer to any of the multiple SSBs in the SSB set indicated by that PDCCH order. 【0369】 In each embodiment, the QCL assumption / TCI state / TRP for the PDCCH order does not have to refer to any of the multiple SSBs in the SSB set indicated by that PDCCH order. 【0370】<Supplement> <<Notification of Information to UE>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE (in other words, reception of any information from the BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE, RRC messages, LTE positioning protocol (LPP) messages), specific signals / channels (e.g., DCI, PDCCH, PDSCH, reference signals), or a combination thereof. 【0371】 When the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader. The MAC CE may be an extension of an existing MAC CE. For example, the MAC CE may introduce a new octet into an existing MAC CE. 【0372】 If the above notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI. The specific field may be an existing DCI field or a new DCI field. The RNTI may be an existing RNTI or a new RNTI. The format of the DCI may be an existing DCI format or a new DCI format. 【0373】 Furthermore, notification of any information to the UE in the above-described embodiment may be periodic, semi-persistent (triggered by the UE or gNB), or aperiodic (triggered by the UE or gNB). 【0374】In the embodiments described above, the UE may receive at least one piece of information (QCL information) from the NW from among several of the following QCL rules / QCL types: ◆ QCL type A (Doppler shift, Doppler spread, mean delay, and delay spread) ◆ QCL type B (Doppler shift and Doppler spread) ◆ QCL type C (Doppler shift and mean delay) ◆ QCL type D (spatial reception parameters) 【0375】 In the embodiments described above, the QCL source RS for each QCL type may be at least one of the following RSs: ◆SSB ◆CSI-RS with / without repetition ◆TRS ◆DMRS for PDCCH / PDSCH 【0376】 In the embodiments described above, information from the network may be set / instructed by the following methods: ◆ Common to multiple UEs, or individual to a UE ◆ Cell-specific, or common to multiple cells ◆ Per UE / Per CC / Per BWP / Per band / Per cell / Per cell group (CG) 【0377】 <<Notification of Information from UE>> Notification of any information from the UE to the NW in the embodiments described above (in other words, transmission / reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE, RRC messages, LPP messages), specific signals / channels (e.g., UCI, PUCCH, PUSCH, PRACH, reference signals), or a combination thereof. 【0378】 When the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader. The MAC CE may be an extension of an existing MAC CE. For example, the MAC CE may introduce a new octet into an existing MAC CE. 【0379】 If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH. 【0380】 Furthermore, the notification of any information from the UE in the above-described embodiments may be periodic, semi-persistent (triggered by the UE or gNB), or aperiodic (triggered by the UE or gNB). 【0381】 <<Regarding the application of each embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: ◆ A higher-layer parameter indicating the specific process / operation / control / assumption / information is set; ◆ The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter; ◆ The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS; ◆ A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported; ◆ The application of the specific process / operation / control / assumption / information is determined based on specific conditions. 【0382】The above-mentioned specific UE capabilities may represent at least one of the following: ◆ Supporting the above-mentioned specific processing / operation / control / assumption / information; ◆ Capabilities of each embodiment; ◆ Capabilities of each option in each embodiment, or the capabilities of a combination of multiple options in each embodiment; ◆ Capabilities of each choice in each embodiment, or the capabilities of a combination of multiple choices in each embodiment; ◆ The UE supports setting / selecting an SSB set (multiple SSBs); ◆ The UE supports selection between one SSB and one SSB set for PRACH transmission; ◆ The UE supports multiple Msg1 transmissions; ◆ The UE supports one or more RAR receptions; ◆ The UE supports one or more Msg3 transmissions; ◆ The UE supports one or more Msg4 receptions; ◆ The UE supports multiple parallel RA procedures; ◆ The UE supports receiving Msg2 / 4 using specific QCL assumptions / TCI states in any of the embodiments / options / choices. ◆The UE supports the transmission of Msg3 using a specific QCL assumption / TCI state in any embodiment / option / choice. ◆The UE supports the use of a specific QCL assumption / TCI state in any embodiment / option / choice for the transmission / reception of a specific channel / RS after the reception of Msg4. 【0383】 Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), a capability per feature set (FS) or feature set per component-carrier (FSPC), or a capability per functionality / model. 【0384】 Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)). 【0385】 If the above conditions are not met, UE / BS may follow the behavior specified in existing 3GPP releases. 【0386】 Information regarding whether one or more of the above embodiments / options / choices / examples apply / are used, or which of the above embodiments / options / choices / examples apply / are used, may be based on several of the following methods: ◆ The information is set by one or more higher layer parameters / RRC IEs. ◆ The information is determined by one or more relevant higher layer parameters / RRC IEs. ◆ The information is indicated by MAC CE / DCI. ◆ The information is based on one or more UE capabilities. ◆ The information is described / defined in the specification. ◆ The information is based on conditions described / defined in the specification. ◆ The information is determined by a combination of several of the above methods. For example, the information is determined by the setting / indication of higher layer parameters / MAC CE / DCIs and reported by UE capabilities. 【0387】 The above multiple embodiments / options / choices may be combined into a single embodiment / option / choice. 【0388】 In the embodiments described above, the measured RS may be a QCL source RS in an active TCI state / indicated / unified TCI state. 【0389】(Note) The following inventions are added with respect to one embodiment of the present disclosure (in particular, embodiment C1). <Note 1> A terminal having: a receiving unit that receives a physical downlink control channel (PDCCH) order that triggers a random access procedure, which includes identification information that indicates one or more synchronization signal blocks from a plurality of synchronization signal blocks; and a control unit that controls the transmission of a physical random access channel (PRACH) in one or more occasions associated with the identification information. <Note 2> The terminal according to Note 1, wherein the identification information is either the index of one of the plurality of synchronization signal blocks or the index of a set of the plurality of synchronization signal blocks. <Note 3> The terminal according to Note 1 or Note 2, wherein one or more occasions are associated with one of the plurality of synchronization signal blocks indicated by the identification information. <Note 4> The terminal according to any one of Notes 1 to 3, wherein one or more occasions are associated with a set of the plurality of synchronization signal blocks indicated by the identification information. <Supplement> The terminal may be a user terminal 20. The receiving unit may be a transmitting / receiving unit 220. The control unit may be a control unit 210. <Note A> A base station having: a transmitting unit that transmits a physical downlink control channel (PDCCH) order that triggers a random access procedure, which includes identification information that indicates one or more synchronization signal blocks among a plurality of synchronization signal blocks; and a control unit that controls the reception of a physical random access channel (PRACH) on one or more occasions associated with the identification information. <Supplement> The base station may be a base station 10. The transmitting unit may be a transmitting / receiving unit 120. The control unit may be a control unit 110. 【0390】 (Wireless Communication System) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any of the wireless communication methods according to the above embodiments of this disclosure, or a combination thereof. 【0391】Figure 23 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP). 【0392】 Furthermore, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like. 【0393】 In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN. 【0394】 The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))). 【0395】The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10. 【0396】 The wireless communication system 1 may utilize Multi Input Multi Output (MIMO). For example, one cell may be formed by one antenna / base station 10, or by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system. 【0397】 The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC). 【0398】Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2. 【0399】 Furthermore, the user terminal 20 may communicate in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD). 【0400】 Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 / Xn interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node. 【0401】 Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc. 【0402】The core network 30 may 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), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN. 【0403】 The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc. 【0404】 In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL). 【0405】The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods. 【0406】 In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, which is shared by each user terminal 20. 【0407】 Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20. 【0408】 User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH. 【0409】 Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH. 【0410】Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data. 【0411】 PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration. 【0412】 A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably. 【0413】 PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery acknowledgment information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell. 【0414】In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels. 【0415】 In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In the wireless communication system 1, the DL-RS may include a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. 【0416】 The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals. 【0417】 Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal). 【0418】(Base Station) Fig. 24 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transmission / reception unit 120, a transmission / reception antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140 may be provided. 【0419】 In this example, the functional blocks of the characteristic parts in the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each part described below may be omitted. 【0420】 The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, etc., which are described based on the common understanding in the technical field related to the present disclosure. 【0421】 The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission / reception, measurement, etc., using the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140. The control unit 110 may generate data, control information, a sequence, etc., to be transmitted as a signal, and transfer it to the transmission / reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of a communication channel, state management of the base station 10, management of radio resources, etc. 【0422】 The transmission / reception unit 120 may include a baseband unit 121, a Radio Frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmission / reception unit 120 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc., which are described based on the common understanding in the technical field related to the present disclosure. 【0423】The transmission / reception unit 120 may be configured as an integrated transmission / reception unit, or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of a transmission processing unit 1211 and an RF unit 122. The reception unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123. 【0424】 The transmission / reception antenna 130 can be composed of an antenna described based on the common knowledge in the technical field related to the present disclosure, such as an array antenna. 【0425】 The transmission / reception unit 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmission / reception unit 120 may receive the above-mentioned uplink channel, uplink reference signal, etc. 【0426】 The transmission / reception unit 120 may form at least one of a transmission beam and a reception beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc. 【0427】 The transmission / reception unit 120 (transmission processing unit 1211) may perform processing of the Packet Data Convergence Protocol (PDCP) layer, processing of the Radio Link Control (RLC) layer (e.g., RLC retransmission control), processing of the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, for example, and generate a bit string to be transmitted. 【0428】 The transmission / reception unit 120 (transmission processing unit 1211) may perform transmission processing such as channel encoding (which may include error correction encoding), modulation, mapping, filtering, discrete Fourier transform (Discrete Fourier Transform (DFT)) processing (if necessary), inverse fast Fourier transform (Inverse Fast Fourier Transform (IFFT)) processing, precoding, digital-to-analog conversion, etc. on the bit string to be transmitted, and output a baseband signal. 【0429】The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130. 【0430】 On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130. 【0431】 The transmitting / receiving unit 120 (receiving processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc. 【0432】 The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may also measure received power (e.g., Reference Signal Received Power (RSRP)), reception quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110. 【0433】The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20. 【0434】 In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140. 【0435】 The base station 10 may be separated into three elements: a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions. 【0436】 In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU. 【0437】 The transmitting / receiving unit 120 may transmit one or more synchronization signal blocks from a plurality of synchronization signal blocks corresponding to a plurality of pseudo-collocation (QCL) assumptions. The control unit 110 may control one or more random access procedures, including the transmission of a plurality of physical random access channels (PRACHs) corresponding to the plurality of synchronization signal blocks. 【0438】The transmitting / receiving unit 120 may transmit one or more synchronization signal blocks from a plurality of synchronization signal blocks corresponding to a plurality of pseudo-collocation (QCL) assumptions. The control unit 110 may control the reception of one or more physical random access channels (PRACHs) from a plurality of PRACHs corresponding to a plurality of synchronization signal blocks, and control the transmission of one or more random access responses (RARs) corresponding to the one or more PRACHs. 【0439】 (User Terminal) Figure 25 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided. 【0440】 In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted. 【0441】 The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure. 【0442】 The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220. 【0443】 The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure. 【0444】The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223. 【0445】 The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna. 【0446】 The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc. 【0447】 The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam. 【0448】 The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210 to generate a bit sequence to be transmitted. 【0449】 The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion, and output a baseband signal. 【0450】Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel. 【0451】 The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230. 【0452】 On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 230. 【0453】 The transmitting / receiving unit 220 (receiving processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc. 【0454】 The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210. 【0455】Incidentally, the measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. The channel measurement resources may be, for example, non-zero power (Non Zero Power (NZP)) CSI-RS resources. Also, the measurement unit 223 may derive interference measurements for CSI calculation based on interference measurement resources. The interference measurement resources may be at least one of NZP CSI-RS resources for interference measurement, CSI-interference measurement (Interference Measurement (IM)) resources, etc. Note that CSI-IM may also be referred to as CSI-interference management (Interference Management (IM)), or may be mutually read as zero power (Zero Power (ZP)) CSI-RS. In the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be mutually read. 【0456】 Incidentally, the transmission unit and the reception unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmission and reception unit 220 and the transmission and reception antenna 230. 【0457】 The transmission and reception unit 220 may receive a plurality of synchronization signal blocks (for example, a plurality of SSBs corresponding to a set of a plurality of SSB indexes) respectively corresponding to a plurality of quasi-collocation (QCL) assumptions (for example, beam / TRP / AP / TCI states). The control unit 210 may control one or more random access procedures including the transmission of a plurality of physical random access channels (PRACHs) respectively corresponding to the plurality of synchronization signal blocks. 【0458】 The one or more random access procedures may be a plurality of parallel random access procedures respectively corresponding to the transmission of the plurality of PRACHs. 【0459】 The control unit 210 may determine a plurality of resources for the transmission of the plurality of PRACHs based on at least one of a first setting for a random access procedure for one synchronization signal block and a second setting for the one or more random access procedures. 【0460】 The control unit 210 may determine a plurality of resources for the plurality of PRACH transmissions based on a first setting for a random access procedure to a single synchronization signal block and an index corresponding to a set of the plurality of synchronization signal blocks. 【0461】 The transmitting / receiving unit 220 may receive multiple synchronization signal blocks corresponding to multiple pseudo-collocation (QCL) assumptions. The control unit 210 may control the transmission of multiple physical random access channels (PRACHs) corresponding to the multiple synchronization signal blocks, and control the reception of one or more random access responses (RARs) corresponding to the multiple PRACHs. 【0462】 The control unit 210 may control the reception of one or more RARs using a plurality of RAR windows corresponding to each of the plurality of PRACHs. 【0463】 The one or more RARs may be multiple RARs. The control unit 210 may control the transmission of one or more messages 3 corresponding to at least one of the multiple RARs. 【0464】 The one or more RARs may be multiple RARs. The control unit 210 may control the reception of one or more messages 4 corresponding to at least one of the multiple RARs. 【0465】 (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software. 【0466】Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited. 【0467】 For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 26 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc. 【0468】 In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices. 【0469】 For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using one or more chips. 【0470】Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or control at least one of reading and writing data in the memory 1002 and storage 1003. 【0471】 The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001. 【0472】 Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. 【0473】The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be called a register, cache, or main memory. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure. 【0474】 The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device. 【0475】The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving unit 120 (220), transmitting / receiving antenna 130 (230), etc., may be implemented by the communication device 1004. The transmitting / receiving unit 120 (220) may be implemented with physically or logically separated transmitting unit 120a (220a) and receiving unit 120b (220b). 【0476】 The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel). 【0477】 Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device. 【0478】Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components. 【0479】 Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above. 【0480】 (Variations) Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc. 【0481】 A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology. 【0482】Here, the neurology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neurology may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain. 【0483】 A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology. 【0484】 A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using minislots may be called a PDSCH (PUSCH) mapping type B. 【0485】 Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable. 【0486】For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, and one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing a TTI may be called a slot, mini-slot, etc., instead of a subframe. 【0487】 Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this. 【0488】 TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI. 【0489】 Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled. 【0490】A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc. 【0491】 Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more. 【0492】 A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology. 【0493】 Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks. 【0494】 One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc. 【0495】Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol. 【0496】 A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP. 【0497】 A BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or more BWPs may be configured within a single carrier for a UE. 【0498】 At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP". 【0499】 The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways. 【0500】Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information. For example, wireless resources may be indicated by a predetermined index. 【0501】 The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements using these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way. 【0502】 The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof. 【0503】 Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes. 【0504】 Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices. 【0505】Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above. 【0506】 Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof. 【0507】 Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Elements (CEs). 【0508】 Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information). 【0509】 The determination may be made by a value represented by one bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value). 【0510】 Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name. 【0511】 Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium. 【0512】 The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations). 【0513】In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably. 【0514】 In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter. 【0515】 The above group may include, for example, at least one of the following: a spatial relationship group, a code division multiplexing (CDM) group, a reference signal (RS) group, a control resource set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group. 【0516】 Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably. 【0517】 Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably. 【0518】 Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably. 【0519】 In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset may be interpreted interchangeably. 【0520】 Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive. 【0521】In this disclosure, terms such as “Base Station (BS),” “wireless base station,” “fixed station,” “NodeB,” “eNB (eNodeB),” “gNB (gNodeB),” “access point,” “Transmission Point (TP),” “Reception Point (RP),” “Transmission / Reception Point (TRP),” “panel,” “cell,” “sector,” “cell group,” “carrier,” and “component carrier” may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell. 【0522】 A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station may be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage. 【0523】 In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information. 【0524】 In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably. 【0525】A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term. 【0526】 At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc. 【0527】 The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands. 【0528】 The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor. 【0529】Figure 27 shows an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60. 【0530】 The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user. 【0531】 The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU). 【0532】 Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc. 【0533】The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40. 【0534】 The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.). 【0535】 The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions. 【0536】The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40. 【0537】 The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20). 【0538】 The communication module 60 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include the information based on the above input. 【0539】 The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60). 【0540】 Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40. 【0541】 Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel, downlink channel, etc., may be interpreted as sidelink channel. 【0542】 Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above. 【0543】 In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof. 【0544】Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented. 【0545】 Each aspect / embodiment described in this disclosure is Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G). 【0546】In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on." 【0547】 Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way. 【0548】 The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to mean judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in tables, databases, or other data structures), ascertaining, etc. 【0549】 Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory). 【0550】Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above. 【0551】 Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….” 【0552】 In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased as "An apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station). 【0553】The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power. 【0554】 As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.” 【0555】 In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain. 【0556】 In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different." 【0557】 Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR. 【0558】In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural. 【0559】 In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest"). 【0560】 In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable. 【0561】In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information. 【0562】 In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably. 【0563】 Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

Claims

A receiver that receives a physical downlink control channel (PDCCH) order which includes identification information that indicates one or more synchronization signal blocks among multiple synchronization signal blocks and triggers a random access procedure, A terminal having a control unit that controls the transmission of a physical random access channel (PRACH) in one or more occasions associated with the aforementioned identification information. 　 The terminal according to claim 1, wherein the identification information is either the index of one of the plurality of synchronization signal blocks or the index of a set of the plurality of synchronization signal blocks. 　 The terminal according to claim 1, wherein the one or more occasions are associated with one of the plurality of synchronization signal blocks indicated by the identification information. 　 The terminal according to claim 1, wherein the one or more occasions are associated with the set of synchronization signal blocks indicated by the identification information. 　 The steps include receiving a physical downlink control channel (PDCCH) order which includes identification information that points to one or more synchronization signal blocks among multiple synchronization signal blocks and triggers a random access procedure, A wireless communication method for a terminal, comprising the step of controlling the transmission of a physical random access channel (PRACH) in one or more occasions associated with the aforementioned identification information. 　 A transmitter that sends a physical downlink control channel (PDCCH) order which includes identification information that indicates one or more synchronization signal blocks among multiple synchronization signal blocks and triggers a random access procedure, A base station having a control unit that controls the reception of a physical random access channel (PRACH) in one or more occasions associated with the aforementioned identification information.

Images