Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a reception unit that receives settings for transmission of a plurality of physical random access channels (PRACH) corresponding to each of a plurality of spatial domain transmission filters; and a control unit that determines a spatial domain transmission filter to be used for uplink transmission on the basis of any one of a specific PRACH among the plurality of PRACHs, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) associated with a contention resolution identifier. According to one mode of the invention, the coverage range of the random access process can be improved.

Description

Technical Field

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

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been standardized to achieve even higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) has been standardized to further enhance the capacity and sophistication of LTE (Release 8 and 9 of the Third Generation Partnership Project (3GPP (registered trademark))).

[0003] Successor systems to LTE (e.g., also referred to as 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later) are also under study.

[0004] Prior art literature

[0005] Non-patent literature

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

[0007] Problems to be solved by the invention

[0008] In future wireless communication systems (eg, NR), coverage improvement is being studied.

[0009] However, the random access procedure for improving coverage is not clear. If such a random access procedure is not clear, there is a concern that communication throughput may be reduced.

[0010] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that improve the coverage of a random access procedure.

[0011] Means for solving problems

[0012] A terminal according to one embodiment of the present disclosure includes: a receiving unit that receives settings for transmitting multiple physical random access channels (PRACHs) corresponding to multiple spatial domain transmit filters; and a control unit that determines a spatial domain transmit filter for uplink transmission based on any one of a specific PRACH, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier among the multiple PRACHs.

[0013] Effects of the Invention

[0014] According to one embodiment of the present disclosure, the coverage of the random access process can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 An example of RACH configuration information element is shown.

[0016] Figure 2A as well as Figure 2B An example of the association between PRACH timing and beam is shown.

[0017] Figure 3 An example of multiple PUCCH resource sets before dedicated PUCCH resource configuration is shown.

[0018] Figure 4 An example of Case 1 is shown.

[0019] Figure 5 An example of Case 2 is shown.

[0020] Figure 6 An example of Case 3 is shown.

[0021] Figure 7 An example of Case 4 is shown below.

[0022] Figure 8 This is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.

[0023] Figure 9 This is a diagram showing an example of the configuration of a base station according to one embodiment.

[0024] Figure 10 This is a diagram showing an example of the configuration of a user terminal according to an embodiment.

[0025] Figure 11 This is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment.

[0026] Figure 12 This is a diagram showing an example of a vehicle according to an embodiment. DETAILED DESCRIPTION

[0027] (TCI, spatial relation, QCL)

[0028] In NR, research is underway to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and coding) of at least one of a signal and a channel (expressed as signal / channel) in the UE based on the transmission configuration indication state (TCI state).

[0029] The TCI state may also refer to the TCI state applied to the downlink signal / channel. The TCI state applied to the uplink signal / channel may also be expressed as a spatial relation.

[0030] The TCI status refers to information related to Quasi-Co-Location (QCL) of signals / channels and can also be referred to as spatial reception parameters or spatial relation information. The TCI status can also be set for each channel or each signal for the UE.

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

[0032] In addition, the spatial reception parameters may also correspond to the UE's receive beam (e.g., receive analog beam), and the beam may also be determined based on spatial QCL. The QCL (or at least one element of QCL) in this disclosure may also be rewritten as sQCL (spatial QCL).

[0033] QCLs can also be specified in multiple types (QCL types). For example, four QCL types, namely types A to D, can be provided. It can be assumed that the same parameters (or parameter sets) in these four QCL types A to D are different. These parameters (also referred to as QCL parameters) are expressed as follows:

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

[0035] QCL type B (QCL-B): Doppler shift and Doppler spread,

[0036] QCL type C (QCL-C): Doppler shift and average delay,

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

[0038] The UE assumes that a certain Control Resource Set (CORESET), channel or reference signal is in a specific QCL relationship (e.g., QCL type D) with other CORESETs, channels or reference signals, which is also called QCL assumption.

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

[0040] The TCI status may also include, for example, information related to the quality of contact (QCL) between the target channel (in other words, the reference signal (RS) used for that channel) and other signals (for example, other RSs). The TCI status may also be set (indicated) via higher layer signaling, physical layer signaling, or a combination thereof.

[0041] The physical layer signaling may be, for example, downlink control information (Downlink Control Information (DCI))).

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

[0043] In addition, the RS that has a QCL relationship with the channel may be, for example, at least one of a synchronization signal block (Synchronization Signal Block (SSB)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a measurement reference signal (Sounding Reference Signal (SRS)), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called QRS).

[0044] The SSB is a signal block that includes at least one of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a broadcast channel (physical broadcast channel (PBCH)). The SSB may also be referred to as an SS / PBCH block.

[0045] The RS of QCL type X in the TCI state may also mean an RS in a QCL type X relationship with a certain channel / signal (DMRS), and the RS may also be called a QCL source of QCL type X in the TCI state.

[0046] (Unified / common TCI framework)

[0047] The unified TCI framework enables control of multiple (UL / DL) channels and RSs using a common framework. Unlike Rel. 15, which specifies TCI states and spatial relationships for each channel, the unified TCI framework allows for the designation of a common beam (common TCI state) and its application to all UL and DL channels, or for the application of a common beam for UL to all UL channels and a common beam for DL ​​to all DL channels.

[0048] One common beam for both DL and UL, or a common beam for DL ​​and a common beam for UL (two common beams overall) are under study.

[0049] The UE may also assume the same TCI state for both UL and DL (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set). The UE may also assume different TCI states for UL and DL (separate TCI state, independent TCI pool, UL independent TCI pool and DL independent TCI pool, independent common TCI pool, UL common TCI pool and DL common TCI pool).

[0050] MAC CE-based beam management (MAC CE-level beam indication) can also be used to align the default UL and DL beams. The default PDSCH TCI state can also be updated to match the default UL beam (spatial relationship).

[0051] DCI-based beam management (DCI-level beam indication) can also indicate a common beam / unified TCI state from the same TCI pool (joint common TCI pool, joint TCI pool, set) for both UL and DL. X (>1) TCI states can also be activated via MAC CE. The UL / DL DCI can also select one of the X activated TCI states. The selected TCI state can also be applied to both UL and DL channels / RSs.

[0052] A TCI pool (set) can be multiple TCI states configured via RRC parameters, or multiple TCI states (activated TCI state, activated TCI pool, set) activated via MAC CE within the multiple TCI states configured via RRC parameters. Each TCI state can also be a QCL-type A / D RS. SSB, CSI-RS, or SRS can also be configured as a QCL-type A / D RS.

[0053] The number of TCI states corresponding to each of one or more TRPs may also be specified. For example, the number N (≥1) of TCI states applied to UL channels / RSs (UL TCI states) and the number M (≥1) of TCI states applied to DL channels / RSs (DL TCI states) may also be specified. At least one of N and M may be notified, configured, or indicated to the UE via higher layer signaling or physical layer signaling.

[0054] In this disclosure, the notation N=M=X (where X is an arbitrary integer) may also mean that X UL and DL TCI states (corresponding to X TRPs) are notified, configured, or indicated to the UE (joint TCI state). Furthermore, the notation N=X (where X is an arbitrary integer) and M=Y (where Y is an arbitrary integer, and may also be Y=X) may also mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (corresponding to Y TRPs) are notified, configured, or indicated to the UE separately (i.e., independent TCI states).

[0055] For example, when N=M=1 is recorded, it may also mean notifying / setting / indicating a TCI state common to a UL and DL for a single TRP (joint TCI state for a single TRP) for the UE.

[0056] In addition, for example, when N=1 and M=1 is described, it may also mean that one UL TCI state and one DL TCI state for a single TRP (independent TCI state for a single TRP) are separately notified / set / indicated to the UE.

[0057] In addition, for example, when N=M=2 is recorded, it can also mean notifying / setting / indicating the TCI state common to multiple (two) ULs and DLs of multiple (two) TRPs (joint TCI state for multiple TRPs) for the UE.

[0058] In addition, for example, when N=2, M=2 is recorded, it can also mean notifying / setting / indicating multiple (two) UL TCI states and multiple (two) DL TCI states (independent TCI states for multiple TRPs) for the UE.

[0059] In the above examples, the case where the values ​​of N and M are 1 or 2 has been described, but the values ​​of N and M may be 3 or greater, or N and M may be different.

[0060] In Rel. 17, support for N=M=1 is under study. For example, RRC / MAC CE / DCI may be used to indicate a common beam (e.g., a beam) that is applied to multiple DL / UL channels / reference signals. Furthermore, other scenarios may be supported in Rel. 18 and beyond.

[0061] In a joint DL / UL TCI state (e.g., a Joint DL / UL TCI state), RRC parameters (information elements) configure multiple TCI states for both DL and UL. In this disclosure, the TCI states configured via RRC parameters may also be referred to as configured TCI states or configured TCI states (e.g., configured TCI states). A MAC CE may also activate multiple TCI states from the configured multiple TCI states. DCI may also indicate one of the multiple activated TCI states. In this disclosure, the TCI state indicated via DCI may also be referred to as an indicated TCI state or an indicated TCI state (e.g., an indicated TCI state).

[0062] The DCI can be either UL DCI (e.g., DCI used for PUSCH scheduling) or DL ​​DCI (e.g., DCI used for PDSCH scheduling). The indicated TCI state may also apply to at least one (or all) UL / DL channels / RSs. A single DCI may also indicate both UL TCI and DL TCI.

[0063] The indicated TCI state ID may be one TCI state applied to both UL and DL, or two TCI states applied to UL and DL respectively.

[0064] At least one of the multiple TCI states configured via RRC parameters and the multiple TCI states activated via MAC CE can also be referred to as a TCI pool (common TCI pool, joint TCI pool, or TCI state pool). The multiple TCI states activated via MAC CE can also be referred to as an activated TCI pool (activated common TCI pool).

[0065] In this disclosure, higher-layer parameters (RRC parameters) that configure multiple TCI states may also be referred to as configuration information for configuring multiple TCI states, or simply as "configuration information." Furthermore, in this disclosure, using DCI to indicate one of multiple TCI states may involve either receiving indication information included in the DCI indicating one of the multiple TCI states or simply receiving the "indication information."

[0066] In separate TCI states (e.g., Separate TCI (DL TCI state and UL TCI state)), RRC parameters configure multiple TCI states for both DL and UL (joint common TCI pool). A MAC CE may also activate multiple TCI states (activated TCI pools) from the configured multiple TCI states. Separate (independent) activated TCI pools for UL and DL may also be configured / activated.

[0067] DL DCI or a new DCI format may also select (indicate) more than one (for example, one) TCI state. The selected TCI state may also be applied to more than one (or all) DL channels / RSs. DL channels may also be PDCCH / PDSCH / CSI-RS. The UE may also use the TCI state operation (TCI framework) of Rel.16 to determine the TCI state of each DL channel / RS. UL DCI or a new DCI format may also select (indicate) more than one (for example, one) TCI state. The selected TCI state may also be applied to more than one (or all) UL channels / RSs. UL channels may also be PUSCH / SRS / PUCCH. In this way, different DCIs may also separately indicate UL TCI and DL DCI.

[0068] From Rel.17 NR onwards, it is envisaged that support for activating / indicating beams in a TCI state associated with a different physical cell identifier (PCI) will be supported via MAC CE / DCI. Furthermore, from Rel.18 NR onwards, support for indicating a change of serving cell to a cell with a different PCI will be supported via MAC CE / DCI.

[0069] The joint TCI state and independent (DL / UL) TCI state can be switched between. The use of the joint TCI state or independent TCI state can be configured by the base station to the UE via higher layer parameters or by using the TCI field (TCI state ID) within the DCI.

[0070] [Antenna port QCL (physical layer process for data)]

[0071] In order to provide reference signals for the DMRS of PDSCH and DMRS of PDCCH, and CSI-RS within a certain CC, and further, when PUSCH and PUCCH resources based on dynamic grant and configured grant, and UL TX (transmit) spatial filter for SRS within a certain CC are available, in order to provide a reference for the decision of the UL TCI filter, in PDSCH-Config (PDSCH setting), the UE can be configured with a list of up to 128 DLorJointTCIState (DL or joint TCI state) settings.

[0072] If the DLorJointTCIState or UL-TCIState (UL TCI state) is not configured in the BWP within the CC, the UE can apply the DLorJointTCIState or UL-TCIState configuration from the reference BWP of the reference CC. If the UE has DLorJointTCIState or UL-TCIState configured in any CC within the same band, it is not assumed that TCI-State, SpatialRelationInfo (spatial relationship information), or PUCCH-SpatialRelationInfo (PUCCH spatial relationship information) is configured, other than SpatialRelationInfoPos (spatial relationship information for position) within the band. The UE is assumed to be such that, when the UE is set to the TCI-State within any CC in the CC list through simultaneousTCI-UpdateList1-r16 (simultaneous TCI update list 1), simultaneousTCI-UpdateList2-r16 (simultaneous TCI update list 2), simultaneousSpatial-UpdatedList1-r16 (simultaneous spatial update list 1), or simultaneousSpatial-UpdatedList2-r16 (simultaneous spatial update list 2), the UE is not set to the DLorJointTCIState or UL-TCIState within any CC in the CC.

[0073] If available, the UE receives an activation command that maps up to eight TCI states and / or TCI state pairs, accompanied by one TCI state for DL ​​channels / signals and one TCI state for UL channels / signals, to the codepoints of the 'Transmission Configuration Indication' (TCI) field of the DCI for one CC / DL BWP or a set of CC / DL BWPs. When a set of TCI state IDs is activated for a set of CC / DL BWPs, and further, if available, for one CC / DL BWP, the same set of TCI state IDs is applied to all DL and / or UL BWPs within the indicated CC. The applicable list of CCs is determined by the CC indicated in the activation command. In the case where the activation command maps DLorJointTCIState and / or UL-TCIState to only one TCI code point, the UE applies the indicated DLorJointTCIState and / or UL-TCIState to one CC / DL BWP or a set of CC / DL BWPs. If the indicated mapping for a single TCI code point is applied, the indicated DLorJointTCIState and / or UL-TCIState is applied to one CC / DL BWP or a set of CC / DL BWPs.

[0074] When the bwp-id or cell of the QCL type A / D source RS in the QCL-Info for the TCI state in which DLorJointTCIState is set is not set, the UE assumes that the QCL type A / D source RS is set in the CC / DL BWP to which the TCI state is applied.

[0075] (TCI status indication)

[0076] The Rel.17 unified TCI framework supports the following modes 1 to 3.

[0077] [Mode 1] MAC CE based TCI state indication

[0078] [Mode 2] DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment

[0079] [Mode 3] DCI based TCI state indication by DCI format 1_1 / 1_2 without DL assignment

[0080] A UE with a TCI state configured and activated with a Rel.17 TCI state ID (e.g., tci-StateId_r17) receives DCI format 1_1 / 1_2 indicating the TCI state with the Rel.17 TCI state ID for one CC, or for all CCs in the same CC list configured with simultaneous TCI update list 1 or simultaneous TCI update list 2 (e.g., simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2). If DL allocation is available, DCI format 1_1 / 1_2 may or may not be associated with DL allocation.

[0081] When DCI format 1_1 / 1_2 is not accompanied by DL allocation, the UE can assume (verify) the following for the DCI.

[0082] - CS-RNTI is used to scramble the CRC for DCI.

[0083] - The values ​​of the following DCI fields (special fields) are set as follows:

[0084] - The redundancy version (RV) field is all '1's.

[0085] - The modulation and coding scheme (MCS) field is all '1's.

[0086] - The new data indicator (NDI) field is 0.

[0087] - The frequency domain resource assignment (FDRA) field is all '0's for FDRA type 0, all '1's for FDRA type 1, or all '0's for Dynamic Switch (same as the validation of the PDCCH for release of DL semi-persistent scheduling (SPS) or UL grant type 2 scheduling).

[0088] In addition, the DCI in the above-mentioned mode 2 / mode 3 can also be called beam indication DCI.

[0089] In Rel.15 / 16, if the UE does not support active BWP changes via DCI, the UE ignores the BWP indicator field. Similar operations are under study regarding the relationship between support for Rel.17 TCI states and the interpretation of the TCI field. Studies are underway to always include the TCI field in DCI formats 1_1 / 1_2 when the UE is configured with the Rel.17 TCI state, and to ignore the TCI field if the UE does not support TCI updates via DCI.

