Terminal, wireless communication method, and base station

Abstract

A terminal according to an aspect of the present disclosure comprises: a reception unit that receives a set of a plurality of synchronization signals corresponding to a plurality of quasi co-location (QCL) assumptions; and a control unit that controls transmission of one or more physical random access channels (PRACHs) in one or more PRACH occasions corresponding to the set among a plurality of PRACH occasions, and determines one or more QCL assumptions for at least one of reception of a random access response based on the one or more PRACHs, transmission of a physical uplink shared channel based on the random access response, and reception of a physical downlink shared channel based on the physical uplink shared channel.

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] In future wireless communication systems (e.g., NR, 6G, etc.), it is being considered that terminals (user terminals, User Equipment (UE)) will communicate using unit areas (e.g., more transmission / reception points (TRPs) / access points (APs)) that are different from existing cells.

[0006] However, specific consideration of such communications has not been sufficient, and if consideration is insufficient, there is a risk that improvements in communication quality / communication throughput may be hindered.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that perform appropriate communication by utilizing 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 set of multiple synchronization signals corresponding to multiple quasi-co-location (QCL) assumptions; and a control unit that controls transmission of one or more physical random access channels (PRACHs) in one or more PRACH occasions corresponding to the set of PRACH occasions among multiple PRACH occasions, and determines one or more QCL assumptions for at least one of receiving a random access response based on the one or more PRACHs, transmitting a physical uplink shared channel based on the random access response, and receiving a physical downlink shared channel based on the physical uplink shared channel.

[0009] According to one aspect of the present disclosure, appropriate communication can be performed by utilizing a unit area different from existing cells.

[0010] FIGS. 1A-1C show an example of a cell-free configuration. FIG. 2 shows an example of a RACH common configuration. FIGS. 3A and 3B show an example of an association between an SSB and an RO. FIG. 4 shows an example of multiple SSBs detected by a UE in a cell-free system based on Assumption 1. FIG. 5 shows another example of multiple SSBs detected by a UE in a cell-free system based on Assumption 1. FIGS. 6A and 6B show an example of an association between an SSB set and an RO. FIG. 7 shows an example of an SSB set. FIG. 8 shows an example of an association between an SSB and an SSB set and an RO. FIGS. 9A and 9B show an example of an RAR window. FIG. 10 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 11 is a diagram showing an example of a configuration of a base station according to an embodiment. FIG. 12 is a diagram showing an example of a configuration of a user terminal according to an embodiment. FIG. 13 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. FIG. 14 is a diagram showing an example of a vehicle according to an embodiment.

[0011] (Cell-free) Existing wireless communication systems (e.g., 5G NR) have adopted a cellular system in which one cell is formed by one antenna / TRP. The area formed by the cell is fixed / static.

[0012] In addition, existing wireless communication systems (e.g., Rel. 16 and later) have introduced distributed multi-input multi-output (Distributed MIMO, e.g., multi-TRP using multiple transmission / reception points (TRPs)), which form a communication area using the coverage of multiple antennas / TRPs. Distributed MIMO allows simultaneous communication using multiple antennas / TRPs and communication using one antenna / TRP.

[0013] By adopting distributed MIMO, it is possible to create a more favorable line-of-sight environment and improve MIMO performance.

[0014] In co-located MIMO, one UE communicates with one antenna / TRP.

[0015] On the other hand, in distributed MIMO, one UE communicates with multiple antennas / TRPs in coordination.

[0016] In future wireless communication systems (e.g., Rel. 20 and later), the introduction of cell-free communication is being considered with the aim of further improving performance and energy efficiency through reducing interference between multiple antennas / TRPs, creating a line-of-sight environment for high-frequency use, improving frequency utilization efficiency throughout the system, and applying equal, high-quality communication to each user.

[0017] Self-Free may also be referred to as cell-free massive MIMO (mMIMO) or large-scale distributed MIMO (D-MIMO). Self-Free uses coherent cooperation of multiple access points. Self-Free may include at least one of ultra-dense deployment, scalable cooperation, user-centric clustering, super-carrier aggregation, and analog fronthaul. The user plane for cell-free may perform more flexible scheduling than existing scheduling. The control plane for cell-free may maintain some form of cell to facilitate signaling.

[0018] In cell-free, unlike conventional cellular systems, one area (which may be called a cell / sub-cell, etc.) may be formed by multiple antennas / TRPs. In other words, the area may mean a cell that does not depend on the position of the antenna.

[0019] In cell-free, the set of antennas / TRPs used to form a coverage area may be changed according to the needs of UEs. For example, the set of antennas / TRPs may be changed based on the number of UEs, the number of traffic, communication purposes (e.g., initial access, data communication, measurement, reporting, etc.), etc., rather than the coverage of the antennas / TRPs.

[0020] In other words, in cell-free, the coverage between multiple antennas / TRPs may overlap.

[0021] In cell-free mode, the direction in which 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.) is transmitted may be controlled for each antenna / TRP.

[0022] In addition, in cell-free, a central unit (CU) / distributed unit (DU) may be virtualized for each antenna / TRP, or each antenna / TRP may be managed by only the CU.

[0023] In existing cellular systems, each antenna / TRP forms a cell, and UEs communicate based on that cell.

[0024] On the other hand, in a cell-free system, an installed antenna / TRP does not form a fixed / static cell as in a cellular system. For example, in a cell-free system, one or more antennas / TRPs form a condition-dependent area. Therefore, in a cell-free system, each antenna / TRP may not correspond to the same physical cell ID, and the areas between multiple antennas / TRPs may overlap.

[0025] Self-regulation may be achieved, for example, by coordinating a set of antennas / TRPs controlled by a central control unit (e.g., CU).

[0026] In a cell-free system, a first cell (e.g., may be referred to as a cell / super cell / macro cell / large cell, etc.) with a fixed physical range like a cell in a 5G NR system, and a second cell (e.g., may be referred to as a subcell / area / micro cell / cell / small cell / second cell within the first cell, etc.) with a quasi-static / dynamic physical range that varies based on conditions may be formed. For example, the first cell may be referred to as a supercell to distinguish it from the second cell. When a supercell is composed 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 referred to as subcells to distinguish them from the first cell. When a supercell or a cell is composed 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 that is newly defined in a future wireless communication system, or may be a cell defined in an existing wireless communication system that is reused.

[0028] The configurations of the first cell and the second cell can be considered as follows: Assumption 1 and Assumption 2: The first cell is composed of multiple TRPs with one cell ID (physical cell ID (PCI)). The multiple TRPs can transmit and receive in coordination. Assumption 2: The first cell is composed of multiple TRPs (or sub-cells) with different cell IDs. The multiple TRPs / sub-cells can transmit and receive in coordination.

