Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives a radio resource control (RRC) parameter indicating the application of an indicated transmission configuration indication (TCI) state, and receives a medium access control (MAC) control element and / or downlink control information (DCI) indicating a plurality of unified TCI states; and a control unit that performs control such that the indicated TCI state for a physical uplink control channel (PUCCH) is applied for each PUCCH resource or each PUCCH resource group on the basis of the RRC parameter and the MAC control element and / or the DCI. According to the one aspect of the present disclosure, the indicated TCI state can be appropriately applied.

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] In current wireless communication systems (e.g., NR Rel. 18), it is agreed that the indicated Transmission Configuration Indication (TCI) state for the PUCCH is applied per PUCCH resource or per PUCCH resource group.

[0006] However, in the current specifications, there are cases where it is not possible to appropriately apply the indicated TCI state for each PUCCH resource group.

[0007] In such a case, the terminal (user terminal, User Equipment (UE)) may not be able to appropriately apply the indicated TCI state, which may inhibit improvement in communication throughput.

[0008] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately apply an indicated TCI state.

[0009] A terminal according to one aspect of the present disclosure includes: a receiving unit that receives a Radio Resource Control (RRC) parameter indicating application of an indicated Transmission Configuration Indication (TCI) state, and receives at least one of a Medium Access Control (MAC) control element and a Downlink Control Information (DCI) that indicate a plurality of unified TCI states; and a control unit that controls application of an indicated TCI state for a Physical Uplink Control Channel (PUCCH) for each PUCCH resource or for each PUCCH resource group based on the RRC parameter and at least one of the MAC control element and the DCI.

[0010] According to one aspect of the present disclosure, the indicated TCI state can be applied appropriately.

[0011] FIG. 1 is a diagram illustrating an example of an extended unified TCI state activation / deactivation MAC CE for a joint TCI state. FIG. 2 is a diagram illustrating an example of an extended unified TCI state activation / deactivation MAC CE for a separate TCI state. FIG. 3A is a diagram illustrating an example of application of an indicated TCI state when a PUCCH resource group is not configured. FIG. 3B is a diagram illustrating an example of application of an indicated TCI state when a PUCCH resource group is configured. FIG. 4 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 5 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 6 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. FIG. 7 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 8 is a diagram illustrating an example of a vehicle according to an embodiment.

[0012] (TCI, spatial relationship, QCL) In NR, 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 encoding) of at least one of a signal and a channel (referred to as signal / channel) in the UE are controlled based on the transmission configuration indication state (TCI state).

[0013] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state that is applied to an uplink signal / channel may be expressed as a spatial relation.

[0014] The TCI state is information about the Quasi-Co-Location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.

[0015] The QCL is an index indicating the statistical properties of signals / channels. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the signals / channels have a QCL with respect to at least one of these).

[0016] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).

[0017] A plurality of types of QCLs (QCL types) may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same.

[0018] The UE's assumption that a Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

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

[0020] The TCI state may be, for example, information about the QCL between the channel of interest (in other words, the Reference Signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

[0021] The physical layer signaling may be, for example, Downlink Control Information (DCI).

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

[0023] Furthermore, the RS that has a QCL relationship with the channel may be, for example, at least one of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).

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

[0025] An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel / signal (DMRS), and this RS may be called a QCL source of QCL type X in the TCI state.

[0026] (Unified / Common TCI Framework) The unified TCI framework allows multiple types of channels / RSs (UL / DL) to be controlled by a common framework. The unified TCI framework does not specify TCI states or spatial relationships for each channel as in Rel. 15. Instead, it may specify a common beam (common TCI state) and apply it to all UL and DL channels, or it may apply a common beam for UL to all UL channels and a common beam for DL ​​to all DL channels.

[0027] One common beam for both DL and UL, or one common beam for DL ​​and one common beam for UL (two common beams overall) are considered.

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

[0029] The default beams for UL and DL may be aligned via MAC CE based beam management (MAC CE level beam indication). The default TCI state of the PDSCH may be updated to align with the default UL beam (spatial relationship).

[0030] DCI-based beam management (DCI-level beam indication) may indicate a common beam / unified TCI state from the same TCI pool for both UL and DL (joint common TCI pool, joint TCI pool, set). X (>1) TCI states may be activated by the MAC CE. The UL / DL DCI may select one from the X active TCI states. The selected TCI state may apply to both UL and DL channels / RS.

[0031] The TCI pool (set) may be multiple TCI states configured by RRC parameters, or multiple TCI states (active TCI states, active TCI pools, sets) activated by MAC CE among the multiple TCI states configured by RRC parameters. Each TCI state may be a QCL type A / D RS. SSB, CSI-RS, or SRS may be configured as the QCL type A / D RS.

[0032] The number of TCI states corresponding to each of one or more TRPs may 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 be specified. At least one of N and M may be notified / configured / instructed to the UE via higher layer signaling / physical layer signaling.

[0033] RRC parameters (information elements) configure multiple TCI states for both DL and UL. MAC CE may activate multiple TCI states from the configured multiple TCI states. DCI may indicate one of the activated multiple TCI states. DCI may be UL / DL DCI. The indicated TCI state may apply to at least one (or all) of the UL / DL channels / RS. One DCI may indicate both UL TCI and DL TCI.

[0034] At least one of the multiple TCI states configured by the RRC parameters and the multiple TCI states activated by the MAC CE may be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool). The multiple TCI states activated by the MAC CE may be referred to as an active TCI pool (active common TCI pool).

[0035] In the present disclosure, higher layer parameters (RRC parameters) for setting multiple TCI states may be referred to as configuration information for setting multiple TCI states, or simply as "configuration information." Also, in the present disclosure, being instructed to set one of multiple TCI states using DCI may mean receiving indication information instructing one of the multiple TCI states included in DCI, or may simply mean receiving "instruction information."