[0090] In Rel.15 / 16, whether the TCI field exists (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.

[0091] The TCI field in DCI format 1_1 is 0 bits when the higher layer parameter tci-PresentInDCI is not valid, and is 3 bits otherwise. When the BWP indicator field indicates a BWP other than the activated BWP, the UE follows the following operation.

[0092] [Operation] When the higher-layer parameter tci-PresentInDCI is not valid for the CORESET used in the PDCCH transmitting the DCI format 1_1, the UE assumes that tci-PresentInDCI is not valid for all CORESETs within the indicated BWP. Otherwise, the UE assumes that tci-PresentInDCI is valid for all CORESETs within the indicated BWP.

[0093] The TCI field in DCI format 1_2 is 0 bits if the higher-layer parameter tci-PresentInDCI-1-2 is not set. Otherwise, it is 1, 2, or 3 bits determined by the higher-layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the activated BWP, the UE follows the following operation.

[0094] [Operation] In the case where the higher layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used in the PDCCH transmitting the DCI format 1_2, the UE assumes that tci-PresentInDCI is not valid for all CORESETs within the indicated BWP. If not, the UE assumes that tci-PresentInDCI-1-2 is set for all CORESETs within the indicated BWP with the same value as tci-PresentInDCI-1-2 set for the CORESET used in the PDCCH transmitting the DCI format 1_2.

[0095] A TCI state ID indicating the joint DL / UL TCI state is associated with the value of the TCI field for joint DL / UL TCI state indication.

[0096] The TCI field value used for independent DL / UL TCI state indication is associated with at least one TCI state ID: a TCI state ID indicating the DL-only TCI state and a TCI state ID indicating the UL-only TCI state. In this example, TCI field values ​​000 to 001 are associated with only one DL TCI state ID, TCI field values ​​010 to 011 are associated with only one UL TCI state ID, and TCI field values ​​100 to 111 are associated with both one DL TCI state ID and one UL TCI state ID.

[0097] (Indicates TCI status / sets TCI status)

[0098] For the Rel.17 TCI state, the unified / common TCI state may also mean a Rel.17 TCI state indicated using DCI / MACCE / RRC (of Rel.17) (indicated Rel.17 TCI state).

[0099] In the present disclosure, the indicated Rel.17 TCI state, the indicated TCI state, the unified / common TCI state, the TCI state applied to multiple signals (channels / RSs), and the TCI state used for multiple signals (channels / RSs) may also be overwritten with each other.

[0100] The Rel.17 TCI state may also be shared with UE-specific reception in the PDSCH / PDCCH (updated using Rel.17 DCI / MAC CE / RRC), dynamic grant (DCI) / configured grant PUSCH, and at least one of multiple (e.g., all) dedicated PUCCH resources. The TCI state indicated by DCI / MAC CE / RRC may also be referred to as the indicated TCI state or the unified TCI state.

[0101] Regarding the Rel.17 TCI state, a TCI state other than the unified TCI state may also refer to a Rel.17 TCI state configured using the (Rel.17) MAC CE / RRC (configured Rel.17 TCI state). In this disclosure, the terms "configured Rel.17 TCI state," "configured TCI state," "TCI state other than the unified TCI state," and "TCI state applied to a specific type of signal (channel / RS)" may override each other.

[0102] The Rel.17 TCI state setting may not be shared with UE-specific reception in the PDSCH / PDCCH (updated using Rel.17 DCI / MAC CE / RRC), dynamic grant (DCI) / configured grant PUSCH, and at least one of multiple (e.g., all) dedicated PUCCH resources. The Rel.17 TCI state setting may also be configured to be set per CORESET / per resource / per resource set via RRC / MAC CE, so that even if the aforementioned indicated Rel.17 TCI state (common TCI state) is updated, the Rel.17 TCI state setting will not be updated.

[0103] The application of Rel.17 TCI status indication for UE-specific channels / signals (RS) is under study. Furthermore, the use of higher-layer signaling (RRC signaling) to notify the UE of the application of Rel.17 TCI status indication for non-UE-specific channels / signals and the setting of the Rel.17 TCI status are under study.

[0104] Research is underway to configure the RRC parameters related to setting the Rel.17 TCI state (TCI state ID) to have the same structure as the RRC parameters for the TCI state in Rel.15 / 16. Research is underway to configure the Rel.17 TCI state to be set / indicated per CORESET / per resource / per resource set using RRC / MAC CE. Furthermore, research is underway to allow the UE to determine this setting / indication based on specific parameters.

[0105] Research is underway to independently update the TCI status indication and the TCI setting for the UE. For example, if the unified TCI status for the TCI indication is updated, the TCI setting can be omitted. Furthermore, research is underway to allow the UE to determine this update based on specific parameters.

[0106] Furthermore, studies are underway to switch whether to apply or not apply the Rel.17 TCI state indication for PDCCH / PDSCH using higher layer signaling (RRC / MAC CE) (applying the Rel.17 TCI state or applying a TCI state set separately from the Rel.17 TCI state indication).

[0107] In addition, for intra-cell beam indication (indication of TCI status), research is underway to support the indication of Rel.17 TCI status for UE-specific CORESETs and the PDSCH associated with the CORESETs, and non-UE-specific CORESETs and the PDSCH associated with the CORESETs.

[0108] In addition, for inter-cell beam indication (e.g., L1 / L2 inter-cell mobility), support for indicating the Rel.17 TCI state for a UE-specific CORESET and the PDSCH associated with that CORESET is under study.

[0109] In Rel. 15, whether or not to indicate the TCI status for CORESET #0 depends on base station implementation. In Rel. 15, for CORESET #0 with an indicated TCI status, the indicated TCI status is applied. For CORESET #0 without an indicated TCI status, the QCL corresponding to the SSB selected during the most recent PRACH transmission is applied.

[0110] In the unified TCI status framework after Rel.17, the TCI status related to CORESET#0 is being studied.

[0111] For example, in the framework of the unified TCI state after Rel.17, the Rel.17 TCI state indication of CORESET#0 can also be set for each CORESET through RRC to determine whether to apply the indicated Rel.17 TCI state associated with the serving cell. If not applied, the legacy MAC CE / RACH signaling mechanism can be used.

[0112] In addition, the CSI-RS associated with the Rel.17 TCI state applied to CORESET#0 can also be QCLed with the SSB associated with the serving cell PCI (Physical Cell ID) (similar to Rel.15).

[0113] For CORESET#0, CORESETs with a common search space (CSS), and CORESETs with a CSS and a UE-specific search space (USS), whether to follow the Rel.17 TCI state can be configured for each CORESET through an RRC parameter. Even if the Rel.17 TCI state is not configured for the CORESET, the Rel.17 TCI state can be configured for the CORESET.

[0114] RRC parameters can also be used to configure whether to follow the Rel.17 TCI state for each channel / resource / resource set for non-UE-dedicated channels / RS (except for CORESET). Even if the Rel.17 TCI state is not set for the channel / resource / resource set, the Rel.17 TCI state can be applied to the channel / resource / resource set.

[0115] (Channel / RS to which TCI status is applied)

[0116] The "indicated TCI state" based on MAC CE / DCI can also be applied to the following channels / RSs.

[0117] [PDCCH]

[0118] If followUnifiedTCIState is set for CORESET 0, the indicated TCI state is applied. Otherwise, the Rel.15 specification applies to this CORESET. In other words, CORESET 0 follows the TCI state activated by the MAC CE or is QCLed with the SSB.

[0119] For CORESETs with USS / CSS type 3 and indexes other than 0, the TCI status is always applied.

[0120] If the unified TCI state is configured for a CORESET with at least a CSS other than CSS type 3 and indexes other than 0, the indicated TCI state is applied. Otherwise, the configured TCI state for the CORESET is applied to the CORESET.

[0121] [PDSCH]

[0122] For all UE-dedicated PDSCHs, the TCI status is always applied.

[0123] When followUnifiedTCIState is set for a non-UE-dedicated PDSCH (a PDSCH scheduled using DCI within the CSS), the indicated TCI state may also be applied. Otherwise, the set TCI state for the PDSCH is applied to the PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether the non-UE-dedicated PDSCH follows the indicated TCI state is determined by whether followUnifiedTCIState is set for the CORESET used for scheduling the PDSCH.

[0124] [CSI-RS]

[0125] When followUnifiedTCIState is set for the A-CSI-RS used for CSI acquisition or beam management (for the CORESET of the PDCCH that triggers the A-CSI-RS), the indicated TCI state is applied. The configured TCI state for that CSI-RS is applied to other CSI-RS.

[0126] [PUCCH]

[0127] For all dedicated PUCCH resources, the TCI status is always applied.

[0128] [PUSCH]

[0129] For dynamically / configured granted PUSCH, the TCI status is always applied.

[0130] [SRS]

[0131] When the SRS resource set for A-SRS (for beam management) and A / SP / P-SRS (for codebook (CB) / non-codebook (NCB) / antenna switching) is configured to follow a unified TCI state, the indicated TCI state is applied. For other SRSs, the configured TCI state within the SRS resource set is applied.

[0132] Beam application time (BAT)

[0133] In DCI-based beam indication in Rel. 17, the following studies 1 and 2 are under study regarding the application time (beam application time (BAT) conditions) of the beam / unified TCI status indication.

[0134] Study 1

[0135] Under study: The first time slot to apply the indicated TCI is at least Y symbols after the last symbol of the positive acknowledgment (ACK) for the joint or independent DL / UL beam indication. Under study: The first time slot to apply the indicated TCI is at least Y symbols after the last symbol of the ACK / negative acknowledgment (NACK) for the joint or independent DL / UL beam indication. The Y symbols may also be set by the base station based on the UE's reported capabilities. These UE capabilities may also be reported in symbol units.

[0136] This ACK may also be an ACK for the PDSCH scheduled by the beam indication DCI. In this example, the PDSCH may not be transmitted. In this case, the ACK may also be an ACK for the beam indication DCI.

[0137] Under study: For Rel.17's DCI-based beam indication, at least one Y symbol is configured for the UE per BWP / CC.

[0138] When the SCS differs between multiple CCs, the value of the Y symbol also differs, so the application time may differ between multiple CCs.

[0139] Study 2

[0140] For the CA scenario, the beam indication application timing / BAT may also follow any one of the following options 1 to 3.

[0141] [Option 1] Both the initial time slot and the Y codeword are determined on the carrier with the minimum SCS within one or more carriers to which the beam indication is applied.

[0142] [Option 2] Both the initial time slot and the Y codeword are determined on the carrier with the smallest SCS among the one or more carriers to which the beam indication is applied and the UL carrier carrying the ACK.

[0143] [Option 3] Both the first time slot and the Y symbols are determined on the UL carrier carrying the ACK.

[0144] As part of the CC simultaneous beam update function in Rel. 17, studies are underway to make beams common across multiple CCs in CA. According to Study 2, the application time is made common across multiple CCs.

[0145] The application time (Y symbols) of beam indication for CA can also be determined on the carrier with the smallest SCS within the carrier to which beam indication is applied. Rel.17 MAC CE-based beam indication (when only a single TCI codepoint is activated) can also follow the Rel.16 application timeline for MAC CE activation.

[0146] Based on these studies, the following operations are being studied in the specification.

[0147] [operate]

[0148] When a UE transmits the last PUCCH symbol accompanied by HARQ-ACK information corresponding to a DCI indicating a TCI state, the indicated TCI state, along with the Rel.17 TCI state, may be applied starting from the first slot at least Y symbols after the last PUCCH symbol. Y may also be a higher-layer parameter (e.g., BeamAppTime_r17 [symbols]). Both the first slot and Y symbols may be determined on a carrier with the minimum SCS within the carriers to which the beam indication is applied. At any given moment, a UE may assume a single indicated TCI state, along with both DL and UL Rel.17 TCI states, or a single indicated TCI state, along with the UL Rel.17 TCI state (separate from the DL).

[0149] X [ms] may be used instead of Y [symbol].

[0150] Regarding application time, the UE is studying whether to report at least one of the following UE capabilities 1 and 2.

[0151] [UE Capability 1]

[0152] The minimum application time of each SCS (the minimum value of Y symbols between the last codeword of the PUCCH carrying ACK and the first time slot to which the beam is applied).

[0153] [UE Capability 2]

[0154] The minimum time gap between the last symbol of the beam indication PDCCH (DCI) and the first time slot to which the beam is applied. The gap between the last symbol of the beam indication PDCCH (DCI) and the first time slot to which the beam is applied can also meet the UE capability (minimum time gap).

[0155] UE capability 2 may also be an existing UE capability (eg, timeDurationForQCL).

[0156] The relationship between the beam indication and the channel / RS to which the beam is applied may also satisfy at least one of UE capabilities 1 and 2.

[0157] Regarding the application time, a parameter set by the base station (eg, BeamAppTime_r17) may be considered an optional field.

[0158] (Initial access process)

[0159] During the initial access procedure, the UE (RRC_IDLE mode) receives the SS / PBCH block (SSB), transmits Msg.1 (PRACH / random access preamble / preamble), receives Msg.2 (PDCCH, PDSCH containing a random access response (RAR)), transmits Msg.3 (PUSCH scheduled by the RAR UL grant), and receives Msg.4 (PDCCH, PDSCH containing the UE contention resolution identifier). Subsequently, when the UE sends an ACK for Msg.4 from the base station (network), an RRC connection is established (RRC_CONNECTED mode).

[0160] SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception. PSS detection involves detecting a portion of the physical cell ID (PCI), detecting (synchronizing) the OFDM symbol timing, and performing (coarse) frequency synchronization. SSS detection includes detecting the physical cell ID. PBCH-DMRS detection involves detecting (a portion of) the SSB index within a half radio frame (5ms). PBCH reception includes detecting the system frame number (SFN) and radio frame timing (SSB index), receiving configuration information for receiving the remaining minimum system information (RMSI, SIB1), and determining whether the UE can camp on the cell (carrier).

[0161] SSB has a 20-bit bandwidth and a 4-symbol duration. The SSB transmission period can be set from 5, 10, 20, 40, 80, or 160 milliseconds. Multiple SSB symbol positions are specified within a half-frame based on the frequency range (FR1 or FR2).

[0162] The PBCH has a 56-bit payload. N repetitions of the PBCH are transmitted in an 80 ms period. N depends on the SSB transmission period.

[0163] System information includes the MIB, RMSI (SIB1), and other system information (OSI) carried on the PBCH. The SIB1 includes RACH configuration and information used for RACH procedures. The time / frequency relationship between the SSB and the PDCCH monitoring resources used by the SIB1 is configured on the PBCH.

[0164] A base station using beam correspondence transmits multiple SSBs using multiple beams per SSB transmission cycle. Each SSB has multiple SSB indices. A UE that detects an SSB transmits a PRACH during the RACH opportunity associated with the SSB index and receives a RAR within the RAR window.

[0165] (Beam and Coverage)

[0166] In high frequency bands, if beamforming is not applied to synchronization signals / reference signals, coverage becomes narrow and it becomes difficult for UEs to find base stations. On the other hand, in order to ensure coverage, if beamforming is applied to synchronization signals / reference signals, strong signals will arrive in a specific direction, but signals in other directions will be more difficult to reach. In the base station before connecting to the UE, if it is assumed that the direction of the UE is unclear, synchronization signals / reference signals cannot be sent using only beams facing the appropriate direction. Consider a method in which the base station sends multiple synchronization signals / reference signals, each with a beam in a different direction, and the UE identifies which beam it has found. If a thin (narrow) beam is used for coverage, a large number of synchronization signals / reference signals need to be sent, so there is a concern that overhead will increase and frequency utilization efficiency will decrease.

[0167] If coarse (wide) beams are used to reduce the number of beams (synchronization signals / reference signals) and suppress overhead, the coverage range will be narrowed.

[0168] In future wireless communication systems (eg, 6G), utilization of frequency bands such as millimeter waves and terahertz waves is expected to further develop. It is also expected that multiple thin beams will be used to construct a cell area / coverage to provide communication services.

[0169] Considerations include expanding the area using existing FR2 and using a higher frequency band than existing FR2. To achieve these goals, it is desirable to improve beam management in addition to using multiple TRPs and reconfigurable intelligent surfaces (RIS).

[0170] Research is underway to enhance coverage, including PRACH enhancements for frequency range (FR) 2. For example, PRACH repetition (multiple PRACH transmissions) using the same beam or multiple different beams is under study. This PRACH enhancement can be applied to both the 4-step RACH procedure and FR1.

[0171] PRACH enhancement can be applied to both short PRACH formats and other formats.

[0172] For multiple PRACH transmissions with the same beam, a single RAR window may be applied to each PRACH transmission. This RAR window may also follow existing designs. For multiple PRACH transmissions with the same beam, a single RAR window may be applied to all of the multiple PRACH transmissions.

[0173] The UE may also use different multiple transmit (Tx) beams in transmitting multiple PRACHs across multiple ROs associated with the same SSB / CSI-RS.

[0174] (PRACH)

[0175] like Figure 1 As shown, the common RACH configuration (RACH-ConfigCommon) may also include: a generic RACH configuration (rach-ConfigGeneric), the total number of RA preambles (totalNumberOfRA-Preambles), the number of SSBs per RACH opportunity, and the number of contention-based (CB) preambles per SSB (ssb-perRACH-OccasionAndCB-PreamblesPerSSB). rach-ConfigGeneric may also include a PRACH configuration index (prach-ConfigurationIndex), message 1 FDM (msg1-FDM, the number of PRACH opportunities for FDM within a time instance). ssb-perRACH-OccasionAndCB-PreamblesPerSSB may also include the number of CB preambles per SSB, corresponding to the number of SSBs per RACH opportunity (oneEighth, one SSB associated with eight RACH opportunities).

[0176] For the type 1 random access procedure (4-step random access procedure, messages 1 / 2 / 3 / 4), the UE may also be informed of the number N of SS / PBCH blocks associated with one PRACH opportunity and the number R of CB preambles per SS / PBCH block per valid PRACH opportunity via ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0177] For the Type 1 random access procedure or the Type 2 random access procedure with a PRACH opportunity configuration independent of the Type 1 random access procedure (2-step random access procedure, message A / B), when N < 1, one SS / PBCH block is mapped to 1 / N consecutive valid RACH opportunities, with R CB preambles with consecutive indices associated with the SS / PBCH block index for each valid PRACH opportunity, starting from preamble index 0. When N >= 1, R CB preambles with consecutive indices associated with the SS / PBCH block index n (0 <= n < -N-1) for each valid PRACH opportunity, starting from preamble index n N_preamble^total / N. Here, for a Type 1 random access procedure, N_preamble^total is given by totalNumberOfRA-Preambles. For a Type 2 random access procedure with a PRACH opportunity configured independently of the Type 1 random access procedure, N_preamble^total is given by msgA-TotalNumberOfRA-Preambles. N_preamble^total is a multiple of N.

[0178] The association period used to map SS / PBCH blocks to PRACH opportunities starting from frame 0 is determined by the relationship between the PRACH configuration period and the association period (the number of PRACH configuration periods) (defined in the specification), with N being the maximum value. Tx SSB The minimum value in the set determined by the PRACH configuration period in such a way that the SS / PBCH block indices are mapped to the PRACH opportunity at least once during the association period. Here, the UE obtains N based on the value of SSB position in burst (ssb-PositionsInBurst) in SIB1 or in the public service cell configuration (ServingCellConfigCommon). Tx SSBIf after an integer number of mapping cycles from SS / PBCH block index to PRACH opportunity within the associated period, there is a Tx SSB Even if a set of PRACH opportunities or PRACH preambles is associated with an integer number of SS / PBCH block indices, an SS / PBCH block index is not mapped to that set of PRACH opportunities or PRACH preambles. The associated pattern period includes one or more associated periods and is determined so that the pattern between PRACH opportunities and SS / PBCH block indices repeats at most every 160 ms. If a PRACH opportunity exists after an integer number of associated periods that is not associated with an SS / PBCH block index, that PRACH opportunity is not used for PRACH.

[0179] In the case of PRACH transmission triggered by higher layers (PRACH transmission not triggered by PDCCH orders), if ssb-ResourceList is provided, the PRACH mask index is represented by ra-ssb-OccasionMaskIndex. The ra-ssb-OccasionMaskIndex indicates the PRACH opportunity used for PRACH transmission associated with the selected SS / PBCH block index.

[0180] PRACH opportunities are mapped consecutively for each corresponding SS / PBCH block index. The indexing of PRACH opportunities, represented by the masked index value, is reset for each SS / PBCH block index and each mapping cycle of consecutive PRACH opportunities. In the first available mapping cycle, the UE selects the PRACH opportunity represented by the PRACH masked index value corresponding to the indicated SS / PBCH block index for PRACH transmission.

[0181] For the indicated preamble index, the order of PRACH opportunities is as follows.

[0182] First, the increasing order of frequency resource indices for frequency division multiplexed PRACH opportunities.

[0183] Second, the increasing order of time resource indices for time-division multiplexed PRACH opportunities within a PRACH slot.

[0184] Third, the ascending order of the PRACH slot index.

[0185] For PRACH transmissions triggered in response to requests from higher layers, if csirs-ResourceList is provided, the value of ra-OccasionList represents a list of PRACH opportunities for PRACH transmission, with the PRACH opportunities being associated with the selected CSI-RS indices indicated by the csi-RS. The indexing of the PRACH opportunities indicated by ra-OccasionList is reset for each association mode period.

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

[0187] The value of the PRACH mask index value (msgA-SSB-SharedRO-MaskIndex) is associated with the allowed PRACH opportunities of the SSB (the value of the PRACH opportunity index).

[0188] Figure 2A This figure shows an example (mapping 1) of the association between PRACH opportunities (RACH opportunities (ROs)) and beams (SSBs / CSI-RSs) based on the higher-layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. When ssb-perRACH-OccasionAndCB-PreamblesPerSSB represents oneHalf,n16 (N=1 / 2, R=16) and msg1-FDM is 4, four ROs are FDMed in one time instance, and one SSB is mapped to two ROs. Preamble indices 0 to 15 are associated with two ROs, and preamble indices 0 to 15 are associated with SSB0. Thus, when N < 1, one SSB is mapped to multiple ROs. This increases the RO capacity per beam.

[0189] Figure 2BThis figure shows another example (mapping 2) of RO-beam association based on the higher-layer parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB. When ssb-perRACH-OccasionAndCB-PreamblesPerSSB represents n4,n16 (N=4, R=16), msg1-FDM is 4, and N_preamble^total is 64, four ROs are FDMed at one time instance, and four SSBs are mapped to one RO. SSBs 0 to 3 are associated with one RO. Preamble indices 0 to 15 are associated with SSB 0, preamble indices 15 to 31 are associated with SSB 1, preamble indices 32 to 47 are associated with SSB 2, and preamble indices 48 to 63 are associated with SSB 3. Thus, 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 through the received PRACH.

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

[0191] The type of RACH process triggered for different purposes varies depending on whether PRACH repetition can be applied to the scenario. The type of RACH process can also be at least one of the following.

[0192] Contention-free random access (CFRA), PDCCH ordered RA (RA initiated by PDCCH command), CFRA for beam failure recovery (BFR), CFRA for system information (SI) request, CFRA for reconfiguration with sync, etc.

[0193] Contention-based random access (CBRA), RA triggered by the MAC entity, RA triggered by event-based RRC, CBRA for BFR, etc.

[0194] 4-step RACH.

[0195] 2-step RACH.

[0196] (PDCCH command)

[0197] 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) field in DCI format 1_0 is scrambled using the C-RNTI and the frequency domain resource assignment field is all 1, DCI format 1_0 is used for random access initiated by a PDCCH order. The remaining fields are the random access preamble, UL / supplementary uplink (SUL) indicator, SS / PBCH index (SSB index), PRACH mask index, and reserved bits (12 bits).

[0198] In the case of PRACH transmission triggered by a PDCCH command, when the value of the Random Access Preamble Index field is not zero, the PRACH Mask Index field indicates the PRACH timing of the PRACH transmission associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of the PDCCH command.

[0199] <Random Access Procedure in MAC Entity>

[0200] The random access procedure is initiated by a PDCCH command, the MAC entity itself, or RRC for events that comply with the specification. Within the MAC entity, only one random access procedure is in progress at any given time. The random access procedure for an SCell is initiated only by a PDCCH command with a ra-PreambleIndex different from 0b000000.

[0201] When the random access procedure is started on the serving cell, the MAC entity performs the following operations.

[0202] When the random access procedure is started by a PDCCH command and the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, or when the random access procedure is started for synchronization reconfiguration and a 4-step RA type contention-free random access resource is explicitly provided by rach-ConfigDedicated for the BWP selected for the random access procedure, RA_TYPE is set to 4-step RA.

[0203] When the selected RA_TYPE is set to 4-step RA, the MAC entity performs the following operations.

[0204] When ra-PreambleIndex is explicitly provided from the PDCCH and ra-PreambleIndex is not 0b000000, PREAMBLE_INDEX is set to the notified ra-PreambleIndex, and the SSB notified through the PDCCH is selected.

[0205] When the SSB is selected as described above, the next available PRACH opportunity is determined from the PRACH opportunities corresponding to the selected SSB that are permitted according to the restrictions given by ra-ssb-OccasionMaskIndex (the MAC entity randomly selects a PRACH opportunity with equal probability from consecutive PRACH opportunities corresponding to the selected SSB according to the specification. When determining the next available PRACH opportunity corresponding to the selected SSB, the MAC entity may also consider the possibility of occurrence of measurement gaps).

[0206] <Time between PDCCH command reception and PRACH transmission>

[0207] When the random access procedure is initiated via a PDCCH command, the UE, if requested by higher layers, shall transmit PRACH within a selected PRACH opportunity, provided that the time between the last symbol received in the PDCCH command and the first symbol transmitted in the PRACH is greater than or equal to N_(T,2) + Δ_BWPSwitching + Δ_Delay + T_switch [msec] (time condition), as specified in the specification. Here, N_(T,2) is the duration of N_2 symbols corresponding to the PUSCH preparation time of UE processing capability 1. It is assumed that μ corresponds to the minimum subcarrier spacing (SCS) setting between the PDCCH command and the corresponding SCS setting transmitted in the PRACH. If the active UL BWP remains unchanged, Δ_BWPSwitching = 0. Otherwise, Δ_BWPSwitching is defined in the specification. In FR1, Δ_delay = 0.5 msec, and in FR2, Δ_delay = 0.25 msec. T_switch is the switching gap duration defined in the specification.

[0208] <PRACH timing valid / invalid conditions (valid conditions)>

[0209] In paired spectrum (FDD) or SUL band, all PRACH opportunities are valid. In unpaired spectrum (TDD), PRACH opportunities may also follow the following rules 1 and 2.

[0210] [Provision 1]

[0211] If the UE is not provided with tdd-UL-DL-ConfigurationCommon, a PRACH opportunity within a PRACH slot is valid if it does not precede the SS / PBCH block within the PRACH slot, but instead begins at least N_gap symbols after the last SS / PBCH block received. N_gap is specified in the specification. If channelAccessMode=semistatic is provided, it does not overlap with the set of consecutive symbols before the start of the next channel occupancy time not transmitted by the UE. The candidate SS / PBCH block index for the SS / PBCH block corresponds to the SS / PBCH block index provided via ssb-PositionsInBurst within SIB1 or within ServingCellConfigCommon.

[0212] [Provision 2]

[0213] When the UE is provided with tdd-UL-DL-ConfigurationCommon, the PRACH opportunity within the PRACH slot is valid in the following cases.

[0214] The PRACH opportunity is within the UL symbol. Or,

[0215] This PRACH opportunity does not precede the SS / PBCH block within the PRACH slot, but rather begins at least N_gap symbols after the last DL symbol and at least N_gap symbols after the last SS / PBCH block symbol. Here, N_gap is specified in the specification. If channelAccessMode=semistatic is provided, as documented in the specification, this PRACH opportunity does not overlap with the set of consecutive symbols before the start of the next channel occupancy time without any transmission. As documented in the specification, the candidate SS / PBCH block index for the SS / PBCH block corresponds to the SS / PBCH block index provided via ssb-PositionsInBurst within SIB1 or within ServingCellConfigCommon.