[0029] 1A shows an example of a cell-free configuration scenario 1. In this example, each TRP included in a first cell (supercell / cell) has the same PCI (PCI #0). Multiple TRPs can communicate cooperatively with one UE.

[0030] Figure 1B shows an example of cell-free configuration scenario 2. In this example, each TRP included in the first cell (super-cell / cell) has a different PCI (PCI #0 to #9). Multiple TRPs can communicate cooperatively with one UE.

[0031] Figure 1C shows an example of a variation of Assumption 2 of the cell-free configuration. In this example, a PCI is assigned to each TRP included in the first cell (supercell / cell). In this variation of Assumption 2, unlike Assumption 2, the same PCI may correspond to multiple TRPs. Multiple TRPs can communicate cooperatively with one UE. Multiple TRPs associated with the same PCI may be included in one cell.

[0032] Transmission / reception with TRP / subcell coordination may be based on at least one of the following schemes supported in NR: ◇ Transmission of a single TRP / subcell with dynamic TRP / subcell switching (single-TRP transmission). ◇ Joint transmission using multiple TRPs / subcells (multi-TRP joint transmission). The joint transmission may be based on a single DCI or multiple DCIs. The joint transmission may be non-coherent joint transmission (NCJT) or coherent joint transmission (CJT).

[0033] For cell-free, assuming ideal backhaul and tight coordination, in the joint transmission scheme, CJT may be prioritized over NCJT, and single DCI-based joint transmission may be prioritized over multi-DCI-based joint transmission.

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

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

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

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

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

[0039] The additional cell is a cell that has an additional PCI different from the PCI of the serving cell. The UE can receive / transmit a UE-dedicated channel (UE-dedicated CH) from the additional cell. On the other hand, the UE needs to be within the coverage of the serving cell to receive UE common channels (e.g., system information / paging / short messages). When the UE moves out of the coverage of the serving cell, a cell switch (e.g., a process such as RRC reconfiguration) is required due to handover (also called L3 mobility).

[0040] <Scenario 2> Scenario 2 applies L1 / L2 inter-cell mobility (e.g., L1L2-triggered mobility (LTM)). L1 / L2 inter-cell mobility enables the serving cell to be changed using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with a candidate cell / additional cell is possible without handover. Since handover requires RRC reconnection and creates a period when data communication is unavailable, applying L1 / L2 inter-cell mobility that does not require handover makes it possible to continue data communication 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 configuration, etc.) for a cell with a different PCI (additional cell / candidate cell / target serving cell) from the serving cell (current serving cell) for beam measurement / serving cell change. (2) The UE performs beam measurement of the cell using the different PCI and reports the measurement results to the serving cell. (3) The UE may receive the configuration of the cell with a different PCI (serving cell / candidate cell configuration) via higher layer signaling (e.g., RRC). That is, pre-configuration for the serving cell change may be performed. This configuration may be performed together with the configuration in (1) or separately. (4) Based on the above report, the TCI state of the cell with the different PCI may be activated via L1 / L2 signaling according to the serving cell change. The activation of the TCI state and the serving cell change may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts receiving / transmitting using the pre-configured UE-specific channel and TCI state.

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

[0043] In Rel. 18, the serving cell is switched by L1 / L2 (e.g., DCI / MAC CE). Here, a case is shown in which the serving cell is switched from PCI #1 corresponding to the current serving cell (e.g., current serving cell) to PCI #3 corresponding to the candidate cell (e.g., target serving cell) by L1 / L2 signaling.

[0044] The UE can receive / transmit common channels (e.g., system information / paging / short messages) / UE-dedicated channels to / from the new serving cell (target serving cell #3), which may cause the UE to move out of the coverage of the previous serving cell PCI #1.

[0045] (Initial Access Procedure) In the initial access procedure, the UE (RRC_IDLE mode) receives an SS / PBCH block (SSB), transmits Msg1 (PRACH / random access preamble / preamble), receives Msg2 (PDCCH, PDSCH including random access response (RAR)), transmits Msg3 (PUSCH scheduled by RAR UL grant), and receives Msg4 (PDCCH, PDSCH including UE contention resolution identity). After that, when an ACK for Msg4 is transmitted from the UE by the base station (network), an RRC connection is established (RRC_CONNECTED mode).

[0046] SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception. PSS detection includes detecting part 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 (part of) the SSB index within a half radio frame (5 ms). 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 recognizing whether the UE can camp on that cell (carrier).

[0047] SSB has a bandwidth of 20 RBs and a time of 4 symbols. The transmission period of SSB can be set to {5, 10, 20, 40, 80, 160} ms. In a half frame, multiple symbol positions of SSB are defined based on the frequency range (FR1, FR2).

[0048] The PBCH has a payload of 56 bits. N repetitions of the PBCH are transmitted within a period of 80 ms, where N depends on the SSB transmission period.

[0049] The system information consists of the MIB, RMSI (SIB1), and other system information (OSI) carried by the PBCH. SIB1 contains information for RACH setup and RACH procedures. The time / frequency resource relationship between the SSB and the PDCCH monitoring resource for SIB1 is configured by the PBCH.

[0050] A base station using beam correspondence transmits multiple SSBs using multiple beams for each SSB transmission period. The multiple SSBs have multiple SSB indices. When a UE detects an SSB, it transmits a PRACH in a PRACH occasion (RACH occasion, RO) associated with the SSB index and receives an RAR in an RAR window.

[0051] (PRACH Configuration) The serving cell configuration (ServingCellConfig) can include an UL configuration (UplinkConfig). The UplinkConfig can include a list of UL BWP configurations (BWP-Uplink). The BWP-Uplink can include a common UL BWP configuration (BWP-UplinkCommon). The BWP-UplinkCommon can include a common RACH configuration (RACH-ConfigCommon).

[0052] RACH-ConfigCommon is used to specify cell-specific random access parameters. As shown in Figure 2, RACH-ConfigCommon may include a generic RACH configuration (RACH-ConfigGeneric), a total number of RA preambles (totalNumberOfRA-Preambles), and a combination of 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-ConfigGeneric is used to specify random access parameters for both normal random access and beam failure recovery. RACH-ConfigGeneric may include a PRACH configuration index (prach-ConfigurationIndex) and message 1 FDM (msg1-FDM, the number of ROs FDMed in one time instance).

[0054] ssb-perRACH-OccasionAndCB-PreamblesPerSSB may include the number of SSBs per RO, N (e.g., N=1 / 8, oneEighth, one SSB associated with eight ROs) and the number of CB preambles per SSB, R.

[0055] The cell group configuration (CellGroupConfig) can include an SpCell configuration (SpCellConfig). The SpCellConfig can include a reconfiguration with synchronization (ReconfigurationWithSync, e.g., handover configuration). The ReconfigurationWithSync can include a dedicated RACH configuration (RACH-ConfigDedicated).

[0056] (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. If the cyclic redundancy check (CRC) of DCI format 1_0 is scrambled by the cell (C)-RNTI and the frequency domain resource assignment field is all 1, then DCI format 1_0 is for a random access procedure initiated by a PDCCH order, and the remaining fields are a random access preamble, a UL / supplementary uplink (SUL) indicator, a SS / PBCH index (SSB index), a PRACH mask index, and reserved bits (12 bits).

[0057] For a PRACH transmission triggered by a PDCCH order, the PRACH Mask Index field indicates the PRACH occasion of the PRACH transmission, where the PRACH Occasion (RACH Occasion, RO) is associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of the PDCCH order, if the value of the Random Access Preamble Index field is not zero.

[0058] (Random Access Preamble) For a Type 1 random access procedure (4-step RA type, RA procedure using messages 1 / 2 / 3 / 4), the UE may apply the number N of SS / PBCH blocks associated with one PRACH occasion (RACH occasion, RO) and the number R of CB preambles per SS / PBCH block per valid PRACH occasion via ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0059] In a Type 2 random access procedure (2-step RA type, RA procedure with messages A / B) with common PRACH occasion configuration as the Type 1 random access procedure, the UE is provided with the number N of SS / PBCH block indices associated with one PRACH occasion via ssb-perRACH-OccasionAndCB-PreamblesPerSSB and the number Q of contention-based preambles per SS / PBCH block index per valid PRACH occasion via msgA-CB-PreamblesPerSSB-PerSharedRO. PRACH transmissions may be on a subset of PRACH occasions associated with the same SS / PBCH block index within an SSB-RO mapping cycle for a UE that is provided with a PRACH mask index via msgA-SSB-SharedRO-MaskIndex.

[0060] In a Type 2 random access procedure involving the configuration of a different PRACH occasion from the Type 1 random access procedure, the UE is provided with the number N of SS / PBCH block indices associated with one PRACH occasion, and if provided, the number R of CB preambles per SS / PBCH block index per valid PRACH occasion via msgA-CB-PreamblesPerSSB-PerSharedRO, otherwise the number R of contention-based preambles per SS / PBCH block index per valid PRACH occasion via ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0061] In the random access procedure associated with the feature combination indicated by FeatureCombinationPreambles, the UE is provided with the number N of SS / PBCH block indices associated with one PRACH occasion, if ssb-perRACH-OccasionAndCB-PreamblesPerSSB or msgA-ssb-perRACH-OccasionAndCB-PreamblesPerSSB is provided, and is provided with the number S of CB preambles per SS / PBCH block index per valid PRACH occasion, via startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition. PRACH transmissions may be on a subset of PRACH occasions associated with the same SS / PBCH block index within an SSB-RO mapping cycle, for UEs that are provided with a PRACH mask index via ssb-SharedRO-MaskIndex.

[0062] For a Type 1 random access procedure, or for a Type 2 random access procedure with PRACH occasion configuration 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 indices associated with SS / PBCH block index for each valid PRACH occasion, starting with preamble index 0. If N>=1, R CB preambles with consecutive indices associated with SS / PBCH block index n (0≦n≦N−1) for each valid PRACH occasion, starting with preamble index n·N. preamble total It starts with / N, where 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 that involves the configuration of a PRACH occasion independent of the Type 1 random access procedure. preamble total is a multiple of N.

[0063] Starting from frame 0, the association period for mapping SS / PBCH blocks to PRACH occasions is N Tx SSB The UE selects the smallest value in the set determined by the PRACH configuration period according to the relationship (defined in the specification) between the PRACH configuration period and the associated period (number of PRACH configuration periods) such that N SS / PBCH block indices are mapped to a PRACH occasion at least once in that associated period, where N SS / PBCH block indices are selected from the values ​​of ssb-PositionsInBurst in SIB1 or in the common serving cell configuration. 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 are not mapped to an SS / PBCH block index, then no SS / PBCH block index is mapped to that set of PRACH occasions or PRACH preambles. An association pattern period includes one or more association periods and is determined such that the pattern between PRACH occasions and SS / PBCH block indices repeats at most every 160 ms. If there is a PRACH occasion that is not associated with an SS / PBCH block index after an integer number of association periods, that PRACH occasion is not used for PRACH.

[0064] For PRACH transmissions triggered by higher layers (PRACH transmissions not triggered by a PDCCH order), if ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex, which indicates the PRACH occasion for the PRACH transmission associated with the selected SS / PBCH block index.

[0065] PRACH occasions are mapped consecutively for each corresponding SS / PBCH block index. The indexing of PRACH occasions indicated by the mask index value is reset for each mapping cycle of consecutive PRACH occasions for each SS / PBCH block index. In the first available mapping cycle, the UE selects for PRACH transmission the PRACH occasion indicated by the PRACH mask index value for the indicated SS / PBCH block index.

[0066] For a given preamble index, the ordering of PRACH occasions is as follows: First, by increasing frequency resource index for PRACH occasions that are frequency multiplexed (at the same time resource index), Second, by increasing time resource index for PRACH occasions that are time multiplexed within a PRACH slot, Third, by increasing PRACH slot index.

[0067] For PRACH transmissions triggered upon request from higher layers, if csirs-ResourceList is provided, the value of ra-OccasionList indicates a list of PRACH occasions for the PRACH transmission, where the PRACH occasions are associated with the selected CSI-RS index indicated by csi-RS. The indexing of the PRACH occasions indicated by ra-OccasionList is reset for each associated pattern period.

[0068] For PRACH configuration 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.

[0069] The value of the PRACH mask index value (msgA-SSB-SharedRO-MaskIndex) is associated with the allowed PRACH occasions (PRACH occasion index values) of the SSB.

[0070] Figure 3A shows an example (mapping 1) of association of PRACH occasions (RACH occasions, ROs) and beams (SSBs / CSI-RSs) based on the upper layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. If ssb-perRACH-OccasionAndCB-PreamblesPerSSB indicates [oneHalf,n16] (the number of SSBs per RO, N = 1 / 2, the number of preambles per SSB, R = 16) and msg1-FDM is 4, four ROs are FDM-multiplexed 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 SSB 0. Thus, when N < 1, one SSB is mapped to multiple ROs. This increases the RO capacity per beam.

[0071] 3B shows another example (mapping 2) of association of ROs and beams based on the upper layer parameters ssb-perRACH-OccasionAndCB-PreamblesPerSSB. ssb-perRACH-OccasionAndCB-PreamblesPerSSB indicates [four,n16] (N=4, R=16), msg1-FDM indicates 4, N preamble totalIf is 64, four ROs are FDM-multiplexed at one time instance, 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 to #3. SSB #0 is associated with preamble indexes #0 to #15, SSB #1 is associated with preamble indexes #16 to #31, SSB #2 is associated with preamble indexes #32 to #47, and SSB #3 is associated with preamble indexes #48 to #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 based on the received PRACH.

[0072] The random access preamble can only be transmitted in the time resources specified in the random access configuration of the specification, which 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 higher layer parameter prach-ConfigurationIndex or, if configured, by msgA-PRACH-ConfigurationIndex. In the specification, each value of the PRACH configuration index is associated with at least one of the following: preamble format, x and y in n_f (frame number) mod x = y, subframe number, starting symbol, number of PRACH slots in a subframe, number of time-domain PRACH occasions in a PRACH slot N_t^RA,slot, and PRACH duration N_dur^RA.

[0073] Depending on whether PRACH repetition is applicable to a scenario, different types of RACH procedures may be triggered for different purposes. The type of RACH 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) request, 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.; four-step RACH; two-step RACH.