[0036] The RRC parameters also configure multiple TCI states (joint common TCI pools) for both DL and UL. The MAC CE may activate multiple TCI states (active TCI pools) from the configured multiple TCI states. Separate active TCI pools for UL and DL may be configured / activated.

[0037] The DL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may apply to one or more (or all) DL channels / RSs. The DL channels may be PDCCH / PDSCH / CSI-RS. The UE may determine the TCI state of each DL channel / RS using the TCI state behavior (TCI framework) of Rel. 16. The UL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may apply to one or more (or all) UL channels / RSs. The UL channels may be PUSCH / SRS / PUCCH. In this way, different DCIs may indicate UL TCI and DL DCI separately.

[0038] It is assumed that in Rel. 17 NR and later, the MAC CE / DCI supports beam activation / indication to a TCI state associated with a different physical cell identifier (PCI), and in Rel. 18 NR and later, the MAC CE / DCI supports indicating a serving cell change to a cell with a different PCI.

[0039] <Channels / RSs to which the indicated TCI state in Rel. 17 is applied> The indicated TCI state by the MAC CE / DCI may be applied to the following UL channels / RSs: Note that, although not described below, the indicated TCI state may also be applied to any DL channels / RSs (PDCCH / PDSCH / CSI-RS).

[0040] <<PUCCH>> - For all dedicated PUCCH resources, the indication TCI state always applies.

[0041] <<PUSCH>> - For dynamic / configured grant PUSCH, the indication TCI state always applies.

[0042] <<SRS>> When the SRS resource set for the A-SRS used for beam management and the A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, the indicated TCI state applies. For other SRSs, the configured TCI state in the SRS resource set applies.

[0043] <Channels / RSs to which the indicated TCI state applies in Rel. 18> When single DCI multi-TRP is applied, the indicated TCI state may be applied to the following channels / RSs: Note that, although not described below, the indicated TCI state may also be applied to any DL channels / RSs (PDCCH / PDSCH / CSI-RS).

[0044] In the following description, applyIndicatedTCIState={1st, 2nd, both} is a parameter indicating that the first TCI state, the second TCI state, or both the first TCI state and the second TCI state are applied.

[0045] <<PUCCH>> - applyIndicatedTCIState={1st, 2nd, both} is set for each PUCCH resource / PUCCH resource group.

[0046] <<PUSCH>> - For dynamic / configured grant PUSCH, the indicated TCI state is always applied. - For PUSCH scheduled / activated by DCI0_0, the first indicated TCI state is always applied. - For Type 1 CG PUSCH, applyIndicatedTCIState={1st,2nd,both} is set. - The SRS resource set indication field indicates one / both of the SRS resource sets used.

[0047] <<SRS>> When the SRS resource set for A-SRS used for beam management and A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, applyIndicatedTCIState={1st,2nd,both} is set for each SRS resource set to indicate that the indicated TCI state applies. For other SRSs, the configured TCI state in that SRS resource set applies.

[0048] In the present disclosure, the terms "indicated TCI state," "unified TCI state," "TCI state applied to channels / signals configured to follow the unified TCI state," "TCI state applied to a UE-specific PDSCH and a CORESET / PDCCH associated with a USS," and "TCI state applied to a PUCCH and a PUSCH" may be interchangeable.

[0049] (Unified TCI Status for Multi-TRP in Rel. 18) In Rel. 18, the specification for unified TCI for multi-TRP has been extended. For example, in the case of multi-TRP with a single DCI, the UE may be indicated up to two joint TCIs or up to two sets of {DL TCI, UL TCI} by the RRC / MAC CE / DCI. In the case of multi-TRP with multi-DCI, the UE may be indicated one joint TCI or one set of {DL TCI, UL TCI} per coresetPoolIndex by the RRC / MAC CE / DCI. The indicated TCI applies to multiple UL / DL channels / RSs. The association of the first and second indicated TCIs with each UL / DL channel / RS may be predefined in the specification, configured by RRC signaling, or indicated by DCI.

[0050] (TCI indication in Rel. 18 NR) The TCI state configuration by RRC is based on the following: Up to 128 TCI states can be configured for one serving cell. In coordination between multiple TRPs with different PCIs, multiple TCI states can be associated with SSBs of different PCIs, and up to 8 PCIs can be configured.

[0051] Activation of TCI states by the MAC CE is based on the following: In single-TRP transmission, up to eight TCI states can be activated for one serving cell or one BWP of one serving cell. In switching between multiple TRPs with different PCIs, multiple activated TCI states can be associated with SSBs of different PCIs, and TCI states of up to eight PCIs can be activated. In multi-TRP joint transmission, up to eight TCI states can be activated per TRP / cell, and up to 16 TCI states can be activated in total. In joint transmission using multiple TRPs with different PCIs, multiple activated TCI states can be associated with SSBs of different PCIs, and TCI states of up to two PCIs can be activated.

[0052] The indication of the TCI state by the DCI is based on the following: Multiple code points in the TCI indication field in the DCI are mapped to multiple TCI states activated via the MAC CE. In a single-TRP transmission, one code point in the TCI indication field in the DCI is mapped to one joint DL and UL TCI, or one DL TCI and one UL TCI, or one DL TCI, or one UL TCI. In a single-DCI-based multi-TRP joint transmission, one code point in the TCI indication field in the DCI is mapped to one or two joint DL and UL TCIs, or one or two DL TCIs and one or two UL TCIs, or one or two DL TCIs, or one or two UL TCIs. In multi-DCI-based multi-TRP joint transmission, one code point of the TCI indication field in the DCI is mapped to one or two DL and UL joint TCIs, or one or two DL TCIs and one or two UL TCIs, or one or two DL TCIs, or one or two UL TCIs. Multiple DCIs indicate the TCI status for multiple TRPs.