[0216] (RAR window)

[0217] The RA Response Window (ra-ResponseWindow) is a time window for monitoring RA Responses (RARs) (special cell (SpCell) only). The RA Contention Resolution Timer (ra-ContentionResolutionTimer) is a timer for RA contention resolution (SpCell only). The Msg.B Response Window is a time window for monitoring RA Responses (RARs) for two-step RA types (SpCell only).

[0218] In the present disclosure, SpCell, primary cell (PCell), and primary secondary cell (PSCell) may also be replaced with each other.

[0219] If the RA preamble is transmitted, the MAC entity performs the following operations 1 to 3 regardless of the possibility of the measurement gap occurring.

[0220] [Operation 1]

[0221] If the contention-free RA preamble for the BFR request is transmitted by the MAC entity, the MAC entity performs the following operations 1-1 and 1-2.

[0222] [[Operation 1-1]] The MAC entity starts the ra-ResponseWindow set in the BFR configuration (BeamFailureRecoveryConfig) at the first PDCCH timing after the end of the RA preamble transmission.

[0223] [[Operation 1-2]] During the operation of the ra-ResponseWindow, the MAC entity monitors PDCCH transmission in the search space indicated by the BFR search space ID (recoverySearchSpaceId) of the SpCell identified by the C-radio network temporary identifier (RNTI).

[0224] [Operation 2]

[0225] If this is not the case, the MAC entity performs the following operations 2-1 and 2-2.

[0226] [[Operation 2-1]] The MAC entity starts the ra-ResponseWindow set in the common RACH configuration (RACH-ConfigCommon) at the first PDCCH timing after the end of the RA preamble transmission.

[0227] [[Operation 2-2]] During the operation of the ra-ResponseWindow, the MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the RA-RNTI.

[0228] [Operation 3]

[0229] If the ra-ResponseWindow set in BeamFailureRecoveryConfig expires and a PDCCH transmission on the search space indicated by the recoverySearchSpaceId for the C-RNTI is received on the serving cell on which the preamble is transmitted, or if the ra-ResponseWindow set in RACH-ConfigCommon expires and a RAR including RA preamble identifiers consistent with the transmitted preamble index (PREAMBLE_INDEX) is received, the MAC entity considers the RAR reception to have failed and increases the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by 1.

[0230] The MAC entity may also stop the ra-ResponseWindow (and may also stop monitoring for the RAR) after successful reception of the RAR including the RA preamble identifier (identifiers) that matches the transmitted PREAMBLE_INDEX.

[0231] Regarding PDCCH monitoring within the RA response window, there are two cases: the PDCCH for the response to the base station for BFR and the PDCCH for RAR. The following content can also be applied to both cases.

[0232] If the MSGA (Msg.A) preamble is transmitted, the MAC entity performs the following operations 4 to 6 regardless of the possibility of the measurement gap occurring.

[0233] [Operation 4]

[0234] The MAC entity starts the Msg.B response window (msgB-ResponseWindow) within the PDCCH monitoring window specified by the specification.

[0235] The msgB-ResponseWindow may also begin at least one symbol after the last symbol of the PRACH opportunity corresponding to the UE's PRACH transmission, i.e., the first symbol of the earliest CORESET configured to receive a PDCCH for a Type-1 PDCCH CSS set. The length of the msgB-ResponseWindow may also correspond to the SCS for the Type-1 PDCCH CSS set.

[0236] [Operation 5]

[0237] While the msgB-ResponseWindow is operating, the MAC entity monitors the PDCCH transmission of the SpCell for RAR identified by the MSGB-RNTI.

[0238] [Operation 6]

[0239] If the C-RNTI MAC CE is included in the MSGA, the MAC entity monitors the PDCCH transmission of the SpCell for the RAR identified by the C-RNTI during the operation of the msgB-ResponseWindow.

[0240] The RA-RNTI associated with the PRACH opportunity for transmitting the RA preamble is calculated as follows.

[0241] RA-RNTI = 1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0242] Here, s_id is the index of the first OFDM symbol of the PRACH opportunity (0 <= s_id < 14). t_id is the index of the first slot of the PRACH opportunity within the system frame (0 <= t_id < 80). The subcarrier spacing (SCS) used to determine t_id is based on the value of μ. f_id is the index of the PRACH opportunity in the frequency domain (0 <= f_id < 8). ul_carrier_id is the UL carrier used for RA preamble transmission (0 for the normal uplink (NUL) carrier and 1 for the supplementary uplink (SUL) carrier). RA-RNTI is calculated according to the specification. RA-RNTI is the RNTI for the four-step RACH.

[0243] The MSGB-RNTI associated with the PRACH opportunity for transmitting the RA preamble is calculated as follows.

[0244] MSGB-RNTI = 1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id +14×80×8×2

[0245] Here, s_id is the index of the first OFDM symbol of the PRACH opportunity (0 <= s_id < 14). t_id is the index of the first slot of the PRACH opportunity within the system frame (0 <= t_id < 80). The subcarrier spacing (SCS) used to determine t_id is based on the value of μ. f_id is the index of the PRACH opportunity in the frequency domain (0 <= f_id < 8). ul_carrier_id is the UL carrier used for RA preamble transmission (0 for the normal uplink (NUL) carrier and 1 for the supplementary uplink (SUL) carrier). MSGB-RNTI is the RNTI used for two-step RACH.

[0246] (RAR Monitoring)

[0247] In response to a PRACH transmission, the UE attempts to detect DCI format 1_0 with a CRC scrambled using the corresponding RA-RNTI within the aforementioned window controlled by higher layers. This window begins in the first symbol of the earliest CORESET in which the UE is configured to receive a PDCCH for a Type-1 PDCCH CSS set, i.e., at least one symbol after the last symbol of the PRACH opportunity corresponding to the PRACH transmission. This symbol duration corresponds to the SCS for the Type-1 PDCCH CSS set. The length of this window is provided as a number of slots based on the SCS for the Type-1 PDCCH CSS set, using the ra-responseWindow.

[0248] When a UE detects DCI format 1_0 with a CRC scrambled with the corresponding RA-RNTI and the LSBs of the SFN field in the same DCI format as the system frame number (SFN) in 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 associated SS / PBCH blocks or CSI-RS resources used by the UE for PRACH, regardless of whether the UE is provided with the TCI-State for the CORESET for receiving the PDCCH with this DCI format 1_0.

[0249] When the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI based on PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for the SpCell, the UE may also assume that the PDCCH including the DCI format 1_0 and the PDCCH order have the same DMRS antenna port QCL properties. When the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI based on PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for the secondary cell, the UE may also assume the DMRS antenna port QCL properties of the CORESET associated with the Type 1-PDCCH CSS set used for reception of the PDCCH including the DCI format 1_0.

[0250] The RAR UL grant may also include at least one of the following: a frequency hopping flag field, a PUSCH frequency resource configuration (allocation) field, a PUSCH time resource configuration field, a modulation and coding scheme (MCS) field, a PUSCH TPC command field, a CSI request field, and a channel access-cyclic prefix extension (CPext) field.

[0251] In single-cell operation, or operation with carrier aggregation in the same frequency band, if the qcl-Type set for the 'typeD' properties of the DMRS used to monitor PDCCHs in the type-1 PDCCH CSS set is not set to the same as the qcl-Type set for the 'typeD' properties of the DMRS used to monitor PDCCHs in the type-0 / 0A / 0B / 2 / 3-PDCCH CSS set or in the USS set, and the PDCCH or the associated PDSCH overlaps with the PDCCH or the associated PDSCH monitored by the UE in the type-1 PDCCH CSS set for at least one symbol, the UE is not assumed to monitor the PDCCHs in the type-0 / 0A / 0B / 2 / 3-PDCCH CSS set or in the USS set.

[0252] If the UE is provided with more than one search space set via PDCCH-Config, via corresponding one or more of searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, peiSearchSpace, ra-SearchSpace, and CSS sets, and is provided with SI-RNTI, P-RNTI, PEI-RNTI, RA-RNTI, MsgB-RNTI, SFI-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI, for any of these RNTIs, the UE does not assume processing of information from more than one DCI format in each time slot, where the more than one DCI format is accompanied by a CRC scrambled with the RNTI.

[0253] (Message 3 PUSCH (Msg3 PUSCH))

[0254] The UE sends a transport block in the PUSCH scheduled by the RAR UL grant in the corresponding RAR message. μ K cell,offset The PUSCH is sent within K cell,offset The cell can be provided by CellSpecific_Koffset. If it is not provided, K cell,offset =0.

[0255] k2 is the slot offset, determined based on the row index m+1 of the allocation table provided by the value m in the PUSCH Time Resource Allocation field of the RAR UL grant, and the PUSCH subcarrier spacing μPUSCH. Δ is the additional subcarrier spacing-specific slot delay for the initial RAR-scheduled PUSCH transmission, specific to the PUSCH subcarrier spacing μPUSCH and applied in addition to K2.

[0256] If the UE requests repetition of PUSCH transmission, the UE PUSCH repeat Here, N PUSCH repeatFor example, it is indicated by the 2 MSBs of the MCS field within the RAR UL grant or DCI format 0_0, from a set of 4 values ​​provided by numberOfMsg3Repetitions, or from {1, 2, 3, 4} if numberOfMsg3Repetitions is not provided.

[0257] UE decides whether to apply Msg3 repetition based on RSRP. In the case of ThresholdMsg3 (threshold), the MAC entity assumes that message 3 repetition can be applied to the current random access (RA) procedure.

[0258] The UE can request Msg3 PUSCH repetition via a dedicated PRACH resource. The MAC entity selects RA resources in the following cases: there are more than one set of available RA resources, and one of the more than one set is used in the indication of all functions that trigger the RA process; and there are more than one set of available RA resources for which indications corresponding to a subset of all functions that trigger the RA process are set. When the Msg3 repetition indication is set for a set of RA resources, if Msg3 repetition cannot be used, the MAC entity regards the set of RA resources as unusable for the RACH process.

[0259] RA resources may also be partitioned for each function, and the functions may include at least one of Msg3 repetition, reduced capacity (RedCap), small data transmission (SDT), and RAN slicing.

[0260] The following information is notified in SIB1 transmitted by the base station.

[0261] Priority of each function (featurePriorities-r17). This priority is used to determine which FeatureCombinationPreamble to use when a function is mapped to more than one FeatureCombinationPreamble.

[0262] Added RO settings. These settings include available functions (which are associated with multiple functions), RA resources (e.g., preamble index), and a mask index used to distinguish ROs.

[0263] The UE determines the RO to use depending on this function.

[0264] SIB1 contains ServingCellConfigCommonSIB. It contains UplinkConfigCommonSIB. It contains BWP UplinkCommon (UL BWP common settings).

[0265] BWP UplinkCommon can also include RACH common settings (RACH ConfigCommon or MsgA ConfigCommon), additionalRACH ConfigList r17 (additional RACH setting list). additionalRACH ConfigList r17 can also include rsrp ThresholdMsg3 r17 (threshold).

[0266] RACH common configurations may also include FeatureCombinationPreambles. FeatureCombinationPreambles associates a set of preambles (partitions) with a feature combination. FeatureCombinationPreambles may also 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 specified by the index of the first preamble and the number of preambles.

[0267] The available RO is explicitly set by the PRACH mask index. Using the relationship between the PRACH mask index and the permitted PRACH opportunities (RO) of the SSB (MAC protocol specification / PRACH mask index value table), at least one of the PRACH opportunity indices 1 to 8 can be set.

[0268] The number of Msg3 repetitions is indicated by the 2 most significant bits (MSBs) (upper 2 bits) of the modulation and coding scheme (MCS) field in the RAR UL grant.

[0269] In PUSCH repetition type A, when a PUSCH scheduled by an RAR UL grant is transmitted, the 2 MSBs of the MCS information field of the RAR UL grant provide the codepoint used to determine the number of repetitions K, based on the relationship between the value (codepoint) of the 2 MSBs of the MCS information field and the number of repetitions K (see table), depending on whether the higher-layer parameter numberOfMsg3Repetitions is set. The number of slots N used to determine the transport block size (TBS) is 1.

[0270] In PUSCH repetition type B, when a PUSCH scheduled using DCI format 0_0 is transmitted and accompanied by a CRC scrambled using the TC-RNTI, the 2 MSBs of the MCS information field of the DCI format provide a code point for determining the number of repetitions K, based on the relationship (table) between the value (code point) of the 2 MSBs of the MCS information field and the number of repetitions K, depending on whether the higher-layer parameter numberOfMsg3Repetitions is set. The number of time slots N used for TBS determination is 1.

[0271] (Contention Resolution)

[0272] If Msg3 is sent, the MAC entity follows operations 1 to 4 below.

[0273] [Operation 1] If Msg3 is sent on a non-terrestrial network, the MAC entity starts the ra-ContentionResolutionTimer and restarts it in each HARQ retransmission within the first codeword after the end of Msg3 plus the UE estimate of the UE-gNB RTT.

[0274] [Operation 2] Otherwise, if the Msg3 transmission (initial transmission or HARQ retransmission) is scheduled with Type A PUSCH repetition, the MAC entity starts or restarts the ra-ContentionResolutionTimer in the first codeword after all repetitions of the Msg3 transmission are completed.

[0275] [Operation 3] Otherwise, the MAC entity starts or restarts the ra-ContentionResolutionTimer within the first codeword after the end of the Msg3 transmission.

[0276] [Operation 4] While the ra-ContentionResolutionTimer is operating, the MAC entity monitors the PDCCH regardless of the possibility of a measurement gap occurring.

[0277] Step 4 (Msg4) of the RA process of Rel.16 NR follows the following Step 4 operations.

[0278] [Step 4 Operation]

[0279] When a UE is not provided with a C-RNTI, based on a PUSCH transmission scheduled via a RAR UL grant, the UE attempts to detect DCI format 1_0 scheduling a PDSCH containing the UE contention resolution identity (UE contention resolution identity) and a CRC scrambled by the corresponding TCI-RNTI. Upon receiving the PDSCH containing the UE contention resolution identity, the UE transmits HARQ-ACK information within the PUCCH. The PUCCH transmission occurs within the same active UL BWP as the PUSCH transmission. The minimum time between the last symbol received on the PDSCH and the first symbol transmitted on the corresponding PUCCH containing HARQ-ACK information is N_T,1 [msec]. N_T,1 is the duration of N_T,1 symbols, equivalent 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.

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

[0281] (PUCCH before dedicated PUCCH resource setting)

[0282] If the UE does not have a dedicated PUCCH resource configuration provided by PUCCH-ResourceSet in PUCCH-Config, the UE can be configured to use the default PUCCH resource table, Figure 3 ) row index, provided by pucch-ResourceCommon for N BWP size The PUCCH resource set for sending HARQ-ACK information on the PUCCH within the initial UL BWP of PRBs (default PUCCH resources).

[0283] The pucch-ResourceCommon field included in SIB1 indicates an index value between 0 and 15. The default PUCCH resource table associates an index with a PUCCH resource set. Each PUCCH resource set includes a set of PUCCH formats 0 / 1, the first PUCCH symbol, the number of PUCCH symbols, the PUCCH PRB offset, and an initial cyclic shift index. The UE determines the PUCCH resource within the PUCCH resource set indicated by the index based on the PDCCH that schedules the PDSCH (the first CCE of the PDCCH and the PUCCH resource indicator field in the DCI).

[0284] The UE transmits the PUSCH using the same spatial domain transmit filter as that used for the PUSCH transmission scheduled by the RAR UL grant.

[0285] If the UE is not provided with any of pdsch-HARQ-ACK-Codebook, pdsch-HARQ-ACK-Codebook-r16, and pdsch-HARQ-ACK-OneShotFeedback, the UE generates at most one HARQ-ACK information bit.

[0286] (PDCCH uses the default beam (controls the physical layer process))

[0287] [Provision 1a]

[0288] For CORESETs other than the CORESET with index 0, the UE follows the following.

[0289] - If the UE is not provided with the configuration of one or more TCI states for the CORESET via the TCI state lists for PDCCH (tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList), or if the UE is provided with the initial configuration of more than one TCI states for the CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList but does not receive a MAC CE activation command for the more than one TCI states, the UE assumes that the DM-RS antenna port associated with PDCCH reception is quasi co-located (QCL) with the SS / PBCH block identified by the UE during the initial access procedure or with the SS / PBCH block for the most recently configured permitted PUSCH for the same HARQ process.

[0290] - In the case that the UE is provided with the initial configuration of more than one TCI states for the CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList as part of the reconfiguration with the sync procedure, but does not receive a MAC CE activation command for the more than one TCI states, the UE assumes that the DM-RS antenna port associated with the PDCCH reception and the SS / PBCH block or CSI-RS resource identified by the UE in the random access procedure started by the reconfiguration with the sync procedure are set to QCL.

[0291] [Provision 1b]

[0292] For CORESET with index 0, the UE follows the following.

[0293] - When the UE is provided with a DL or joint TCI state (DLorJoint-TCIState, dl-OrJoint-TCIStateList) and the unified TCI state is activated for the CORESET (followUnifiedTCIstate='enabled'), the UE assumes that the DM-RS antenna ports associated with PDCCH reception and the reference signals provided by the indicated DLorJoint-TCIState are set to QCL.

[0294] Otherwise, the UE assumes that the DM-RS antenna port associated with PDCCH reception in the CORESET and any of the following reference signals are set to QCL:

[0295] -- If there is more than one DL RS set by a TCI state, and the TCI state is indicated by the MAC CE activation command for the CORESET, then the DL RS, or,

[0296] -- the SS / PBCH blocks identified by the UE in the most recent random access procedure, if no MAC CE activation command indicating a TCI state for the CORESET was received after the most recent random access procedure that was not started by a PDCCH command triggering a contention-free random access (CFRA) procedure, or,

[0297] -- The SS / PBCH block identified by this UE in the latest configured granted PUSCH transmission.

[0298] (PDCCH / PDSCH / CSI-RS / PUCCH / PUSCH / SRS use default beams (data uses physical layer procedures))

[0299] [Provision 2a]

[0300] After a UE receives an initial higher layer configuration of more than one DLorJoint-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the DM-RS of the PDSCH, the DM-RS of the PDCCH, and the CSI-RS to which the indicated TCI state is applied are set to QCL with the SS / PBCH blocks identified by the UE during the initial access procedure.

[0301] [Provision 2b]

[0302] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL transmit (TX) spatial filters for PUSCH, PUCCH, and SRS based on a dynamic grant or a configured grant to which the indicated TCI state is applied are the same as the UL TX spatial filters for PUSCH transmissions scheduled by the RAR UL grant in the initial access procedure.

[0303] [Regulation 2c]

[0304] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of a reconfiguration accompanying a synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the DM-RS of the PDSCH, the DM-RS of the PDCCH, and the CSI-RS to which the indicated TCI state is applied are set to QCL with the SS / PBCH blocks or CSI-RS resources identified by the UE in the random access procedure initiated by the reconfiguration accompanying the synchronization procedure.

[0305] [Regulation 2d]

[0306] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration with a synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filter for PUSCH, PUCCH and SRS based on a dynamic grant or a configured grant to which the indicated TCI state is applied is the same as the UL TX spatial filter for PUSCH transmission scheduled by the RAR UL grant in the random access procedure initiated with the reconfiguration of the synchronization procedure.

[0307] [Regulation 2e]

[0308] When the UE wants to send PUCCH with HARQ-ACK information in time slot n corresponding to the PDSCH of the transmission activation command, the indicated mapping between multiple TCI states and multiple code points of the DCI field 'Transmission Configuration Indication' (TCI field) starts from time slot n+3N slot subframe,μ +2 μ / 2 μKmac ･k mac Here, μ is the SCS setting for PUCCH, and μKmac is k with a value of 0 for frequency range 1 (FR1). mac SCS setting, k mac is the number of time slots provided by K-Mac, or k if K-Mac is not provided mac = 0. If the TCI presence setting (tci-PresentInDCI) in DCI is set to 'enabled' or the TCI presence setting (tci-PresentDCI-1-2) in DCI1-2 is set for the CORESET scheduling the PDSCH, if the QCL time (timeDurationForQCL) is available, when the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than timeDurationForQCL, after the UE receives the initial higher layer configuration of multiple TCI states and before receiving the activation command, the UE assumes that if the QCL type (qcl-Type) set to 'typeA' and the qcl-Type set to 'typeD' are available, the DM-RS ports of the PDSCH of the serving cell are set to QCL with respect to the qcl-Type set to 'typeD' and the SS / PBCH blocks determined in the initial access procedure.

[0309] For a PUSCH scheduled by fallback DCI (DCI format 0_0), the UE follows the following.

[0310] - For a PUSCH scheduled using DCI format 0_0 on a cell, if the spatial relation corresponding to the dedicated PUCCH resource with the lowest ID within the activated UL BWP of the cell is available, the UE shall transmit the PUSCH following the spatial relation. If the dedicated PUCCH resource with the lowest ID within the activated UL BWP of the cell corresponds to two spatial relations, the UE shall transmit the PUSCH following the spatial relation with the lowest ID.

[0311] - For PUSCH scheduled using DCI format 0_0 on a cell, if the higher layer parameter enableDefaultBeamPL-ForPUSCH0-0 is set to 'enabled', the UE is not configured with PUCCH resources on the activated UL BWP, and the UE is in RRC connected mode, the UE transmits the PUSCH following the spatial relation associated with the RS configured with the qcl-Type set to 'typeD' for the QCL assumption of the CORESET with the lowest ID on the activated DL BWP of the cell, if available. If the CORESET is indicated with two TCI states, the SFN PDCCH scheme (sfnSchemePdcch) is configured, and the UE supports the default beam and PL-RS for PUSCH in SFN PDCCH (DefaultBeamPL-ForPUSCH-SfnPdcch), the UE uses the first TCI state (of the two TCI states) as the QCL assumption.