[0074] In the present disclosure, the mapping cycle, the SSB-RO mapping cycle, and the mapping cycle from SS / PBCH block index to PRACH occasion may be read interchangeably.

[0075] (SSB / CSI-RS selection: MAC protocol specification / Random Access Resource selection) If the RA_TYPE is set to 4-step RA, the MAC entity performs the following actions:

[0076] - If an RA procedure is initiated for SpCell beam failure recovery, and the beam failure recovery timer (beamFailureRecoveryTimer) is running or not set, and CFRA resources for the beam failure recovery request associated with at least one SSB / CSI-RS are explicitly provided by RRC, and at least one of the following is available: one or more SSBs with SS-RSRP exceeding the SS-RSRP threshold (rsrp-ThresholdSSB) among the multiple SSBs in the candidate beam RS list (candidateBeamRSList) and one or more CSI-RSs with CSI-RSRP exceeding the CSI-RSRP threshold (rsrp-ThresholdCSI-RS) among the multiple CSI-RSs in the candidate beam RS list (candidateBeamRSList), the MAC entity shall perform the following operations. The MAC entity selects one SSB with an SS-RSRP that exceeds rsrp-ThresholdSSB from among the SSBs in the candidateBeamRSList, or one CSI-RS with a CSI-RSRP that exceeds rsrp-ThresholdCSI-RS from among the CSI-RSs in the candidateBeamRSList. If a CSI-RS is selected and there is an RA-PreambleIndex associated with the selected CSI-RS, the MAC entity sets the preamble index (PREAMBLE_INDEX) to the ra-PreambleIndex corresponding to the SSB in the candidateBeamRSList 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 failure recovery request.

[0077] Otherwise, if ra-PreambleIndex is explicitly provided by the PDCCH and is not 0b000000, the MAC entity shall set PREAMBLE_INDEX to the signaled ra-PreambleIndex and select the SSB signaled by the PDCCH.

[0078] Otherwise, if CFRA resources associated with multiple SSBs are explicitly provided in the dedicated RACH configuration (rach-ConfigDedicated) and at least one SSB with SS-RSRP above rsrp-ThresholdSSB is available, the MAC entity shall select one SSB from the associated SSBs with SS-RSRP above rsrp-ThresholdSSB and set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB.

[0079] Otherwise, if CFRA resources associated with multiple CSI-RSs are explicitly provided in the dedicated RACH configuration (rach-ConfigDedicated) and at least one CSI-RS with a CSI-RS SRP above rsrp-ThresholdCSI-RS is available among the multiple CSI-RSs, the MAC entity shall select one CSI-RS with a CSI-RS SRP above rsrp-ThresholdCSI-RS among its associated multiple CSI-RSs and set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected CSI-RS.