[0053] In Rel. 18, the unified TCI state for single TRP (sTRP) is extended to support multi-TRP (mTRP) in Rel. 16-18 as follows: mTRP based on single DCI (sDCI): - Rel. 16 sDCI mTRP PDSCH (NCJT, repetition) - Rel. 17 sDCI mTRP PUSCH / PUCCH / PDCCH repetition - Rel. 17 SFN-PDCCH / PDSCH - Rel. 18 PDSCH-CJT - Rel. 18 sDCI simultaneous transmission with multiple panels (STxMP) PUSCH / PUCCH mTRP based on multi-DCI (mDCI): - Rel. 16 mDCI mTRP PDSCH (NCJT) - Rel. 18 mDCI STxMP PUSCH / PUCCH

[0054] In the Rel. 18 unified TCI framework, the following are assumed: RRC-based switching between joint TCI states and separate UL and DL TCI states. RRC-configured TI state lists are common across multiple TRPs. Both CC-specific and CC-common TCI pools in Rel. 17 are supported. MAC CE / DCI-based TCI state ID indication in the CC list in Rel. 17 is reused. Beam adaptation timing (BAT) in Rel. 17 is reused.

[0055] In the sDCI mTRP, one DCI / MAC CE indicates a joint TCI state or up to two sets of UL and DL TCI states. The indication may be based on:

[0056] The TCI field in DCI format 1_2 / 1_2 (with or without DL assignment) indicates at least one TCI state, first and second. If only one TCI state (e.g., the second TCI state) is indicated, the UE updates the indicated TCI state and maintains the other TCI state (e.g., the first TCI state). If two TCI states are indicated, the UE updates both TCI states.

[0057] Once two TCI states are indicated, the UE maintains the two indicated TCI states. However, this does not mean that both of the two indicated TCI states are always applied to all channels / RSs. Which of the indicated TCI states applies to each channel / RS is defined in the specification, configured by RRC, or indicated by DCI.

[0058] Figure 1 shows an example of an Enhanced Unified TCI States Activation / Deactivation MAC CE for Joint TCI States. This MAC CE consists of the following fields and has a variable size: Serving Cell ID: This field indicates the ID of the serving cell to which the MAC CE applies. DL BWP ID: This field indicates the DL BWP to which the MAC CE applies as a codepoint of the BWP indicator field. F i,j : This field indicates whether the j-th joint TCI state exists for the TCI State ID field associated with codepoint i of the DCI TCI field, where j=1, 2. If F i,j If the field is set to 1, it indicates that the jth joint TCI state for codepoint i exists. If F i,j If the field is set to 0, it indicates that there is no jth joint TCI state for code point i. The code point to which a TCI state is mapped is determined by its ordinal position among all TCI state ID fields. TCI state ID: This field indicates the 7-bit long TCI state ID identified by TCI-StateId. The maximum number of activated TCI states is 16. R: Reserved bit set to 0.

[0059] 2 shows an example of an Enhanced Unified TCI States Activation / Deactivation MAC CE for Separate TCI States. This MAC CE consists of the following fields and has a variable size: Serving Cell ID: This field indicates the ID of the serving cell to which the MAC CE applies. DL BWP ID: This field indicates the DL BWP to which the MAC CE applies as a codepoint in the BWP indicator field. UL BWP ID: This field indicates the UL BWP to which the MAC CE applies as a codepoint in the BWP indicator field. F i,j : This field indicates whether the j-th DL TCI state exists for the TCI State ID field associated with codepoint i of the DCI TCI field, where j=1, 2. If F i,j If the field is set to 1, it indicates that the jth DL TCI state for codepoint i exists. If F i,j If the field is set to 0, it indicates that the jth DL TCI state for codepoint i does not exist. i,j : This field indicates whether the j-th UL TCI state exists for the TCI State ID field associated with codepoint i of the DCI TCI field, where j=1, 2. If S i,j If the field is set to 1, it indicates that the jth UL TCI state for codepoint i exists. If S i,jIf the field is set to 0, it indicates that the jth UL TCI state for codepoint i does not exist. TCI state ID: This field indicates the TCI state identified by TCI-StateId. If the indicated TCI state ID is a DL TCI state, a 7-bit long TCI state ID, i.e., TCI-StateId, is used. If the indicated TCI state ID is a UL TCI state, the most significant bit (MSB) of the TCI state ID is considered a reserved bit, and the remaining 6 bits indicate TCI-UL-StateId. The TCI state ID is i,j and S i,j The codepoint to which a TCI state is mapped is determined by its ordinal position among all TCI State ID fields. The maximum number of activated TCI states is 32. R: Reserved bit set to 0.

[0060] For example, {F i,1 , F i,2 , S i,1 , S i,2} is {0,0,0,0}, there is no DL TCI state and no UL TCI state corresponding to one codepoint.

[0061] For example, {F i,1 , F i,2 , S i,1 , S i,2} is {0,0,0,1}, then only the second UL TCI state corresponds to one codepoint.

[0062] For example, {F i,1 , F i,2 , S i,1 , S i,2} is {0,0,1,0}, then only the first UL TCI state corresponds to one codepoint.

[0063] For example, {F i,1 , F i,2 , S i,1 , S i,2} is {0,1,0,0}, then only the second DL TCI state corresponds to one codepoint.

[0064] For example, {F i,1 , F i,2 , S i,1 , S i,2} is {1,0,0,0}, then only the first DL TCI state corresponds to one codepoint.

[0065] Such a Rel. 18 MAC CE for separate TCI states is designed to indicate {0,1,2} DL TCI states and {0,1,2} UL TCI states.

[0066] (Analysis) As described above, in the case of multi-TRP for single DCI / multi-DCI in Rel. 18, the RRC parameter (applyIndicatedTCIState) indicating the application of the indicated TCI state is applied for each PUCCH resource or PUCCH resource group.