[0312] - For PUSCH scheduled using DCI format 0_0 on a cell, if the higher layer parameter enableDefaultBeamPL-ForPUSCH0-0 is set to 'enabled', the UE is configured to activate PUCCH resources on the UL BWP, and no spatial relationship is configured for all PUCCH resources, and the UE is in RRC connected mode, if more than one CORESET is configured on the cell, then the UE shall transmit PUSCH following the spatial relationship of the RSs configured with the qcl-Type set to 'typeD' corresponding to the QCL assumption of the CORESET with the lowest ID on the activated DL BWP of the cell, if applicable. If the CORESET is indicated with two TCI states, sfnSchemePdcch is configured, and the UE supports DefaultBeamPL-ForPUSCH-SfnPdcch, the UE shall use the first TCI state (of the two TCI states) as the QCL assumption.

[0313] For PUSCHs scheduled using non-fallback DCI (UL DCI other than DCI format 0_0), the UE follows the SRS resource indicator (SRI) indication. In other words, it assumes SRS configuration.

[0314] (Default beam for PDCCH / PDSCH / CSI-RS / PUCCH / PUSCH / SRS (controlled by physical layer procedures))

[0315] The beam (spatial relationship) used for the PUCCH before individual configuration (for example, HARQ-ACK for Msg4) follows the Msg3 PUSCH.

[0316] The individually configured PUCCH beam complies with PUCCH spatial relationship information (pucch-SpatialRelationInfo). pucch-SpatialRelationInfo indicates the ID of the SSB, CSI-RS, or SRS.

[0317] (Default beam)

[0318] Before appropriate configuration / indication of beams for DL ​​PDCCH / PDSCH (eg, configuration of a list / activation of a MAC CE), the SSB or CSI-RS identified in the initial access procedure or random access procedure is considered as a QCL source RS.

[0319] In the case of unified TCI of Rel. 17, the UL TX spatial filter of Msg3 PUSCH is regarded as a UL TX spatial filter before appropriate setting / indication of beams for UL PUSCH / PUCCH / SRS.

[0320] In the case of the spatial relationship of Rel.15 / 16, the beam used for UL PUSCH / PUCCH / SRS follows the following.

[0321] - The UL TX spatial filter for PUSCH scheduled via fallback DCI follows the PUCCH resource with the lowest ID or the CORESET with the lowest ID.

[0322] - The UL TX spatial filter for PUSCH scheduled via non-fallback DCI follows the SRI indication.

[0323] - The UL TX spatial filter for PUCCH before individual configuration follows the UL TX spatial filter for Msg3 PUSCH.

[0324] - The UL TX spatial filter for PUCCH after individual configuration complies with pucch-SpatialRelationInfo.

[0325] (BFR (Physical Layer Control Procedure) for PCell / PSCell)

[0326] [Provision 3a]

[0327] In PCell or PSCell, UE can be provided with the configuration for PRACH transmission using dedicated PRACH resource configuration (PRACH-ResourceDedicatedBFR) through BFR. new In the PRACH in slot n associated with the periodic CSI-RS resource configuration or the antenna port QCL parameters associated with the SS / PBCH block, the UE monitors the following PDCCH, which is provided by the recovery search space ID (recoverySearchSpaceId) for detecting the DCI format with the CRC scrambled by the C-RNTI or MCS-C-RNTI, starting from slot n+4+2 μ ･k mac Here, μ is the SCS configuration for the PRACH transmission, and k is the PDCCH in the search space set that starts. macis the number of time slots provided by K-Mac, or k if K-Mac is not provided mac = 0. For PDCCH monitoring and corresponding PDSCH reception within the search space set provided by recoverySearchSpaceId, the UE assumes that new The UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or any one of the multiple parameters of the TCI state list for PDCCH (at least one of tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) from a higher layer. After the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or any one of the multiple parameters of the TCI state list for PDCCH (at least one of tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList).

[0328] [Provision 3b]

[0329] In a PCell or PSCell, after 28 symbols from the last symbol received from the first PDCCH within the search space set provided by the recovery search space ID (recoverySearchSpaceId) in the DCI format for the UE to detect a CRC with scrambled by the C-RNTI or MCS-C-RNTI, until the UE receives an activation command for PUCCH-SpatialRelationInfo or until the UE is provided with PUCCH-SpatialRelationInfo for PUCCH resources, the UE transmits PUCCH on the same cell as the PRACH transmission using the following parameters:

[0330] - The same spatial filter as the latest PRACH transmission,

[0331] - Use q u =0,q d =q new , and the power determined by l=0.

[0332] [Regulation 3c]

[0333] For PCell or PSCell, and q0 bar and q1 bar, 28 symbols after the last symbol received from the first PDCCH in the search space set provided by recoverySearchSpaceId for UE detection of DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI, the UE assumes that the search space set with index q1 is the same as the search space set with index q2 in the PDCCH monitoring in CORESET with index 0. new The associated antenna port quasi-co-location (QCL) parameters are the same as the QCL parameters of the antenna port.

[0334] In the present disclosure, the q0 bar may also be marked by adding an overline to "q0", and the q1 bar may also be marked by adding an overline to "q1".

[0335] [Regulation 3d]

[0336] When a UE is provided with TCI-State_r17 indicating a unified TCI state for a PCell or PSCell, the UE follows the following rules starting from the last symbol of the initial PDCCH reception within the search space set provided by recoverySearchSpaceId and for which the UE detects a DCI format with a CRC scrambled by the C-RNTI or MCS-C-RNTI.

[0337] - In the case that additional PCI information (AdditionalPCIInfo) is not provided, if the corresponding index q new If the associated antenna port QCL parameter exists, the UE uses the same antenna port QCL parameter as the antenna port QCL parameter, monitors the PDCCH in all CORESETs, and receives the PDSCH and the non-periodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH.

[0338] - Using the same spatial domain filter as the latest spatial domain filter used for PRACH transmission, the PUCCH, the PUSCH, and the SRS using the same spatial domain filter are transmitted with the same TCI state as that indicated for the PUCCH and PUSCH.

[0339] [Regulation 3e]

[0340] When a PDCCH reception includes two PDCCH candidates from two linked search space sets based on search space linking, the last symbol of the PDCCH reception is the last symbol of the later-ending PDCCH candidate (of the two PDCCH candidates). If the UE needs to monitor one of the two PDCCH candidates, the PDCCH reception includes both PDCCH candidates.

[0341] [Regulation 3f]

[0342] For PCell or PSCell, when the BFR MAC CE is provided in Msg3 or MsgA of the contention based random access (CBRA) procedure and PUCCH resources with PUCCH-SpatialRelationInfo are provided, the UE transmits the PUCCH on the same cell as the PRACH transmission using the following two parameters 28 symbols after the last symbol received from the PDCCH that determines the end of the CBRA procedure.

[0343] - The same spatial filter as the latest PRACH transmission.

[0344] - Use q u =0,q d =q new , and the power determined by l=0. Here, q new It is the SS / PBCH block index selected for the latest PRACH transmission.

[0345] [Regulation 3g]

[0346] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, and the UE provides a BFR MAC CE in Msg3 or MsgA of the CBRA procedure, the UE follows the following rules after X symbols from the last symbol received in the PDCCH that determines the end of the CBRA procedure.

[0347] - In the case that AdditionalPCIInfo is not provided, if the corresponding index q newIf the associated antenna port QCL parameter exists, the UE uses the same antenna port QCL parameter as the antenna port QCL parameter, monitors the PDCCH in all CORESETs, receives the PDSCH, and the non-periodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH.

[0348] - Using the same spatial domain filter as the latest spatial domain filter used for PRACH transmission, the PUCCH, the PUSCH, and the SRS using the same spatial domain filter are transmitted with the same TCI state as that indicated for the PUCCH and PUSCH.

[0349] (analyze)

[0350] When a UE uses different transmission beams corresponding to different SSBs / CSI-RSs to transmit multiple PRACHs, it is unclear how to determine the beam during or after the random access process. If this operation is unclear, there is a concern that it may lead to a decrease in communication quality.

[0351] Therefore, the inventors of the present invention came up with a method for determining a beam.

[0352] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In addition, each of the following embodiments (eg, each situation) can be used alone or in combination of at least two.

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

[0354] In the present disclosure, the words “notify,” “activate,” “deactivate,” “indicate,” “select,” “configure,” “update,” and “determine” may be used interchangeably. In the present disclosure, the words “support,” “control,” “controllable,” “operate,” and “operable” may also be used interchangeably.

[0355] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IEs), and settings may also be overwritten. In this disclosure, Medium Access Control (MAC) Control Elements (CEs), update commands, and activation / deactivation commands may also be overwritten.

[0356] In the present disclosure, high-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (for example, positioning protocols (for example, NR Positioning Protocol A (NRPPa)) / LTE Positioning Protocol (LTE Positioning Protocol (LPP)))), etc.), or any one of them, or a combination thereof.

[0357] In the present disclosure, MAC signaling may include, for example, a MAC Control Element (MACCE) and a MAC Protocol Data Unit (PDU). Broadcast information may include, for example, a Master Information Block (MIB), a System Information Block (SIB), minimum system information (Remaining Minimum System Information (RMSI)), and other system information (Other System Information (OSI)).

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

[0359] (Wireless Communication Method)

[0360] In each embodiment, the SSB / CSI-RS index / indicator, beam index, TCI status, spatial domain transmit filter, and spatial domain receive filter may also be overwritten.

[0361] In various embodiments, the RAR window, ra-ResponseWindow, time window, RAR timer, and timer operating period may also be overwritten. In the present disclosure, the contention resolution window, contention window, contention resolution timer, ra-ContentionResolutionTimer, and contention resolution timer operating period may also be overwritten. In the present disclosure, the contention resolution identifier, contention resolution identifier, contention resolution ID, and UE contention resolution identity may also be overwritten.

[0362] In various embodiments, ports, antenna ports, DMRS ports, and DMRS antenna ports may be interchangeable. In this disclosure, the ports and RS reception may be configured as QCL, and the ports may use the same spatial domain (transmit / receive) filters as RS reception.

[0363] In each embodiment, DCI (format) / PDCCH (candidate) with CRC scrambled by a specific RNTI, DCI (format) / PDCCH (candidate) using a specific RNTI, and DCI (format) / PDCCH (candidate) monitored using a specific RNTI may be overwritten.

[0364] In each embodiment, RACH resources, RA resources, PRACH preamble, opportunity, RACH opportunity (RO), PRACH opportunity, repetition resources, repetition configuration resources, resources configured for RO / repetition, time instance and frequency instance, time resources and frequency resources, RO / preamble resources, and repetition may be interchangeable. In each embodiment, period, cycle, frame, subframe, time slot, symbol, opportunity, and RO may be interchangeable.

[0365] In each embodiment, the PDCCH command, PDCCH command DCI, DCI format 1_0, and message (Msg) 0 may also be overwritten. In each embodiment, PRACH, preamble, PRACH preamble, sequence, preamble format, and Msg1 may also be overwritten. In each embodiment, the response to PRACH, RAR, Msg2, MsgB, Msg4, the base station response to BFR, and the DCI of the scheduling response (RAR) may also be overwritten. In each embodiment, transmissions other than PRACH during the random access procedure, Msg3, PUSCH scheduled by RAR, HARQ-ACK / PUCCH for Msg4, and MsgA PUSCH may also be overwritten. In each embodiment, Msg3, PUSCH scheduled by RAR UL grant, and RRC connection request may also be overwritten. In each embodiment, Msg4, contention resolution, RRC connection setup, and PDSCH with UE contention resolution identity may also be overwritten.

[0366] In each embodiment, the RAR, the DCI (PDCCH) that schedules the RAR, the PDSCH with the UE contention resolution identifier, and the DCI that schedules the PDSCH with the UE contention resolution identifier may be overwritten.

[0367] In each embodiment, beam, SSB, SSB index, CSI-RS, CSI-RS resource, CSI-RS resource index, RS, QCL assumption, TCI state, unified TCI state, DL or joint TCI state, UL TCI state, UL Tx spatial filter, spatial domain filter, spatial domain transmit filter, spatial domain receive filter, antenna port QCL parameters, and QCL parameters can also be rewritten with each other.

[0368] In each embodiment, the random access (RA) procedure, CFRA / CBRA, 4-step RACH / 2-step RACH, a specific type of random access procedure, a random access procedure using a specific PRACH format, a random access procedure initiated by a PDCCH command, a random access procedure initiated without a PDCCH command, and a random access procedure initiated by a higher layer may also be overwritten.

[0369] In each embodiment, time resources, Msg1, Msg2, Msg3, Msg4, HARQ-ACK information, RAR window, contention resolution window, DCI for scheduling Msg2, and DCI for scheduling Msg4 may also overwrite each other. In the operation of each embodiment, an earlier time resource may be a time resource earlier than the operation among multiple time resources corresponding to multiple PRACH repetitions, or a time resource with an index smaller than the index of the operation with respect to the repetition (time domain index). In the operation of each embodiment, a later time resource may be a time resource later than the operation among multiple time resources corresponding to multiple PRACH repetitions, or a time resource with an index larger than the index of the operation with respect to the repetition (time domain index).

[0370] In each embodiment, the default beam, the beam applied in reception / transmission before receiving the setting of the beam / MAC CE, the beam applied when the setting of the beam is not provided, the beam applied after receiving the setting of multiple beams and before applying one of the multiple beams, and the beam applied from the indication of the received beam until a specific time has passed may also overwrite each other.

[0371] In each embodiment, the monitored / received / detected RAR and the PDCCH that schedules and monitors / receives / detects the RAR may also override each other. In each embodiment, the monitoring of the RAR and the monitoring of the PDCCH that schedules the RAR may also override each other. In each embodiment, the monitoring of the RAR and the monitoring of the PDCCH that schedules the RAR may also override each other. In each embodiment, the monitoring of the Msg4 and the monitoring of the DCI format_0 that schedules the PDSCH containing the UE contention resolution identifier and the CRC scrambled by the corresponding TC-RNTI may also override each other.

[0372] In each embodiment, RAR received / detected, successfully received / detected / monitored RAR may overwrite each other. In each embodiment, Msg4 received / detected, successfully received / detected / monitored Msg4, and ARQ / ACK sent for Msg4 reception may overwrite each other.

[0373] For a UE that reports the capability corresponding to multiple PRACH transmissions using different multiple transmission beams, or for a UE that reports the capability corresponding to multiple PRACH transmissions using different multiple transmission beams and where PRACH using different multiple transmission beams is repeatedly activated / set, the following scenarios can be considered.

[0374] - Scenario 1

[0375] The UE uses different multiple transmission beams corresponding to different multiple SSB / CSI-RS to transmit multiple PRACHs respectively. Each of the multiple different transmission beams can also be a wide transmission beam. For each PRACH transmission, individual RAR / Msg3 / Msg4 is transmitted / received ( Figure 4 ).

[0376] (Post-RA Issues)

[0377] When a UE receives multiple Msg4s with contention resolution identities, it is unclear how the UE determines the default beam for PDCCH / PDSCH / CSI-RS / PUCCH / PUSCH after the random access procedure is successfully completed.

[0378] - Scenario 2

[0379] The UE uses different multiple transmission beams corresponding to different multiple SSB / CSI-RS to transmit multiple PRACHs respectively. Each of the different multiple transmission beams can also be a wide transmission beam. For multiple PRACH transmissions, a single RAR is transmitted / received ( Figure 5 ).

[0380] (Problems in RA)

[0381] When reference resources / reference beams are not assumed / set, it is unclear how the UE determines the monitoring of RAR and Msg4, and the transmission beam of Msg3.

[0382] (Post-RA Issues)

[0383] When a UE receives multiple Msg4s with contention resolution identifiers, it is unclear how the UE determines the default beam for PDCCH / PDSCH / CSI-RS / PUCCH / PUSCH after the random access procedure is successfully completed.

[0384] - Scenario 3

[0385] The UE uses different multiple transmission beams corresponding to the same SSB / CSI-RS to transmit multiple PRACHs. Each of the multiple different transmission beams can also be a narrow transmission beam. For each PRACH transmission, individual RAR / Msg3 / Msg4 is transmitted / received ( Figure 6 ).

[0386] (Post-RA Issues)

[0387] When a UE receives multiple Msg4s with contention resolution identifiers, it is unclear how the UE determines the default beam for PDCCH / PDSCH / CSI-RS / PUCCH / PUSCH after the random access procedure is successfully completed.

[0388] - Scenario 4

[0389] The UE uses different multiple transmission beams corresponding to the same SSB / CSI-RS to transmit multiple PRACHs respectively. Each of the different multiple transmission beams can also be a narrow transmission beam. For multiple PRACH transmissions, a single RAR is transmitted / received ( Figure 7 ).

[0390] (Problems in RA)

[0391] When reference resources / reference beams are not assumed / set, it is unclear how the UE determines the monitoring of RAR and Msg4, and the transmission beam of Msg3.

[0392] (Post-RA Issues)

[0393] When a UE receives multiple Msg4s with contention resolution identifiers, it is unclear how the UE determines the default beam for PDCCH / PDSCH / CSI-RS / PUCCH / PUSCH after the random access procedure is successfully completed.

[0394] <Implementation Method #1>

[0395] This embodiment relates to scenario 1.

[0396] - Implementation #1-1: DL default beam after RA

[0397] When the UE sends multiple PRACHs using different multiple beams corresponding to different multiple SSB / CSI-RSs in a RACH attempt during the initial access process, and receives multiple Msg4s sent for the multiple PRACHs, the UE may also follow at least one of the following options.

[0398] -- Option 1

[0399] The UE determines the first / last / randomly determined (arbitrary) received beam among multiple receptions of SSBs or CSI-RS associated with multiple PRACHs of multiple received Msg4s as the default beam for PDCCH / PDSCH / CSI-RS.

[0400] For example, when the default beam for PDCCH / PDSCH / CSI-RS is the "initial" received beam, the aforementioned Figure 4 In the example, the default beam is the beam of SSB#1. For example, when the default beam for PDCCH / PDSCH / CSI-RS is the "last" received beam, the aforementioned Figure 4 For example, when the default beam for PDCCH / PDSCH / CSI-RS is a "randomly determined" received beam, the aforementioned Figure 4 The default beam in the example is any one of SSB#1 / #2 / #3 / #4.

[0401] --- PDCCH uses the default beam

[0402] In the control physical layer process, at least one of the following provisions may also be specified.

[0403] [Provision 1a]

[0404] For CORESETs other than the CORESET with index 0, the UE complies with at least one of the following provisions.

[0405] - If the UE is not provided with the configuration of more than one TCI state for the CORESET using the TCI state lists (tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) via PDCCH, or if the UE is provided with the initial configuration of more than one TCI state for the CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList but does not receive a MAC CE activation command for the more than one TCI state, the UE assumes that the DM-RS antenna port associated with the PDCCH reception and the following SS / PBCH blocks are set to QCL:

[0406] -- the SS / PBCH block identified by the UE during initial access (SS / PBCH block A), or,

[0407] -- the first / last / arbitrary SS / PBCH block (SS / PBCH block B) among the multiple SS / PBCH blocks corresponding to the multiple PRACHs corresponding to the PDSCH with the contention resolution identifier received by the UE in the latest initial access procedure, when the UE transmits multiple PRACHs corresponding to the multiple SS / PBCH blocks in the last random access attempt in the latest initial access procedure, or,

[0408] -- The DM-RS antenna port associated with PDCCH reception, and the latest configuration of the permitted SS / PBCH blocks for PUSCH for the same HARQ process.

[0409] - In case the UE is provided with the initial configuration of more than one TCI state for the CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList as part of the reconfiguration with synchronization procedure, but does not receive a MAC CE activation command for the more than one TCI state, the UE assumes that the DM-RS antenna port associated with PDCCH reception and the following SS / PBCH blocks or CSI-RS resources are set to QCL:

[0410] -- the SS / PBCH blocks or CSI-RS resources identified by the UE during the random access procedure initiated by the reconfiguration accompanying the synchronization procedure, or,

[0411] -- In the case where the UE sends multiple PRACHs corresponding to multiple SS / PBCH blocks or multiple CSI-RSs in the last random access attempt of the latest random access procedure started by the reconfiguration of the synchronization procedure, the initial / last / arbitrary SS / PBCH block or CSI-RS among the multiple SS / PBCH blocks or multiple CSI-RSs corresponding to the multiple PRACHs corresponding to the PDSCH accompanied by the contention resolution identifier received by the UE in the latest random access procedure.

[0412] [Provision 1b]

[0413] For a CORESET with index 0, the UE follows at least one of the following operations.

[0414] - When the UE is provided with DLorJoint-TCIState and followUnifiedTCIstate='enabled' for the CORESET, the UE assumes that the DM-RS antenna ports associated with PDCCH reception and the reference signals provided by the indicated DLorJoint-TCIState are set to QCL.

[0415] Otherwise, the UE assumes that the DM-RS antenna ports associated with PDCCH reception in the CORESET and the following reference signals are set to QCL:

[0416] -- If there is more than one DL RS set by a TCI state, and the TCI state is indicated by the MAC CE activation command for the CORESET, then the DL RS, or,

[0417] -- the SS / PBCH blocks identified by the UE in the most recent random access procedure, if no MAC CE activation command indicating a TCI state for the CORESET was received after the most recent random access procedure that was not started by a PDCCH command triggering a CFRA procedure, or,

[0418] -- After the latest random access procedure started without a PDCCH command triggering a CFRA procedure, if no MAC CE activation command indicating a TCI state for the CORESET was received, if the UE sent multiple PRACHs corresponding to multiple SS / PBCH blocks in the last random access attempt of the latest random access procedure, then the first / last / any SS / PBCH block among the multiple SS / PBCH blocks corresponding to the multiple PRACHs corresponding to the PDSCH with the contention resolution identifier received by the UE, or,

[0419] -- The SS / PBCH blocks identified by the UE in the most recently configured granted PUSCH transmission.

[0420] --- Default beams for multiple types of channels / RS

[0421] In the data physical layer process, at least one of the following provisions may also be specified.

[0422] [Provision 2a]

[0423] After a UE receives an initial higher layer configuration of more than one DLorJoint-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the PDSCH DM-RS, PDCCH DM-RS, and CSI-RS to which the indicated TCI state is applied, and the following SS / PBCH blocks are set to QCL:

[0424] - the SS / PBCH blocks identified by the UE during initial access, or,

[0425] - When the UE transmits multiple PRACHs corresponding to multiple SS / PBCH blocks in the last random access attempt in the latest initial access procedure, the first / last / arbitrary SS / PBCH block among the multiple SS / PBCH blocks corresponding to the multiple PRACHs corresponding to the PDSCH with the contention resolution identifier received by the UE in the latest initial access procedure.