[0080] - Otherwise, if an RA procedure is initiated for an SI request and RA resources for the SI request have been explicitly provided by RRC, the MAC entity shall: -- If at least one SSB with SS-RSRP above rsrp-ThresholdSSB is available, the MAC entity shall select one SSB with SS-RSRP above rsrp-ThresholdSSB. -- Otherwise, the MAC entity shall select any SSB. -- The MAC entity shall select an RA preamble corresponding to the selected SSB from the RA preambles examined according to the RA-PreambleStartIndex (ra-PreambleStartIndex) and set PREAMBLE_INDEX to the selected RA preamble.

[0081] - Otherwise (CBRA preamble selection), the MAC entity shall: -- If at least one SSB with SS-RSRP above rsrp-ThresholdSSB is available, the MAC entity shall select one SSB with SS-RSRP above rsrp-ThresholdSSB. -- Otherwise, the MAC entity shall select any SSB.

[0082] - 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 those corresponding to the selected SSB within the association period given by ra-AssociationPeriodIndex within si-RequestPeriod that are allowed by the constraint given by ra-ssb-OccasionMaskIndex (if it is set) (the MAC entity selects a PRACH occasion randomly with equal probability from consecutive PRACH occasions corresponding to the selected SSB).

[0083] Otherwise, if the SSB is selected, the MAC entity performs the following steps: -- If a set of RA resources associated with a Msg1 repetition is selected for this RA procedure, the MAC entity determines the set of next available PRACH occasions corresponding to the selected SSB, for the Msg1 repetition number applied to this RA procedure, as allowed by the constraints given by ra-ssb-OccasionMaskIndex (if it is set) or ssb-SharedRO-MaskIndex (if it is set). (The MAC entity selects PRACH occasions randomly with equal probability from among consecutive PRACH occasions corresponding to the selected SSB and the Msg1 repetition number of this RA procedure, regardless of the FR2 UL gap; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps 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 allowed by the constraints given by ra-ssb-OccasionMaskIndex (if set) or ssb-SharedRO-MaskIndex (if set). (The MAC entity selects a PRACH occasion randomly with equal probability from consecutive PRACH occasions according to the procedure corresponding to the selected SSB, regardless of the FR2 UL gap; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected SSB.)

[0084] Otherwise, 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 allowed by the constraints given by the ra-ssb-OccasionMaskIndex (if it is set) (the MAC entity selects a PRACH occasion randomly with equal probability from consecutive PRACH occasions corresponding to the selected CSI-RS and QCL'd SSB, regardless of the FR2 UL gap; the MAC entity may take into account the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected CSI-RS and QCL'd SSB). -- Otherwise, the MAC entity determines the next available PRACH occasion from the PRACH occasions in the ra-OccasionList corresponding to the selected CSI-RS (the MAC entity selects a PRACH occasion randomly with equal probability from PRACH occasions occurring simultaneously on different subcarriers corresponding to the selected CSI-RS, regardless of the FR2 UL gap; the MAC entity may take into account the possibility of measurement gaps and MUSIM gaps occurring when determining the next available PRACH occasion corresponding to the selected CSI-RS).

[0085] That is, in the Msg1 repetition, the MAC entity determines the set of allowed PRACH occasions by the mask index value.

[0086] 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 controlled by higher layers (the RAR window). The window starts at the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for the 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 period corresponds to the SCS for the Type 1-PDCCH CSS set. The length of the window, based on the SCS for the Type 1-PDCCH CSS set, is provided by the ra-responseWindow in number of slots.

[0087] If a UE detects DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI and with the least significant bits (LSBs) of the system frame number (SFN) field in that DCI format being the same as the LSBs of the SFN with which the UE transmitted the PRACH, and the UE receives a transport block in the corresponding PDSCH, the UE may assume the same DMRS antenna port QCL properties for 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 with which it receives the PDCCH with that DCI format 1_0.

[0088] If a UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for the SpCell, the UE may assume that the PDCCH containing that 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 a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for the secondary cell, the UE may assume the DMRS antenna port QCL properties of the CORESET associated with the Type 1-PDCCH CSS set for reception of the PDCCH containing that DCI format 1_0.

[0089] The RAR UL grant may include at least one of 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.

[0090] In single-cell operation or operation with carrier aggregation within the same frequency band, if the qcl-Type set in the 'type D' properties of a DMRS for monitoring a PDCCH in a Type 1-PDCCH CSS set is not set to the same as the qcl-Type set in the 'type D' properties of a DMRS for monitoring a PDCCH in a Type 0 / 0A / 0B / 2 / 3-PDCCH CSS set or in a USS set, and that PDCCH or associated PDSCH overlaps by at least one symbol with a PDCCH or associated PDSCH that the UE monitors in the Type 1-PDCCH CSS set, then the UE shall not assume to monitor a PDCCH in a Type 0 / 0A / 0B / 2 / 3-PDCCH CSS set or in a USS set.

[0091] If a UE is provided with one or more search space sets by PDCCH-Config, corresponding to one or more of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, peiSearchSpace, ra-SearchSpace, and a CSS set, 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, for an RNTI from any of these RNTIs, the UE shall not process information from more than one DCI format with CRC scrambled using that RNTI per slot.

[0092] (Msg3 PUSCH) The UE transmits a transport block on the PUSCH scheduled by the RAR UL grant in the corresponding RAR message. The UE transmits a transport block on the PUSCH in slot n+k2+Δ+2. μ ・K cell,offset The PUSCH is transmitted within K cell,offsetThe offset is provided by CellSpecific_Koffset, and if not provided, K cell,offset =0.

[0093] 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 spacing μPUSCH. Δ is an additional subcarrier spacing-specific slot delay time value for the first transmission of the PUSCH scheduled by the RAR, which is specific to the PUSCH subcarrier spacing μPUSCH and is applied in addition to K2.

[0094] The following are signaled in SIB1 sent by the base station: Priority of each feature (priority, featurePriorities-r17). This priority is used by the UE to decide which FeatureCombinationPreamble to use if a feature is mapped to more than one. Additional RO configuration. The configuration includes available features (which may be associated with multiple features), RA resources (e.g., preamble index), and mask index to distinguish ROs.

[0095] The UE decides which RO to use depending on its capabilities.

[0096] SIB1 includes ServingCellConfigCommonSIB, which includes UplinkConfigCommonSIB, which includes BWP-UplinkCommon (UL BWP common configuration).

[0097] BWP-UplinkCommon may include a RACH common configuration (RACH-ConfigCommon or MsgA-ConfigCommon) and an additionalRACH-ConfigList-r17 (an additional RACH configuration list). The additionalRACH-ConfigList-r17 may include a rsrp-ThresholdMsg3-r17 (a threshold value).

[0098] The RACH common configuration may include FeatureCombinationPreambles. FeatureCombinationPreambles associates one set of preambles (partition) with one feature combination. FeatureCombinationPreambles may include FeatureCombination (feature combination configuration), 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). A partition is given by the index of the first preamble and the number of preambles.

[0099] The PRACH mask index explicitly configures the available ROs. Using the relationship between the PRACH mask index and the allowed PRACH occasions for SSB (MAC protocol specification / PRACH mask index value table), at least one of the PRACH occasion indexes 1 to 8 can be configured.