[0067] Application of these RRC parameters and selection of PUCCH resources allows dynamic switching between single-TRP and multi-TRP operation.

[0068] 3A is a diagram illustrating an example of application of the indication TCI state when a PUCCH resource group is not configured. In the example shown in FIG. 3A, no PUCCH resource group is configured for the UE.

[0069] In the example shown in Fig. 3A, the MAC CE / DCI indicates a first UL / joint TCI state and a second UL / joint TCI state, and for each PUCCH resource, the indicated TCI state is applied according to an RRC parameter (applyIndicatedTCI-State-r18) indicating application of the indicated TCI state.

[0070] In the example shown in FIG. 3A , the first UL / joint TCI state, the first UL / joint TCI state, the second UL / joint TCI state, and the second UL / joint TCI state are applied to PUCCH resources #1, #2, #3, and #4, respectively.

[0071] 3B is a diagram illustrating an example of application of the indication TCI state when a PUCCH resource group is configured. In the example shown in FIG. 3B, a PUCCH resource group is configured for a UE.

[0072] In the example shown in FIG. 3B , the MAC CE / DCI indicates a first UL / joint TCI state and a second UL / joint TCI state, and for each PUCCH resource, the indicated TCI state is applied according to an RRC parameter (applyIndicatedTCI-State-r18) indicating application of the indicated TCI state and the PUCCH resource group.

[0073] In the example shown in FIG. 3B , a first UL / joint TCI state is applied to PUCCH resources #1 and #2 included in PUCCH resource group 1, and a second UL / joint TCI state is applied to PUCCH resources #3 and #4 included in PUCCH resource group 2.

[0074] More specifically, the following has been agreed upon regarding the application of the indication TCI state to the PUCCH in Rel.

[0075] In a time division multiplexing (TDM) / single frequency network (SFN) based PUCCH transmission scheme, both of the two indicated TCI states apply.

[0076] For each PUCCH resource / resource group, an RRC configuration may be provided indicating that the UE applies the first or second indication joint / UL TCI state to the corresponding PUCCH transmission, where the first and second indication joint / DL TCI states correspond to the indication joint / UL TCI states specific to the coresetPoolIndex values ​​0 and 1, respectively (action 1).

[0077] If the UCI of a PUCCH transmission carries only HARQ-ACK information, for PUCCH transmissions triggered by PDCCH in the CORESET, the UE applies to the PUCCH the indicated joint / UL TCI state specific to the coresetPoolIndex value, which is determined from the one associated with that CORESET. Otherwise, follow action 1.

[0078] When the UE is provided with one or two BFR scheduling request IDs (schedulingRequestID-BFR) (only), for PUCCH transmissions where a Link Recovery Request (LRR) is triggered by either the first or second BFD-RS set, the UE applies the indication joint / UL TCI state specific to the coresetPoolIndex value to the PUCCH transmission. The coresetPoolIndex value is 1 when an LRR is triggered for the first BFD-RS set and 0 when an LRR is triggered for the second BFD-RS set. Otherwise, follow action 1.

[0079] On the other hand, the current Rel. 18 only specifies that the RRC parameter (applyIndicatedTCIState) is set for each PUCCH resource, and there are cases where the application of the RRC parameter (applyIndicatedTCIState) for each PUCCH resource group is not properly specified.

[0080] More specifically, in the current Rel. 18, the spatial setting of PUCCH transmission by a UE is provided by the indicated applyIndicatedTCIState, where if applyIndicatedTCIState is 'first', the UE uses the spatial domain filter corresponding to the first TCI-State or TCI-UL-State, if applyIndicatedTCIState is 'second', the UE uses the spatial domain filter corresponding to the second TCI-State or TCI-UL-State, and if applyIndicatedTCIState is 'both', the UE transmits PUCCH using the spatial domain filters corresponding to both the first and second TCI-States or TCI-UL-States.

[0081] In addition, a list of PUCCH resource groups is configured in the PUCCH configuration (PUCCH-Config), and a list of PUCCH resource IDs is configured for each PUCCH resource group. In the current Rel. 18, only "spatial relationships" are applicable to these PUCCH resource groups, i.e., the TCI framework of Rel. 15 / 16 is applicable, and there is no provision for the application of unified TCI states.

[0082] Furthermore, although the current Rel. 18 specifies that a MAC CE for PUCCH spatial relationships applies to all PUCCH resources within a PUCCH resource group, this MAC CE does not apply to the unified TCI framework of Rel. 17 / 18.

[0083] In addition, the RRC parameter (applyIndicatedTCI-State-r18) indicating the application of the indicated TCI state specified in Rel. 18 applies only to the Rel. 18 unified TCI state, and this RRC parameter is configured for each PUCCH resource. For this RRC parameter, the network (e.g., base station) configures the same value for PUCCH resources belonging to one PUCCH group (PUCCH resource group) (Constraint 1).

[0084] According to Constraint 1, the TCI status of the PUCCH resources in a PUCCH resource group can be updated simultaneously, but there is a possibility that appropriate operation cannot be performed in cases where the PUCCH resource group is configured and where it is not configured. For example, when a PUCCH resource group is configured, a notification is required to determine the application of the indicated TCI status for each PUCCH resource group, so additional RRC configuration, etc. must be considered.

[0085] As described above, if the current specifications are followed, it may not be possible to appropriately apply the designated TCI state to each PUCCH resource group, which may result in inappropriate PUCCH transmission using the designated TCI state, and may inhibit improvement of communication throughput.

[0086] Therefore, the present inventors came up with a method for solving these problems.

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

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

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

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

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

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

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

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

[0095] In the present disclosure, the terms drop, abort, cancel, puncture, rate match, postpone, do not transmit, etc. may be read interchangeably.