[0426] [Provision 2b]

[0427] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filter for PUSCH, PUCCH, and SRS based on dynamic grant or configured grant to which the indicated TCI state is applied, and the UL TX spatial filter for PUSCH transmission scheduled by the RAR UL grant in the initial access procedure are the same.

[0428] [Regulation 2c]

[0429] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of the reconfiguration accompanying the synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the PDSCH DM-RS, PDCCH DM-RS, and CSI-RS to which the indicated TCI state is applied, and the following SS / PBCH blocks or CSI-RS resources are set to QCL:

[0430] - the SS / PBCH blocks or CSI-RS resources identified by the UE during the random access procedure initiated by the reconfiguration accompanying the synchronization procedure, or,

[0431] - When the UE transmits multiple PRACHs corresponding to multiple SS / PBCH blocks or multiple CSI-RSs in the last random access attempt of the latest random access procedure started by the reconfiguration of the synchronization procedure, the first / last / arbitrary SS / PBCH block or CSI-RS among the multiple SS / PBCH blocks or multiple CSI-RSs corresponding to the multiple PRACHs corresponding to the PDSCH with the contention resolution identifier received by the UE in the latest random access procedure.

[0432] [Regulation 2d]

[0433] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration accompanying a synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filters for PUSCH, PUCCH and SRS based on dynamic grant or configured grant to which the indicated TCI state is applied, and the UL TX spatial filters for PUSCH transmissions scheduled by RAR UL grant in the random access procedure initiated with the reconfiguration of the synchronization procedure are the same.

[0434] [Regulation 2e]

[0435] When the UE wants to send PUCCH with HARQ-ACK information in time slot n corresponding to the PDSCH of the transmission activation command, the indicated mapping between multiple TCI states and multiple code points of the DCI field 'Transmission Configuration Indication' (TCI field) starts from time slot n+3N slot subframe,μ +2 μ / 2 μKmac ･k mac Here, μ is the SCS setting for PUCCH, and μKmac is k with a value of 0 for frequency range 1 (FR1). mac SCS setting, k mac is the number of time slots provided by K-Mac, or k if K-Mac is not provided mac = 0. When tci-PresentInDCI is set to 'enabled' or tci-PresentDCI-1-2 is set for the CORESET scheduling the PDSCH, if timeDurationForQCL is available, when the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than timeDurationForQCL, after the UE receives the initial higher layer configuration of multiple TCI states and before receiving the activation command, the UE assumes that if qcl-Type set to 'typeA' and qcl-Type set to 'typeD' are available, the DM-RS ports of the PDSCH of the serving cell are set to QCL with respect to qcl-Type set to 'typeD' and the following SS / PBCH blocks.

[0436] - the SS / PBCH blocks determined during the initial access procedure, or

[0437] - When the UE transmits multiple PRACHs corresponding to multiple SS / PBCH blocks in the last random access attempt in the latest initial access procedure, the first / last / arbitrary SS / PBCH block among the multiple SS / PBCH blocks corresponding to the multiple PRACHs corresponding to the PDSCH with the contention resolution identifier received by the UE in the latest initial access procedure.

[0438] ---BFR

[0439] In the control physical layer process, at least one of the following provisions may also be specified.

[0440] [Regulation 3d]

[0441] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, the UE follows the following rules after X symbols from the last symbol of the initial PDCCH reception within the search space set provided by recoverySearchSpaceId and the search space set for which the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI.

[0442] - If AdditionalPCIInfo is not provided, the UE monitors the PDCCH in all CORESETs and receives the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH using the following antenna port QCL parameters:

[0443] -- If the corresponding index q new If the associated antenna port QCL parameter exists, then the antenna port QCL parameter (antenna port QCL parameter A) that is the same as the antenna port QCL parameter, or,

[0444] -- A number of indices q within the last random access attempt in which the UE sent the latest random access procedure triggered for beam failure recovery purposes newIn the case of multiple PRACHs corresponding to the UE, the antenna port QCL parameter (antenna port QCL parameter B) is the same as the antenna port QCL parameter associated with the initial / last / arbitrary periodic CSI-RS resource or SS / PBCH block in the multiple periodic CSI-RS resources or multiple SS / PBCH blocks corresponding to the multiple PRACHs corresponding to the DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI detected by the UE in the search space set provided by recoverySearchSpaceId.

[0445] [Regulation 3e]

[0446] When a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the later-ending PDCCH candidate (of the two PDCCH candidates). If the UE needs to monitor one of the two PDCCH candidates, the PDCCH reception includes both PDCCH candidates.

[0447] [Regulation 3f]

[0448] For PCell or PSCell, when the BFR MAC CE is provided in Msg3 or MsgA of the CBRA procedure and PUCCH resources with PUCCH-SpatialRelationInfo are provided, the UE transmits the PUCCH on the same cell as the PRACH transmission using the following parameters 28 symbols after the last symbol received from the PDCCH that determines the end of the CBRA procedure.

[0449] - The same spatial filter as the latest PRACH transmission,

[0450] - Use q u =0,q d =q new , and the power determined by l=0. Here, q new It is the SS / PBCH block index selected for the latest PRACH transmission.

[0451] [Regulation 3g]

[0452] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, and the UE provides a BFR MAC CE in Msg3 or MsgA of the CBRA procedure, the UE follows the following rules after X symbols from the last symbol received in the PDCCH that determines the end of the CBRA procedure.

[0453] - In the case that AdditionalPCIInfo is not provided, if the corresponding index q new If the associated antenna port QCL parameter exists, the UE uses the same antenna port QCL parameter as the antenna port QCL parameter, monitors the PDCCH in all CORESETs, receives the PDSCH, and the non-periodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH.

[0454] - Using the same spatial domain filter as the latest spatial domain filter used for PRACH transmission, the PUCCH, the PUSCH, and the SRS using the same spatial domain filter are transmitted with the same TCI state as that indicated for the PUCCH and PUSCH.

[0455] In use cases 1 and 2, in specification 3d (specification 1a), the UE can use antenna port QCL parameter B (SS / PBCH block B) for PDCCH reception after BFR ends. In use cases 3 and 4, in specification 3d (specification 1a), the UE can use antenna port QCL parameter A (SS / PBCH block A) for PDCCH reception after BFR ends.

[0456] -- Option 2

[0457] The UE determines the SSB / CSI-RS beam corresponding to the first / last / randomly determined (arbitrary) reception among the multiple Msg4 receptions as the default beam for PDCCH / PDSCH / CSI-RS.

[0458] For example, when the default beam for PDCCH / PDSCH / CSI-RS is the "initial" received beam, the aforementioned Figure 4 For example, when the default beam for PDCCH / PDSCH / CSI-RS is the "last" received beam, the above Figure 4For example, when the default beam for PDCCH / PDSCH / CSI-RS is a "randomly determined" received beam, the aforementioned Figure 4 In the example, the default beam is any one of SSB#1 / #2 / #3 / #4. Multiple Msg4 reception can also be rewritten as multiple RAR reception.

[0459] --- PDCCH uses the default beam

[0460] In the control physical layer process, at least one of the following provisions may also be specified.

[0461] [Provision 1a]

[0462] For CORESETs other than the CORESET with index 0, the UE complies with at least one of the following provisions.

[0463] - If the UE is not provided with the configuration of more than one TCI state for the CORESET using the TCI state lists (tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) via PDCCH, or if the UE is provided with the initial configuration of more than one TCI state for the CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList but does not receive a MAC CE activation command for the more than one TCI state, the UE assumes that the DM-RS antenna port associated with the PDCCH reception and the following SS / PBCH blocks are set to QCL:

[0464] -- the SS / PBCH block identified by the UE during initial access (SS / PBCH block A), or,

[0465] -- In the case where the UE transmits multiple PRACHs corresponding to multiple SS / PBCH blocks in the last random access attempt in the latest initial access procedure, the SS / PBCH block corresponding to the first / last / any PDSCH in the multiple PDSCHs with the contention resolution identifier received by the UE in the latest initial access procedure (SS / PBCH block B), or,

[0466] -- The DM-RS antenna port associated with PDCCH reception and the latest configuration of the permitted SS / PBCH blocks for PUSCH for the same HARQ process.

[0467] - In case the UE is provided with the initial configuration of more than one TCI state for the CORESET via tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList as part of the reconfiguration with synchronization procedure, but does not receive a MAC CE activation command for the more than one TCI state, the UE assumes that the DM-RS antenna port associated with PDCCH reception and the following SS / PBCH blocks or CSI-RS resources are set to QCL:

[0468] -- the SS / PBCH blocks or CSI-RS resources identified by the UE during the random access procedure initiated by the reconfiguration accompanying the synchronization procedure, or,

[0469] -- When the UE sends multiple PRACHs corresponding to multiple SS / PBCH blocks or multiple CSI-RSs in the last random access attempt of the latest random access procedure started by the reconfiguration of the synchronization procedure, the SS / PBCH block or CSI-RS corresponding to the first / last / arbitrary PDSCH among the multiple PDSCHs accompanied by the contention resolution identifier received by the UE in the latest random access procedure.

[0470] [Provision 1b]

[0471] For a CORESET with index 0, the UE follows at least one of the following operations.

[0472] - When the UE is provided with DLorJoint-TCIState and followUnifiedTCIstate='enabled' for the CORESET, the UE assumes that the DM-RS antenna ports associated with PDCCH reception and the reference signals provided by the indicated DLorJoint-TCIState are set to QCL.

[0473] Otherwise, the UE assumes that the DM-RS antenna ports associated with PDCCH reception in the CORESET and the following reference signals are set to QCL:

[0474] -- If there is more than one DL RS set by a TCI state, and the TCI state is indicated by the MAC CE activation command for the CORESET, then the DL RS, or,

[0475] -- the SS / PBCH blocks identified by the UE in the most recent random access procedure, if no MAC CE activation command indicating a TCI state for the CORESET was received after the most recent random access procedure that was not started by a PDCCH command triggering a CFRA procedure, or,

[0476] -- After the latest random access procedure started without a PDCCH command triggering a CFRA procedure, if no MAC CE activation command indicating a TCI state for the CORESET was received, if the UE sent multiple PRACHs corresponding to multiple SS / PBCH blocks in the last random access attempt of the latest random access procedure, then the SS / PBCH block corresponding to the first / last / any PDSCH among the multiple PDSCHs with contention resolution identifier received by the UE, or,

[0477] -- The SS / PBCH blocks identified by the UE in the most recently configured granted PUSCH transmission.

[0478] --- Default beams for multiple types of channels / RS

[0479] In the data physical layer process, at least one of the following provisions may also be specified.

[0480] [Provision 2a]

[0481] After a UE receives an initial higher layer configuration of more than one DLorJoint-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the PDSCH DM-RS, PDCCH DM-RS, and CSI-RS to which the indicated TCI state is applied, and the following SS / PBCH blocks are set to QCL:

[0482] - the SS / PBCH blocks identified by the UE during initial access, or,

[0483] - In the case where the UE sends multiple PRACHs corresponding to multiple SS / PBCH blocks in the last random access attempt in the latest initial access procedure, the SS / PBCH block of the first / last / arbitrary PDSCH among the multiple PDSCHs accompanied by the contention resolution identifier received by the UE in the latest initial access procedure.

[0484] [Provision 2b]

[0485] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filter for PUSCH, PUCCH, and SRS based on dynamic grant or configured grant to which the indicated TCI state is applied, and the UL TX spatial filter for PUSCH transmission scheduled by the RAR UL grant in the initial access procedure are the same.

[0486] [Regulation 2c]

[0487] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of the reconfiguration accompanying the synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the PDSCH DM-RS, PDCCH DM-RS, and CSI-RS to which the indicated TCI state is applied, and the following SS / PBCH blocks or CSI-RS resources are set to QCL:

[0488] - the SS / PBCH blocks or CSI-RS resources identified by the UE during the random access procedure initiated by the reconfiguration accompanying the synchronization procedure, or,

[0489] - In a case where the UE transmits multiple PRACHs corresponding to multiple SS / PBCH blocks or multiple CSI-RSs in the last random access attempt of the latest random access procedure started by the reconfiguration of the synchronization procedure, the SS / PBCH block or CSI-RS corresponding to the first / last / arbitrary PDSCH among the multiple PDSCHs accompanied by the contention resolution identifier received by the UE in the latest random access procedure.

[0490] [Regulation 2d]

[0491] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration accompanying a synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filters for PUSCH, PUCCH and SRS based on dynamic grant or configured grant to which the indicated TCI state is applied, and the UL TX spatial filters for PUSCH transmissions scheduled by RAR UL grant in the random access procedure initiated with the reconfiguration of the synchronization procedure are the same.

[0492] [Regulation 2e]

[0493] When the UE wants to send PUCCH with HARQ-ACK information in time slot n corresponding to the PDSCH of the transmission activation command, the indicated mapping between multiple TCI states and multiple code points of the DCI field 'Transmission Configuration Indication' (TCI field) starts from time slot n+3N slot subframe,μ +2 μ / 2 μKmac ･k mac Here, μ is the SCS setting for PUCCH, μKmac is the k value with a value of 0 for FR1. mac SCS setting, k mac is the number of time slots provided by K-Mac, or k if K-Mac is not provided mac = 0. When tci-PresentInDCI is set to 'enabled' or tci-PresentDCI-1-2 is set for the CORESET scheduling the PDSCH, if timeDurationForQCL is available, when the time offset between the reception of the DL DCI and the corresponding PDSCH is greater than timeDurationForQCL, after the UE receives the initial higher layer configuration of multiple TCI states and before receiving the activation command, the UE assumes that if qcl-Type set to 'typeA' and qcl-Type set to 'typeD' are available, the DM-RS ports of the PDSCH of the serving cell are set to QCL with respect to qcl-Type set to 'typeD' and the following SS / PBCH blocks.

[0494] - the SS / PBCH blocks determined during the initial access procedure, or

[0495] - When the UE transmits multiple PRACHs corresponding to multiple SS / PBCH blocks in the last random access attempt in the latest initial access procedure, the SS / PBCH block corresponding to the first / last / any PDSCH among the multiple PDSCHs accompanied by the contention resolution identifier received by the UE in the latest initial access procedure.

[0496] ---BFR

[0497] In the control physical layer process, at least one of the following provisions may also be specified.

[0498] [Regulation 3d]

[0499] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, the UE follows the following rules after X symbols from the last symbol of the initial PDCCH reception within the search space set provided by recoverySearchSpaceId and the search space set for which the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI.

[0500] - If AdditionalPCIInfo is not provided, the UE monitors the PDCCH in all CORESETs and receives the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH using the following antenna port QCL parameters:

[0501] -- If the corresponding index q new If the associated antenna port QCL parameter exists, then the antenna port QCL parameter (antenna port QCL parameter A) that is the same as the antenna port QCL parameter, or,

[0502] -- A number of indices q within the last random access attempt in which the UE sent the latest random access procedure triggered for beam failure recovery purposes new In the case of multiple PRACHs corresponding to the UE, the antenna port QCL parameter (antenna port QCL parameter B) is the same as the antenna port QCL parameter corresponding to the multiple PRACHs corresponding to the initial / last / arbitrary DCI format among the multiple DCI formats with CRC scrambled by C-RNTI or MCS-C-RNTI detected by the UE in the search space set provided by recoverySearchSpaceId.

[0503] [Regulation 3e]

[0504] When a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the later-ending PDCCH candidate (of the two PDCCH candidates). If the UE needs to monitor one of the two PDCCH candidates, the PDCCH reception includes both PDCCH candidates.

[0505] [Regulation 3f]

[0506] For PCell or PSCell, when the BFR MAC CE is provided in Msg3 or MsgA of the CBRA procedure and PUCCH resources with PUCCH-SpatialRelationInfo are provided, the UE transmits the PUCCH on the same cell as the PRACH transmission using the following parameters 28 symbols after the last symbol received from the PDCCH that determines the end of the CBRA procedure.

[0507] - The same spatial filter as the latest PRACH transmission,

[0508] - Use q u =0,q d =q new , and the power determined by l=0. Here, q new It is the SS / PBCH block index selected for the latest PRACH transmission.

[0509] [Regulation 3g]

[0510] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, and the UE provides a BFR MAC CE in Msg3 or MsgA of the CBRA procedure, the UE follows the following rules after X symbols from the last symbol received in the PDCCH that determines the end of the CBRA procedure.

[0511] - In the case that AdditionalPCIInfo is not provided, if the corresponding index q new If the associated antenna port QCL parameter exists, the UE uses the same antenna port QCL parameter as the antenna port QCL parameter, monitors the PDCCH in all CORESETs, receives the PDSCH, and the non-periodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH.

[0512] - Using the same spatial domain filter as the latest spatial domain filter used for PRACH transmission, the PUCCH, the PUSCH, and the SRS using the same spatial domain filter are transmitted with the same TCI state as that indicated for the PUCCH and PUSCH.

[0513] In use cases 1 and 2, in specification 3d (specification 1a), the UE can use antenna port QCL parameter B (SS / PBCH block B) for PDCCH reception after BFR ends. In use cases 3 and 4, in specification 3d (specification 1a), the UE can use antenna port QCL parameter A (SS / PBCH block A) for PDCCH reception after BFR ends.

[0514] - Implementation #1-2: UL default beam after RA

[0515] When the UE sends multiple PRACHs using different multiple beams corresponding to different multiple SSB / CSI-RSs in a RACH attempt during the initial access process, and receives multiple Msg4s sent for the multiple PRACHs, the UE may also follow at least one of the following options.

[0516] -- Option 1

[0517] The UE determines as the default beam for PUCCH / PUSCH the same beam as at least one of the initial / last / randomly determined (arbitrary) PRACH transmissions among the multiple PRACH transmissions corresponding to the multiple received Msg4s, and the initial / last / randomly determined (arbitrary) Msg3 PUSCH among the multiple Msg3 PUSCHs corresponding to the multiple received Msg4s.

[0518] For example, when the default beam for PDCCH / PDSCH / CSI-RS is the "initial" received beam, the aforementioned Figure 4 In the example, the default beam is the beam of SSB#1. For example, when the default beam for PDCCH / PDSCH / CSI-RS is the "last" received beam, the aforementioned Figure 4 For example, when the default beam for PDCCH / PDSCH / CSI-RS is a "randomly determined" received beam, the aforementioned Figure 4 The default beam in the example is any one of SSB#1 / #2 / #3 / #4.