[0100] (Contention Resolution) When Msg 3 is transmitted, the MAC entity follows actions 1 to 4 below. [Action 1] If Msg 3 is transmitted over a non-terrestrial network, the MAC entity starts the ra-ContentionResolutionTimer and restarts it at each HARQ retransmission in the first symbol after the end of Msg 3 plus the UE estimate of the UE-gNB RTT. [Action 2] Otherwise, if the Msg 3 transmission (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 Msg 3 transmission. [Action 3] Otherwise, the MAC entity starts or restarts the ra-ContentionResolutionTimer in the first symbol after the end of the Msg 3 transmission. [Operation 4] The MAC entity monitors the PDCCH while the ra-ContentionResolutionTimer is running, regardless of the possibility of a measurement gap occurring.

[0101] Step 4 (Msg4) in the RA procedure for Rel. 16 NR follows the following step 4 operations:

[0102] Step 4 Operation: If the UE is not provided with a C-RNTI, in response to a PUSCH transmission scheduled by the RAR UL grant, the UE schedules a PDSCH containing the UE contention resolution identity and attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding TCI-RNTI. In response to receiving a PDSCH containing the UE contention resolution identity, the UE transmits HARQ-ACK information in 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 N_T,1 symbols, 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.

[0103] When detecting a DCI format in response to a PUSH transmission scheduled by an RAR UL grant or in response to a corresponding PUSH retransmission scheduled by DCI format 0_0 with CRC scrambled by the TC-RNTI provided in the corresponding RAR message, the UE may assume that the PDCCH carrying that DCI format has the same DM-RS antenna port quasi co-location (QCL) properties as the DM-RS antenna port QCL properties for the SS / PBCH block used by the UE for PRACH association, regardless of whether the UE has been provided with the TCI state for the CORESET in which the UE received the PDCCH with that DCI format.

[0104] (Analysis) The concept / scenario / definition of cell-free includes the evolution of MIMO and mobility.

[0105] 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, lower layer mobility, and flexible TRP clustering (high-density TRP, clustering of cells / TRPs for mobility, control and data may be separated).

[0106] Selfry may include at least one of the following features: ◆ Denser TRP placement (per cell), which can achieve better SNR for all UEs, including those in traditional cell edge areas. ◆ Flexible (e.g., UE-centric) TRP clustering for cell construction, which can reduce the impact of interference between multiple cells / TRPs on UEs. ◆ Low layer mobility, which can consider more TRPs within a single clustering, enabling seamless mobility through L1 level operation.

[0107] Selfie may include at least one of several concepts:

[0108] ◆ Concept 1: Selection / transmission of multiple TRPs / APs is performed for data only (physical (PHY) / MAC layer). There is no significant impact on the specifications regarding cell selection, initial access, and mobility. Existing LTMs may be reused or extended. The main impact on the specifications is the extension of L1 measurement / reporting or SRS transmission for selection of multiple TRPs / APs, and the extension of CSI measurement / reporting or SRS transmission for CSI of clustering of TRPs / APs (different from their selection), etc.

[0109] ◆ Concept 2: Selection / transmission of multiple TRPs / APs for both control (RRC) and data. There are impacts to the specifications regarding cell selection, initial access, and mobility, in addition to L1 / CSI for data in Concept 1. For example, the UE may need to access multiple TRPs / APs in initial access, and SSB / SI / RACH may be redesigned. The clustering of multiple TRPs / APs for control and data may be the same or different. There may be impacts to the specifications in the case of clustering more than one DU / CU that are not geographically co-located.

[0110] In another aspect, CCs within different frequencies (CA scenarios) may be considered, and multiple TRPs / APs may be processed separately for each CC or jointly across multiple CCs (e.g., clustering and scheduling may jointly consider the TRP dimension and the CC dimension).

[0111] In Concept 2, if a UE needs to access multiple TRPs / APs in initial access, how to redesign the initial access procedure to achieve this has not been fully considered. From the viewpoint of network deployment, each TRP / AP can have one or more SSBs for coverage.

[0112] As described above, the operation regarding SSB / initial access in a cell-free environment has not been sufficiently considered, and if this operation is not sufficiently considered, there is a risk that communication quality / throughput will deteriorate.

[0113] Therefore, the inventors have studied the initial access method and conceived the following embodiments.

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

[0115] (Various Reinterpretations) In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Furthermore, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding (ignoring) the word in the meaning of the entire sentence. Note that "( )" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

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

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

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

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

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

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

[0122] In the present disclosure, ceil(x), ceiling function, and ceiling function may be interchangeable. In the present disclosure, floor(x), floor function, and floor function may be interchangeable. In the present disclosure, sqrt(x), square root of x, and root x may be interchangeable. In the present disclosure, x mod y, mod(x, y), mod function, and modulo operation may be interchangeable. In the present disclosure, Σ i=M M+N-1 f(i),Σ i=MM+N-1 f i , f(i) or f(i) for i=M, M+1, ..., M+N-1 i summation, f(M)+f(M+1)+...+f(M+N-1), f M +f M+1 +...+f M+N-1 , may be read interchangeably. C(n, k) is the number of combinations of selecting k values ​​from n values ​​(combinatorial coefficient), binomial coefficients, n C k , C n k , may be read as interchangeable. In the present disclosure, x / / y and floor(x / y) may be read as interchangeable.

[0123] In this disclosure, A b , A_b, Ab, and A with b added to the bottom right may be read interchangeably. c , A^c, and the notation of A with c added to the upper right may be read interchangeably. b c , A_b^c, and the notation in which b is added to the bottom right of A and c is added to the top right of A may be read interchangeably. ~ may be expressed by adding 〜 to the x, or may be referred to as x tilde. - may be represented by placing a - on top of the x, or may be referred to as an x-bar. ＾ may be represented by placing a ^ above the x, or may be called an x-hat.

[0124] In the present disclosure, FR may be, for example, at least one of FR1, FR2, FR2-1, FR2-2, FR3, sub-terahertz, and terahertz. In the present disclosure, the frequency range corresponding to FR1 may be 410-7125 MHz. In the present disclosure, FR2 may include FR2-1 and FR2-2, and the frequency range corresponding to FR2-1 may be 24250-52600 MHz, and the frequency range corresponding to FR2-1 may be 52600-71000 MHz.

[0125] 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

[0126] In the present disclosure, the base station (BS), TRP, AP, gNB, and network (NW) may be interchangeable.

[0127] In the present disclosure, receiving, detecting, monitoring, and selecting may be read interchangeably.

[0128] In the present disclosure, the terms cell, area, coverage, first cell, and second cell may be interchangeable. In the present disclosure, the terms first cell, super cell, multiple TRPs / APs, and set / group of TRPs / APs may be interchangeable. In the present disclosure, the terms second cell, sub cell, multiple TRPs / APs, and set / group / subset / cluster of TRPs / APs may be interchangeable.

[0129] In the present 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 particular RSRP, and beam may be read interchangeably.

[0130] In the present disclosure, QCL Type A, "Doppler shift, Doppler spread, mean delay, and delay spread" may be read as interchangeable. In the present disclosure, QCL Type B, "Doppler shift and Doppler spread" may be read as interchangeable. In the present disclosure, QCL Type C, "Doppler shift and mean delay" may be read as interchangeable. In the present disclosure, QCL Type D, "spatial reception parameters" may be read as interchangeable.

[0131] In the present disclosure, RAC / RACH / PRACH / preamble resources, (PRACH) preamble, occasion, RACH occasion (RO), PRACH occasion, time / frequency instance, time / frequency resource (for PRACH), RACH / PRACH / preamble / mask setting / index may be read interchangeably.

[0132] In the present disclosure, the terms time instance, time occasion, time domain location, time position, PRACH occasion, PRACH slot, period, period / offset, symbol / slot / subframe / frame / time domain (index) may be interchangeable. In the present disclosure, the terms frequency instance, frequency occasion, frequency domain location, frequency location, subcarrier / RE / RB / CC / time domain (index) may be interchangeable.

[0133] In the present disclosure, Msg1 (Message 1, Msg.1), RACH, PRACH (preamble), and random access preamble may be interchangeable. In the present disclosure, Msg2 (Message 2, Msg.2), RAR, at least one of RAR PDSCH and a PDCCH scheduling the same, and RAR UL grant may be interchangeable. In the present disclosure, Msg3 (Message 3, Msg.3), a PUSCH carrying an RRC setup request message, and Msg3 PUSCH may be interchangeable. In the present disclosure, Msg4 (Message 4, Msg.4), a PDSCH carrying an RRC setup message, Msg4 PDSCH, and a PDSCH received after Msg3 PUSCH transmission may be interchangeable.

[0134] In the present disclosure, 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.

[0135] (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 super-cell / cell has multiple TRPs / APs. Multiple TRPs / APs (that super-cell / 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 (transmitted in two directions and received by two UEs).

[0136] Figure 5 shows another example of multiple SSBs detected by a UE in a cell-free system based on Assumption 1. In this example, one super-cell / cell has multiple TRPs / APs. Multiple TRPs / APs (that super-cell / 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 but in different directions).

[0137] In a cell-free system based on assumption 2, an SSB is associated with a supercell (supercell ID) instead of a PCI, and multiple SSBs may be associated with different PCIs.

[0138] First Embodiment A set of SSB indices (SSB set) may be associated with one or more PRACH occasions (RACH occasions, ROs). Multiple SSB indices within each SSB set may be provided by an SIB / RRC IE. Association settings between each SSB set and one or more ROs may be provided by the SIB / RRC IE.

[0139] One SSB set may be associated with multiple TRPs / APs within one supercell / cell / area / coverage. While legacy UEs detect one SSB during initial access, UEs supporting this embodiment may detect multiple SSBs (within one SSB set). Based on the multiple SSBs, a random access procedure may be performed for multiple TRPs / APs (multiple PRACHs / preambles may be transmitted for multiple SSBs / TRPs / APs) (multiple TRPs / APs corresponding to multiple SSBs may be clustered). Compared to legacy specifications, the number of SSBs detected by a UE and the number of ROs that can be utilized by the UE may be increased.

[0140] According to this embodiment, a UE can connect to multiple TRPs / APs at the initial access stage, and can obtain cell-free effects / gains.

[0141] In the existing specifications (as explained above in "Initial Access Procedure"), one SSB is associated with one or more ROs, and the parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB is used for this configuration. In this embodiment, the existing SSB may be replaced with a set of SSB indices (SSB set).

[0142] The number of SSB indices in each SSB set may be based on at least one of several options:

[0143] Option 1: The number of SSB indices in each SSB set is the same.

[0144] ◆ Option 2 The number of SSB indices in each SSB set is different. The number of SSB indices in an SSB set may be related to the corresponding coverage or TRP number.

[0145] The SSB indexes in the SSB set may be determined by the UE or may be determined through cooperation between the NW and the UE.

[0146] The association between an SSB set and one or more PRACH occasions may be determined based on at least one of several options:

[0147] ◆ Option 3 Similar to the existing parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB, which indicates the combination of the number of SSBs per PRACH occasion N and the number of CB preambles per SSB R, Set and the number of CB preambles per SSB set (per valid PRACH occasion) R SetNew parameters indicating the combination of ssbSet-perRACH-OccasionAndCB-PreamblesPerSSBSet (e.g., ssbSet-perRACH-OccasionAndCB-PreamblesPerSSBSet).

[0148] ◆ 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 indicating the number of SSB indices (e.g., M) in the SSB set. For example, the number of SSB sets per PRACH occasion, N Set = "Number of SSBs per PRACH occasion N" / M*α, where α may be defined in the specification. For example, the number of CB preambles per SSB set R S = "Number of CB preambles per SSB R" * M * β, where β may be defined in the specification. The larger the number of SSB indices in the SSB set, the larger the number of ROs / preambles associated with the SSB set may be.

[0149] When one SSB association to one RO and one SSB set association to one RO can be configured, new parameters can be defined to distinguish them from the existing parameters.

[0150] (If the number of SSB sets per PRACH occasion is less than 1,) a portion / subset within one SSB set may be associated with one RO. For example, an SSB set may include SSBs #1 to #4, with SSBs #1 and #2 (SSB subset #1) associated with RO #1 and SSBs #3 and #4 (SSB subset #2) associated with RO #2.

[0151] The UE may receive the existing parameters / new parameters via SIB / RRC IE.

[0152] The SSB indices in the different SSB sets may be based on at least one of several options:

[0153] ◆ Option 5 One SSB index can only exist in one SSB set.

[0154] ◆ Option 6: One SSB index can exist in multiple SSB sets. As a constraint, two different SSB sets can have at most X identical SSB indices. For example, X can be 1.

[0155] The association period may ensure that every SSB set is mapped to a PRACH occasion at least once within an association period.

[0156] In the above Option 3, the association of the SSB set and the RO may be represented by at least one of the following examples:

[0157] ◆ Figure 6A shows ssbSet-perRACH-OccasionAndCB-PreamblesPerSSBSet=[oneHalf,n16] (N Set =1 / 2,R Set 16), msg1-FDM=4. In this example, four ROs are FDMed 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 to #15.

[0158] ◆ 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= 64. In this example, four ROs are FDM'd at 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 to #15. SSB set #1 is associated with preambles #16 to #31. SSB set #2 is associated with preambles #32 to #47. SSB set #3 is associated with preambles #48 to #63.

[0159] Each SSB set in these examples may be an SSB set based on Option 6, as in the example of 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.

[0160] Second Embodiment The relationship between SSB and RO may include both an association between SSB and RO (SSB-RO association similar to that in the existing specifications) and a new association between SSB set and RO (SSB set-RO association in the first embodiment). The two associations may be configured by SIB / RRC IE. The two associations may be configured by the same (joint) parameters or by separate parameters.

[0161] According to this embodiment, both the SSB-RO association and the SSB set-RO association can be properly configured.

[0162] Multiple ROs may be first mapped to one or more SSBs and then to one or more SSB sets.

[0163] For the SSB-RO association case and the SSB set-RO association case, the same or different parameters may be configured for at least one of the number of associated SSBs / SSB sets per RO and the number of associated preambles per SSB / SSB set.

[0164] An association period may ensure that every SSB and every SSB set is mapped to a PRACH occasion at least once within an association period.

[0165] Other RACH related parameters may be provided in common or separately for the SSB-RO association case and the SSB set-RO association case, such as parameters indicating at least one of RO resource configuration, power, RAR window, and contention resolution window, or parameters related to at least one of msg1-FDM, preambleReceivedTargetPower, preambleTransMax, powerRampingStep, ra-ResponseWindow, ra-ContentionResolutionTimer, and prach-RootSequenceIndex.

[0166] In the first embodiment, the RACH-related parameters may also be introduced for PRACH configuration for SSB set-RO association.

[0167] FIG. 8 shows the case where ssb-perRACH-OccasionAndCB-PreamblesPerSSB=oneHalf,n16 (N=1 / 2,R=16), ssbSet-perRACH-OccasionAndCB-PreamblesPerSSBSet=1,n16 (N Set =1,R Set16), msg1-FDM=4. In this example, four ROs are FDM-multiplexed at one time instance. Among the multiple ROs, the first ROs (first ROs) (in order of RO index, or in order of frequency index followed by time index) may be mapped to one or more SSBs (in order of SSB index, from SSB #0 to #3), and the next ROs (second ROs) (in order of RO index, or in order of frequency index followed by time index) may be mapped to one or more SSB sets (in order of SSB set index, 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.

[0168] <Embodiment 3> The UE may select one SSB set (from multiple SSB sets) for PRACH transmission based on measurement results for multiple SSB indices for each SSB set (if multiple SSB sets are received). According to this embodiment, the UE can select an appropriate SSB set for PRACH transmission. The rules for selecting an SSB (within an SSB set) may be based on the "SSB / CSI-RS selection" described above.

[0169] The rules for the selection of the SSB set may be based on at least one of several options:

[0170] Option 1: An SSB set is selected if all SSBs in the set have RSRP values ​​above a threshold, which may be configured by RRC or defined in a specification.

[0171] Option 2: An SSB set is selected if at least Y SSBs in the set have RSRP values ​​above a threshold. For example, Y may be 2. The threshold may be configured by RRC or defined in a specification.

[0172] Option 3: An SSB set is selected if the average RSRP of all SSBs in the set exceeds a threshold, which may be set by the RRC or defined in a specification.

[0173] ◆ Option 4 If the RSRP of the best SSB in an SSB set exceeds threshold 1 and the RSRP of the worst SSB in the SSB set exceeds threshold 2, the SSB set is selected. Threshold 2 may be less than threshold 1. Threshold 1 / 2 may be set by RRC or defined in the specification.

[0174] The rule for selecting one SSB and one SSB set (in the case of embodiment 2) may be based on at least one of UE capabilities and UE RRM measurement results of multiple SSB indices per SSB set.

[0175] Fourth Embodiment After a PRACH transmission, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding random access (RA)-RNTI during a window controlled by higher layers for RAR detection. After a PRACH transmission, the UE's assumption of the QCL of the PDCCH / PDSCH DMRS for RAR detection (receive beam for the PDSCH carrying the RAR and the PDCCH scheduling it) may be based on at least one of the following options:

[0176] ◆ Option 1: The QCL assumption is the same as the QCL assumption of the lowest SSB index in the SSB set for the associated PRACH. The NW may transmit one RAR using the beam with the lowest SSB index in the SSB set.

[0177] ◆ Option 2 The QCL assumption is the same as the QCL assumption of one or more specific SSB indices in the SSB set for the associated PRACH. The specific one or more SSB indices may be determined based on rules defined in the specification. For example, the specific one or more SSB indices may be the lowest SSB index and the highest SSB index. The NW may transmit multiple RARs using different beams corresponding to the specific SSB indices in the SSB set.

[0178] ◆ Option 3 The QCL assumption is the same as the QCL assumption of 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 different time-frequency resources within the RAR window.

[0179] ◆ 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 NW may transmit multiple RARs using multiple beams corresponding to all SSB indices in the SSB set in the same time-frequency resource.

[0180] ◆ Option 5 The RAR window (time / length) is divided into N parts based on a rule defined in the specification or an SIB / RRC IE. Here, N may be the number of SSB indices in the SSB set. In multiple parts of the RAR window, the UE may assume different QCLs for RAR reception. The association between each part and an SSB index may be based on a rule defined in the specification. The rule may associate the N parts with SSB indices in SSB index order. The network is free to select one part / SSB index for RAR transmission, taking into account different loads on different beams.

[0181] The transmit beam of the PRACH based on the QCL of the SSB index in the SSB set may correspond to the receive beam (QCL) of the RAR.

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

[0183] Figure 9B shows an example of one RAR window with N = 3 in option 5. In this example, one RAR window is divided into three parts, and the UE assumes three different QCLs for RAR reception in the three parts.

[0184] Depending on the QCL type assumed for RAR reception, any of options 1 to 5 may be applied. The same option may be applied to 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.

[0185] The multiple RARs to which multiple QCL assumptions are respectively applied may be TDM / FDM / CDM / SDM / SFN.

[0186] According to this embodiment, the UE can receive the RAR corresponding to the SSB set using the appropriate QCL.

[0187] <Embodiment 5> 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 depends 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.

[0188] The QCL assumption for Msg3 PUSCH retransmissions may be based on at least one of the following options: ◆ Option 0 / 1 / 2 as described above. The same option may be applied to the initial transmission and the retransmission, or different options may be applied. ◆ Option 3: The QCL assumption is the same as the QCL for the initial transmission.

[0189] In option 1, if a UE transmits multiple PRACHs using multiple QCL assumptions, the UE may transmit multiple initial transmissions / retransmissions of Msg3 PUSCHs using the multiple QCL assumptions. In option 2, if a UE receives multiple RARs using multiple QCL assumptions, the UE may transmit multiple initial transmissions / retransmissions of Msg3 PUSCHs using the multiple QCL assumptions.

[0190] Multiple Msg3 PUSCHs (initial transmission / retransmission) to which multiple QCL assumptions are respectively applied may be TDM / FDM / CDM / SDM / SFN.

[0191] According to this embodiment, the UE can transmit the Msg3 PUSCH corresponding to the SSB set using an appropriate QCL.

[0192] <Embodiment 6> A UE may detect a DCI format in response to a PUSCH transmission scheduled by an RAR UL grant or a corresponding PUSCH retransmission scheduled by DCI format 0_0 with a CRC scrambled by the temporary cell (TC)-RNTI provided in the corresponding RAR message, and receive a Msg4 PDSCH scheduled by that DCI format. After Msg3, the UE's assumption of the QCL of the DMRS of the PDCCH carrying that DCI format for the Mgg.4 PDSCH (the receive beam for the Mgg.4 PDSCH and the PDCCH that schedules it) may be based on at least one of the following options: ◆ Options 0 / 1 / 2 / 3 / 4 in embodiment 4. ◆ 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 QCL assumption is the same as the QCL of the transmitted Msg3.

[0193] In option 5, if a UE transmits multiple PRACHs using multiple QCL assumptions, respectively, the UE may receive multiple Msg4 PDSCHs using the multiple QCL assumptions. In option 6, if a UE receives multiple RARs using multiple QCL assumptions, respectively, the UE may receive multiple Msg4 PDSCHs using the multiple QCL assumptions, respectively. In option 7, if a UE transmits Msg3 PUSCHs using multiple QCL assumptions, respectively, the UE may receive multiple Msg4 PDSCHs using the multiple QCL assumptions, respectively.

[0194] Multiple Msg4 PDSCHs to which multiple QCL assumptions are respectively applied may be TDM / FDM / CDM / SDM / SFN.

[0195] According to this embodiment, the UE can receive Msg4 corresponding to the SSB set using the appropriate QCL.

[0196] <Variations> In each embodiment, an example has been described in which an SSB is applied as an RS associated with an RO and an RS indicating a QCL, but a CSI-RS may be applied in addition to an SSB.

[0197] In each embodiment, an example in which CBRA is applied as the RA procedure has been described, but CFRA may also be applied in addition to CBRA.

[0198] In each embodiment, an example in which a four-step RACH is applied as the RA procedure has been described, but in addition to the four-step RACH, a two-step RACH may also be applied.

[0199] The assumption of QCL upon reception by the UE of a particular channel / RS after Msg4 and before subsequent configuration / indication / reporting may be based on at least one of options 1 to 7 in embodiment 6.

[0200] The assumption of QCL in transmission by the UE of a particular channel / RS after Msg4 and before subsequent configuration / indication / reporting may be based on at least one of options 1 to 7 in embodiment 6.

[0201] The specific channel / RS may be, for example, DCI format 0_0 (PDCCH) with CRC scrambled by the C-RNTI, a PUSCH (Msg5 PUSCH) scheduled by the DCI format 0_0, or a DMRS of the PDCCH / PUSCH. The PUSCH may carry RRCSetupComplete, which confirms that the RRC setup is complete from the UE to the NW. Subsequent configuration / instruction / report may be a report of UE capability information.

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

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

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

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

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

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

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

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

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

[0211] <<Regarding Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-mentioned embodiments may be applied (used) when one or more of the following conditions are met: - a higher layer parameter indicating the specific processes / operations / controls / assumptions / information is configured; - the specific processes / operations / controls / assumptions / information is determined based on related higher layer parameters; - the specific processes / operations / controls / assumptions / information is specified / activated / triggered by a MAC CE / DCI / UCI / resource / channel / RS; - a specific UE capability indicating (or related to) the specific processes / operations / controls / assumptions / information is reported or supported; - the application of the specific processes / operations / controls / assumptions / information is determined based on specific conditions.

[0212] The specific UE capability may indicate at least one of the following: - Supporting the specific process / operation / control / assumption / information; - Capability of each embodiment; - Capability of each option in each embodiment, or a combination of multiple options in each embodiment; - Capability of each option in each embodiment, or a combination of multiple options in each embodiment; - The UE supporting one PRACH occasion (RO) associated with a set of SSB indices; - The UE supporting selection between one SSB and one SSB set for PRACH transmission; - The UE supporting reception of Msg2 / 4 using a certain QCL assumption, as in one option in embodiment 4 / 6; - The UE supporting transmission of Msg3 using a certain QCL assumption, as in one option in embodiment 5; - The UE supporting transmission / reception of a specific channel / RS after reception of Msg4 using a certain QCL assumption, as in one option in embodiment 4 / 5 / 6.

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

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

[0215] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.

[0216] (Supplementary Notes) The following inventions are supplementary notes regarding Embodiment 1, Embodiment 2, and Embodiment 3 of the present disclosure. [Supplementary Note 1] A terminal having: a receiver unit that receives multiple sets of synchronization signals corresponding to multiple quasi-co-location (QCL) assumptions; and a controller that controls transmission of one or more physical random access channel (PRACH) in one or more PRACH occasions corresponding to the sets among multiple PRACH occasions. [Supplementary Note 2] The terminal described in Supplementary Note 1, wherein the receiver unit receives information indicating at least one of the number of sets per PRACH occasion, the number of PRACH occasions per set, and the number of synchronization signals in the set, and the controller determines the one or more PRACH occasions based on the sets and the information. [Supplementary Note 3] The terminal described in Supplementary Note 1 or Supplementary Note 2, wherein the multiple PRACH occasions include PRACH occasions corresponding to one or more synchronization signals and PRACH occasions corresponding to one or more sets. [Supplementary Note 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the control unit selects the set from the plurality of sets based on a plurality of measurement results corresponding to the plurality of sets.

[0217] (Supplementary Notes) The following inventions are supplementary notes with respect to Embodiment 4, Embodiment 5, and Embodiment 6 of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver unit that receives a set of multiple synchronization signals corresponding to multiple quasi-co-location (QCL) assumptions; and a controller that controls transmission of one or more physical random access channel (PRACH) in one or more PRACH occasions corresponding to the set among multiple PRACH occasions, and determines one or more QCL assumptions for at least one of receiving a random access response based on the one or more PRACHs, transmitting a physical uplink shared channel based on the random access response, and receiving a physical downlink shared channel based on the physical uplink shared channel. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the controller determines one or more QCL assumptions for the random access response based on one or more synchronization signals in the set. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the controller determines one or more QCL assumptions for the physical uplink shared channel, based on any of the plurality of QCL assumptions and one or more QCL assumptions for the random access response. [Supplementary Note 4] The terminal according to any of Supplementary Note 1 to Supplementary Note 3, wherein the controller determines one or more QCL assumptions for the physical uplink shared channel, based on any of the plurality of QCL assumptions, one or more QCL assumptions for the random access response, and one or more QCL assumptions for the physical uplink shared channel.

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

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

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

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

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

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

[0224] 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 may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be composed of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static / dynamically variable physical range. In this case, the wireless communication system 1 may be called a cell-free system.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0263] 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 functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement the functions of the PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer.

[0264] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

[0265] The transceiver 120 may transmit one or more synchronization signals from a set of synchronization signals corresponding to a plurality of quasi-co-location (QCL) scenarios, and the controller 110 may control reception of one or more physical random access channel (PRACH) occasions corresponding to the set of PRACH occasions.

[0266] The transceiver unit 120 may transmit one or more synchronization signals from a set of multiple synchronization signals corresponding to multiple quasi-co-location (QCL) assumptions. The controller 110 may control reception of one or more physical random access channel (PRACH) occasions corresponding to the set of multiple PRACH occasions, and determine one or more QCL assumptions for at least one of transmission of a random access response based on the one or more PRACHs, reception of a physical uplink shared channel based on the random access response, and transmission of a physical downlink shared channel based on the physical uplink shared channel.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0285] The transceiver unit 220 may receive a set of synchronization signals (e.g., a set of SSBs (indexes)) corresponding to a set of SSB indices (e.g., a set of SSBs corresponding to a set of SSB indices) corresponding to a set of quasi-co-location (QCL) scenarios (e.g., beam / TRP / AP / TCI states). The controller 210 may control transmission of one or more physical random access channel (PRACH) occasions (e.g., ROs) corresponding to the set of PRACH occasions (e.g., Msg1 / random access preambles).

[0286] The transceiver 220 may receive information indicating at least one of a number of sets per PRACH occasion, a number of PRACH occasions per set, and a number of synchronization signals in the set, and the controller 210 may determine the one or more PRACH occasions based on the sets and the information.

[0287] The control unit 210 may determine one or more candidates for a set, and determine the set from the one or more candidates based on the mask index.

[0288] The control unit 210 may select the set from the plurality of sets based on a plurality of measurement results corresponding to the plurality of sets.

[0289] The transceiver unit 220 may receive a plurality of sets of synchronization signals corresponding to a plurality of quasi-co-location (QCL) assumptions. The controller 210 may control transmission of one or more physical random access channel (PRACH) occasions corresponding to the set of PRACH occasions among a plurality of PRACH occasions, and may determine one or more QCL assumptions for at least one of reception of a random access response (e.g., a RAR PDCCH / PDSCH) based on the one or more PRACHs, transmission of a physical uplink shared channel (e.g., an Msg3 PUSCH) based on the random access response, and reception of a physical downlink shared channel (e.g., an Msg4 PDCCH / PDSCH) based on the physical uplink shared channel.

[0290] The controller 210 may determine one or more QCL assumptions for the random access response based on one or more synchronization signals in the set.

[0291] The control unit 210 may determine one or more QCL assumptions for the physical uplink shared channel based on either the plurality of QCL assumptions or one or more QCL assumptions for the random access response.

[0292] The control unit 210 may determine one or more QCL assumptions for the physical uplink shared channel based on any of the plurality of QCL assumptions, one or more QCL assumptions for the random access response, and one or more QCL assumptions for the physical uplink shared channel.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0307] In addition, the devices included in the core network 30 (for example, network nodes that provide NF) may also be realized by the above-mentioned functional block / hardware configuration.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0333] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / specifying (or relating to) the value of the any information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0349] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A terminal having: a receiver unit that receives a set of multiple synchronization signals corresponding to multiple quasi-co-location (QCL) assumptions; and a controller that controls transmission of one or more physical random access channels (PRACHs) in one or more PRACH occasions corresponding to the set of multiple PRACH occasions, and determines one or more QCL assumptions for at least one of receiving a random access response based on the one or more PRACHs, transmitting a physical uplink shared channel based on the random access response, and receiving a physical downlink shared channel based on the physical uplink shared channel.