[0096] In the present disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0097] In the present disclosure, the terms single TRP, channel / signal using single TRP, channel using one TCI state / spatial relationship, multi-TRP not enabled by RRC / DCI, multiple TCI states / spatial relationships not enabled by RRC / DCI, a CORESETPoolIndex value of 1 not set for any CORESET, and no code point in the TCI field mapped to two TCI states may be read interchangeably.

[0098] In the present disclosure, multi-TRP, channel / signal using multi-TRP, channel using multiple TCI states / spatial relationships, multi-TRP enabled by RRC / DCI, multiple TCI states / spatial relationships enabled by RRC / DCI, and at least one of multi-TRP based on a single DCI and multi-TRP based on multiple DCI may be read interchangeably.

[0099] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, and activation of two TCI states on at least one TCI codepoint may be read interchangeably.

[0100] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, and setting two CORESET pool indices or CORESET pool index = 1 (or a value greater than or equal to 1) may be read interchangeably.

[0101] In the present disclosure, the terms cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within a CC, and band may be interchangeable. In the present disclosure, the terms cell, PCI, cell with an additional PCI, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the PCI of the current serving cell, another serving cell, target cell, neighbor cell, and inter-RAT neighbor cell may be interchangeable. The target cell may be a cell selected from multiple candidate cells. In the present disclosure, the terms switch, change, and update may be interchangeable. The term serving cell may be interchangeable with the serving cell before the switch or the serving cell after the switch.

[0102] In the present disclosure, being set and receiving a setting (setting information) may be read interchangeably.

[0103] In the present disclosure, TCI, TCI state, TCI state ID, TCI state list / set / pool / group, and TCI state list / set / pool / group ID may be read interchangeably.

[0104] In this disclosure, a unified TCI state may refer to a TCI state / spatial relationship / QCL assumption / beam that applies to multiple channels / signals (RS).

[0105] In the present disclosure, the terms "indicated TCI state," "unified TCI state," "unified TCI state in which multi-TRP is not configured / used / applied," "unified TCI state defined in Rel. 17," "Rel. 17 unified TCI state," and "first unified TCI state" may be interchangeable.

[0106] In the present disclosure, the terms "indication TCI state," "unified TCI state," "unified TCI state in which multi-TRP is configured / used / applied," "unified TCI state in which multi-TRP can be configured / used / applied," "indication TCI state in which multi-TRP is configured / used / applied," "indication TCI state in which multi-TRP can be configured / used / applied," "unified TCI state defined in Rel. 18," "Rel. 18 unified TCI state," "Rel. 18 unified TCI framework," "unified TCI state for multi-TRP," and "second unified TCI state" may be interchangeable.

[0107] In the present disclosure, the terms TCI state indicated by DCI, indicated TCI state, indicated TCI state, unified TCI state, TCI state applied to multiple types of channels / signals, joint TCI state (for DL ​​and UL), DL TCI state, UL TCI state, Rel. 17 TCI state, common TCI state, configured single unified TCI state, activated single unified TCI state, and Rel. 17 unified TCI framework may be read interchangeably.

[0108] In the present disclosure, the terms TCI state set by RRC parameters, configured TCI state, set TCI state, TCI state that does not conform to the unified TCI state, TCI state other than the unified TCI state, TCI state / spatial relationship set for a specific channel / signal, and individual TCI state may be read interchangeably.

[0109] The unified / common TCI state may refer to the indicated TCI state indicated using DCI / MAC CE / RRC (in Rel. 17).

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

[0111] If the indicated TCI state is supported (in Rel. 17), a TCI state other than the unified TCI state may refer to the TCI state configured using MAC CE / RRC (in Rel. 17) (configured TCI state).

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

[0113] In the present disclosure, a first TRP may correspond to a first TCI state. In the present disclosure, a second TRP may correspond to a second TCI state. In the present disclosure, an n-th TRP may correspond to an n-th TCI state.

[0114] In the present disclosure, a first CORESET pool index value (e.g., 0), a first TRP index value (e.g., 1), and a first TCI state (first DL / UL (joint / separate) TCI state) may correspond to each other. In the present disclosure, a second CORESET pool index value (e.g., 1), a second TRP index value (e.g., 2), and a second TCI state (second DL / UL (joint / separate) TCI state) may correspond to each other.

[0115] In the present disclosure, the new upper layer parameters are not limited to the names shown below, and may have other names.

[0116] In the present disclosure, each embodiment / option may be applied alone or in combination with other embodiments / options.

[0117] In the present disclosure, applying a TCI state ID may mean applying a TCI state corresponding to the TCI state ID.

[0118] In the present disclosure, the indicated TCI state / unified TCI state of the PUCCH, the indicated TCI state / unified TCI state for the PUCCH, the indicated TCI state / unified TCI state applied to the PUCCH, etc. may be read interchangeably.

[0119] (Wireless Communication Method) A UE may receive a MAC CE / DCI indicating multiple (e.g., two) unified TCI states (UL / joint TCI states), which may be referred to as indicated TCI states.

[0120] The UE may determine the application of the TCI state indicated by the MAC CE / DCI to the PUCCH for each PUCCH resource or each PUCCH resource group.

[0121] First Embodiment The first embodiment relates to a provision for applying a unified TCI state (UL / joint TCI state) to each PUCCH resource group.

[0122] This embodiment may be applied when an RRC parameter (e.g., applyIndicatedTCIState / applyIndicatedTCI-State / applyIndicatedTCI-State-r18) indicating application of the indicated TCI state defined in Rel. 18 is set / provided.

[0123] In this disclosure, this RRC parameter may be referred to as an indicated TCI state applied RRC parameter.

[0124] In the present disclosure, the RRC parameter is not limited to an RRC parameter indicating application of the indicated TCI state defined in Rel. 18, but may be an RRC parameter indicating application of the indicated TCI state defined in Rel. 17, or an RRC parameter indicating application of the indicated TCI state defined in Rel. 19 or later.