[0519] The following data physical layer procedures / physical layer procedures can be used in Case 3 (Embodiment #3) / Case 4 (Embodiment #4-2).

[0520] --- Default beams for multiple types of channels / RS

[0521] In the data physical layer process, at least one of the following provisions may also be specified.

[0522] [Provision 2a]

[0523] After a UE receives an initial higher layer configuration of more than one DLorJoint-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the PDSCH DM-RS, PDCCH DM-RS, and CSI-RS to which the indicated TCI state is applied, and the following SS / PBCH blocks are set to QCL:

[0524] - The SS / PBCH blocks identified by the UE during the initial access procedure.

[0525] [Provision 2b]

[0526] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filter for PUSCH, PUCCH, and SRS based on a dynamic grant or a configured grant to which the indicated TCI state is applied is the same as the following UL TX spatial filter:

[0527] - UL TX spatial filter for PUSCH transmission scheduled by the RAR UL grant during the initial access procedure, or

[0528] - When the UE transmits multiple PRACHs assumed to use multiple different spatial filters in the last random access attempt of the most recent initial access procedure, the UL TX spatial filter used for the first / last / arbitrary PRACH transmission among the multiple PRACH transmissions corresponding to the PDSCH with the contention resolution identifier received by the UE.

[0529] [Regulation 2c]

[0530] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of the reconfiguration accompanying the synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the PDSCH DM-RS, PDCCH DM-RS, and CSI-RS to which the indicated TCI state is applied, and the following SS / PBCH blocks or CSI-RS resources are set to QCL:

[0531] - The SS / PBCH blocks or CSI-RS resources identified by the UE during the random access procedure initiated by the reconfiguration accompanying the synchronization procedure.

[0532] [Regulation 2d]

[0533] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration with synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filters for PUSCH, PUCCH and SRS based on a dynamic grant or a configured grant to which the indicated TCI state is applied are the same as the following UL TX spatial filters:

[0534] - UL TX spatial filter for PUSCH transmission scheduled by RAR UL grant in the random access procedure started with the resetting of the synchronization procedure, or

[0535] - When the UE transmits multiple PRACHs assumed to use different multiple spatial filters in the last random access attempt of the latest initial access procedure started by the reconfiguration of the synchronization procedure, the UL TX spatial filter for the first / last / arbitrary PRACH transmission among the multiple PRACH transmissions corresponding to the PDSCH with the contention resolution identifier received by the UE.

[0536] ---BFR

[0537] In the control physical layer process, at least one of the following provisions may also be specified.

[0538] [Provision 3a]

[0539] In PCell or PSCell, UE can be provided with the configuration for PRACH transmission through PRACH-ResourceDedicatedBFR. new In the PRACH in slot n associated with the periodic CSI-RS resource configuration or the antenna port QCL parameters associated with the SS / PBCH block, the UE monitors the following PDCCH: μ ･k mac Here, μ is the SCS setting for the PRACH transmission, k is the PDCCH in the search space set that starts. macis the number of time slots provided by K-Mac, or k if K-Mac is not provided mac = 0. For PDCCH monitoring and corresponding PDSCH reception within the search space set provided by recoverySearchSpaceId, the UE assumes that new The UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or any one of the multiple parameters of at least one of tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList through a higher layer. After the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or any one of the multiple parameters of at least one of tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList.

[0540] [Provision 3b]

[0541] In a PCell or PSCell, after 28 symbols from the last symbol received for the initial PDCCH in the search space set provided by recoverySearchSpaceId in a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI for the UE to detect, until the UE receives an activation command for PUCCH-SpatialRelationInfo or until the UE is provided with PUCCH-SpatialRelationInfo for PUCCH resources, the UE transmits PUCCH on the same cell as the PRACH transmission using the following parameters:

[0542] - the same spatial filter as that used for the latest PRACH transmission, or, when the UE transmits multiple PRACHs assumed to use different spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery, the spatial filter used for the first / last / any PRACH transmission among multiple PRACH transmissions corresponding to the PDSCH received by the UE and accompanied by a contention resolution identifier or a PDCCH indicating a successful random access,

[0543] - Use q u =0,q d =q new , and the power determined by l=0.

[0544] [Regulation 3c]

[0545] For PCell or PSCell, and q0 bar and q1 bar, 28 symbols after the last symbol received from the first PDCCH in the search space set provided by recoverySearchSpaceId for UE detection of DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI, the UE assumes that the search space set with index q1 is the same as the search space set with index q2 in the PDCCH monitoring in CORESET with index 0. new The antenna port QCL parameters are the same as the associated antenna port QCL parameters.

[0546] [Regulation 3d]

[0547] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, the UE follows the following rules after X symbols from the last symbol of the initial PDCCH reception within the search space set provided by recoverySearchSpaceId and the search space set for which the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI.

[0548] - If AdditionalPCIInfo is not provided, the UE monitors the PDCCH in all CORESETs and receives the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH using the following antenna port QCL parameters:

[0549] -- If the corresponding index q new If the associated antenna port QCL parameter exists, then the antenna port QCL parameter that is the same as the antenna port QCL parameter, or,

[0550] -- In the case of sending multiple PRACHs assumed using different multiple spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery purposes, the same spatial domain filter as the spatial domain filter used for the first / last / arbitrary PRACH transmission among the multiple PRACH transmissions corresponding to the PDSCH received by the UE, accompanied by a contention resolution identifier or a PDCCH indicating the success of random access.

[0551] [Regulation 3e]

[0552] When a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the later-ending PDCCH candidate (of the two PDCCH candidates). If the UE needs to monitor one of the two PDCCH candidates, the PDCCH reception includes both PDCCH candidates.

[0553] [Regulation 3f]

[0554] For PCell or PSCell, when a BFR MAC CE is provided in Msg3 or MsgA of the CBRA procedure and PUCCH resources with PUCCH-SpatialRelationInfo are provided, the UE shall transmit the PUCCH on the same cell as the PRACH transmission 28 symbols after the last symbol received from the PDCCH that determines the end of the CBRA procedure, using the following parameters:

[0555] - the same spatial filter as that used for the latest PRACH transmission, or, when the UE transmits multiple PRACHs assumed to use multiple different spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery, the same spatial filter as that used for the first / last / any PRACH transmission among multiple PRACH transmissions corresponding to the PDSCH received by the UE and accompanied by a contention resolution identifier or a PDCCH indicating a successful random access,

[0556] - Use q u =0,q d =q new , and the power determined by l=0. Here, q new It is the SS / PBCH block index selected for the latest PRACH transmission.

[0557] [Regulation 3g]

[0558] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, and the UE provides a BFR MAC CE in Msg3 or MsgA of the CBRA procedure, the UE follows the following rules after X symbols from the last symbol received in the PDCCH that determines the end of the CBRA procedure.

[0559] - In the case that AdditionalPCIInfo is not provided, if the corresponding index q new If the associated antenna port QCL parameter exists, the UE uses the same antenna port QCL parameter as the antenna port QCL parameter, monitors the PDCCH in all CORESETs, receives the PDSCH, and the non-periodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH.

[0560] - The UE transmits the PUCCH, the PUSCH, and the SRS using the same spatial domain filter with the same TCI state as that used for the PUCCH and PUSCH:

[0561] -- the same spatial domain filter as that used for the latest PRACH transmission, or

[0562] -- When the UE transmits multiple PRACHs assumed using different multiple spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery purposes, the same spatial domain filter as the spatial domain filter used for the first / last / arbitrary PRACH transmission among the multiple PRACH transmissions corresponding to the PDSCH received by the UE and accompanied by a contention resolution identifier or a PDCCH indicating the success of random access.

[0563] -- Option 2

[0564] The UE determines the same beam as the PRACH transmission corresponding to the first / last / randomly determined (arbitrary) Msg4 received, and at least one beam of the Msg3 PUSCH corresponding to the first / last / randomly determined (arbitrary) Msg4 received as the default beam for PUCCH / PUSCH.

[0565] For example, when the default beam for PDCCH / PDSCH / CSI-RS is the "initial" received beam, the aforementioned Figure 4For example, when the default beam for PDCCH / PDSCH / CSI-RS is the "last" received beam, the above Figure 4 For example, when the default beam for PDCCH / PDSCH / CSI-RS is a "randomly determined" received beam, the aforementioned Figure 4 The default beam in the example is any one of SSB#1 / #2 / #3 / #4.

[0566] The following data physical layer procedures / physical layer procedures can be used in Case 3 (Embodiment #3) / Case 4 (Embodiment #4-2).

[0567] --- Default beams for multiple types of channels / RS

[0568] In the data physical layer process, at least one of the following provisions may also be specified.

[0569] [Provision 2a]

[0570] After a UE receives an initial higher layer configuration of more than one DLorJoint-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the PDSCH DM-RS, PDCCH DM-RS, and CSI-RS to which the indicated TCI state is applied, and the following SS / PBCH blocks are set to QCL:

[0571] - The SS / PBCH blocks identified by the UE during the initial access procedure.

[0572] [Provision 2b]

[0573] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filter for PUSCH, PUCCH, and SRS based on a dynamic grant or a configured grant to which the indicated TCI state is applied is the same as the following UL TX spatial filter:

[0574] - UL TX spatial filter for PUSCH transmission scheduled by the RAR UL grant during the initial access procedure, or

[0575] - UL TX spatial filter used for PRACH transmission (or PUSCH transmission scheduled by RAR UL grant) corresponding to the first / last / arbitrary PDSCH among multiple PDSCHs accompanied by contention resolution identifiers received by the UE, when the UE transmitted multiple PRACHs assumed to use different spatial filters in the last random access attempt of the most recent initial access procedure.

[0576] [Regulation 2c]

[0577] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of the reconfiguration accompanying the synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the PDSCH DM-RS, PDCCH DM-RS, and CSI-RS to which the indicated TCI state is applied, and the following SS / PBCH blocks or CSI-RS resources are set to QCL:

[0578] - The SS / PBCH blocks or CSI-RS resources identified by the UE during the random access procedure initiated by the reconfiguration accompanying the synchronization procedure.

[0579] [Regulation 2d]

[0580] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration with synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filters for PUSCH, PUCCH and SRS based on a dynamic grant or a configured grant to which the indicated TCI state is applied are the same as the following UL TX spatial filters:

[0581] - UL TX spatial filter for PUSCH transmission scheduled by RAR UL grant in the random access procedure started with the resetting of the synchronization procedure, or

[0582] - When the UE transmits multiple PRACHs assumed to use different multiple spatial filters in the last random access attempt of the latest initial access procedure started by the reconfiguration of the synchronization procedure, the UL TX spatial filter used for PRACH transmission corresponding to the first / last / arbitrary PDSCH among multiple PDSCHs accompanied by the contention resolution identifier received by the UE (or PUSCH transmission scheduled by the RAR UL grant).

[0583] ---BFR

[0584] In the control physical layer process, at least one of the following provisions may also be specified.

[0585] [Provision 3a]

[0586] In PCell or PSCell, UE can be provided with the configuration for PRACH transmission through PRACH-ResourceDedicatedBFR. new In the PRACH in slot n associated with the periodic CSI-RS resource configuration or the antenna port QCL parameters associated with the SS / PBCH block, the UE monitors the following PDCCH, which is provided by the recoverySearchSpaceId to detect the DCI format with the CRC scrambled by the C-RNTI or MCS-C-RNTI, starting from slot n+4+2 μ ･k mac Here, μ is the SCS setting for the PRACH transmission, k is the PDCCH in the search space set that starts. mac is the number of time slots provided by K-Mac, or k if K-Mac is not provided mac = 0. For PDCCH monitoring and corresponding PDSCH reception within the search space set provided by recoverySearchSpaceId, the UE assumes that new The UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or any one of the multiple parameters of at least one of tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList through a higher layer. After the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or any one of the multiple parameters of at least one of tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList.

[0587] [Provision 3b]

[0588] In a PCell or PSCell, after 28 symbols from the last symbol received for the initial PDCCH in the search space set provided by recoverySearchSpaceId in a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI for the UE to detect, until the UE receives an activation command for PUCCH-SpatialRelationInfo or until the UE is provided with PUCCH-SpatialRelationInfo for PUCCH resources, the UE transmits PUCCH on the same cell as the PRACH transmission using the following parameters:

[0589] - the same spatial filter as that used for the latest PRACH transmission, or, in the case where the UE transmits multiple PRACHs assumed to use different spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery purposes, the spatial filter used for the PRACH transmission (or PUSCH transmission scheduled by an RAR UL grant) corresponding to the first / last / arbitrary PDSCH among multiple PDSCHs received by the UE and accompanied by a contention resolution identifier or a PDCCH indicating the success of random access,

[0590] - Use q u =0,q d =q new , and the power determined by l=0.

[0591] [Regulation 3c]

[0592] For PCell or PSCell, and q0 bar and q1 bar, 28 symbols after the last symbol received from the first PDCCH in the search space set provided by recoverySearchSpaceId for UE detection of DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI, the UE assumes that the search space set with index q1 is the same as the search space set with index q2 in the PDCCH monitoring in CORESET with index 0. new The antenna port QCL parameters are the same as the associated antenna port QCL parameters.

[0593] [Regulation 3d]

[0594] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, the UE follows the following rules after X symbols from the last symbol of the initial PDCCH reception within the search space set provided by recoverySearchSpaceId and the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI.

[0595] - If AdditionalPCIInfo is not provided, the UE monitors the PDCCH in all CORESETs and receives the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH using the following antenna port QCL parameters:

[0596] -- If the corresponding index q new If the associated antenna port QCL parameter exists, then the antenna port QCL parameter that is the same as the antenna port QCL parameter, or,

[0597] -- In the case of sending multiple PRACHs assumed using different multiple spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery purposes, the same spatial domain filter as the spatial domain filter used for the PRACH transmission corresponding to the first / last / arbitrary PDSCH among multiple PDSCHs received by the UE, accompanied by a contention resolution identifier or a PDCCH indicating the success of random access (or PUSCH transmission scheduled by a RAR UL grant).

[0598] [Regulation 3e]

[0599] When a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the later-ending PDCCH candidate (of the two PDCCH candidates). If the UE needs to monitor one of the two PDCCH candidates, the PDCCH reception includes both PDCCH candidates.

[0600] [Regulation 3f]

[0601] For PCell or PSCell, when a BFR MAC CE is provided in Msg3 or MsgA of the CBRA procedure and PUCCH resources with PUCCH-SpatialRelationInfo are provided, the UE shall transmit the PUCCH on the same cell as the PRACH transmission 28 symbols after the last symbol received from the PDCCH that determines the end of the CBRA procedure, using the following parameters:

[0602] - The same spatial filter as that used for the latest PRACH transmission, or, when the UE transmits multiple PRACHs assumed to be transmitted using different multiple spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery purposes, the same spatial domain filter as that used for PRACH transmission corresponding to the first / last / arbitrary PDSCH among multiple PDSCHs received by the UE (or PUSCH transmission scheduled by a RAR UL grant) accompanied by a contention resolution identifier or a PDCCH indicating the success of random access.

[0603] - Use q u =0,q d =q new , and the power determined by l=0. Here, q new It is the SS / PBCH block index selected for the latest PRACH transmission.

[0604] [Regulation 3g]

[0605] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, and the UE provides a BFR MAC CE in Msg3 or MsgA of the CBRA procedure, the UE follows the following rules after X symbols from the last symbol received in the PDCCH that determines the end of the CBRA procedure.

[0606] - In the case that AdditionalPCIInfo is not provided, if the corresponding index q new If the associated antenna port QCL parameter exists, the UE uses the same antenna port QCL parameter as the antenna port QCL parameter, monitors the PDCCH in all CORESETs, receives the PDSCH, and the non-periodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH.

[0607] - The UE transmits the PUCCH, the PUSCH, and the SRS using the same spatial domain filter with the same TCI state as that used for the PUCCH and PUSCH:

[0608] -- the same spatial domain filter as that used for the latest PRACH transmission, or

[0609] -- When the UE transmits multiple PRACHs assumed using different multiple spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery purposes, the same spatial domain filter as the spatial domain filter used for the PRACH transmission corresponding to the first / last / arbitrary PDSCH among multiple PDSCHs received by the UE and accompanied by a contention resolution identifier or a PDCCH indicating the success of random access (or PUSCH transmission scheduled by a RAR UL grant).

[0610] -- Option 3

[0611] The UE determines as the default beam for PUCCH / PUSCH the PDSCH scheduled by the initial / last / randomly determined (arbitrary) RAR UL grant among the multiple RAR UL grants (multiple RARs) received corresponding to the multiple Msg4s, and the beam that is the same as at least one of the beams sent by the PRACH corresponding to the initial / last / randomly determined (arbitrary) RAR UL grant among the multiple RAR UL grants (multiple RARs) received corresponding to the multiple Msg4s.

[0612] The following data physical layer procedures / physical layer procedures can be used in Case 3 (Embodiment #3) / Case 4 (Embodiment #4-2).

[0613] --- Default beams for multiple types of channels / RS

[0614] In the data physical layer process, at least one of the following provisions may also be specified.

[0615] [Provision 2a]

[0616] After a UE receives an initial higher layer configuration of more than one DLorJoint-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the PDSCH DM-RS, PDCCH DM-RS, and CSI-RS to which the indicated TCI state is applied, and the following SS / PBCH blocks are set to QCL:

[0617] - The SS / PBCH blocks identified by the UE during the initial access procedure.

[0618] [Provision 2b]

[0619] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filter for PUSCH, PUCCH, and SRS based on a dynamic grant or a configured grant to which the indicated TCI state is applied is the same as the following UL TX spatial filter:

[0620] - UL TX spatial filter for PUSCH transmission scheduled by the RAR UL grant during the initial access procedure, or

[0621] - UL TX spatial filter for PRACH transmission scheduled by the first / last / arbitrary RAR UL grant among multiple RAR UL grants corresponding to multiple PDSCHs with contention resolution identifiers received by the UE (or PUSCH transmission corresponding to the RAR UL grant), when the UE transmits multiple PRACHs assumed to be transmitted using different spatial filters in the last random access attempt of the latest initial access procedure.

[0622] [Regulation 2c]

[0623] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState as part of the reconfiguration accompanying the synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the PDSCH DM-RS, PDCCH DM-RS, and CSI-RS to which the indicated TCI state is applied, and the following SS / PBCH blocks or CSI-RS resources are set to QCL:

[0624] - The SS / PBCH blocks or CSI-RS resources identified by the UE during the random access procedure initiated by the reconfiguration accompanying the synchronization procedure.

[0625] [Regulation 2d]

[0626] After the UE receives an initial higher layer configuration of more than one DLorJoint-TCIState or UL-TCIState as part of a reconfiguration with synchronization procedure, and before applying an indicated TCI state from the configured multiple TCI states, the UE assumes that the UL TX spatial filters for PUSCH, PUCCH and SRS based on a dynamic grant or a configured grant to which the indicated TCI state is applied are the same as the following UL TX spatial filters:

[0627] - UL TX spatial filter for PUSCH transmission scheduled by RAR UL grant in the random access procedure started with the resetting of the synchronization procedure, or

[0628] - When the UE transmits multiple PRACHs assumed to be transmitted using multiple different spatial filters in the last random access attempt of the latest initial access procedure started by the reconfiguration of the synchronization procedure, the UL TX spatial filter used for PRACH transmission scheduled by the first / last / arbitrary RAR UL grant among multiple RAR UL grants corresponding to multiple PDSCHs with contention resolution identifiers received by the UE (or PUSCH transmission corresponding to the RAR UL grant).

[0629] ---BFR

[0630] In the control physical layer process, at least one of the following provisions may also be specified.

[0631] [Provision 3a]

[0632] In PCell or PSCell, UE can be provided with the configuration for PRACH transmission through PRACH-ResourceDedicatedBFR. new In the PRACH in slot n associated with the periodic CSI-RS resource configuration or the antenna port QCL parameters associated with the SS / PBCH block, the UE monitors the following PDCCH, which is provided by the recoverySearchSpaceId to detect the DCI format with the CRC scrambled by the C-RNTI or MCS-C-RNTI, starting from slot n+4+2 μ ･k mac Here, μ is the SCS setting for the PRACH transmission, k is the PDCCH in the search space set that starts. mac is the number of time slots provided by K-Mac, or k if K-Mac is not providedmac = 0. For PDCCH monitoring and corresponding PDSCH reception within the search space set provided by recoverySearchSpaceId, the UE assumes that new The UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or any one of the multiple parameters of at least one of tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList through a higher layer. After the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI in the search space set provided by recoverySearchSpaceId, the UE continues to monitor PDCCH candidates in the search space set provided by recoverySearchSpaceId until the UE receives a MAC CE activation command for a TCI state or any one of the multiple parameters of at least one of tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList.

[0633] [Provision 3b]

[0634] In a PCell or PSCell, after 28 symbols from the last symbol received for the initial PDCCH in the search space set provided by recoverySearchSpaceId in a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI for the UE to detect, until the UE receives an activation command for PUCCH-SpatialRelationInfo or until the UE is provided with PUCCH-SpatialRelationInfo for PUCCH resources, the UE transmits PUCCH on the same cell as the PRACH transmission using the following parameters:

[0635] - the same spatial filter as that used for the latest PRACH transmission, or, when the UE transmits multiple PRACHs assumed to be transmitted using different spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery purposes, the spatial filter used for the PUSCH transmission (or the PRACH transmission corresponding to the RAR UL grant) scheduled by the first / last / arbitrary RAR UL grant among multiple RAR UL grants corresponding to multiple PDSCHs, received by the UE and accompanied by a contention resolution identifier or a PDCCH indicating the success of random access,

[0636] - Use q u =0,q d =q new , and the power determined by l=0.

[0637] [Regulation 3c]

[0638] For PCell or PSCell, and q0 bar and q1 bar, 28 symbols after the last symbol received from the first PDCCH in the search space set provided by recoverySearchSpaceId for UE detection of DCI format with CRC scrambled by C-RNTI or MCS-C-RNTI, the UE assumes that the search space set with index q1 is the same as the search space set with index q2 in the PDCCH monitoring in CORESET with index 0. new The antenna port QCL parameters are the same as the associated antenna port QCL parameters.

[0639] [Regulation 3d]

[0640] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, the UE follows the following rules after X symbols from the last symbol of the initial PDCCH reception within the search space set provided by recoverySearchSpaceId and the UE detects a DCI format with a CRC scrambled by C-RNTI or MCS-C-RNTI.

[0641] - If AdditionalPCIInfo is not provided, the UE monitors the PDCCH in all CORESETs and receives the PDSCH and aperiodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH using the following antenna port QCL parameters:

[0642] -- If the corresponding index qnew If the associated antenna port QCL parameter exists, then the antenna port QCL parameter that is the same as the antenna port QCL parameter, or,

[0643] -- In the case of sending multiple PRACHs assumed using different multiple spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery purposes, the same spatial domain filter as the spatial domain filter used for the PUSCH transmission scheduled by the first / last / arbitrary RAR UL grant among the multiple RAR UL grants corresponding to multiple PDSCHs received by the UE and accompanied by a contention resolution identifier or a PDCCH indicating the success of random access (or the PRACH transmission corresponding to the RAR UL grant).

[0644] [Regulation 3e]

[0645] When a PDCCH reception includes two PDCCH candidates from two linked search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the later-ending PDCCH candidate (of the two PDCCH candidates). If the UE needs to monitor one of the two PDCCH candidates, the PDCCH reception includes both PDCCH candidates.

[0646] [Regulation 3f]

[0647] For PCell or PSCell, when a BFR MAC CE is provided in Msg3 or MsgA of the CBRA procedure and PUCCH resources with PUCCH-SpatialRelationInfo are provided, the UE shall transmit the PUCCH on the same cell as the PRACH transmission 28 symbols after the last symbol received from the PDCCH that determines the end of the CBRA procedure, using the following parameters:

[0648] - The same spatial filter as that used for the latest PRACH transmission, or, when the UE transmits multiple PRACHs assumed to be transmitted using multiple different spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery, the same spatial domain filter as that used for PUSCH transmission (or PRACH transmission corresponding to the RAR UL grant) scheduled by the first / last / arbitrary RAR UL grant among multiple RAR UL grants corresponding to multiple PDSCHs received by the UE and accompanied by a contention resolution identifier or a PDCCH indicating the success of random access.

[0649] - Use q u =0,q d =q new , and the power determined by l=0. Here, q new It is the SS / PBCH block index selected for the latest PRACH transmission.

[0650] [Regulation 3g]

[0651] When the UE is provided with TCI-State_r17 indicating a unified TCI state for the PCell or PSCell, and the UE provides a BFR MAC CE in Msg3 or MsgA of the CBRA procedure, the UE follows the following rules after X symbols from the last symbol received in the PDCCH that determines the end of the CBRA procedure.

[0652] - In the case that AdditionalPCIInfo is not provided, if the corresponding index q new If the associated antenna port QCL parameter exists, the UE uses the same antenna port QCL parameter as the antenna port QCL parameter, monitors the PDCCH in all CORESETs, receives the PDSCH, and the non-periodic CSI-RS from the CSI-RS resource set with the same TCI state as the indicated TCI state for the PDCCH and the PDSCH.

[0653] - The UE transmits the PUCCH, the PUSCH, and the SRS using the same spatial domain filter with the same TCI state as that used for the PUCCH and PUSCH:

[0654] -- the same spatial domain filter as that used for the latest PRACH transmission, or

[0655] -- When the UE transmits multiple PRACHs assumed using different multiple spatial filters in the last random access attempt of the latest random access procedure triggered for beam failure recovery purposes, the same spatial domain filter as the spatial domain filter used for the PUSCH transmission scheduled by the first / last / arbitrary RAR UL grant among the multiple RAR UL grants corresponding to multiple PDSCHs received by the UE and accompanied by a contention resolution identifier or a PDCCH indicating the success of random access (or the PRACH transmission corresponding to the RAR UL grant).

[0656] According to this embodiment, the UE can appropriately determine the default beam in scenario 1.

[0657] <Implementation Method #2>

[0658] This embodiment relates to scenario 2.

[0659] - Implementation #2-1: RAR monitoring beam in RA

[0660] When a UE sends multiple PRACHs using different beams corresponding to different multiple SSB / CSI-RSs in one RACH attempt during the initial access process, and is assumed to receive only one RAR sent for the multiple PRACHs, the UE may also follow at least one of the following options.

[0661] -- Option 1

[0662] The UE monitors the RAR within the determined RAR window using the same beam as the first / last received beam among multiple SSB / CSI-RS receptions associated with multiple PRACH transmissions.

[0663] For example, in the case where the RAR monitoring beam is the "initial" received beam, the aforementioned Figure 5 In the example, the RAR monitoring beam is the beam of SSB#1. For example, when the RAR monitoring beam is the "last" received beam, the aforementioned Figure 5 In the example, the RAR monitoring beam is the beam of SSB#4.

[0664] -- Option 2

[0665] The UE follows the rules and uses different beams to monitor the RAR in different monitoring opportunities (MOs) within the determined RAR window.

[0666] For example, in the aforementioned Figure 5 In the example, the UE uses the beam of SSB#1 in the first MO within the RAR window, the beam of SSB#2 in the second MO within the RAR window, and the beam of SSB#k (k=1,2,3,4) in the kth MO within the RAR window to monitor the RAR.

[0667] - Implementation #2-2: Msg3 Transmission Beam in RA

[0668] When a UE sends multiple PRACHs using different beams corresponding to different multiple SSB / CSI-RSs in one RACH attempt during the initial access process, and is assumed to receive only one RAR sent for the multiple PRACHs, the UE may also follow at least one of the following options.

[0669] -- Option 1

[0670] For the Msg3 transmission beam, a new field or reserved bit within the RAR explicitly indicated by the RAR UL grant may also indicate one of multiple PRACH transmission beams. For example, '00' may indicate the first UL transmission beam used for PRACH transmission, '01' may indicate the second UL transmission beam used for PRACH transmission, '10' may indicate the third UL transmission beam used for PRACH transmission, and '11' may indicate the fourth UL transmission beam used for PRACH transmission. The indicated beam is used for Msg3 transmission.

[0671] -- Option 2

[0672] The Msg3 transmission beam can also be implicitly determined based on the monitored / received RAR beam. If the UE successfully performs RAR monitoring using the SSB / CSI-RS beam corresponding to the first / second / third / fourth PRACH transmission, the UE can also transmit Msg3 using the same UL transmission beam as the UL transmission beam of the PRACH transmission.

[0673] -- Option 3

[0674] The Msg3 transmit beam can also be implicitly determined based on the RA-RNTI of the monitored / received RAR. If the UE successfully monitors the RAR using the RA-RNTI calculated based on the first / second / third / fourth PRACH transmission, the UE can also transmit Msg3 using the same UL transmit beam as that used for the PRACH transmission.

[0675] - Implementation #2-3: Msg4 monitoring beam in RA

[0676] When a UE sends multiple PRACHs using different beams corresponding to different multiple SSB / CSI-RSs in one RACH attempt during the initial access process, and is assumed to receive only one RAR sent for the multiple PRACHs, the UE may also follow at least one of the following options.

[0677] -- Option 1

[0678] The Msg4 monitoring beam is the same beam used for monitoring the (detected) RAR. The beam where the UE successfully monitors / detects the RAR can also be used for Msg4 monitoring.

[0679] -- Option 2

[0680] The Msg4 monitoring beam is explicitly indicated by the RAR. Similar to option 1 of implementation #2-2, a new field or reserved bit within the RAR may also indicate multiple monitoring beams for Msg4. A new field or reserved bit within the RAR may also indicate one beam among multiple SSB / CSI-RSs for multiple PRACH transmissions. For example, '00' may indicate the SSB / CSI-RS for the first PRACH transmission, '01' may indicate the SSB / CSI-RS for the second PRACH transmission, '10' may indicate the SSB / CSI-RS for the third PRACH transmission, and '11' may indicate the SSB / CSI-RS for the fourth PRACH transmission, and the indicated SSB / CSI-RS beam is used for Msg4 monitoring.

[0681] -- Option 3

[0682] The Msg4 monitoring beam can also be implicitly determined based on the RA-RNTI of the monitored / received RAR. If a UE successfully monitors the RAR using the RA-RNTI calculated based on the first / second / third / fourth PRACH transmission, the UE can also monitor Msg4 using the SSB / CSI-RS beam used for that PRACH transmission.

[0683] -- Option 4

[0684] Different multiple Msg4 monitoring beams within different multiple monitoring opportunities (MO) are determined according to a rule.

[0685] For example, in the aforementioned Figure 5 In the example, the UE uses the beam of SSB#1 in the first MO within the contention resolution window, uses the beam of SSB#2 in the second MO within the contention resolution window, and uses the beam of SSB#k (k=1,2,3,4) in the kth MO within the contention resolution window to monitor Msg4.

[0686] - Implementation #2-4: DL default beam after RA

[0687] When a UE sends multiple PRACHs using different beams corresponding to different multiple SSB / CSI-RSs in one RACH attempt during the initial access process, and is assumed to receive only one RAR sent for the multiple PRACHs, the UE may also follow at least one of the following options.

[0688] -- Option 1

[0689] The UE determines the default beam for PDCCH / PDSCH / CSI-RS (DL default beam) to be the same beam as the beam used for monitoring (detected) RA.

[0690] -- Option 2

[0691] The UE determines the default beam for PDCCH / PDSCH / CSI-RS to be the beam explicitly or implicitly indicated by the RAR. This indication may also follow the following options.

[0692] --- Option 2-1: Explicit Instruction

[0693] Similar to Option 1 of Implementation #2, a new field or reserved bit within the RAR may also indicate a default beam for PDCCH / PDSCH / CSI-RS after the completion of RA. A new field or reserved bit within the RAR may also indicate one beam among multiple SSB / CSI-RS for multiple PRACH transmissions. For example, '00' may indicate the SSB / CSI-RS for the first PRACH transmission, '01' may indicate the SSB / CSI-RS for the second PRACH transmission, '10' may indicate the SSB / CSI-RS for the third PRACH transmission, and '11' may indicate the SSB / CSI-RS for the fourth PRACH transmission. The indicated beam of SSB / CSI-RS is used as the default beam for PDCCH / PDSCH / CSI-RS after the completion of RA.

[0694] ---change

[0695] The field / bit used to indicate the default beam for PDCCH / PDSCH / CSI-RS after the end of RA can also be the same as the field / bit of at least one of the Msg3 transmission beam in option 1 of implementation #2-2 and the Msg4 monitoring beam in implementation #2-3.

[0696] --- Option 2-2: Implicit indication based on the RA-RNTI used by the detected RAR

[0697] When the UE successfully monitors the RAR using the RA-RNTI calculated based on the 1st / 2nd / 3rd / 4th PRACH transmission, the SSB / CSI-RS beam used for the PRACH transmission can also be used as the default beam for PDCCH / PDSCH / CSI-RS after the RA is completed.

[0698] -- Option 3

[0699] The UE determines the default beam for PDCCH / PDSCH / CSI-RS to be the same beam as that used for monitoring of (detected) Msg4.

[0700] -- Option 4

[0701] The UE determines the default beam for PDCCH / PDSCH / CSI-RS to be the beam explicitly indicated by Msg 4. The indication of the default beam for PDCCH / PDSCH / CSI-RS after RA is completed may also follow the following options.

[0702] --- Option 4-1

[0703] This indication may also be a new field or an existing field (reinterpretation of the existing field) of DCI format 1_0 that schedules the DCI for the PDSCH containing the UE contention resolution identifier and is accompanied by a CRC scrambled by the TC-RNTI.

[0704] --- Option 4-2

[0705] The indication may also be a PDSCH including a UE contention resolution identifier and a default beam indication.

[0706] The DCI format 1_0 or the PDSCH may also indicate a beam of one SSB / CSI-RS among multiple SSB / CSI-RSs for multiple PRACH transmissions. For example, '00' may indicate the SSB / CSI-RS for the first PRACH transmission, '01' may indicate the SSB / CSI-RS for the second PRACH transmission, '10' may indicate the SSB / CSI-RS for the third PRACH transmission, and '11' may indicate the SSB / CSI-RS for the fourth PRACH transmission. The indicated SSB / CSI-RS beam is used as the default beam for PDCCH / PDSCH / CSI-RS after RA is completed.

[0707] - Implementation #2-5: UL default beam after RA

[0708] When a UE sends multiple PRACHs using different beams corresponding to different multiple SSB / CSI-RSs in one RACH attempt during the initial access process, and is assumed to receive only one RAR sent for the multiple PRACHs, the UE may also follow at least one of the following options.

[0709] -- Option 1

[0710] The UE determines the default beam for PUCCH / PUSCH (UL default beam) to be the same beam as the beam used for Msg3 transmission.

[0711] In implementation #1-2, "the UL TX spatial filter used for the PRACH transmission corresponding to the first / last / arbitrary PDSCH among multiple PDSCHs accompanied by a contention resolution identifier received by the UE (or, the PUSCH transmission scheduled by the RAR UL grant)" can also be rewritten as "the same spatial transmission filter as the spatial transmission filter used for the PUSCH transmission scheduled by the RAR UL grant in the initial access procedure / random access procedure."

[0712] -- Option 2

[0713] The UE determines the default beam for PUCCH / PUSCH as the beam explicitly or implicitly indicated by the RAR. This indication may also follow the following options.

[0714] --- Option 2-1: Explicit Instruction

[0715] Similar to Option 1 of Implementation #2, a new field or reserved bit within the RAR may also indicate a default beam for PUCCH / PUSCH after the completion of RA. A new field or reserved bit within the RAR may also indicate one beam among multiple SSB / CSI-RSs for multiple PRACH transmissions. For example, '00' may indicate the SSB / CSI-RS for the first PRACH transmission, '01' may indicate the SSB / CSI-RS for the second PRACH transmission, '10' may indicate the SSB / CSI-RS for the third PRACH transmission, and '11' may indicate the SSB / CSI-RS for the fourth PRACH transmission. The indicated SSB / CSI-RS beam is used as the default beam for PUCCH / PUSCH after the completion of RA.

[0716] --- Option 2-2: Implicit indication based on the RA-RNTI used by the detected RAR

[0717] When the UE successfully monitors the RAR using the RA-RNTI calculated based on the 1st / 2nd / 3rd / 4th PRACH transmission, the SSB / CSI-RS beam used for the PRACH transmission can also be used as the default beam for PUCCH / PUSCH after the RA is completed.

[0718] -- Option 3

[0719] The UE determines the default beam for PUCCH / PUSCH to be the beam explicitly indicated by Msg 4. The indication of the default beam for PUCCH / PUSCH after RA is completed may also follow the following options.

[0720] --- Option 3-1

[0721] This indication may also be a new field or an existing field (reinterpretation of the existing field) of DCI format 1_0 that schedules the DCI for the PDSCH containing the UE contention resolution identifier and is accompanied by a CRC scrambled by the TC-RNTI.

[0722] --- Option 3-2

[0723] The indication may also be a PDSCH including a UE contention resolution identifier and a default beam indication.

[0724] The DCI format 1_0 or the PDSCH may also indicate one UL transmission beam among multiple UL transmission beams for multiple PRACH transmissions. For example, '00' may indicate the UL transmission beam for the first PRACH transmission, '01' may indicate the UL transmission beam for the second PRACH transmission, '10' may indicate the SSB / CSI-RS for the third PRACH transmission, and '11' may indicate the UL transmission beam for the fourth PRACH transmission. The indicated SSB / CSI-RS beam is used as the default beam for the PUCCH / PUSCH after the RA is completed.

[0725] -- Option 4

[0726] The UE determines the default beam for PUCCH / PUSCH to be the same beam as that used for monitoring the (detected) RAR or Msg4.

[0727] The beam in which the UE successfully monitors / detects RAR / Mg4 can also be used to determine the default beam for PUCCH / PUSCH. If the UE successfully monitors / detects RAR / Mg4 using the same UL transmit beam as the 1st / 2nd / 3rd / 4th PRACH transmission, the UL transmit beam used for that PRACH transmission can also be used as the default beam for PUCCH / PUSCH after RA completion.

[0728] According to this embodiment, the UE can appropriately determine the default beam in scenario 2.

[0729] <Implementation Method #3>

[0730] This embodiment relates to scenario 3.

[0731] - Implementation #3-1: UL default beam after RA

[0732] When the UE sends multiple PRACHs using different multiple beams corresponding to the same SSB / CSI-RS in a RACH attempt during the initial access process, and receives multiple Msg4s sent for the multiple PRACHs, the UE may also follow at least one of options 1 to 3 in implementation #1-2.

[0733] According to this embodiment, the UE can appropriately determine the default beam in scenario 3.

[0734] <Implementation Method #4>

[0735] This embodiment relates to scenario 4.

[0736] - Implementation #4-1: Msg3 Transmit Beam in RA

[0737] When the UE sends multiple PRACHs using different multiple beams corresponding to the same SSB / CSI-RS within a RACH attempt during the initial access process, and is assumed to receive only one RAR sent for the multiple PRACHs, the UE may also follow at least one of options 1 and 3 in implementation #2-2.

[0738] - Implementation #4-2: UL default beam after RA

[0739] When the UE sends multiple PRACHs using different multiple beams corresponding to the same SSB / CSI-RS within a RACH attempt during the initial access process, and is assumed to receive only one RAR sent for the multiple PRACHs, the UE may also follow at least one of options 1 to 3 in implementation methods #2-5.

[0740] According to this embodiment, the UE can appropriately determine the default beam in scenario 4.

[0741] <Supplement>

[0742] [Notification of information to UE]

[0743] In the above-mentioned embodiment, the notification of arbitrary information (from the network (NW)) (e.g., the base station (BS))) to the UE (in other words, the reception of arbitrary information from the BS in the UE) can also be performed using physical layer signaling (e.g., DCI), high-layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals) or a combination thereof.

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

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

[0746] Furthermore, the notification of arbitrary information to the UE in the above-mentioned embodiments may be performed periodically, semi-continuously, or aperiodically.

[0747] [Notification of information from UE]

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

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

[0750] When the notification is performed using UCI, the notification may be transmitted using PUCCH or PUSCH.

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

[0752] [Regarding the application of each embodiment]

[0753] At least one of the above embodiments may also be applied to a situation where a specific condition is satisfied. The specific condition may be specified in a specification or may be notified to the UE / BS using higher layer signaling / physical layer signaling.

[0754] At least one of the above-mentioned embodiments may also be applied only to UEs that report a specific UE capability (UE capability) or support the specific UE capability.

[0755] The specific UE capability may also indicate at least one of the following:

[0756] The UE supports multiple PRACH transmissions using different multiple transmission beams corresponding to different multiple SSB / CSI-RS.

[0757] The UE supports multiple PRACH transmissions using different multiple transmission beams corresponding to the same SSB / CSI-RS.

[0758] The UE supports separate RAR / Msg3 / Msg4 for multiple PRACH transmissions using different multiple transmission beams corresponding to different multiple SSB / CSI-RS.

[0759] The UE supports a single RAR for multiple PRACH transmissions using different multiple transmission beams corresponding to different multiple SSB / CSI-RSs.

[0760] The UE supports separate RAR / Msg3 / Msg4 for multiple PRACH transmissions using different multiple transmission beams corresponding to the same SSB / CSI-RS.

[0761] The UE supports a single RAR for multiple PRACH transmissions using different multiple transmission beams corresponding to the same SSB / CSI-RS.

[0762] The UE supports RAR indicating the Msg3 transmission beam (or Msg4 monitoring beam) for the case of multiple PRACH transmission using different multiple transmission beams.

[0763] The UE supports RAR / Msg4 indicating the default beam of PDCCH / PDSCH / CSI-RS for the case of multiple PRACH transmissions using different multiple transmission beams corresponding to different multiple SSB / CSI-RSs.

[0764] The UE supports RAR / Msg4 indicating the default beam of PUCCH / PUSCH for the case of multiple PRACH transmissions using different multiple transmission beams.

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

[0766] Furthermore, the specific UE capability may be a capability applied across all duplex modes (common regardless of the duplex mode) or a capability for each duplex mode (eg, time division duplex (TDD) or frequency division duplex (FDD)).

[0767] Furthermore, at least one of the above-mentioned embodiments may also be applied to a case where specific information associated with the above-mentioned embodiments (or actions of the above-mentioned embodiments) is configured / activated / triggered by the UE through higher layer signaling / physical layer signaling. For example, the specific information may be information indicating activation of the actions of the above-mentioned embodiments, arbitrary RRC parameters for a specific release (e.g., Rel. 18 / 19), etc.

[0768] The UE may also apply Rel.15 / 16 operations, for example, when it does not support at least one of the above-mentioned specific UE capabilities or is not set with the above-mentioned specific information.

[0769] (Note)

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

[0771] [Note 1]

[0772] A terminal having:

[0773] a receiving unit that receives settings for transmitting a plurality of physical random access channels (PRACHs) corresponding to the plurality of spatial domain transmit filters, respectively; and

[0774] The control unit determines a spatial domain transmit filter for uplink transmission based on a specific PRACH among the multiple PRACHs, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier.

[0775] [Note 2]

[0776] The terminal as described in Supplement 1, wherein:

[0777] The control unit monitors one or more random access responses for transmission of the plurality of PRACHs.

[0778] [Note 3]

[0779] The terminal as described in Supplement 1 or Supplement 2, wherein:

[0780] The control unit monitors one random access response for transmission of the plurality of PRACHs.

[0781] [Note 4]

[0782] The terminal according to any one of Supplement 1 to Supplement 3, wherein:

[0783] The control unit receives one or more random access responses for the transmission of the plurality of PRACHs, and determines the spatial domain transmit filter based on a specific random access response among the one or more random access responses.

[0784] (Note)

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

[0786] [Note 1]

[0787] A terminal having:

[0788] Receiver unit, receive beam failure recovery settings, and,

[0789] A control unit determines antenna port quasi-co-location parameters for monitoring a physical downlink control channel (PDCCH) for at least one of a plurality of PRACHs corresponding respectively to a plurality of spatial domain transmit filters for beam failure recovery, based on a specific PRACH within a specific random access procedure, a downlink control information (DCI) format detected in a search space for beam failure recovery, a random access response within the specific random access procedure, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier within the specific random access procedure.

[0790] [Note 2]

[0791] The terminal as described in Supplement 1, wherein:

[0792] The control unit monitors one or more random access responses for transmission of the plurality of PRACHs.

[0793] [Note 3]

[0794] The terminal as described in Supplement 1 or Supplement 2, wherein:

[0795] The control unit monitors one random access response for transmission of the plurality of PRACHs.

[0796] [Note 4]

[0797] The terminal according to any one of Supplement 1 to Supplement 3, wherein:

[0798] The control unit determines the antenna port quasi co-location parameter based on a specific reference signal among a plurality of reference signals for receiving DCI formats transmitted for the plurality of PRACHs and any one of the one or more DCI formats transmitted for the plurality of PRACHs.

[0799] (Note)

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

[0801] [Note 1]

[0802] A terminal having:

[0803] a receiving unit that receives settings for transmitting a plurality of physical random access channels (PRACHs) corresponding to the plurality of spatial domain transmit filters, respectively; and

[0804] The control unit determines a quasi-co-location assumption for downlink reception based on a specific PRACH among the multiple PRACHs, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier.

[0805] [Note 2]

[0806] The terminal as described in Supplement 1, wherein:

[0807] The control unit monitors one or more random access responses for transmission of the plurality of PRACHs.

[0808] [Note 3]

[0809] The terminal as described in Supplement 1 or Supplement 2, wherein:

[0810] The control unit monitors one random access response for transmission of the plurality of PRACHs.

[0811] [Note 4]

[0812] The terminal according to any one of Supplement 1 to Supplement 3, wherein:

[0813] The control unit determines the quasi co-location assumption based on a specific reference signal among multiple reference signals corresponding to a PDSCH accompanied by a contention resolution identifier for the transmission of the multiple PRACHs, and any one of the specific PDSCHs among one or more PDSCHs accompanied by a contention resolution identifier for the transmission of the multiple PRACHs.

[0814] (Wireless Communication System)

[0815] The following describes a configuration of a wireless communication system according to an embodiment of the present disclosure. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof.

[0816] Figure 8This figure illustrates an example of a schematic configuration of a wireless communication system according to one embodiment. Wireless communication system 1 (also referred to simply as system 1) may be a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP), the fifth-generation mobile communication system New Radio (5GNR), or the like.

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

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

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

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

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