2. The terminal of claim 1, wherein the control unit determines one or more QCL assumptions for the random access response based on one or more synchronization signals in the set.

3. The terminal according to claim 1, wherein the control unit determines one or more QCL assumptions for the physical uplink shared channel based on either the plurality of QCL assumptions or one or more QCL assumptions for the random access response.

4. The terminal according to claim 1, wherein the control unit determines one or more QCL assumptions for the physical uplink shared channel based on any of the plurality of QCL assumptions, one or more QCL assumptions for the random access response, and one or more QCL assumptions for the physical uplink shared channel.

5. A wireless communication method for a terminal, comprising: receiving a set of multiple synchronization signals corresponding to multiple quasi-co-location (QCL) assumptions; and controlling transmission of one or more physical random access channels (PRACHs) in one or more PRACH occasions corresponding to the set among multiple PRACH occasions, and determining one or more QCL assumptions for at least one of receiving a random access response based on the one or more PRACHs, transmitting a physical uplink shared channel based on the random access response, and receiving a physical downlink shared channel based on the physical uplink shared channel.

6. A base station comprising: a transmitter unit that transmits one or more synchronization signals among a set of multiple synchronization signals corresponding to multiple quasi-co-location (QCL) assumptions; and a controller that controls reception of one or more physical random access channel (PRACH) occasions in one or more PRACH occasions corresponding to the set among a plurality of PRACH occasions, and determines one or more QCL assumptions for at least one of transmitting a random access response based on the one or more PRACHs, receiving a physical uplink shared channel based on the random access response, and transmitting a physical downlink shared channel based on the physical uplink shared channel.

Images