[0125] <<Embodiment 1-1A>> Embodiment 1-1A relates to the definition of MAC CE for unified TCI state in [Rel. 18].

[0126] In the present disclosure, the MAC CE may be, for example, an Enhanced Unified TCI States Activation / Deactivation MAC CE for Joint TCI States or an Enhanced Unified TCI States Activation / Deactivation MAC CE for Separate TCI States.

[0127] The UE may determine to apply the indicated TCI state to each PUCCH resource group based on a specific field included in the MAC CE.

[0128] For a field indicating a TCI state ID (e.g., TCI state ID) in the MAC CE, if the indicated TCI state ID applies to a PUCCH resource and the indicated PUCCH resource ID is included in a PUCCH resource group of the indicated UL BWP, the UE may assume / determine that other PUCCH resources in the same PUCCH resource group are not indicated by the MAC CE.

[0129] Also, in this case, the UE may assume / determine that the MAC CE indicates the TCI state IDs to be applied to multiple (eg, all) PUCCH resources in the PUCCH resource group.

[0130] According to embodiment 1-1A, even when a PUCCH resource group is configured, the TCI state activated / deactivated by a MAC CE can be applied to each PUCCH resource group.

[0131] <<Embodiment 1-1B>> Embodiment 1-1B relates to configuration parameters for a PUCCH resource group.

[0132] The UE may be configured / provided with configuration parameters for the PUCCH resource groups.

[0133] The UE may determine to apply the indicated TCI state for each PUCCH resource group based on the configuration parameters.

[0134] The configuration parameter may be, for example, at least one of a parameter indicating a list of additions / modifications of PUCCH resource groups (e.g., resourceGroupToAddModList) and a parameter indicating a list of releases of PUCCH resource groups (e.g., resourceGroupToReleaseList).

[0135] The PUCCH resource group indicated by the configuration parameter may be, for example, a group including PUCCH resources whose spatial relationship or UL / joint TCI status can be updated simultaneously by a MAC CE.

[0136] According to embodiment 1-1B, it is possible to clearly specify that the UL / joint TCI state can be applied in the configuration of a PUCCH resource group.

[0137] <<Embodiment 1-2>> The indicated TCI state (UL / joint TCI state) ID may be applied to a PUCCH resource, and the indicated PUCCH resource ID may be included in a PUCCH resource group of the indicated UL BWP. In this case, the PUCCH resource group may be configured using, for example, a parameter (e.g., resourceGroupToAddModList) indicating a list of added / modified PUCCH resource groups.

[0138] The UE may determine to apply the indicated TCI state for each PUCCH resource group based on the parameter.

[0139] For example, in this case, the UE may determine that the MAC CE for the unified TCI state applies to multiple (eg, all) PUCCH resources within the PUCCH resource.

[0140] According to this method, MAC CE-based TCI indication for a PUCCH resource group can be performed appropriately.

[0141] In this case, the UE may also determine that the TCI state (UL / joint TCI state) ID indicated using the MAC CE for unified TCI state applies to multiple (e.g., all) PUCCH resources within the PUCCH resource.

[0142] According to this method, DCI / MAC CE-based TCI indication for a PUCCH resource group can be performed appropriately.

[0143] According to the first embodiment described above, it is possible to appropriately define the application of the unified TCI state (UL / joint TCI state) to each PUCCH resource group.

[0144] Second Embodiment The second embodiment relates to association of PUCCH resource groups and PUCCH resources in the Rel. 18 unified TCI framework.

[0145] The UE may assume / expect / determine that one or more PUCCH resources associated with one indication TCI state application RRC parameter (e.g., applyIndicatedTCIState / applyIndicatedTCI-State / applyIndicatedTCI-State-r18) are associated with [only] one PUCCH resource group.

[0146] The UE may determine a PUCCH resource group corresponding to a PUCCH resource based on the association between the indicated TCI state application RRC parameter and the PUCCH resource, and determine application of the indicated TCI state for each PUCCH resource group.

[0147] For example, one or more PUCCH resources associated with an indication TCI state application RRC parameter indicating a first indication TCI state (1st) may be associated with (included in) a first PUCCH resource group.

[0148] For example, one or more PUCCH resources associated with an indication TCI state application RRC parameter indicating a second indication TCI state (2nd) may be associated with (included in) a second PUCCH resource group.

[0149] For example, if a UE is configured with the Rel. 17 / 18 unified TCI framework (e.g., a DL / joint TCI state list parameter (e.g., dl-OrJointTCI-StateList) or a UL TCI state parameter (e.g., TCI-UL-State)), the UE may not assume / expect that a third or more (e.g., third / fourth) PUCCH resource group will be configured.

[0150] According to the second embodiment, by associating the PUCCH resources associated with the indicated TCI state application RRC parameters with the PUCCH resource groups, the indicated TCI state can be applied to each PUCCH resource group.

[0151] Third Embodiment The third embodiment relates to support for PUCCH resource groups in the Rel. 17 / 18 unified TCI framework.

[0152] In the Rel. 17 / 18 unified TCI framework, PUCCH resource groups may not be supported.

[0153] For example, if the UE is configured with the Rel. 17 / 18 unified TCI framework (e.g., a parameter for the DL / joint TCI state list (e.g., dl-OrJointTCI-StateList) or a parameter for the UL TCI state (e.g., TCI-UL-State)), the UE may not assume / expect that a configuration regarding the PUCCH resource group is provided / configured.

[0154] The configuration related to the PUCCH resource group may be, for example, at least one of a PUCCH resource group configuration (e.g., PUCCH-ResourceGroup), a PUCCH resource group ID (e.g., PUCCH-ResourceGroupId), a list of PUCCH resource groups for each PUCCH resource (e.g., resourcePerGroupList), a parameter indicating a list of added / modified PUCCH resource groups (e.g., resourceGroupToAddModList), and a parameter indicating a list of PUCCH resource group releases (e.g., resourceGroupToReleaseList).