[0822] 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)). Macrocell C1 may be included in FR1, and small cell C2 may be included in FR2. For example, FR1 may be a frequency band below 6 GHz (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). The frequency bands and definitions of FR1 and FR2 are not limited to these. For example, FR1 may correspond to a frequency band higher than FR2.

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

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

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

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

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

[0828] In the wireless communication system 1 , a radio access scheme based on orthogonal frequency division multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and uplink (UL), cyclic prefix OFDM (CP-OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), orthogonal frequency division multiple access (OFDMA), or single carrier frequency division multiple access (SC-FDMA) may be used.

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

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

[0831] In addition, as uplink channels, the wireless communication system 1 can also use 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)), etc.

[0832] The PDSCH transmits user data, higher-layer control information, and the System Information Block (SIB). The PUSCH also transmits user data and higher-layer control information. The PBCH also transmits the Master Information Block (MIB).

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

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

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

[0836] A search space may also correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space set. Furthermore, the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and so on, used in this disclosure, may be interchangeable.

[0837] The PUCCH can also transmit uplink control information (uplink control information (UCI)) including at least one of channel state information (CSI), delivery confirmation information (e.g., also known as hybrid automatic repeat request ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH can also transmit the random access preamble used to establish a connection with a cell.

[0838] In the present disclosure, downlink, uplink, etc. may be expressed without the word “link.” In addition, various channels may be expressed without the word “Physical” at the beginning.

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

[0840] For example, a synchronization signal may be at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SSs (PSS, SSS) and PBCHs (and DMRS for the PBCH) may also be referred to as an SS / PBCH block or an SS block (SSB). Furthermore, SSs and SSBs may also be referred to as reference signals.

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

[0842] (Base Station)

[0843] Figure 9 This figure illustrates an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission path interface (transmission line interface) 140. Furthermore, one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140 may be provided.

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

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

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

[0847] Transmitter / receiver unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. Baseband unit 121 may also include a transmit processing unit 1211 and a receive processing unit 1212. Transmitter / receiver unit 120 may include a transmitter / receiver, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmit / receive circuits, and the like, as described based on common knowledge in the technical fields involved in this disclosure.

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

[0849] The transmitting and receiving antenna 130 can be formed of an antenna described based on common knowledge in the technical field to which this disclosure relates, such as an array antenna.

[0850] The transmitting and receiving unit 120 may also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may also receive the aforementioned uplink channel, uplink reference signal, etc.

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

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

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

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

[0855] On the other hand, the transmitting and receiving unit 120 (RF unit 122 ) may also perform amplification, filtering, and demodulation into baseband signals on the radio frequency band signals received via the transmitting and receiving antenna 130 .

[0856] The transmitting and receiving unit 120 (receiving processing unit 1212) may also apply receiving processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filtering processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to obtain user data, etc.

[0857] The transmitting / receiving unit 120 (measuring unit 123) may also perform measurements related to received signals. For example, the measuring unit 123 may perform radio resource management (RRM) measurements and channel state information (CSI) measurements based on the received signals. The measuring unit 123 may also 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)), and propagation path information (e.g., CSI). The measurement results may also be output to the control unit 110.

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