[0155] Also, for example, if the UE has two indicated TCI states, the UE may not assume / expect that a configuration regarding PUCCH resource groups is provided / configured.

[0156] Also, for example, when a UE is provided / configured with a configuration regarding PUCCH resource groups, the UE may not assume / expect to have two indicated TCI states.

[0157] Furthermore, the above-mentioned constraint 1 may be deleted from the specification. In other words, for the indication TCI state application RRC parameters (e.g., applyIndicatedTCIState / applyIndicatedTCI-State / applyIndicatedTCI-State-r18), the network (e.g., base station) may set the same value or different values ​​for PUCCH resources belonging to one PUCCH group (PUCCH resource group).

[0158] According to the third embodiment, it is possible to specify appropriate UE operation by disabling application of the indicated TCI state for each PUCCH resource group in the unified TCI framework.

[0159] Furthermore, in the Rel.18 unified TCI framework, two TCI states for each TCI codepoint are indicated by a MAC CE, and a TCI state is not indicated for each PUCCH resource, so MAC CE overhead cannot be reduced even when PUCCH resource groups are used. From this perspective, this embodiment is preferable.

[0160] <Fourth embodiment> The fourth embodiment relates to UE capability for application of an indicated TCI state for each PUCCH resource group.

[0161] For each PUCCH resource group, a UE capability may be supported / defined indicating whether the indication TCI state apply RRC parameter (e.g., applyIndicatedTCIState / applyIndicatedTCI-State / applyIndicatedTCI-State-r18) is set.

[0162] If the UE does not support / report this capability, the UE may assume / expect that the Indication TCI State Apply RRC parameter is configured for each PUCCH resource.

[0163] If the UE does not support / report this capability, the UE may assume / expect that parameters related to PUCCH resource groups (e.g., PUCCH-ResourceGroup-r16 or any RRC parameters included in PUCCH-ResourceGroup-r16 (e.g., at least one of the following: PUCCH resource group configuration (e.g., PUCCH-ResourceGroup), PUCCH resource group ID (e.g., PUCCH-ResourceGroupId), list of PUCCH resource groups per PUCCH resource (e.g., resourcePerGroupList), parameter indicating a list of additions / modifications of PUCCH resource groups (e.g., resourceGroupToAddModList), and parameter indicating a list of releases of PUCCH resource groups (e.g., resourceGroupToReleaseList))) are not configured / provided.

[0164] If the UE supports / reports this capability, the UE may assume / expect that the Indication TCI State Apply RRC parameter may be configured per PUCCH resource group.

[0165] For example, if the UE supports / reports the capability, the UE may determine based on a specific RRC parameter whether the indication TCI state application RRC parameter is configured per PUCCH resource or per PUCCH resource group.

[0166] According to the fourth embodiment, by defining the UE capability regarding application of the indicated TCI state for each PUCCH resource group, it is possible to realize an appropriate operation for applying the indicated TCI state.

[0167] Fifth Embodiment The fifth embodiment relates to a modification of the above-described embodiment 1-1B.

[0168] The UE may be configured / provided with configuration parameters for the PUCCH resource group (e.g., at least one of a parameter indicating a list of additions / modifications of PUCCH resource groups (e.g., resourceGroupToAddModList) and a parameter indicating a list of releases of PUCCH resource groups (e.g., resourceGroupToReleaseList)).

[0169] Simultaneous updating of the Rel. 17 / 18 unified TCI state may not be supported in the configuration parameter, i.e., the PUCCH resource group related to the configuration parameter may not be used for simultaneous updating of multiple PUCCH resources of the Rel. 17 / 18 unified TCI state (indicated TCI state).

[0170] When the UE updates the indication TCI status using MAC CE / DCI, the UE may not take into account (may ignore) the configuration of the PUCCH resource group.

[0171] When updating the indication TCI state using MAC CE / DCI, the UE may follow the indication TCI state apply RRC parameters (e.g., applyIndicatedTCIState / applyIndicatedTCI-State / applyIndicatedTCI-State-r18) corresponding to each PUCCH resource.

[0172] In this way, even if the UE does not rely on the configuration of the PUCCH resource group, by following the indicated TCI state application RRC parameters, it is possible to ultimately realize application of the indicated TCI state for each PUCCH resource group.

[0173] The configuration of the PUCCH resource group ID may not be used to update the unified TCI state of the PUCCH.

[0174] The PUCCH resource group configured by the PUCCH resource group configuration parameter (e.g., at least one of a parameter indicating a list of additions / modifications of PUCCH resource groups (e.g., resourceGroupToAddModList) and a parameter indicating a list of releases of PUCCH resource groups (e.g., resourceGroupToReleaseList)) may be, for example, a group including PUCCH resources whose spatial relationships can be simultaneously updated by a MAC CE, or a group including PUCCH resources for which the same value of the indication TCI state application RRC parameter can be set.

[0175] According to the fifth embodiment, it is possible to apply the indication TCI state for each PUCCH resource or PUCCH resource group without extending the existing PUCCH resource group for the Rel.

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

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

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

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

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

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

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

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

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

[0185] The specific UE capability may indicate at least one of the following: - Supporting the specific processing / operation / control / assumptions / information; - Supporting multi-TRP scenarios with a single DCI; - Supporting scenario 1 (UL dense deployment); - Supporting scenario 2 (HetNet); - Supporting UL transmission (SRS / PUSCH / PUCCH / PRACH) to UL reception points; - Number of supported UL reception points / DL transmission points; - Supporting the same / different CL-PC adjustment state as PUSCH; - Supporting simultaneous setting of the same / different CL-PC adjustment state as PUSCH; - Supporting DCI format 2_3 indicating first / second TPC commands for a CC; - Supporting srs-TPC-PDCCH-Group = {typeA, typeB} for CL-PC adjustment state different from PUSCH. Supporting SRS carrier switching / HetNet-oriented functionality (i.e., UE function #1 / #2), Supporting simultaneous configuration of UE function #1 / #2, Supporting DCI format 1_1 / 1_2 to indicate TPC commands for two CL-PC adjustment states for SRS.

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

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

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

[0189] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment of the present disclosure. [Supplementary Note 1] A terminal including: a receiver that receives a Radio Resource Control (RRC) parameter indicating the application of an indicated Transmission Configuration Indication (TCI) state, and that receives at least one of a Medium Access Control (MAC) control element and downlink control information (DCI) that indicate a plurality of unified TCI states, and a controller that controls, based on the RRC parameter and at least one of the MAC control element and the DCI, to apply the indicated TCI state for a Physical Uplink Control Channel (PUCCH) for each PUCCH resource or for each PUCCH resource group. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the controller controls, based on at least one of a specific field included in the MAC control element and a configuration parameter of a PUCCH resource group, to apply the indicated TCI state for the PUCCH for each PUCCH resource group. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the controller controls to apply the indicated TCI state for the PUCCH for each PUCCH resource group based on an association between the RRC parameter and a PUCCH resource. [Supplementary Note 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein application of the indicated TCI state for the PUCCH for each PUCCH resource group is not supported.

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

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

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

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

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

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

[0196] The wireless communication system 1 may utilize multi-input multi-output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be composed of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static / dynamically variable physical range. In this case, the wireless communication system 1 may be called a cell-free system.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0211] For the detection of PDCCH, a control resource set (Control Resource SET (CORESET)) and a search space may be used. CORESET corresponds to the resource for searching DCI. The search space corresponds to the search area and search method of PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space setting.

[0212] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting", etc. in the present disclosure may be read as each other.

[0213] By PUCCH, uplink control information (UCI) including at least one of channel state information (Channel State Information (CSI)), delivery confirmation information (for example, may be referred to as Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.) and scheduling request (Scheduling Request (SR)) may be transmitted. By PRACH, a random access preamble for establishing connection with the cell may be transmitted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0235] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement the functions of the PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer.

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

[0237] The transceiver unit 210 may transmit a Radio Resource Control (RRC) parameter indicating the application of an indicated Transmission Configuration Indication (TCI) state, or may transmit at least one of a Medium Access Control (MAC) control element and Downlink Control Information (DCI) indicating a plurality of unified TCI states. The control unit 210 may use the RRC parameter and at least one of the MAC control element and the DCI to instruct the application of an indicated TCI state for a Physical Uplink Control Channel (PUCCH) for each PUCCH resource or for each PUCCH resource group (first to fifth embodiments).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0255] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0256] The transceiver unit 220 may receive a Radio Resource Control (RRC) parameter indicating the application of an indicated Transmission Configuration Indication (TCI) state, or may receive at least one of a Medium Access Control (MAC) control element and a Downlink Control Information (DCI) indicating a plurality of unified TCI states. The controller 210 may control the application of an indicated TCI state for a Physical Uplink Control Channel (PUCCH) for each PUCCH resource or for each PUCCH resource group based on the RRC parameter and at least one of the MAC control element and the DCI (first to fifth embodiments).

[0257] The control unit 210 may control the indication TCI state for the PUCCH to be applied to each of the PUCCH resource groups based on at least one of a specific field included in the MAC control element and a configuration parameter of the PUCCH resource group (first embodiment).

[0258] The control unit 210 may perform control so that the indicated TCI state for the PUCCH is applied to each PUCCH resource group based on the association between the RRC parameters and PUCCH resources (second embodiment).

[0259] The application of the indication TCI state to the PUCCH for each PUCCH resource group may not be supported (third embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A terminal having: a receiving unit that receives a Radio Resource Control (RRC) parameter indicating the application of an instruction Transmission Configuration Indication (TCI) state, and receives at least one of a Medium Access Control (MAC) control element and a Downlink Control Information (DCI) that indicates a plurality of unified TCI states; and a control unit that controls the application of the instruction TCI state for a Physical Uplink Control Channel (PUCCH) for each PUCCH resource or for each PUCCH resource group based on the RRC parameter and at least one of the MAC control element and the DCI.

2. The terminal according to claim 1, wherein the control unit controls the indication TCI state for the PUCCH to be applied for each PUCCH resource group based on at least one of a specific field included in the MAC control element and a configuration parameter of a PUCCH resource group.

3. The terminal according to claim 1, wherein the control unit controls the indication TCI state for the PUCCH to be applied to each of the PUCCH resource groups based on an association between the RRC parameters and PUCCH resources.

4. The terminal according to claim 1, wherein application of the indication TCI state to the PUCCH for each PUCCH resource group is not supported.

5. A wireless communication method for a terminal, comprising: a step of receiving a Radio Resource Control (RRC) parameter indicating the application of an indicated Transmission Configuration Indication (TCI) state, and receiving at least one of a Medium Access Control (MAC) control element and a Downlink Control Information (DCI) indicating a plurality of unified TCI states; and a step of controlling, based on the RRC parameter and at least one of the MAC control element and the DCI, to apply the indicated TCI state for a Physical Uplink Control Channel (PUCCH) for each PUCCH resource or for each PUCCH resource group.

6. A base station having: a transmitter that transmits a Radio Resource Control (RRC) parameter indicating the application of an indicated Transmission Configuration Indication (TCI) state, and transmits at least one of a Medium Access Control (MAC) control element and downlink control information (DCI) that indicate a plurality of unified TCI states; and a controller that uses the RRC parameter and at least one of the MAC control element and the DCI to instruct the application of an indicated TCI state for a physical uplink control channel (PUCCH) for each PUCCH resource or for each PUCCH resource group.

Images