[0859] In addition, the transmitting unit and the receiving unit of the base station 10 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 120 , the transmitting and receiving antenna 130 , and the transmission path interface 140 .

[0860] Furthermore, the transmitting / receiving unit 120 may also transmit configurations for transmitting multiple physical random access channels (PRACHs) corresponding to the multiple spatial domain transmit filters. The control unit 110 may also determine the spatial domain transmit filter for uplink transmission based on any one of the multiple PRACHs: a specific PRACH, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier.

[0861] In addition, the transmitting and receiving unit 120 may also transmit a beam failure recovery configuration. The control unit 110 may also determine antenna port quasi-co-location parameters for monitoring a physical downlink control channel (PDCCH) for at least one of a plurality of PRACHs corresponding to each of the plurality of spatial domain transmit filters for beam failure recovery based on a specific PRACH within a specific random access procedure, a downlink control information (DCI) format detected within the search space for beam failure recovery, a random access response within the specific random access procedure, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier within the specific random access procedure.

[0862] Furthermore, the transmitting / receiving unit 120 may also transmit a configuration for transmitting multiple physical random access channels (PRACHs) corresponding to the multiple spatial domain transmit filters. The control unit 110 may also determine a quasi-co-location assumption for downlink reception based on any one of a specific PRACH among the multiple PRACHs, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier.

[0863] (User Terminal)

[0864] Figure 10 This figure shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Furthermore, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

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

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

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

[0868] The transceiver unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may include a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter (phase shifter), a measurement circuit, a transceiver circuit, and the like, which are described based on common knowledge in the technical fields involved in this disclosure.

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

[0870] The transmitting and receiving antenna 230 can be formed of an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

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

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

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

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

[0875] Furthermore, whether or not to apply DFT processing may also be determined based on the transform precoding configuration. For a particular channel (e.g., PUSCH), if transform precoding is enabled, the transceiver unit 220 (transmit processing unit 2211) may perform DFT processing as part of the aforementioned transmission process in order to transmit the channel using a DFT-s-OFDM waveform. Otherwise, the transceiver unit 220 (transmit processing unit 2211) may perform DFT processing as part of the aforementioned transmission process.

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

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

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

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

[0880] In addition, the measurement unit 223 may also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may also be, for example, non-zero power (NZP) CSI-RS resources. In addition, the measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may also be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, and the like. In addition, CSI-IM may also be referred to as CSI-Interference Management (IM) and may be interchangeable with Zero Power (ZP) CSI-RS. In addition, in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeable.

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

[0882] Furthermore, the transmitting / receiving unit 220 may also receive configurations for transmitting multiple physical random access channels (PRACHs), each corresponding to a plurality of spatial domain transmit filters. The control unit 210 may also determine a spatial domain transmit filter for uplink transmission based on any one of the multiple PRACHs: a specific PRACH, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier.

[0883] The control unit 210 may also monitor one or more random access responses for the transmission of the multiple PRACHs.

[0884] The control unit 210 may also monitor one random access response for the transmission of the multiple PRACHs.

[0885] The control unit 210 may also receive one or more random access responses for the transmission of the multiple PRACHs, and determine the spatial domain transmit filter based on a specific random access response among the one or more random access responses.

[0886] In addition, the transmitting and receiving unit 220 may also receive a beam failure recovery configuration. The control unit 210 may also determine antenna port quasi-co-location parameters for monitoring a physical downlink control channel (PDCCH) for at least one of a plurality of PRACHs corresponding to each of the plurality of spatial domain transmit filters for beam failure recovery based on a specific PRACH within a specific random access procedure, a downlink control information (DCI) format detected within the search space for beam failure recovery, a random access response within the specific random access procedure, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier within the specific random access procedure.

[0887] The control unit 210 may also monitor one or more random access responses for the transmission of the multiple PRACHs.

[0888] The control unit 210 may also monitor one random access response for the transmission of the multiple PRACHs.

[0889] The control unit 210 may also determine the antenna port quasi-co-location parameter based on any one of the following: a specific reference signal among multiple reference signals for receiving the DCI format sent for the multiple PRACHs; and a DCI format among one or more DCI formats sent for the multiple PRACHs.

[0890] Furthermore, the transmitting / receiving unit 220 may also receive a configuration for transmitting multiple physical random access channels (PRACHs) corresponding to the multiple spatial domain transmit filters. The control unit 210 may also determine a quasi-co-location assumption for downlink reception based on any one of a specific PRACH among the multiple PRACHs, a random access response, a physical uplink shared channel (PUSCH) scheduled by the random access response, and a physical downlink shared channel (PDSCH) with a contention resolution identifier.

[0891] The control unit 210 may also monitor one or more random access responses for the transmission of the multiple PRACHs.

[0892] The control unit 210 may also monitor one random access response for the transmission of the multiple PRACHs.

[0893] The control unit 210 may also determine the quasi-co-location assumption based on any one of the following: a specific reference signal among multiple reference signals for a PDSCH, wherein the one PDSCH is a PDSCH accompanied by a contention resolution identifier for the transmission of the multiple PRACHs; and a specific PDSCH among more than one PDSCH accompanied by a contention resolution identifier for the transmission of the multiple PRACHs.

[0894] (Hardware structure)

[0895] Furthermore, the block diagrams used in the description of the above embodiments illustrate blocks of functional units. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. Furthermore, the implementation method of each functional block is not particularly limited. Specifically, each functional block can be implemented using a single device that is physically or logically combined, or by connecting two or more physically or logically separate devices directly or indirectly (e.g., by wired or wireless connections) to implement these multiple devices. A functional block can also be implemented by combining one or more of these devices with software.

[0896] Here, the term "function" includes, but is not limited to, judging, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. For example, a functional block (structural unit) that implements a transmitting function may also be referred to as a transmitting unit, a transmitter, or the like. Any of these terms are as described above, and their implementation methods are not particularly limited.

[0897] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 11 This figure shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. The base station 10 and user terminal 20 described above can also 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, and a bus 1007.

[0898] In this disclosure, the terms "device," "circuit," "equipment," "section," and "unit" are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figures, or may exclude some of the devices.

[0899] For example, although only one processor 1001 is shown, multiple processors may be provided. Furthermore, processing may be performed by a single processor, or by two or more processors simultaneously, sequentially, or using other methods. Furthermore, processor 1001 may be implemented using more than one chip.

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

[0901] Processor 1001 controls the entire computer by, for example, operating an operating system. Processor 1001 may also be comprised of a central processing unit (CPU) including interfaces with peripheral devices, a control device, a computing device, registers, and the like. For example, at least a portion of the aforementioned control unit 110 (210) and transceiver unit 120 (220) may also be implemented by processor 1001.

[0902] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes based on these programs. As a program, a program that causes a computer to execute at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and executed by the processor 1001, and the other functional blocks can also be implemented similarly.

[0903] Memory 1002 may also be a computer-readable recording medium, such as at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), or other suitable storage medium. Memory 1002 may also be referred to as a register, a cache, a main memory (main storage device), or the like. Memory 1002 can store executable programs (program code), software modules, and the like for implementing the wireless communication method according to an embodiment of the present disclosure.

[0904] Storage 1003 may also be a computer-readable recording medium, such as at least one of a flexible disk, a floppy disk, an optical disk (such as a compact disk (Compact Disc ROM (CD-ROM))), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (such as a card, stick, or 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.

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

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

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

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

[0909] (Variation)

[0910] In addition, the terms described in this disclosure and the terms required for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be replaced with each other. In addition, a signal may also be a message. Reference Signal (RS) may also be referred to as RS, and may also be referred to as Pilot, Pilot Signal, etc. depending on the applied standard. In addition, Component Carrier (CC) may also be referred to as Cell, Frequency Carrier, Carrier Frequency, etc.

[0911] A radio frame can also be composed of one or more time periods (frames) in the time domain. Each of these one or more time periods (frames) that make up a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (for example, 1ms) that is independent of the numerology.

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

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

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

[0915] Radio frames, subframes, time slots, mini-slots, and symbols all represent time units used for signal transmission. Radio frames, subframes, time slots, mini-slots, and symbols may also be referred to by their respective equivalents. Furthermore, the time units of frame, subframe, time slot, mini-slot, and symbol in this disclosure may be interchangeable.

[0916] For example, a subframe can be called a TTI, multiple consecutive subframes can be called a TTI, and a slot or a mini-slot can be called a TTI. That is, at least one of a subframe and a TTI can 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. Furthermore, the unit representing a TTI can be called a slot, a mini-slot, or the like, rather than a subframe.

[0917] Here, TTI refers to, for example, the minimum time unit used for scheduling in wireless communications. For example, in the LTE system, a base station schedules each user terminal by allocating radio resources (such as the frequency bandwidth and transmit power available to each user terminal) in TTI units. The definition of TTI is not limited to this.

[0918] A TTI can also be a unit of time for transmitting channel-coded data packets (transport blocks), code blocks, code words, etc., and can also be a unit of processing for scheduling, link adaptation, etc. Furthermore, when a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, code block, code word, etc. is actually mapped can be shorter than the TTI.

[0919] Furthermore, while a time slot or mini-slot is referred to as a TTI, one or more TTIs (i.e., one or more time slots or one or more mini-slots) can also be the minimum time unit for scheduling. Furthermore, the number of time slots (mini-slots) that constitute this minimum time unit for scheduling can also be controlled.

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

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

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

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

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

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

[0926] A Bandwidth Part (BWP) (also known as a fractional bandwidth) can also represent a subset of contiguous common resource blocks (RBs) used for a particular parameter set within a carrier. Common RBs can also be identified by their index relative to the common reference point for that carrier. PRBs can also be defined within a BWP and numbered within that BWP.

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

[0928] At least one of the configured BWPs may be activated, and the UE may not assume that it will transmit or receive specific signals / channels outside the activated BWP.

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

[0930] Furthermore, the information and parameters described in this disclosure may be expressed as absolute values, relative values ​​relative to a specific value, or other corresponding information. For example, wireless resources may be indicated by specific indexes.

[0931] The names used for parameters, etc. in this disclosure are not intended to be limiting in any respect. Furthermore, the mathematical formulas used for these parameters may differ from those explicitly disclosed in this disclosure. Various channels (such as PUCCH and PDCCH) and information elements can be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any respect.

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

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

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

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

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

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

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

[0939] The term “software” or “firmware” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, sub-programs, software modules, applications, software applications, software packages, routines, sub-routines, objects, executable files, execution threads, procedures, functions, etc.

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

[0941] The terms "system" and "network" used in this disclosure are interchangeable. "Network" may also refer to devices included in the network (eg, base stations).

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

[0943] Furthermore, in the present disclosure, antenna ports can be interchanged with antenna ports used for any signal / channel (e.g., DeModulation Reference Signal (DMRS) ports). In the present disclosure, resources can be interchanged with resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.). Furthermore, resources can include time / frequency / symbol / space / power resources. Furthermore, a spatial domain transmit filter can include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0944] The above-mentioned group may also 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 (for example, a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, etc.

[0945] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. can also be rewritten.

[0946] In addition, in the present disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state (unified TCI state), common TCI state (common TCI state), joint TCI state, etc. can also be rewritten with each other.

[0947] In addition, in the present disclosure, "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL characteristics (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) characteristics", "specific QCL type (e.g., type A, type D)", etc. can also be rewritten with each other.

[0948] In the present disclosure, index, identifier (ID), indicator, indication, resource ID, etc. may also be overwritten with each other. In the present disclosure, sequence, list, set, group, group, cluster, subset, etc. may also be overwritten with each other.

[0949] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and spatial relationship information (TCI state) can also be overwritten. "Spatial relationship information (TCI state)" can also be overwritten with "a collection of spatial relationship information (TCI state)," "one or more spatial relationship information," and so on. TCI states and TCIs can also be overwritten. Spatial relationship information and spatial relationships can also be overwritten.

[0950] In this disclosure, terms such as "base station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP))", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" are used interchangeably. In some cases, a base station may be referred to as a macrocell, small cell, femtocell, or picocell.

[0951] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the base station's overall coverage area can be divided into multiple smaller areas, each of which can be provided with communications services by a base station subsystem (for example, a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or the entire coverage area of ​​at least one of a base station and a base station subsystem providing communications services within that coverage area.

[0952] In the present disclosure, the matter of a base station sending information to a terminal may be replaced with the matter of the base station instructing the terminal to control / operate based on the information.

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

[0954] The 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, hand set, user agent, mobile client, client, or some other appropriate terminology.

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

[0956] The mobile object refers to a movable object, and the moving speed can be arbitrary, including situations where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, ships (ships and other watercraft), airplanes, rockets, satellites, drones, multicopters, quadcopters, hot air balloons, and objects aboard such objects. Furthermore, the mobile object may also be one that moves autonomously based on operational instructions.

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

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

[0959] The drive unit 41 is composed of, for example, at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also referred to as a handle), and steers at least one of the front wheels 46 and the rear wheels 47 based on the user's operation of the steering wheel.

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

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

[0962] Information service unit 59 is composed of various devices that provide (output) various types of information, including driving information, traffic information, and entertainment information, such as a navigation system, audio system, speakers, displays, televisions, and radios, and one or more ECUs that control these devices. Information service unit 59 uses information acquired from external devices via communication module 60 and other means to provide various information and services (e.g., multimedia information and multimedia services) to the occupants of vehicle 40.

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

[0964] The driving assistance system unit 64 is composed of various devices for providing functions for preventing accidents or reducing the driver's driving burden, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning sensors (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., inertial measurement units (IMUs)), inertial navigation systems (INSs), etc.), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driving assistance system unit 64 transmits and receives various information via the communication module 60 to implement driving assistance functions or autonomous driving functions.

[0965] 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 with the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, microprocessor 61 and memory (ROM, RAM) 62 within the electronic control unit 49, and various sensors 50-58 included in the vehicle 40.

[0966] The communication module 60 is controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, various information can be transmitted and received with the external device via wireless communication. The communication module 60 can be located either inside or outside the electronic control unit 49. Examples of external devices include the aforementioned base station 10 and user terminal 20. Furthermore, the communication module 60 can also be, for example, at least one of the aforementioned base station 10 and user terminal 20 (and can function as at least one of the base station 10 and user terminal 20).

[0967] The communication module 60 may also transmit at least one of the signals input to the electronic control unit 49 from the various sensors 50-58, information obtained based on these signals, and information based on external (user) input received 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, and the like may also be referred to as input units that receive input. For example, the PUSCH transmitted by the communication module 60 may also include information based on these inputs.

[0968] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from external devices and displays it on the vehicle's information service unit 59. The information service unit 59 can also be referred to as 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)).

[0969] 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 can also 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 included in the vehicle 40.

[0970] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, the various methods / implementations of this disclosure can also be applied to a structure in which communication between a base station and a user terminal is replaced by communication between multiple user terminals (e.g., device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, the user terminal 20 can also have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" can also be rewritten with terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channels, downlink channels, etc. can also be rewritten as sidelink channels.

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

[0972] In this disclosure, actions are described as being performed by a base station, and sometimes, depending on circumstances, by its upper node. In a network comprising one or more network nodes including a base station, various operations for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (for example, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0973] The various methods / implementations described in this disclosure may be used individually or in combination, and may be switched between them during execution. Furthermore, the processing procedures, timings, flow charts, and the like of the various methods / implementations described in this disclosure may be reversed as long as they do not conflict. For example, the methods described in this disclosure use an illustrative order to present elements of various steps, but are not limited to the specific order presented.

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

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

[0976] Any reference to an element using the designations "first," "second," etc., as used in this disclosure, does not necessarily define the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to a first and a second element does not imply that only two elements may be used or that the first element must in some way take precedence over the second element.

[0977] The term "determining" as used in this disclosure may encompass a variety of operations. For example, "determining" may also include judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching a table, database, or other data structure), ascertaining, and the like as performing a "determination."

[0978] In addition, “judgment (decision)” may also refer to situations where receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc. are regarded as “judgment (decision)”.

[0979] In other words, "judgment (decision)" can also refer to situations where certain actions are considered to be "judgments (decisions)." Furthermore, "judgment (decision)" can be rewritten as "assuming," "expecting," "considering," and so on. In this disclosure, "judgment (decision)" and the aforementioned operations can be rewritten interchangeably.

[0980] In this disclosure, "determine / determining" can be interchanged with "assume / assuming," "expect / expecting," "consider / considering," and the like. Furthermore, in this disclosure, "not assuming that..." can be interchanged with "assuming that..."

[0981] In the present disclosure, "expect" and "be expected" can be interchanged. For example, "expect(s) ..." ("..." can also be expressed, for example, using the that clause, the to-infinitive, etc.) can be interchanged with "be expected ...". "Does not expect..." can also be interchanged with "Does not expect ...". Furthermore, "An apparatus A is not expected ..." can be interchanged with "An apparatus B other than apparatus A does not expect ..." (for example, when apparatus A is a UE, apparatus B can also be a base station).

[0982] The “maximum transmit power” described in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated maximum transmit power).

[0983] As used in this disclosure, the terms "connected," "coupled," and all variations 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 the two elements being "connected" or "coupled." The coupling or connection between elements can be physical, logical, or a combination thereof. For example, "connected" can also be rephrased as "accessed."

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

[0985] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other." Alternatively, the term may also mean "A and B are each different from C." Terms such as "separate" and "bound" may also be interpreted in the same manner as "different."

[0986] When used in this disclosure, "include," "including," and variations thereof have the same inclusive meaning as the term "comprising." Furthermore, the term "or" used in this disclosure does not mean an exclusive OR.

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

[0988] In the present disclosure, “below,” “less than,” “above,” “more,” “equal to,” and the like may be replaced with each other. Furthermore, in the present disclosure, words meaning “good,” “bad,” “big,” “small,” “high,” “low,” “early,” “slow,” “wide,” “narrow,” and the like are not limited to the positive, comparative, and superlative forms, but may be replaced with each other. Furthermore, in the present disclosure, words meaning “good,” “bad,” “big,” “small,” “high,” “low,” “early,” “slow,” “wide,” “narrow,” and the like are not limited to the positive, comparative, and superlative forms, but may be replaced with each other as expressions appended with “the ith” (i is an arbitrary integer) (for example, “the highest” may be replaced with “the ith highest”).

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

[0990] In the present disclosure, expressions 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” can be replaced with each other. Furthermore, A, B, and the like here can be replaced with nouns, gerunds, or ordinary sentences, depending on the context. Furthermore, the time difference between A and B can be approximately zero (immediately after or immediately before). Furthermore, a time offset can be applied to the time when A occurs. For example, “A” can be replaced with “before / after the time offset when A occurs.” This time offset (eg, one or more symbols / time slots) may be predetermined or determined by the UE based on notified information.

[0991] In the present disclosure, timing, moment, time, time instance, arbitrary time unit (eg, time slot, sub-time slot, symbol, sub-frame), period, occasion, resource, etc. may also be interchangeable.

[0992] While the inventions disclosed herein have been described in detail above, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The disclosure herein is provided for illustrative purposes only and is not intended to limit the inventions disclosed herein.

Claims

1. A terminal comprising: a receiving unit, receiving a plurality of physical random access channel (PRACH) transmission settings corresponding to the plurality of spatial domain transmit filters; and The control unit determines a spatial domain transmission filter for uplink transmission based on any one of a specific PRACH among the multiple PRACHs, a random access response, a physical uplink shared channel PUSCH scheduled by the random access response, and a physical downlink shared channel PDSCH accompanied by a contention resolution identifier.

2. The terminal according to claim 1, wherein: The control unit monitors one or more random access responses for transmission of the plurality of PRACHs.

3. The terminal according to claim 1, wherein: The control unit monitors one random access response for transmission of the plurality of PRACHs. The terminal according to claim 1 , wherein: The control unit receives one or more random access responses for the transmission of the plurality of PRACHs, and determines the spatial domain transmit filter based on a specific random access response among the one or more random access responses.

5. A wireless communication method for a terminal, comprising: receiving a plurality of physical random access channel (PRACH) transmission settings corresponding to the plurality of spatial domain transmit filters; and The step of determining a spatial domain transmit filter for uplink transmission based on any one of a specific PRACH among the multiple PRACHs, a random access response, a physical uplink shared channel PUSCH scheduled by the random access response, and a physical downlink shared channel PDSCH accompanied by a contention resolution identifier.

6. A base station comprising: a transmitting unit configured to transmit a plurality of physical random access channels (PRACHs) respectively corresponding to the plurality of spatial domain transmit filters; and The control unit determines a spatial domain transmission filter for uplink transmission based on any one of a specific PRACH among the multiple PRACHs, a random access response, a physical uplink shared channel PUSCH scheduled by the random access response, and a physical downlink shared channel PDSCH accompanied by a contention resolution identifier.

Images