Terminal, wireless communication method, base station and system

Abstract

A terminal according to one aspect of the present disclosure comprises a reception unit which receives a configuration relating to a physical uplink control channel (PUCCH) for each cell and which receives downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH) and a control unit which determines, on the basis of the configuration relating to the PUCCH of a specific cell, a PUCCH for transmitting a hybrid automatic repeat request acknowledgement (HARQ-ACK) corresponding to the PDSCH and is characterized in that the configuration relating to the PUCCH for each cell is a configuration of any one of: a plurality of PUCCHs that are transmitted in at least the same time domain using a single-frequency network (SFN); a time-division-multiplexed PUCCH repetition; a time-division-multiplexed PUCCH repetition based on a single DCI; and a PUCCH for a single transmission / reception point. According to the one aspect of the present disclosure, UL transmission using a plurality of panels can be appropriately performed.

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] In future wireless communication systems, a UE will be able to use one of multiple panels (or multiple beams) for uplink (UL) transmission. Furthermore, in Rel. 18 and later, support for simultaneous transmission across multiple panels (STxMP) is being considered to improve UL throughput and reliability.

[0006] However, there has been insufficient consideration on how to control UL transmission using multiple panels (e.g., simultaneous UL transmission) when it is supported. If UL transmission using multiple panels is not performed appropriately, there is a risk of degradation of system performance, such as a decrease in throughput.

[0007] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control UL transmission even when UL transmission is performed using multiple panels.

[0008] A terminal according to one aspect of the present disclosure includes: a receiving unit that receives a configuration related to a physical uplink control channel (PUCCH) for each cell and receives downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH); and a control unit that determines a PUCCH for transmitting a hybrid automatic repeat request acknowledgment (HARQ-ACK) corresponding to the PDSCH based on the configuration related to the PUCCH of a specific cell, wherein the configuration related to the PUCCH for each cell is any one of a plurality of PUCCHs transmitted in at least the same time domain using a single frequency network (SFN), time-division multiplexed PUCCH repetition, time-division multiplexed PUCCH repetition based on a single DCI, and a PUCCH for a single transmission / reception point.

[0009] According to one aspect of the present disclosure, UL transmission using multiple panels can be performed appropriately.

[0010] Figures 1A and 1B show an example of a unified / common TCI framework. Figures 2A and 2B show an example of a DCI-based TCI status indication. Figure 3 shows an example of an association between a precoder type and a TPMI index. Figures 4A and 4B show an example of a single-panel UL transmission. Figures 5A to 5C show examples of methods 1 to 3 for simultaneous UL transmission using multiple panels. Figures 6A to 6C show an example of a PUSCH transmission method. Figures 7A to 7C show other examples of PUSCH transmission methods. Figure 8 shows an example of simultaneous UL transmission using multiple panels. Figure 9 shows an example of simultaneous transmission of PUSCH and PUCCH. Figure 10 shows an example of PUCCH cell switching scheme 1. Figure 11 shows an example of PUCCH cell switching scheme 2. Figure 12 shows another example of PUCCH cell switching scheme 2. Figures 13A to 13D show an example of an STxMP scheme. FIG. 14 is a diagram illustrating an example of the maximum number of layers. FIG. 15 is a diagram illustrating an example of application of an indicated TCI state according to the first embodiment. FIG. 16 is a diagram illustrating an example of association between an indicated TCI state, an SRS resource set, and layers according to Option 1-3-1-1. FIG. 17 is a diagram illustrating an example of association between an indicated TCI state, an SRS resource set, and layers according to Option 1-3-2-1. FIG. 18 is a diagram illustrating an example of application of an indicated TCI state according to the second embodiment. FIG. 19 is a diagram illustrating an example of association between an indicated TCI state, an SRS resource set, and layers according to Option 2-2-1-1. FIG. 20 is a diagram illustrating an example of association between an indicated TCI state, an SRS resource set, and layers according to embodiment 2-2-2. FIG. 21 is a diagram illustrating an example of transmission of a PUCCH according to embodiment 3-2. FIG. 22 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 23 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 24 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. Fig. 25 is a diagram illustrating an example of a hardware configuration of a base station and a user terminal according to an embodiment. Fig. 26 is a diagram illustrating an example of a vehicle according to an embodiment.

[0011] (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.

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

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

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

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

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

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

[0018] In the present disclosure, when N=M=X (X is any integer), it may mean that X TCI states (joint TCI states) common to UL and DL (corresponding to X TRPs) are notified / configured / indicated to the UE. Also, when N=X (X is any integer) and M=Y (Y may be any integer, Y=X), it may mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (i.e., separate TCI states) (corresponding to Y TRPs) are notified / configured / indicated to the UE.

[0019] For example, when N=M=1 is written, this may mean that a TCI state common to one UL and DL for a single TRP is notified / configured / indicated to the UE (joint TCI state for a single TRP).

[0020] Also, for example, when N=1 and M=1 are written, this may mean that one UL TCI state and one DL TCI state for a single TRP are separately notified / configured / instructed to the UE (separate TCI states for a single TRP).

[0021] Also, for example, when N=M=2 is written, this may mean that a TCI state common to multiple (two) ULs and DLs for multiple (two) TRPs is notified / configured / instructed to the UE (joint TCI state for multiple TRPs).

[0022] Also, for example, when N=2 and M=2, it may mean that multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs are notified / configured / instructed to the UE (separate TCI states for multiple TRPs).

[0023] In the above example, the values ​​of N and M are 1 or 2, but the values ​​of N and M may be 3 or more, and N and M may be different.

[0024] It is being considered that N=M=1 will be supported in Rel. 17. It is being considered that other cases will be supported in Rel. 18 and later.

[0025] In the example of Figure 1A, RRC parameters (information elements) configure multiple TCI states for both DL and UL. The MAC CE may activate multiple TCI states from the configured multiple TCI states. A DCI may indicate one of the activated multiple TCI states. The DCI may be a 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.

[0026] In the example of this figure, a point may be one TCI state that applies to both UL and DL, or two TCI states that apply to UL and DL respectively.

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

[0028] 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."

[0029] In the example of Figure 1B, the RRC parameters 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 each of the UL and DL may be configured / activated.

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

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

[0032] [Physical Layer Procedures for Data / Antenna Port QCL] In PDSCH-Config, the UE can configure a list of up to 128 DLorJointTCIState configurations to provide reference signals for PDSCH DMRS and PDCCH DMRS and CSI-RS within a CC, and also to provide a reference for determining the UL TX (Transmit) spatial filter for PUSCH and PUCCH resources and SRS within a CC based on dynamic and configuration grants, if available.

[0033] If there is no DLorJointTCIState or UL-TCIState (UL TCI state) configuration in the BWP in that CC, the UE may apply the DLorJointTCIState or UL-TCIState configuration from the reference BWP of the reference CC. If the UE has DLorJointTCIState or UL-TCIState configured in any CC in the same band, it does not assume that TCI-State, SpatialRelationInfo (spatial relation information), or PUCCH-SpatialRelationInfo (PUCCH spatial relation information) in that band are configured, except for SpatialRelationInfoPos (spatial relation information for position). The UE assumes that if the UE has TCI-State in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16 (simultaneous TCI update list 1), simultaneousTCI-UpdateList2-r16 (simultaneous TCI update list 2), simultaneousSpatial-UpdatedList1-r16 (simultaneous spatial update list 1), or simultaneousSpatial-UpdatedList2-r16 (simultaneous spatial update list 2), the UE does not have DLorJointTCIState or UL-TCIState configured in any CC in that CC list.

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

[0035] If the bwp-id or cell for a QCL type A / D source RS in the QCL-Info of a TCI state with DLorJointTCIState set is not set, the UE shall assume that the QCL type A / D source RS is set in the CC / DL BWP to which the TCI state applies.

[0036] (TCI State Indication) The Rel. 17 unified TCI framework supports the following modes 1 to 3: [Mode 1] MAC CE based TCI state indication [Mode 2] DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment [Mode 3] DCI based TCI state indication by DCI format 1_1 / 1_2 without DL assignment

[0037] A UE with a TCI state configured and activated with a Rel. 17 TCI State ID (e.g., tci-StateId_r17) receives DCI format 1_1 / 1_2 providing an indicated TCI state with the Rel. 17 TCI State ID for one CC, or receives DCI format 1_1 / 1_2 providing an indicated TCI state with the Rel. 17 TCI State ID for all CCs in the same CC list as the CC list configured by simultaneous TCI update list 1 or simultaneous TCI update list 2 (e.g., simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2). DCI format 1_1 / 1_2 may or may not be accompanied by a DL assignment if one is available.

[0038] If DCI format 1_1 / 1_2 does not carry a DL assignment, the UE can assume (verify) the following for that DCI: - the CS-RNTI is used to scramble the CRC for the DCI; - the values ​​of the following DCI fields (special fields) are set as follows: - the redundancy version (RV) field is all '1's; - the modulation and coding scheme (MCS) field is all '1's; - the new data indicator (NDI) field is 0; - the frequency domain resource assignment (FDRA) field is all '0's for FDRA type 0, or all '1's for FDRA type 1, or all '0's for Dynamic Switch (similar to PDCCH validation for release of DL semi-persistent scheduling (SPS) or UL grant type 2 scheduling).

[0039] Note that the DCI in the above-mentioned mode 2 / mode 3 may be referred to as beam instruction DCI.

[0040] In Rel. 15 / 16, if a UE does not support active BWP changes via DCI, the UE ignores the BWP indicator field. A similar behavior is considered for the relationship between support for Rel. 17 TCI states and the interpretation of the TCI field. It is considered that if a UE is configured with Rel. 17 TCI states, the TCI field will always be present in DCI format 1_1 / 1_2, and if the UE does not support TCI updates via DCI, the UE will ignore the TCI field.

[0041] In Rel. 15 / 16, whether or not a TCI field is present (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.

[0042] The TCI field in DCI format 1_1 is 0-bit if the higher layer parameter tci-PresentInDCI is not enabled, and 3-bit otherwise. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following behavior: [Action] If the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying that DCI format 1_1, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI is enabled for all CORESETs in the indicated BWP.

[0043] The TCI field in DCI format 1_2 is 0 bit if the higher layer parameter tci-PresentInDCI-1-2 is not set, otherwise it is 1, 2 or 3 bits determined by the higher layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following actions. [Operation] If the higher layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used for the PDCCH carrying that DCI format 1_2, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI-1-2 for all CORESETs in the indicated BWP is set with the same value as tci-PresentInDCI-1-2 set for the CORESET used for the PDCCH carrying that DCI format 1_2.

[0044] 2A shows an example of a DCI-based joint DL / UL TCI status indication, in which a TCI status ID indicating the joint DL / UL TCI status is associated with a value of the TCI field for the joint DL / UL TCI status indication.

[0045] 2B shows an example of DCI-based separate DL / UL TCI status indication. At least one TCI status ID, indicating a DL-only TCI status or indicating a UL-only TCI status, is associated with a value of the TCI field for the separate DL / UL TCI status indication. In this example, TCI field values ​​000 to 001 are associated with only one TCI status ID for DL, TCI field values ​​010 to 011 are associated with only one TCI status ID for UL, and TCI field values ​​100 to 111 are associated with both one TCI status ID for DL ​​and one TCI status ID for UL.

[0046] (Indicated TCI State / Configured TCI State) For Rel. 17 TCI states, unified / common TCI state may mean the Rel. 17 TCI state indicated using (Rel. 17) DCI / MAC CE / RRC (indicated Rel. 17 TCI state).

[0047] In the present disclosure, the terms indicated Rel. 17 TCI state, indicated TCI state, unified / common TCI state, TCI state applicable to multiple types of signals (channels / RS), and TCI state for multiple types of signals (channels / RS) may be interpreted interchangeably.

[0048] The indicated Rel. 17 TCI state may be shared with at least one of the UE-specific reception of PDSCH / PDCC (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 or the unified TCI state.

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

[0050] The configured Rel. 17 TCI state may not be shared with at least one of the UE-specific reception of PDSCH / PDCC (updated using Rel. 17 DCI / MAC CE / RRC), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The configured Rel. 17 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 Rel. 17 TCI state (common TCI state) is updated.

[0051] It is being considered that the indicated Rel. 17 TCI state will be applied to UE-specific channels / signals (RS), and that the UE will be notified by higher layer signaling (RRC signaling) whether the indicated Rel. 17 TCI state or the configured Rel. 17 TCI state will be applied to non-UE-specific channels / signals.

[0052] It is being considered that the RRC parameters for the configured Rel. 17 TCI state (TCI state ID) will have the same configuration as the RRC parameters for the TCI state in Rel. 15 / 16. It is also being considered that the configured Rel. 17 TCI state will be configured / instructed per CORESET / per resource / per resource set using RRC / MAC CE. It is also being considered that the UE will determine the configuration / instruction based on specific parameters.

[0053] It is considered that the UE updates the indicated TCI state and the configured TCI state separately. For example, if the unified TCI state for the indicated TCI state is updated, the UE may not update the configured TCI state. It is also considered that the UE may determine whether to update the configured TCI state based on a specific parameter.

[0054] Furthermore, regarding the PDCCH / PDSCH, it is being considered to use higher layer signaling (RRC / MAC CE) to switch whether the indication Rel. 17 TCI state is applied or not (the configured Rel. 17 TCI state is applied, or a TCI state configured separately from the indication Rel. 17 TCI state is applied).

[0055] Regarding intra-cell beam indication (TCI state indication), it is being considered to support Rel. 17 TCI state indication for a UE-specific CORESET and its associated PDSCH, and a non-UE-specific CORESET and its associated PDSCH.

[0056] Also, for inter-cell beam indication (e.g., L1 / L2 inter-cell mobility), it is being considered to support Rel. 17 TCI state indication for a UE-specific CORESET and its associated PDSCH.

[0057] In Rel. 15, whether to indicate the TCI state for CORESET #0 was up to the implementation of the base station. In Rel. 15, for CORESET #0 for which a TCI state is indicated, the indicated TCI state is applied. For CORESET #0 for which a TCI state is not indicated, the SSB and QCL selected at the time of the latest (most recent) PRACH transmission are applied.

[0058] In the unified TCI state framework for Rel. 17 and later, the TCI state for CORESET #0 is being considered.

[0059] For example, in the unified TCI state framework for Rel. 17 and later, whether or not to apply the indicated Rel. 17 TCI state associated with the serving cell for the Rel. 17 TCI state indication in CORESET #0 is configured by RRC for each CORESET, and if not, the legacy MAC CE / RACH signaling mechanism may be used.

[0060] Note that the CSI-RS associated with the Rel. 17 TCI state applied to CORESET #0 may be QCL'd with the SSB associated with the serving cell PCI (physical cell ID) (similar to Rel. 15).

[0061] For CORESET #0, a CORESET with a common search space (CSS), and a CORESET with a CSS and a UE-specific search space (USS), whether to follow the Rel. 17 TCI state may be configured for each CORESET by an RRC parameter. If the Rel. 17 TCI state is not configured to be followed for that CORESET, the configured Rel. 17 TCI state may be applied to that CORESET.

[0062] For non-UE-dedicated channels / RSs (except CORESET), whether to follow the indicated Rel. 17 TCI state may be configured by an RRC parameter for each channel / resource / resource set. If the indicated Rel. 17 TCI state is not configured for that channel / resource / resource set, the configured Rel. 17 TCI state may apply to that channel / resource / resource set.

[0063] (Channels / RSs to which the indicated TCI state applies) The indicated TCI state by the MAC CE / DCI may apply to the following channels / RSs:

[0064] [PDCCH] - If followUnifiedTCIState is configured for CORESET0, the indicated TCI state applies. Otherwise, the Rel. 15 specifications apply for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCL'd with SSB. - For CORESETs with USS / CSS type 3 and index other than 0, the indicated TCI state always applies. - For CORESETs with index other than 0 and at least CSS type other than 3, if followUnifiedTCIState is configured, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.

[0065] [PDSCH] - The indicated TCI state always applies to all UE-dedicated PDSCHs. - For non-UE-dedicated PDSCHs (PDSCHs scheduled by DCI in CSS), the indicated TCI state may apply if followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules that PDSCH). Otherwise, the configured TCI state for that PDSCH applies to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state may depend on whether followUnifiedTCIState is set for the CORESET used to schedule that PDSCH.

[0066] [CSI-RS] For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for CORESET of the PDCCH that triggers that A-CSI-RS), the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS applies.

[0067] [PUCCH] - For all dedicated PUCCH resources, the indicated TCI state always applies.

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

[0069] [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 is applied. For other SRSs, the configured TCI state in the SRS resource set is applied.

[0070] (PUSCH Precoder) In NR, it is being considered that a UE will support at least one of codebook (CB)-based transmission and non-codebook (NCB)-based transmission.

[0071] For example, it is being considered that the UE determines a precoder (precoding matrix) for CB-based and / or NCB-based Physical Uplink Shared Channel (PUSCH) transmission using at least a Sounding Reference Signal (SRS) resource indicator (SRI).

[0072] In the case of CB-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), a Transmitted Precoding Matrix Indicator (TPMI), etc. In the case of NCB-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI.

[0073] The SRI, TRI, TPMI, etc. may be notified to the UE using Downlink Control Information (DCI). The SRI may be specified by the SRS Resource Indicator field (SRI field) of the DCI, or may be specified by the parameter "srs-ResourceIndicator" included in the RRC information element "ConfiguredGrantConfig" of the configured grant PUSCH. The TRI and TPMI may be specified by the "Precoding information and number of layers" field of the DCI.

[0074] The UE may report UE capability information related to a precoder type, and the base station may configure the precoder type based on the UE capability information through higher layer signaling. The UE capability information may be information on the precoder type used by the UE in PUSCH transmission (which may be represented by the RRC parameter "pusch-TransCoherence").

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

[0076] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), etc.

[0077] The UE may determine the precoder to be used for PUSCH transmission based on precoder type information (which may be represented by the RRC parameter "codebookSubset") included in PUSCH configuration information ("PUSCH-Config" information element of RRC signaling) notified by higher layer signaling. The UE may be configured with a subset of the PMI specified by the TPMI by the codebookSubset.

[0078] The precoder type may be specified by any one of full coherent, partial coherent, and non-coherent, or a combination of at least two of these (for example, it may be expressed by parameters such as "fully and partial and non-coherent" or "partial and non-coherent").

[0079] Fully coherent may mean that all antenna ports used for transmission are synchronized (may be expressed as being able to match the phase, using the same precoder, etc.). Partially coherent may mean that some of the antenna ports used for transmission are synchronized, but those some ports cannot be synchronized with other ports. Non-coherent may mean that each antenna port used for transmission cannot be synchronized.

[0080] Note that a UE that supports a fully coherent precoder type may be assumed to support partially coherent and non-coherent precoder types, and a UE that supports a partially coherent precoder type may be assumed to support a non-coherent precoder type.

[0081] The precoder type may be interpreted as coherency, PUSCH transmission coherence, coherent type, coherence type, codebook type, codebook subset, codebook subset type, or the like.

[0082] The UE may determine, from multiple precoders (which may also be called precoding matrices, codebooks, etc.) for CB-based transmission, a precoding matrix corresponding to a TPMI index obtained from a DCI (e.g., DCI format 0_1, etc.) that schedules an UL transmission.

[0083] 3 is a diagram showing an example of association between precoder types and TPMI indexes, which corresponds to a table of precoding matrices W for single-layer (rank 1) transmission using four antenna ports in DFT-s-OFDM (Discrete Fourier Transform spread OFDM, transform precoding is effective).

[0084] In Fig. 3, when the precoder type (codebookSubset) is fully, partial, and noncoherent (fullyAndPartialAndNonCoherent), the UE is notified of a TPMI of any one of 0 to 27 for single layer transmission. Also, when the precoder type is partial and noncoherent (partialAndNonCoherent), the UE is configured with a TPMI of any one of 0 to 11 for single layer transmission. When the precoder type is noncoherent, the UE is configured with a TPMI of any one of 0 to 3 for single layer transmission.

[0085] As shown in Figure 3, a precoding matrix in which only one element in each column is non-zero may be called a non-coherent codebook. A precoding matrix in which a predetermined number (not all) of elements in each column are non-zero may be called a partially coherent codebook. A precoding matrix in which all elements in each column are non-zero may be called a fully coherent codebook.

[0086] Non-coherent and partially coherent codebooks may be referred to as antenna selection precoders, and fully coherent codebooks may be referred to as non-antenna selection precoders.

[0087] In the present disclosure, a partially coherent codebook may correspond to a codebook (precoding matrix) corresponding to a TPMI specified by DCI for codebook-based transmission by a UE configured with a partially coherent codebook subset (e.g., RRC parameter “codebookSubset”=“partialAndNonCoherent”), excluding a codebook corresponding to a TPMI specified by DCI for a UE configured with a non-coherent codebook subset (e.g., RRC parameter “codebookSubset”=“nonCoherent”) (i.e., in the case of single-layer transmission with four antenna ports, a codebook with TPMI=4 to 11).

[0088] In the present disclosure, a fully coherent codebook may correspond to a codebook (precoding matrix) corresponding to a TPMI specified by DCI for codebook-based transmission by a UE configured with a fully coherent codebook subset (e.g., RRC parameter “codebookSubset”=“fullyAndPartialAndNonCoherent”), excluding a codebook corresponding to a TPMI specified by DCI for a UE configured with a partially coherent codebook subset (e.g., RRC parameter “codebookSubset”=“partialAndNonCoherent”) (i.e., in the case of single-layer transmission with four antenna ports, a codebook with TPMI=12 to 27).

[0089] (Control of Transmission of SRS and PUSCH) In Rel. 15 NR, a terminal (user terminal, User Equipment (UE)) may receive information (SRS configuration information, for example, parameters in the RRC control element "SRS-Config") used for transmitting a measurement reference signal (for example, a sounding reference signal (SRS)).

[0090] Specifically, the UE may receive at least one of information regarding one or more SRS resource sets (SRS resource set information, e.g., the RRC control element "SRS-ResourceSet") and information regarding one or more SRS resources (SRS resource information, e.g., the RRC control element "SRS-Resource").

[0091] An SRS resource set may be associated with (or group together) a predetermined number of SRS resources, each of which may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).

[0092] The SRS resource set information may include an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type, and information on SRS usage.

[0093] Here, the SRS resource type may indicate any one of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic CSI (Aperiodic SRS (A-SRS)). Note that the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation), and transmit A-SRS based on an SRS request in the DCI.

[0094] Furthermore, the use ("usage" of the RRC parameter, "SRS-SetUse" of the L1 (Layer-1) parameter) may be, for example, beam management, codebook (CB), non-codebook (NCB), antenna switching, etc. The SRS for codebook or non-codebook use may be used to determine a precoder for codebook-based or non-codebook-based uplink shared channel (Physical Uplink Shared Channel (PUSCH)) transmission based on the SRI.

[0095] For example, in the case of codebook-based transmission, the UE may determine a precoder (precoding matrix) for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), and a Transmitted Precoding Matrix Indicator (TPMI). In the case of non-codebook-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI.

[0096] The SRS resource information may include an SRS resource ID (SRS-ResourceId), the number of SRS ports, the SRS port number, a transmission comb, an SRS resource mapping (e.g., time and / or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping-related information, an SRS resource type, a sequence ID, spatial relationship information of the SRS, etc.

[0097] The spatial relationship information of the SRS (e.g., the RRC information element "spatialRelationInfo") may indicate spatial relationship information between a predetermined reference signal and the SRS. The predetermined reference signal may be at least one of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Channel State Information Reference Signal (CSI-RS), and an SRS (e.g., another SRS). The SS / PBCH block may be referred to as a Synchronization Signal Block (SSB).

[0098] The spatial relationship information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the predetermined reference signal.

[0099] In the present disclosure, the SSB index, SSB resource ID, and SSB Resource Indicator (SSBRI) may be interchangeable. Furthermore, the CSI-RS index, CSI-RS resource ID, and CSI-RS Resource Indicator (CRI) may be interchangeable. Furthermore, the SRS index, SRS resource ID, and SRI may be interchangeable.

[0100] The spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc. corresponding to the predetermined reference signal.

[0101] When the UE is configured with spatial relationship information regarding the SRS and an SSB or CSI-RS for a certain SRS resource, the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter for receiving the SSB or CSI-RS (spatial domain receive filter). In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

[0102] When the UE is configured with spatial relationship information between another SRS (reference SRS) and the target SRS for a certain SRS (target SRS), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain transmit filter) for transmitting the reference SRS. That is, in this case, the UE may assume that the UE transmit beam of the reference SRS and the UE transmit beam of the target SRS are the same.

[0103] The UE may determine the spatial relationship of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on the value of a predetermined field (e.g., an SRS resource identifier (SRI) field) in the DCI. Specifically, the UE may use spatial relationship information of the SRS resources (e.g., the RRC information element "spatialRelationInfo") determined based on the value of the predetermined field (e.g., the SRI) for PUSCH transmission.

[0104] In Rel. 15 / 16 NR, when codebook-based transmission is used for PUSCH, the UE is configured by RRC with an SRS resource set of a codebook usage having up to two SRS resources, and one of the up to two SRS resources may be indicated by DCI (a 1-bit SRI field). The transmission beam for PUSCH is specified by the SRI field.

[0105] The UE may determine the TPMI and the number of layers (transmission rank) for the PUSCH based on the precoding information and number of layers field (hereinafter also referred to as the precoding information field). The UE may select a precoder from an uplink codebook for the same number of SRS ports as the number of SRS ports indicated by the upper layer parameter "nrofSRS-Ports" configured for the SRS resource specified by the SRI field based on the TPMI, the number of layers, etc.

[0106] In Rel. 15 / 16 NR, when non-codebook-based transmission is used for PUSCH, a non-codebook-used SRS resource set having up to four SRS resources may be configured for the UE by RRC, and one or more of the up to four SRS resources may be indicated by DCI (a 2-bit SRI field).

[0107] The UE may determine the number of layers (transmission rank) for the PUSCH based on the SRI field. For example, the UE may determine that the number of SRS resources specified by the SRI field is the same as the number of layers for the PUSCH. The UE may also calculate a precoder for the SRS resources.

[0108] If a CSI-RS (which may be referred to as an associated CSI-RS) associated with the SRS resource (or an SRS resource set to which the SRS resource belongs) is configured by a higher layer, the transmission beam for the PUSCH may be calculated based on (measurements of) the configured associated CSI-RS. Otherwise, the transmission beam for the PUSCH may be specified by the SRI.

[0109] The UE may be configured to use codebook-based PUSCH transmission or non-codebook-based PUSCH transmission by a higher layer parameter "txConfig" indicating a transmission scheme. The parameter may indicate a value of "codebook" or "non-codebook."

[0110] In the present disclosure, a codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) may refer to a PUSCH when a UE is configured with "codebook" as a transmission scheme. In the present disclosure, a non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission) may refer to a PUSCH when a UE is configured with "non-codebook" as a transmission scheme.

[0111] Incidentally, future wireless communication systems (e.g., Rel. 18 NR and later) are expected to support simultaneous UL transmission (e.g., simultaneous multi-panel UL transmission (STxMP)) using multiple beams / panels / TRPs toward one or more transmission / reception points (TRPs).

[0112] For example, Rel. 18 considers simultaneous UL transmission using up to two TRPs per two panels. It also considers single-DCI-based and multi-DCI-based multi-TRP operation, and assumes that the total number of layers across all panels is up to four, and the total number of codewords across all panels is up to two. Of course, the number of TRPs, panels, layers, and codewords are not limited to these.

[0113] (Single Panel Transmission) The single panel UL transmission scheme or a candidate single panel UL transmission scheme may employ at least one of the following transmission schemes A and B (single panel UL transmission schemes A and B). In the present disclosure, a panel / UE panel may be interpreted as a UE capability value set (e.g., a UE capability value set) reported for each UE capability. In the present disclosure, different panels, different spatial relationships, different joint TCI states, different TPC parameters, different antenna ports, etc. may be interpreted as interchangeable terms.

[0114] <Transmission Scheme A: Single Panel Single TRP UL Transmission> In Rel. 15 and Rel. 16, a transmission scheme is used in which a UE transmits UL for one TRP at a time from only one beam and panel (FIG. 4A).

[0115] <Transmission Scheme B: Single Panel Multi-TRP UL Transmission> Rel. 17 considers UL transmission from only one beam and panel at a time and repeated transmission for multiple TRPs (see Figure 4B). In the example of Figure 4B, the UE transmits a PUSCH from panel #1 to TRP #1 (switching beams and panels), and then transmits a PUSCH from panel #2 to TRP #2. The two TRPs are connected via an ideal backhaul.

[0116] (Multi-panel Transmission) In Rel. 18 and later, in order to improve UL throughput / reliability, support for simultaneous UL transmission using multiple panels (e.g., simultaneous multi-panel UL transmission (STxMP)) for one or more TRPs is being considered. Also, a multi-panel UL transmission scheme is being considered for a specific UL channel (e.g., PUSCH / PUCCH).

[0117] For example, up to X (e.g., X = 2) and up to Y (e.g., Y = 2) panels may be supported for multi-panel UL transmission. In multi-panel UL transmission, if UL precoding indication for PUSCH is supported, a codebook of a legacy system (e.g., pre-Rel. 16) may be supported for simultaneous multi-panel transmission. Considering single DCI and multi-DCI-based multi-TRP operation, the number of layers may be up to x (e.g., x = 4) across all panels, and the number of codewords (CWs) may be up to y (e.g., y = 2) across all panels.

[0118] At least one of the following methods 1 to 3 (multi-panel UL transmission methods 1 to 3) is being considered as a multi-panel UL transmission method or a candidate multi-panel UL transmission method. Only one of transmission methods 1 to 3 may be supported. Multiple methods including at least one of transmission methods 1 to 3 may be supported, and one of the multiple transmission methods may be configured in the UE.

[0119] <Transmission Scheme 1: Coherent Multi-Panel UL Transmission> Multiple panels may be synchronized with each other. All layers are mapped to all panels. Multiple analog beams are directed. The SRS Resource Indicator (SRI) field may be extended. This scheme may use up to 4 layers for UL.

[0120] In the example of Figure 5A, the UE maps one codeword (CW) or one transport block (TB) to L layers (PUSCH (1, 2, ..., L)) and transmits the L layers from each of two panels. Panels #1 and #2 are coherent. Transmission scheme 1 can obtain diversity gain. The total number of layers in the two panels is 2L. If the maximum total number of layers is 4, the maximum number of layers in one panel is 2.

[0121] <Transmission Scheme 2: Non-coherent Multi-Panel UL Transmission of One Codeword (CW) or Transport Block (TB)> The multiple panels may not be synchronized. Different layers are mapped to one CW or TB for different panels and PUSCHs from multiple panels. A layer corresponding to one CW or TB may be mapped to multiple panels. This transmission scheme may use up to four layers or up to eight layers for the UL. If up to eight layers are supported, this transmission scheme may support one CW or TB using up to eight layers.

[0122] In the example of FIG. 5B, the UE maps 1 CW or 1 TB to k layers (PUSCH(1, 2, ..., k)) and L-k layers (PUSCH(k+1, k+2, ..., L)), transmits k layers from panel #1, and transmits L-k layers from panel #2. Transmission scheme 2 can obtain gains through multiplexing and diversity. The total number of layers in the two panels is L.

[0123] <Transmission Scheme 3: Non-coherent Multi-Panel UL Transmission of Two CWs or TBs> The multiple panels may not be synchronized. Different layers are mapped to different panels and two CWs or TBs for PUSCHs from the multiple panels. A layer corresponding to one CW or TB may be mapped to one panel. Layers corresponding to multiple CWs or TBs may be mapped to different panels. This transmission scheme may use up to four layers or up to eight layers for the UL. When up to eight layers are supported, this transmission scheme may support up to four layers per CW or TB.

[0124] In the example of FIG. 5C , the UE maps CW#1 or TB#1 of the 2CWs or 2TBs to k layers (PUSCH (1, 2, ..., k)), maps CW#2 or TB#2 to L-k layers (PUSCH (k+1, k+2, ..., L)), and transmits k layers from panel #1 and L-k layers from panel #2. Transmission method 3 can obtain gains through multiplexing and diversity. The total number of layers in the two panels is L.

[0125] In each of the above transmission schemes, the base station may configure or indicate panel-specific transmission for UL transmission using UL TCI or panel ID. UL TCI (UL TCI state) may be based on signaling similar to DL beam indication supported in Rel. 15. The panel ID may be implicitly or explicitly applied to transmission of at least one of the target RS resource or target RS resource set, PUCCH, SRS, and PRACH. When the panel ID is explicitly signaled, the panel ID may be configured in at least one of the target RS, target channel, and reference RS (e.g., DL RS resource configuration or spatial relationship information).

[0126] (Simultaneous Multi-Panel Transmission) In one or more of the transmission methods / modes described above, multi-panel UL transmission (e.g., simultaneous transmission across multiple panels (STxMP)) for scheduling a PUSCH based on one DCI (single DCI) / scheduling a PUSCH based on multiple DCIs (multi-DCI) is being considered.

[0127] <Single DCI-Based STxMP> In simultaneous multi-panel transmission (STxMP) in a single DCI-based multi-TRP system, the following schemes may be applied to UL transmissions (e.g., PUSCH): Space Division Multiplexing (SDM): Different layers / DMRS ports of one PUSCH are separately precoded and transmitted simultaneously from different UE beams / panels (see Figures 6A and 6B); SDM repetition: Two PUSCH transmission opportunities with different redundancy versions (RVs) of the same TB are transmitted simultaneously from two different UE beams / panels on the same time and frequency resources (see Figure 6C); and Frequency Division Multiplexing (FDM)-A: Different portions of the frequency domain resources of one PUSCH transmission opportunity (e.g., one PUSCH transmission occasion) are transmitted from different UE beams / panels (see Figure 7A). FDM-B scheme: Two PUSCH transmission opportunities with the same / different RVs of the same TB are transmitted from different UE beams / panels on non-overlapping frequency and time domain resources (see Figure 7B). SFN-based transmission scheme: All the same layers / DMRS ports of one PUSCH are transmitted simultaneously from two different UE beams / panels (see Figure 7C).

[0128] In the present disclosure, the terms "repeated transmission" and "transmission" may be interchangeable. Transmitting multiple TBs may mean transmitting the same TB multiple times or transmitting different TBs.

[0129] Space Division Multiplexing (SDM) The UE may assume that repeated PUSCH transmissions employing Space Division Multiplexing (SDM) are scheduled on the same time and frequency resources, i.e., the UE may transmit repeated PUSCH transmissions employing SDM on the same time and frequency resources when using coherent panels.

[0130] 6A is a diagram showing an example of repeated transmission using SDM in one CW, in which the time and frequency resources of layers #1-2 and #3-4 corresponding to the PUSCH / PUCCH are the same.

[0131] 6B is a diagram showing an example of repeated transmission using SDM in two CWs, in which CW#1 and CW#2 corresponding to PUSCH / PUCCH have the same time and frequency resources.

[0132] 6C is a diagram showing an example of repeated transmission using SDM, in which the time and frequency resources of PUSCH / PUCCH repetition #1 and repetition #2 are the same.

[0133] Note that PUSCH transmission using SDM (for example, repeated PUSCH transmission) may be configured such that at least a portion of the time and frequency resources overlap.

[0134] Frequency Division Multiplexing (FDM) The UE may assume that PUSCH / PUCCH repeat transmissions employing Frequency Division Multiplexing (FDM) are scheduled on the same time resources but different frequency resources, i.e., the UE may transmit PUSCH / PUCCH repeat transmissions employing FDM on the same time resources but different frequency resources when using coherent panels.

[0135] 7A is a diagram showing a first example of repeated transmission using FDM (FDM-A), in which one PUSCH / PUCCH repeated transmission is performed for one TB / UCI.

[0136] 7B is a diagram showing a second example of repeated transmission using FDM (FDM-B), in which PUSCH / PUCCH repeated transmission is performed twice per TB / UCI.

[0137] 7C is a diagram illustrating an example of repeated transmission using a single frequency network (SFN), in which one PUSCH / PUCCH is transmitted using a different beam / panel for one TB / UCI.

[0138] As shown in Figures 6A and 6B, when simultaneous multi-panel transmission based on spatial division multiplexing (STxMP SDM scheme) is performed for non-codebook PUSCH transmission, different layers / DMRS ports of one PUSCH can be precoded separately and transmitted simultaneously from different UP panels.

[0139] For simultaneous multi-panel transmission based on spatial division multiplexing of non-codebook-based PUSCH, the following two options are assumed as an SRI indication (e.g., SRI indication):

[0140] Option 1: One SRI combination is indicated. The SRI combination may be indicated from non-codebook SRS resources across two panels.

[0141] Option 2: Multiple (e.g., two) SRS combinations (e.g., two SRI combinations) are indicated, and each SRI combination may be indicated from non-codebook SRS resources of one panel (e.g., NCB SRS resources of one panel).

[0142] An SRI combination may include one or more SRS resources (e.g., SRS resources for non-codebooks). For example, one SRI combination (or SRI field) may indicate the SRI / SRS resources corresponding to each panel. An SRI combination may be referred to as an SRI set or an SRI group.

[0143] <Multi-DCI-based STxMP> In Rel. 18 and later, simultaneous transmission of UL channels / UL signals (e.g., PUSCH+PUSCH and PUSCH+PUCCH) is expected to be supported in STxMP in a multi-DCI-based multi-TRP system (see Figure 8). As an example, it is expected that at least one of simultaneous transmission of multiple PUSCHs (e.g., PUSCH+PUSCH) and simultaneous transmission of PUSCH and PUCCH will be supported.

[0144] In Rel. 18 and later, a UCI multiplexing / mapping method has been studied for the case where one PUCCH overlaps with multiple PUSCHs in simultaneous transmission of PUSCH and PUCCH, and the multiple PUSCHs may be multiple PUSCHs (related to STxMP) that are simultaneously transmitted.

[0145] In this case, the multiple PUSCHs may be associated with different TRPs / panels (see FIG. 9).

[0146] In the existing specifications (up to Rel. 17), for multi-DCI multi-TRP, when the RRC parameter "ackNackFeedbackMode" is set to "separate", the UE does not assume that dynamically scheduled PUSCH / PUCCH overlaps with other dynamically scheduled PUSCH / PUCCH in the time domain (see Figure 8).

[0147] This is because when the RRC parameter "ackNackFeedbackMode" is set to "separate", non-ideal backhaul is assumed between the two TRPs, and each TRP cannot be aware of the dynamic schedule of the other TRP in a timely manner.

[0148] In the present disclosure, dynamically scheduled PUSCH / PUCCH may refer to PUSCH / PUCCH scheduled using a dynamic grant, or PUSCH / PUCCH dynamically scheduled using DCI.

[0149] (PUCCH Cell Switching) In Rel. 17, PUCCH cell switching between multiple (e.g., two) TDD cells in the same PUCCH cell group is supported to reduce HARQ-ACK feedback delay in TDD operation.

[0150] In addition to the PCell / PSCell / PUCCH-SCell, one additional SCell may be configured for PUCCH resources / transmission.

[0151] If two PUCCH cell groups are configured, an additional SCell may be configured for each PUCCH cell group.

[0152] PUCCH cell switching may be performed based on dynamic instructions or semi-static settings.

[0153] When PUCCH cell switching is based on dynamic indication (which may be referred to as Scheme 1), the PUCCH cell may be indicated using a new field (PUCCH cell indicator field) included in the DCI. In this case, K1 indicated by a field indicating the timing of HARQ-ACK feedback included in the DCI may be interpreted / determined based on the numerology (e.g., subcarrier spacing setting) of the cell after switching (target PUCCH cell).

[0154] Fig. 10 is a diagram showing an example of PUCCH cell switching scheme 1. In the example shown in Fig. 10, a DL CC (cell), a PCell, and a PUCCH SCell #1 are configured, and DCI and PDSCH are received in the DL CC (cell).

[0155] In the example shown in FIG. 10, the slot length of the DL CC and PCell is different from the slot length of PUCCH SCell#1.

[0156] In the example shown in Figure 10, the DCI includes a field indicating the timing of HARQ-ACK feedback and a PUCCH cell indicator field, where the field indicating the timing of HARQ-ACK feedback indicates K1 = 2 and the PUCCH cell indicator field indicates PUCCH SCell #1 as the target cell.

[0157] At this time, the UE determines that the slot (slot #3) in PUCCH SCell #1 two slots after the slot in which the PDSCH was received is the slot in which to transmit HARQ-ACK for the PDSCH.

[0158] When PUCCH cell switching is based on semi-static configuration (which may be referred to as Scheme 2), the time domain of the PUCCH cell pattern may be configured for each PUCCH cell group with a granularity of one slot of the PCell / PSCell / PUCCH-SCell. In this case, K1 indicated by the field indicating the timing of HARQ-ACK feedback included in the DCI may be interpreted / determined based on the numerology of the PCell / PSCell / PUCCH-SCell (e.g., subcarrier spacing setting).

[0159] Fig. 11 is a diagram showing an example of PUCCH cell switching scheme 2. In the example shown in Fig. 11, a PDSCH cell, a PC cell, and a PUCCH SCell #1 are configured, and PDSCH #1 and PDSCH #2 are received in the PDSCH cell. Furthermore, a target PUCCH cell is configured for each slot of the PDSCH cell / PCell (PUCCH cell pattern).

[0160] In the example shown in Figure 11, the timing of transmission of HARQ-ACK for PDSCH #1 is the slot (slot #1) to which SCell is set in the PUCCH cell pattern. At this time, the UE transmits HARQ-ACK for PDSCH #1, which is instructed to be transmitted in PCell, in PUCCH SCell (by switching).

[0161] In the example shown in Figure 11, the timing of transmission of HARQ-ACK for PDSCH #2 is the slot (slot #3) to which PCell is set in the PUCCH cell pattern. At this time, the UE transmits HARQ-ACK for PDSCH #1, which is instructed to be transmitted in PCell, in PCell (without switching).

[0162] Fig. 12 is a diagram showing another example of PUCCH cell switching scheme 2. The example shown in Fig. 12 differs from Fig. 11 above in the slot length of PUCCH SCell #1.

[0163] If the slots of the PCell / PSCell / PUCCH-SCell overlap with multiple slots of the target PUCCH cell, the UE may determine that the first slot of the multiple slots is the slot to be used for PUCCH / HARQ-ACK transmission.

[0164] In the example shown in FIG. 12, the UE transmits HARQ-ACK for PDSCH #1 in (by switching to) slot #2, which is the first slot of slots #2 and #3 of PUCCH SCell #1 that overlap with slot #1 in PCell.

[0165] (Analysis) As mentioned above, in future wireless communication systems (Rel. 18 and later), simultaneous UL transmission (which may be called, for example, simultaneous multi-panel UL transmission (STxMP)) using multiple beams / panels / TRPs is being considered for a UE.

[0166] Specifically, at least one of the following is considered for STxMP: - Single DCI PUSCH SDM scheme - Single DCI PUSCH SFN scheme - Multi-DCI overlapping PUSCH+PUSCH scheme - Single DCI PUCCH SFN scheme.

[0167] The single DCI PUSCH SDM scheme may mean that different layers / DMRS ports of one PUSCH scheduled / triggered by one DCI are transmitted simultaneously using different panels (for different TRPs) (Fig. 13A).

[0168] The single DCI PUSCH SFN scheme may mean that multiple (e.g., all) layers / DMRS ports of one PUSCH scheduled / triggered by one DCI are transmitted simultaneously using different panels (for different TRPs) (Fig. 13B).

[0169] A multi-DCI overlapping PUSCH+PUSCH scheme may mean that multiple (e.g., two) PUSCHs that overlap (at least partially) in the time domain are transmitted simultaneously using different panels (for different TRPs) (Fig. 13C).

[0170] The single DCI PUCCH SFN scheme may mean that one PUCCH is transmitted simultaneously using different panels (for different TRPs) (FIG. 13D).

[0171] In this disclosure, the above scheme names are used for convenience, but these are merely examples and are not limited to these examples.

[0172] It should be noted that up to n layers (e.g., n=4) may be transmitted across m panels (e.g., m=2).

[0173] In addition, in Rel. 18 and later, it is being considered to extend the unified TCI state framework to beam direction.

[0174] In the single DCI PUSCH SDM / SFN scheme, multiple (e.g., two) SRS resource sets may be configured and multiple (e.g., two) SRI / TPMI fields may be indicated.

[0175] In a multi-DCI PUSCH+PUSCH scheme, multiple (eg, two) SRS resource sets may be configured, and each of the multiple SRS resource sets may be associated with a different CORESET pool index.

[0176] In a single DCI PUCCH SFN scheme, multiple (eg, two) TCI states may be associated with one PUCCH resource.

[0177] It is considered that multiple (for example, two) SRS resource sets with CB / NCB usage are applied to the PUSCH of the SDM / SFN scheme for STxMP.

[0178] Dynamic switching for STxMP does not support switching between the SDM / SFN scheme for STxMP and the TDM scheme using multiple TRPs defined in Rel. 17. However, support for switching between the SDM / SFN scheme for STxMP and the single TRP scheme is under consideration.

[0179] It is being considered that a specific field in the DCI (e.g., SRS resource set indicator) be utilized to switch between single DCI-based STxMP (scheme) and single TRP.

[0180] The maximum number of layers for single TRP and STxMP SDM may be set separately.

[0181] In the case of single TRP transmission, the maximum number of layers may be set by the RRC parameter maxRank (or Lmax), as in existing specifications.

[0182] For the SDM STxMP scheme, a separate maximum number of layers may be configured for the first SRS resource set and the second SRS resource set (apart from maxRank (or Lmax) in the single TRP case), e.g., an RRC parameter (e.g., maxRankPerSRSResourceSet) indicating the maximum number of layers per SRS resource set.

[0183] Figure 14 shows an example of the maximum number of layers. In the example shown in Figure 14, in the case of a single TRP, the RRC parameter maxRank is set to 4 for the UE. The UE transmits a maximum of four layers (layer 1) of PUSCH using a single TRP / single panel (panel #1).

[0184] In the example shown in Fig. 14, an RRC parameter (e.g., maxRankPerSRSResourceSet) that sets the maximum number of layers for the STxMP scheme is configured for the UE. For example, if this parameter is set to 2, the UE transmits PUSCHs of up to two layers (Layer 1) using the first TRP / panel (Panel #1) and the second TRP / panel (Panel #2), respectively.

[0185] The example shown in FIG. 14 illustrates an example of dynamic switching between the single TRP PUSCH and the SDM PUSCH.

[0186] In addition, in Rel. 18 and later, it is being considered to apply / extend the unified TCI status framework to PUSCH transmission using single DCI-based multi-TRP.

[0187] When multiple (e.g., two) SRS resource sets are configured for CB / NCB, the TCI state (joint / UL TCI state) to be applied to the PUSCH scheduled / activated by the DCI may be determined based on a specific field (e.g., an SRS resource set indicator field) included in the DCI.

[0188] In addition, the DCI may be, for example, DCI format 0_1 / 0_2, or may be DCI for at least one of a DL grant (DG) and a type 2 configured grant (CG) that dynamically schedules a PUSH.

[0189] For example, if the code point of the particular field indicates a first value (e.g., "00"), the UE may apply a first indicated (joint / UL) TCI state to multiple (e.g., all) PUSH antenna ports corresponding to the PUSH transmission opportunity.

[0190] For example, if the code point of the particular field indicates a second value (e.g., "01"), the UE may apply the second indicated (joint / UL) TCI state to multiple (e.g., all) PUSH antenna ports corresponding to the PUSH transmission opportunity.

[0191] For example, when the code point of the specific field indicates a third value (e.g., "10") / fourth value (e.g., "11"), in the case of TDM-based PUSCH transmission, a first indicated (joint / UL) TCI state may be applied to a PUSCH transmission opportunity associated with a first SRS resource set, and a second indicated (joint / UL) TCI state may be applied to a PUSCH transmission opportunity associated with a second SRS resource set. These SRS resource sets may be SRS resource sets for CB / NCB.

[0192] On the other hand, when the code point of the specific field indicates a third value (e.g., "10") / fourth value (e.g., "11") and SDM / SFN-based PUSH transmission is used, no progress has been made in studying how to apply the TCI state.

[0193] As mentioned above, from Rel. 18 onwards, it is being considered to apply / extend a unified TCI state framework to each STxMP scheme.

[0194] However, there has been insufficient research into its application method, more specifically, there has been insufficient research into how to indicate the TCI state in STxMP of SDM / SFN-based PUSCH / PUCCH and the association between the indicated TCI state and PUSCH / PUCCH.

[0195] If these considerations are not taken into account, the overlapping UL channels / signals may not be transmitted properly, resulting in degradation of system performance, such as reduced throughput.

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

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

[0198] 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."

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

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

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

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

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

[0204] In the present disclosure, the terms "multi-TRP," "multi-TRP system," "multi-TRP transmission," "multi-PDSCH," "channel using multi-TRP," "channel using multiple TCI states / spatial relationships," "multi-TRP being enabled by RRC / DCI," "multiple TCI states / spatial relationships being 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 interchangeable. In the present disclosure, the terms "multi-TRP based on multiple DCI," and "setting a CORESET pool index (CORESETPoolIndex) value of 1 for the CORESET" may be interchangeable. In the present disclosure, the terms "multi-TRP based on a single DCI," and "at least one code point in the TCI field is mapped to two TCI states" may be interchangeable.

[0205] In the present disclosure, the terms single TRP, single DCI, single PDCCH, multi-TRP based on single DCI, single TRP system, single TRP transmission, single PDSCH, channel using single TRP, channel using one TCI state / spatial relationship, multi-TRP not being enabled by RRC / DCI, multiple TCI states / spatial relationships not being enabled by RRC / DCI, a CORESETPoolIndex value of 1 not being set for any CORESET and no code point in the TCI field being mapped to two TCI states, and two TCI states on at least one TCI code point being activated may be read interchangeably.

[0206] In the present disclosure, a panel, a UE capability value set (e.g., a UE capability value set), a TRP, an SRS resource set, a CORESET pool index, a beam group, a TCI state group, a spatial relationship group, a reference signal group, and a path loss RS group may be interchangeable.

[0207] In the present disclosure, STxMP, simultaneous UL transmission using multiple panels, UL transmission (multiple UL transmissions) in at least the same time resource / domain using multiple panels, UL transmission (multiple UL transmissions) in at least the same time resource / domain using multiple TRP, UL transmission (multiple UL transmissions) in at least the same time resource / domain for multiple TRP, etc. may be read as interchangeable.

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

[0209] In the present disclosure, a PUSCH related to an STxMP subjected to SDM, a PUSCH of an STxMP subjected to SDM, an STxMP PUSCH SDM, a PUSCH SDM, a PUSCH subjected to SDM, an SDM PUSCH, etc. may be read as interchangeable.

[0210] In the present disclosure, PUSCH related to STxMP using SFN, PUSCH of STxMP using SFN, STxMP PUSCH SFN, PUSCH SFN, PUSCH using SFN, SFN PUSCH, etc. may be read as interchangeable.

[0211] In the present disclosure, PUCCH for STxMP using SFN, PUCCH of STxMP using SFN, STxMP PUCCH SFN, PUCCH SFN, PUCCH using SFN, SFN PUCCH, etc. may be read as interchangeable.

[0212] Wireless Communication Method A UE may use multiple panels to transmit one or more UL signals / channels at least in the same time domain (eg, same time resource / symbol / slot / sub-slot).

[0213] The embodiments of the present disclosure may also be applied to STxMP of multi-DCI-based PUSCH+PUSCH as appropriate. The multi-DCI-based PUSCH+PUSCH may be transmitted when the configuration information for multi-DCI-based PUSCH+PUSCH is set to enabled / on and (two) CORESET pool indices are set for the UE.

[0214] First Embodiment The first embodiment relates to TCI conditions that apply to UL signals / channels that utilize SDM.

[0215] The UL signal / channel in the first embodiment may be, for example, a PUSCH.

[0216] The PUSCH in the first embodiment may be, for example, STxMP of the SDM-processed PUSCH. A PUSCH related to the SDM-processed STxMP may be configured for the UE. This configuration may be performed using higher layer signaling (RRC / MAC CE).

[0217] The PUSCH in the first embodiment may be scheduled by a single DCI.

[0218] A UE may be configured with multiple (e.g., two) SRS resource sets for a specific purpose (e.g., codebook (CB) / non-codebook (NCB)). In this embodiment, the SRS resource set may be an SRS resource set for the specific purpose.

[0219] Embodiment 1-1 A UE may schedule / activate / trigger a PUSCH using a specific DCI.

[0220] The particular DCI may be, for example, a DCI that schedules a PUSH (e.g., DCI format 0_1 / 0_2), or may be a DCI for at least one of a DL grant (DG) and a type 2 configured grant (CG) that dynamically schedules a PUSH.

[0221] The UE may transmit PUSCHs corresponding to different layers at least in the same time domain (e.g., time resources / symbols / slots / subslots).

[0222] The UE may determine the instruction (joint / UL) TCI state to apply to the PUSCH / PUSCH antenna port / PUSCH transmission opportunity corresponding to different layers based on a specific field included in the DCI.

[0223] The UE may determine whether the scheduled PUSCH is a single-TRP PUSCH or an SDM STxMP PUSCH based on the specific field. The UE may also determine whether to switch between single-TRP PUSCH transmission and SDM STxMP PUSCH transmission based on the specific field.

[0224] The specific field may be, for example, an SRS resource set indicator field or a new field defined in Rel. 18 or later.

[0225] The specific field may be defined as a specific number of bits (for example, 2 bits).

[0226] The UE may determine whether to switch between single-TRP PUSCH transmission and SDM STxMP PUSCH transmission based on the presence or absence of the specific field with the specific number of bits in the DCI. For example, the UE may make the switch if the specific field with the specific number of bits is present in the DCI. The UE may determine / assume not to make the switch if the specific field with the specific number of bits is not present in the DCI.

[0227] For example, if the code point of the particular field indicates a first value (e.g., "00"), the UE may apply the first indicated (joint / UL) TCI state to multiple (e.g., all) PUSCH antenna ports / layers associated with the first SRS resource set.

[0228] For example, if the code point of the specific field indicates a first value (e.g., "00"), the UE may transmit a PUSH using one TRP (single TRP) associated with a first SRS resource set.

[0229] For example, if the code point of the particular field indicates a second value (e.g., "01"), the UE may apply the second indicated (joint / UL) TCI state to multiple (e.g., all) PUSCH antenna ports / layers associated with the second SRS resource set.

[0230] For example, if the code point of the specific field indicates a second value (e.g., "01"), the UE may transmit a PUSH using one TRP (single TRP) associated with the second SRS resource set.

[0231] For example, if the code point of the particular field indicates a third value (e.g., "10"), the UE may apply a first indicated (joint / UL) TCI state to one or more first PUSCH antenna ports / layers associated with a first SRS resource set, and may apply a second indicated (joint / UL) TCI state to one or more second PUSCH antenna ports / layers associated with a second SRS resource set.

[0232] For example, if the code point of the specific field indicates a third value (e.g., "10"), the UE may transmit a PUSCH related to STxMP that is SDM-based.

[0233] For example, if the code point of the specific field indicates a fourth value (e.g., "11"), the UE may apply the first indicated (joint / UL) TCI state to one or more second PUSCH antenna ports / layers associated with the second SRS resource set, and may apply the second indicated (joint / UL) TCI state to one or more first PUSCH antenna ports / layers associated with the first SRS resource set.

[0234] For example, if the code point of the specific field indicates the fourth value (e.g., "11"), the UE may transmit a PUSCH related to STxMP that is SDM-based.

[0235] In addition, in the present disclosure, when the maximum number of layers for a UE is set to n, the first PUSH antenna port / layer may include the 1st layer, ..., the mth layer (m<n), and the first PUSH antenna port / layer may include the m+1th layer, ..., the nth layer.

[0236] In the present disclosure, the first SRS resource set may be an SRS resource set corresponding to a lower (or higher) SRS resource set ID among SRS resource sets whose usage is CB / NCB, and the second SRS resource set may be an SRS resource set corresponding to a higher (or lower) SRS resource set ID among SRS resource sets whose usage is CB / NCB.

[0237] Regarding the operations related to the code points (first to fourth values) of the specific field, the operations may be applied to all code points, or only to some code points (e.g., first to third values). For example, if only the first to third code points are used / supported, the fourth code point may be reserved or may be used for other purposes.

[0238] For example, if the operation is applied to only some code points, it is necessary to associate the SRS resource set with the indicated TCI state.

[0239] The UE may determine the association between the SRS resource set and the indicated TCI state based on a specific rule (eg, a predefined specification).

[0240] For example, the UE may assume / expect that a first SRS resource set is associated with a first indicated TCI state and a second SRS resource set is associated with a second indicated TCI state.

[0241] The UE may determine the association of the SRS resource set with the indicated TCI state based on higher layer signaling (eg, RRC / MAC CE).

[0242] For example, information indicating either the first or second indicated TCI state may be included in the RRC parameters of the SRS resource set, and the UE may determine the association between the SRS resource set and the indicated TCI state based on the information.

[0243] 15 is a diagram illustrating an example of application of the indication TCI state according to the first embodiment. In the example illustrated in FIG. 15, the UE performs SDM on the first layer (Layer 1) and the second layer (Layer 2) of the PUSCH and transmits them in the same time domain.

[0244] In the example shown in Figure 15, if the code point of a specific field included in the DCI indicates "10", the UE applies a first indicated TCI state to Layer 1 and a second indicated TCI state to Layer 2.

[0245] In the example shown in Figure 15, if the code point of a specific field included in the DCI indicates "11", the UE applies the second indication TCI state to Layer 1 and the 21st indication TCI state to Layer 2.

[0246] According to embodiment 1-1, it is possible to appropriately switch between a single TRP PUSCH and a PUSCH of STxMP subjected to SDM.

[0247] <<Embodiment 1-2>> In embodiment 1-2, association between PUSCH antenna ports / layers and SRS resource sets will be described.

[0248] [Option 1-2-1] The UE may determine the association between the PUSCH antenna port / layer and the SRS resource set based on a rule predefined in the specification.

[0249] For example, the UE may assume / determine that the PUSCH antenna ports of the lower (or higher) n ports / layers are associated with the first SRS resource set and the PUSCH antenna ports of the higher (or lower) m ports / layers are associated with the first SRS resource set.

[0250] The n and m may be the same value or different values.

[0251] For example, the UE may assume that n≦m. Also, for example, the UE may assume that n≧m.

[0252] The number of ports / layers (n and / or m) associated with the first / second SRS resource set may be determined based on a specific field in a DCI, which may be a DCI that schedules / activates / triggers a PUSCH.

[0253] For example, n may be determined based on a first TPMI field (eg, a first TPMI field for a CB) or a first SRI field (eg, a first SRI field for an NCB).

[0254] For example, m may be determined based on a second TPMI field (eg, a second TPMI field for CB) or a second SRI field (eg, a second SRI field for NCB).

[0255] Also, the UE may be notified / instructed which of the PUSCH antenna ports of the lower port / layer and the higher PUSCH antenna ports is associated with the first / second SRS resource set, for example, by using a specific field (e.g., SRS resource set indicator field) in the DCI (e.g., scheduling DCI).

[0256] [Option 1-2-2] The UE may be configured / instructed / notified of the association between the PUSCH antenna port / layer and the SRS resource set based on higher layer signaling (RRC / MAC CE) / DCI.

[0257] For example, an association with a PUSCH antenna port / layer may be configured for each SRS resource set for a specific use (e.g., CB / NCB).

[0258] According to embodiment 1-2, the association of SRS resource sets and PUSCH ports / layers can be appropriately defined.

[0259] <<Embodiment 1-3>> In embodiment 1-3, at least two mappings / associations of an SRS resource set (index of the SRS resource set), a PUSCH port / layer (index of the PUSCH port / layer), and an indication (joint / UL) TCI state (index of the indication (joint / UL) TCI state) are described.

[0260] The UE may determine the mapping / association based on the specific field in the above embodiment 1-1.

[0261] The UE may determine the mapping / association according to the following embodiments 1-3-1 / 1-3-2.

[0262] [Embodiment 1-3-1] The code point of a specific field may indicate a first value (for example, "00") / a second value (for example, "01").

[0263] [[Option 1-3-1-1]] When the code point of a specific field indicates a first value (e.g., "00"), the UE may assume / determine that a first indicated (joint / UL) TCI state, a first SRS resource set, and multiple (e.g., all) layers are associated.

[0264] At this time, the UE may decide to transmit a single TRP PUSCH.

[0265] When the code point of the particular field indicates a second value (e.g., "01"), the UE may assume / determine that a second indicated (joint / UL) TCI state, a second SRS resource set, and multiple (e.g., all) layers are associated.

[0266] At this time, the UE may decide to transmit a single TRP PUSCH.

[0267] 16 is a diagram showing an example of associations between an indication TCI state, an SRS resource set, and layers according to Option 1-3-1-1. In the example shown in FIG. 16, when the code point of the specific field indicates "00", the UE determines that a first indication (joint / UL) TCI state, a first SRS resource set, and all PUSCH layers (layers 1 and 2) are associated. Also, when the code point of the specific field indicates "01", the UE determines that a second indication (joint / UL) TCI state, a second SRS resource set, and all PUSCH layers (layers 1 and 2) are associated.

[0268] [[Option 1-3-1-2]] When the code point of a specific field indicates a first value (e.g., "00"), the UE may assume / determine that the first indicated (joint / UL) TCI state, the second SRS resource set, and multiple (e.g., all) layers are associated.

[0269] At this time, the UE may decide to transmit a single TRP PUSCH.

[0270] When the code point of the particular field indicates a second value (e.g., "01"), the UE may assume / determine that the second indicated (joint / UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated.

[0271] At this time, the UE may decide to transmit a single TRP PUSCH.

[0272] [Embodiment 1-3-2] The code point of a specific field may indicate a third value (for example, "10") / a second value (for example, "11").

[0273] [[Option 1-3-2-1]] When the code point of the specific field indicates a third value (e.g., "10"), the UE may assume / determine that the first indicated (joint / UL) TCI state, the first SRS resource set, and the first layer are associated, and the second indicated (joint / UL) TCI state, the second SRS resource set, and the second layer are associated.

[0274] At this time, the UE may decide to transmit the SDM STxMP PUSCH.

[0275] When the code point of the specific field indicates a fourth value (e.g., "11"), the UE may assume / determine that the first indicated (joint / UL) TCI state, the first SRS resource set, and the second layer are associated, and that the second indicated (joint / UL) TCI state, the second SRS resource set, and the first layer are associated.

[0276] At this time, the UE may decide to transmit the SDM STxMP PUSCH.

[0277] 17 is a diagram showing an example of associations between an indication TCI state, an SRS resource set, and layers according to Option 1-3-2-1. In the example shown in FIG. 17, when the code point of the specific field indicates "01," the UE determines that the first indication (joint / UL) TCI state, the first SRS resource set, and the PUSCH Layer 1 are associated, and the second indication (joint / UL) TCI state, the second SRS resource set, and the PUSCH Layer 2 are associated. Also, when the code point of the specific field indicates "11," the UE determines that the first indication (joint / UL) TCI state, the first SRS resource set, and the PUSCH Layer 2 are associated, and the second indication (joint / UL) TCI state, the second SRS resource set, and the PUSCH Layer 1 are associated.

[0278] [[Option 1-3-2-2]] When the code point of the specific field indicates a third value (e.g., "10"), the UE may assume / determine that the first indicated (joint / UL) TCI state, the first SRS resource set, and the first layer are associated, and the second indicated (joint / UL) TCI state, the second SRS resource set, and the second layer are associated.

[0279] At this time, the UE may decide to transmit the SDM STxMP PUSCH.

[0280] When the code point of the specific field indicates a fourth value (e.g., "11"), the UE may assume / determine that the first indicated (joint / UL) TCI state, the second SRS resource set, and the first layer are associated, and that the second indicated (joint / UL) TCI state, the first SRS resource set, and the second layer are associated.

[0281] At this time, the UE may decide to transmit the SDM STxMP PUSCH.

[0282] [[Option 1-3-2-3]] When the code point of the specific field indicates a third value (e.g., "10"), the UE may assume / determine that the first indicated (joint / UL) TCI state, the first SRS resource set, and the first layer are associated, and the second indicated (joint / UL) TCI state, the second SRS resource set, and the second layer are associated.

[0283] At this time, the UE may decide to transmit the SDM STxMP PUSCH.

[0284] When the code point of the specific field indicates a fourth value (e.g., “11”), the UE may assume / determine that the first indicated (joint / UL) TCI state, the second SRS resource set, and the second layer are associated, and that the second indicated (joint / UL) TCI state, the first SRS resource set, and the first layer are associated.

[0285] At this time, the UE may decide to transmit the SDM STxMP PUSCH.

[0286] In addition, in at least one option of embodiment 1-3-2, the fourth value (for example, "11") may be reserved (may not be used).

[0287] According to embodiments 1 to 3, the association between the SRS resource set, the port / layer of the PUSCH, and the indication TCI state can be appropriately defined.

[0288] According to the first embodiment, it is possible to appropriately transmit the STxMP PUSCH subjected to SDM.

[0289] Second Embodiment The second embodiment relates to the indication of TCI status that applies to UL signals / channels (UL transmissions) that utilize a single frequency network (SFN).

[0290] The UL signal / channel in the second embodiment may be, for example, a PUSCH.

[0291] In this disclosure, UL transmission using SFN may mean that the UE transmits the same UL signal / channel on the same resources (resource elements) in each panel using different indications (joint / UL TCI states), and may also mean that multiple (e.g., all) DMRS ports / antenna ports for the UL transmission are in a QCL relationship with multiple (e.g., two) TCI states (indicated TCI states).

[0292] The PUSCH in the second embodiment may be, for example, STxMP of the PUSCH using the SFN. A PUSCH related to STxMP using the SFN may be configured for the UE. This configuration may be performed using higher layer signaling (RRC / MAC CE).

[0293] The PUSCH in the second embodiment may be scheduled by a single DCI.

[0294] A UE may be configured with multiple (e.g., two) SRS resource sets for a specific purpose (e.g., codebook (CB) / non-codebook (NCB)). In this embodiment, the SRS resource set may be an SRS resource set for the specific purpose.

[0295] Embodiment 2-1 A UE may schedule / activate / trigger a PUSCH using a specific DCI.

[0296] The particular DCI may be, for example, a DCI that schedules a PUSH (e.g., DCI format 0_1 / 0_2), or may be a DCI for at least one of a DL grant (DG) and a type 2 configured grant (CG) that dynamically schedules a PUSH.

[0297] For the same PUSCH, the UE may transmit each PUSCH with a different indication TCI state at least in the same time domain (eg, time resource / symbol / slot / subslot).

[0298] The UE may determine the instruction (joint / UL) TCI state to apply to the PUSCH / PUSCH antenna port / PUSCH transmission opportunity based on a specific field included in the DCI.

[0299] The UE may determine whether to switch between single TRP PUSCH transmission and SFN STxMP PUSCH transmission based on the specific field.

[0300] The specific field may be, for example, an SRS resource set indicator field or a new field defined in Rel. 18 or later.

[0301] The specific field may be defined as a specific number of bits (for example, 2 bits).

[0302] The UE may determine whether to switch between single-TRP PUSCH transmission and SFN STxMP PUSCH transmission based on the presence or absence of the specific field with the specific number of bits in the DCI. For example, the UE may make the switch if the specific field with the specific number of bits is present in the DCI. The UE may determine / assume not to make the switch if the specific field with the specific number of bits is not present in the DCI.

[0303] For example, if the code point of the particular field indicates a first value (e.g., "00"), the UE may apply the first indicated (joint / UL) TCI state to multiple (e.g., all) PUSCH antenna ports / layers associated with the first SRS resource set.

[0304] For example, if the code point of the specific field indicates a first value (e.g., "00"), the UE may transmit a PUSH using one TRP (single TRP) associated with a first SRS resource set.

[0305] For example, if the code point of the particular field indicates a second value (e.g., "01"), the UE may apply the second indicated (joint / UL) TCI state to multiple (e.g., all) PUSCH antenna ports / layers associated with the second SRS resource set.

[0306] For example, if the code point of the specific field indicates a second value (e.g., "01"), the UE may transmit a PUSH using one TRP (single TRP) associated with the second SRS resource set.

[0307] For example, if the code point of the specific field indicates a third value (e.g., "10"), the UE may apply a first indicated (joint / UL) TCI state to one or more (e.g., all) PUSCH antenna ports / layers associated with a first SRS resource set, and may apply a second indicated (joint / UL) TCI state to one or more (e.g., all) PUSCH antenna ports / layers associated with a second SRS resource set.

[0308] For example, if the code point of the specific field indicates a third value (e.g., "10"), the UE may transmit a PUSCH related to STxMP using the SFN.

[0309] For example, if the code point of the specific field indicates a fourth value (e.g., "11"), the UE may apply the first indicated (joint / UL) TCI state to one or more (e.g., all) PUSCH antenna ports / layers associated with the second SRS resource set, and may apply the second indicated (joint / UL) TCI state to one or more (e.g., all) PUSCH antenna ports / layers associated with the first SRS resource set.

[0310] For example, if the code point of the specific field indicates the fourth value (e.g., "11"), the UE may transmit a PUSCH related to STxMP using the SFN.

[0311] Regarding the operations related to the code points (first to fourth values) of the specific field, the operations may be applied to all code points, or only to some code points (e.g., first to third values). For example, if only the first to third code points are used / supported, the fourth code point may be reserved or may be used for other purposes.

[0312] For example, if the operation is applied to only some code points, it is necessary to associate the SRS resource set with the indicated TCI state.

[0313] The UE may determine the association between the SRS resource set and the indicated TCI state based on a specific rule (eg, a predefined specification).

[0314] For example, the UE may assume / expect that a first SRS resource set is associated with a first indicated TCI state and a second SRS resource set is associated with a second indicated TCI state.

[0315] The UE may determine the association of the SRS resource set with the indicated TCI state based on higher layer signaling (eg, RRC / MAC CE).

[0316] For example, information indicating either the first or second indicated TCI state may be included in the RRC parameters of the SRS resource set, and the UE may determine the association between the SRS resource set and the indicated TCI state based on the information.

[0317] Fig. 18 is a diagram illustrating an example of application of the indication TCI state according to the second embodiment. In the example illustrated in Fig. 18, the UE transmits Layers 1 and 2 of the PUSCH in the same time domain using the SFN.

[0318] In the example shown in Figure 18, when the code point of a specific field included in the DCI indicates "10" /

[11] , the UE applies the first indicated TCI state and the second indicated TCI state to all layers (layers 1 and 2) and performs PUSH transmission using the SFN.

[0319] According to embodiment 2-1, it is possible to appropriately switch between a single TRP PUSCH and an STxMP PUSCH using an SFN.

[0320] <<Embodiment 2-2>> In embodiment 2-2, at least two mappings / associations of an SRS resource set (index of the SRS resource set), a PUSCH port / layer (index of the PUSCH port / layer), and an indication (joint / UL) TCI state (index of the indication (joint / UL) TCI state) are described.

[0321] The UE may determine the mapping / association based on the specific field in the above embodiment 2-1.

[0322] The UE may determine the mapping / association according to the following embodiments 2-2-1 / 2-2-2.

[0323] [Embodiment 2-2-1] The code point of a specific field may indicate a first value (for example, "00") / a second value (for example, "01").

[0324] [[Option 2-2-1-1]] When the code point of a specific field indicates a first value (e.g., "00"), the UE may assume / determine that a first indicated (joint / UL) TCI state, a first SRS resource set, and multiple (e.g., all) layers are associated.

[0325] At this time, the UE may decide to transmit a single TRP PUSCH.

[0326] When the code point of the particular field indicates a second value (e.g., "01"), the UE may assume / determine that a second indicated (joint / UL) TCI state, a second SRS resource set, and multiple (e.g., all) layers are associated.

[0327] At this time, the UE may decide to transmit a single TRP PUSCH.

[0328] 19 is a diagram showing an example of associations between an indication TCI state, an SRS resource set, and layers according to Option 2-2-1-1. In the example shown in FIG. 19, when the code point of the specific field indicates "00", the UE determines that the first indication (joint / UL) TCI state, the first SRS resource set, and all PUSCH layers (layers 1 and 2) are associated. Also, when the code point of the specific field indicates "01", the UE determines that the second indication (joint / UL) TCI state, the second SRS resource set, and all PUSCH layers (layers 1 and 2) are associated.

[0329] [[Option 2-2-1-2]] When the code point of a specific field indicates a first value (e.g., "00"), the UE may assume / determine that the first indicated (joint / UL) TCI state, the second SRS resource set, and multiple (e.g., all) layers are associated.

[0330] At this time, the UE may decide to transmit a single TRP PUSCH.

[0331] When the code point of the particular field indicates a second value (e.g., "01"), the UE may assume / determine that the second indicated (joint / UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated.

[0332] At this time, the UE may decide to transmit a single TRP PUSCH.

[0333] [Embodiment 2-2-2] The code point of a specific field may indicate a third value (for example, "10") / a second value (for example, "11").

[0334] When the code point of the specific field indicates a third value (e.g., "10"), the UE may assume / determine that the first indicated (joint / UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated, and that the second indicated (joint / UL) TCI state, the second SRS resource set, and multiple (e.g., all) layers are associated.

[0335] At this time, the UE may determine to transmit a PUSCH of STxMP using SFN.

[0336] When the code point of the specific field indicates a fourth value (e.g., “11”), the UE may assume / determine that the first indicated (joint / UL) TCI state, the second SRS resource set, and multiple (e.g., all) layers are associated, and that the second indicated (joint / UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated.

[0337] At this time, the UE may decide to transmit the SDM STxMP PUSCH.

[0338] 20 is a diagram showing an example of associations between an indication TCI state, an SRS resource set, and layers according to embodiment 2-2-2. In the example shown in FIG. 20, when the code point of the specific field indicates "01", the UE determines that the first indication (joint / UL) TCI state, the first SRS resource set, and all layers are associated, and the second indication (joint / UL) TCI state, the second SRS resource set, and all layers are associated. Also, when the code point of the specific field indicates "11", the UE determines that the first indication (joint / UL) TCI state, the second SRS resource set, and all layers are associated, and the second indication (joint / UL) TCI state, the first SRS resource set, and all layers are associated.

[0339] In addition, in at least one option of embodiment 2-2-2, the fourth value (for example, "11") may be reserved (may not be used).

[0340] According to embodiment 2-2, the association between the SRS resource set, the port / layer of the PUSCH, and the indication TCI state can be appropriately defined.

[0341] According to the second embodiment described above, it is possible to appropriately transmit the PUSCH of STxMP using SFN.

[0342] Third Embodiment The third embodiment relates to indication of TCI status applied to UL signals / channels (UL transmissions) that utilize a single frequency network (SFN).

[0343] The UL signal / channel in the third embodiment may be, for example, the PUCCH.

[0344] The PUCCH in the third embodiment may be, for example, STxMP of PUCCH using SFN. A PUCCH related to STxMP using SFN may be configured for a UE. This configuration may be performed using higher layer signaling (RRC / MAC CE).

[0345] The PUCCH in the third embodiment may be scheduled / triggered by a single DCI. The PUCCH in the third embodiment may be a PUCCH corresponding to a single DCI.

[0346] <<Embodiment 3-1>> A UE may determine the instruction (joint / UL) TCI state to apply to a PUCCH based on higher layer signaling (RRC / MAC CE) / DCI.

[0347] The UE may determine whether the configured / instructed PUCCH is a PUCCH that uses an SFN based on higher layer signaling (RRC / MAC CE) / DCI.

[0348] In other words, the UE may determine switching between the PUCCH of STxMP using SFN and another PUCCH (e.g., single-TRP PUCCH) based on higher layer signaling (RRC / MAC CE) / DCI.

[0349] One or more (e.g., two) joint / UL TCI states may be indicated (associated) with one PUCCH resource. For example, one PUCCH resource may be indicated (associated) with either a first joint / UL TCI state, a second joint / UL TCI state, or both using RRC signaling.

[0350] The UE may then determine the PUCCH resource using a specific field (eg, a PUCCH Resource Indicator (PRI) field) included in the DCI that schedules / activates / triggers the PUCCH.

[0351] In this case, if multiple (e.g., two) joint / UL TCI states are indicated (associated) with the PUCCH resources used by the UE for UCI transmission, the UE may decide to perform SFN PUCCH transmission or PUCCH TDM repetition (defined in Rel. 17).

[0352] Also, if one joint / UL TCI state is indicated (associated) with the PUCCH resource used by the UE for UCI transmission, the UE may determine to transmit for a single TRP PUCCH.

[0353] In this case, the UE may decide between single TRP PUCCH and single DCI-based PUCCH TDM based on the configured / instructed number of PUCCH repetitions.

[0354] If (dynamic) switching between SFN PUCCH transmission and PUCCH TDM repetition (as specified in Rel. 17) is supported, a decision needs to be made as to which of these to use.

[0355] For example, the UE may determine whether to perform SFN PUCCH transmission or Rel. 17 PUCCH TDM repetition for each PUCCH resource based on higher layer signaling (RRC / MAC CE).

[0356] For example, either SFN PUCCH transmission or repetition of PUCCH TDM (defined in Rel. 17) may be configured for each PUCCH resource (PUCCH resource configuration). A specific field (e.g., a PRI field) may be used to switch PUCCH resources.

[0357] Furthermore, for example, the UE may determine whether to perform SFN PUCCH transmission or PUCCH TDM repetition transmission (defined in Rel. 17) based on the number of repetitions indicated for the PUCCH resource. A specific field (e.g., a PRI field) may be used for switching the PUCCH resource.

[0358] For example, if no repetition is indicated, the UE may determine to perform SFN PUCCH transmission. If a repetition number greater than 1 is indicated, the UE may determine to perform PUCCH TDM repetition.

[0359] According to this, when a network / base station cannot secure resources for scheduling PUCCH repetition of multiple slots / subslots, it can use SFN PUCCH, making it possible to schedule according to the resource situation.

[0360] In the present disclosure, the number of repetitions of PUCCH may be set for each PUCCH resource, or may be set commonly for multiple (e.g., all) PUCCH resources in a CC / BWP.

[0361] Furthermore, for example, the UE may determine whether to perform SFN PUCCH transmission or PUCCH TDM repetition transmission (defined in Rel. 17) based on a specific field included in DCI (scheduling / triggering DCI). For the specific field, a new field defined in Rel. 18 or later may be used, or an existing field (defined up to Rel. 17) may be reused.

[0362] Also, for example, when a repetition number greater than 1 is instructed / configured to a UE and an SFN PUCCH is configured, the UE may ignore the instruction / configuration of the repetition number and determine / consider the repetition number to be 1.

[0363] Also, for example, the UE may not assume that an SFN PUCCH is configured and a repetition number greater than one is configured / indicated.

[0364] Also, for example, when a repetition number greater than 1 is configured / instructed and an SFN PUCCH is configured, the UE may perform repeated transmission of the SFN PUCCH based on the repetition number.

[0365] SFN PUCCH transmission and (dynamic) switching between PUCCH TDM repetition (as specified in Rel. 17) may not be supported.

[0366] In this case, the UE may be configured with either SFN PUCCH transmission or PUCCH TDM repetition (as specified in Rel. 17).

[0367] This setting may be performed for each BWP / CC.

[0368] If this configuration is not performed, the UE may decide to perform either single TRP PUCCH or single DCI-based PUCCH TDM, and in this case, the UE may not assume / expect to be instructed on multiple (e.g., two) joint / UL TCI states per PUCCH (resource).

[0369] If the configuration is not performed, the UE may determine to perform either single-TRP PUCCH or single-DCI-based PUCCH TDM. If multiple (e.g., two) joint / UL TCI states are indicated to the UE, the UE may select a specific indicated TCI state (e.g., the first (or second) indicated (joint / UL) TCI state).

[0370] According to embodiment 3-1, it is possible to appropriately switch between STxMP PUCCH using SFN and other PUCCH transmission.

[0371] <<Embodiment 3-2>> The UE may support PUCCH cell switching.

[0372] The PUCCH configuration (for example, any one of SFN PUCCH, (Rel. 17) PUCCH TDM repetition, single DCI-based PUCCH TDM repetition, and single TRP PUCCH configuration) may be configured for each cell / CC / BWP / cell group.

[0373] If the PUCCH configuration differs for each cell / CC / BWP / cell group, when a PUCCH cell switch is performed, the UE needs to determine which cell / CC / BWP / cell group configuration to follow.

[0374] [Option 3-2-1] The UE may transmit the PUCCH according to the configuration of the cell / CC / BWP / cell group in which the PDSCH is transmitted.

[0375] Fig. 21 is a diagram illustrating an example of transmission of a PUCCH according to embodiment 3-2. In the example illustrated in Fig. 21, a DL CC (cell), a PCell, and a PUCCH SCell #1 are configured, and DCI and PDSCH are received in the DL CC (cell).

[0376] In the example shown in Figure 21, the DCI includes a field indicating the timing of HARQ-ACK feedback and a PUCCH cell indicator field, where the field indicating the timing of HARQ-ACK feedback indicates K1 = 2 and the PUCCH cell indicator field indicates PUCCH SCell #1 as the target cell.

[0377] At this time, the UE determines that the slot (slot #3) in PUCCH SCell #1 two slots after the slot in which the PDSCH was received is the slot in which to transmit HARQ-ACK for the PDSCH. The UE switches the slot in which to transmit the PUCCH from the PCell to PUCCH SCell #1.

[0378] In option 3-2-1, the UE transmits PUCCH in PUCCH SCell#1 according to the configuration in the cell in which the PDSCH is transmitted (i.e., the DL CC).

[0379] [Option 3-2-2] The UE may transmit the PUCCH according to the configuration of the cell / CC / BWP / cell group (triggering cell / CC / BWP / cell group) in which the DCI is transmitted.

[0380] In the example shown in FIG. 21, in option 3-2-2, the UE transmits PUCCH in PUCCH SCell#1 according to the configuration in the cell (i.e., DL CC) in which DCI is transmitted.

[0381] [Option 3-2-3] The UE may transmit the PUCCH according to the configuration in the cell / CC / BWP / cell group in which the PUCCH is triggered (triggered cell / CC / BWP / cell group).

[0382] In the example shown in FIG. 21, in option 3-2-3, the UE transmits PUCCH in PUCCH SCell #1 according to the configuration in the cell where PUCCH is triggered (i.e., PCell).

[0383] [Option 3-2-4] The UE may transmit the PUCCH according to the configuration of the cell / CC / BWP / cell group in which the PUCCH is (actually) transmitted.

[0384] In the example shown in FIG. 21, in option 3-2-4, the UE transmits PUCCH in PUCCH SCell #1 according to the configuration in the cell in which the PUCCH is transmitted (i.e., PUCCH SCell).

[0385] Note that, although the above options have been described using PUCCH cell switching scheme 1 as an example, they can also be applied to PUCCH cell switching scheme 2 as appropriate.

[0386] According to embodiment 3-2, even when PUCCH cell switching is performed, PUCCH transmission can be performed appropriately.

[0387] According to the third embodiment, it is possible to appropriately perform operations related to the PUCCH of STxMP using SFN.

[0388] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified 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) 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.

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

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

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

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

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

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

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

[0396] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0397] At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0398] The specific UE capability may indicate at least one of the following: Supporting specific processing / operation / control / information for at least one of the above embodiments (e.g. STxMP for PUSCH / PUCCH); Supporting STxMP PUSCH SDM; Supporting STxMP PUSCH SFN; Supporting STxMP PUCCH SFN; Supporting PUCCH cell switching; Supporting number of panels available for simultaneous transmission.

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

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

[0401] Furthermore, at least one of the above-described embodiments may be applied when a UE configures / activates / triggers specific information related to the above-described embodiment (or performs the operations of the above-described embodiment) through higher layer signaling / physical layer signaling. For example, the specific information may be information indicating that STxMP PUSCH SDM / STxMP PUSCH SFN / STxMP PUCCH SFN are enabled, any RRC parameters for a specific release (e.g., Rel. 18 / 19), etc.

[0402] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, Rel. 15 / 16 behavior.

[0403] (Supplementary Note A) The following invention is added to one embodiment of the present disclosure. [Supplementary Note A-1] A terminal having: a receiver that receives downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH); and a controller that determines, based on a specific field included in the DCI, whether the PUSCH is one of a plurality of PUSCHs that are spatially division multiplexed and transmitted in at least the same time domain, or a PUSCH intended for a single transmission / reception point. [Supplementary Note A-2] The terminal according to Supplementary Note A-1, wherein the controller determines that the PUSCH is a PUSCH intended for a transmission / reception point corresponding to a first sounding reference signal (SRS) resource set when a code point in the specific field indicates a first value, and that the PUSCH is a PUSCH intended for a transmission / reception point corresponding to a second SRS resource set when the code point in the specific field indicates a second value. [Supplementary Note A-3] The terminal according to Supplementary Note A-1 or Supplementary Note A-2, wherein the control unit determines that the PUSCH is a PUSCH transmitted in at least the same time domain as the spatial division multiplexed PUSCH when the code point of the specific field indicates a third value or a fourth value. [Supplementary Note A-4] The terminal according to any of Supplementary Note A-1 to Supplementary Note A-3, wherein the control unit determines the number of layers associated with a first sounding reference signal (SRS) resource set based on a first Transmitted Precoding Matrix Indicator (TPMI) field or a first SRS Resource Indicator (SRI) field, and determines the number of layers associated with a second SRS resource set based on a second TPMI field or a second SRI field.

[0404] (Supplementary Note B) The following invention is added to one embodiment of the present disclosure. [Supplementary Note B-1] A terminal having: a receiver that receives downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH); and a controller that determines, based on a specific field included in the DCI, whether the PUSCH is one of a plurality of PUSCHs transmitted in at least the same time domain using a single frequency network (SFN) or a PUSCH intended for a single transmission / reception point. [Supplementary Note B-2] The terminal according to Supplementary Note B-1, wherein the controller determines that the PUSCH is a PUSCH intended for a transmission / reception point corresponding to a first sounding reference signal (SRS) resource set when a code point in the specific field indicates a first value, and that the PUSCH is a PUSCH intended for a transmission / reception point corresponding to a second SRS resource set when the code point in the specific field indicates a second value. [Supplementary Note B-3] The terminal according to Supplementary Note B-1 or Supplementary Note B-2, wherein the control unit determines that the PUSCHs are multiple PUSCHs transmitted in at least the same time domain using the SFN when the code point of the specific field indicates a third value. [Supplementary Note B-4] The terminal according to any of Supplementary Note B-1 to Supplementary Note B-3, wherein the control unit assumes that a fourth value is not used for the code point of the specific field.

[0405] (Supplementary Note C) The following inventions are added to one embodiment of the present disclosure: [Supplementary Note C-1] A terminal including: a receiving unit that receives a configuration of physical uplink control channel (PUCCH) resources associated with one or more joint or uplink (UL) Transmission Configuration Indication (TCI) states and receives downlink control information (DCI) including a PUCCH resource indicator (PRI) field; and a control unit that determines, based on the number of joint or UL TCI states associated with a PUCCH resource indicated using the PRI field, whether the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using a single frequency network (SFN). [Supplementary Note C-2] The terminal according to Supplementary Note C-1, wherein the control unit determines that the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using the SFN when a number of joint or UL TCI states associated with the indicated PUCCH resource is plural. [Supplementary Note C-3] The terminal according to Supplementary Note C-1 or Supplementary Note C-2, wherein the receiving unit further receives configuration related to time division multiplexed PUCCH repetition or PUCCH using an SFN by using higher layer signaling, and the control unit further determines, when a number of joint or UL TCI states associated with the indicated PUCCH resource is plural, whether the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using the SFN or the time division multiplexed PUCCH repetition based on the configuration.[Supplementary Note C-4] The terminal according to any one of Supplementary Note C-1 to Supplementary Note C-3, wherein the receiving unit further receives information regarding the number of PUCCH repetitions, and the control unit further determines, when a number of joint or UL TCI states associated with the indicated PUCCH resource is plural, whether the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using the SFN, or whether the time-division multiplexed PUCCH repetition is the PUCCH.

[0406] (Supplementary Note D) The following inventions are added to one embodiment of the present disclosure: [Supplementary Note D-1] A terminal, comprising: a receiver that receives a configuration related to a physical uplink control channel (PUCCH) for each cell and receives downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH); and a controller that determines a PUCCH for transmitting a hybrid automatic repeat request acknowledgment (HARQ-ACK) corresponding to the PDSCH based on the PUCCH configuration of a specific cell, wherein the PUCCH configuration for each cell is any one of a plurality of PUCCHs transmitted in at least the same time domain using a single frequency network (SFN), time-division multiplexed PUCCH repetition, time-division multiplexed PUCCH repetition based on a single DCI, and a PUCCH for a single transmission / reception point. [Supplementary Note D-2] The terminal according to Supplementary Note D-1, wherein the control unit determines a PUCCH for transmitting the HARQ-ACK based on a PUCCH-related setting in a cell that receives the PDSCH. [Supplementary Note D-3] The terminal according to Supplementary Note D-1 or Supplementary Note D-2, wherein the control unit determines a PUCCH for transmitting the HARQ-ACK based on a PUCCH-related setting in a cell that receives the DCI. [Supplementary Note D-4] The terminal according to any of Supplementary Note D-1 to Supplementary Note D-3, wherein the control unit determines a PUCCH for transmitting the HARQ-ACK based on a PUCCH-related setting in a cell that transmits the HARQ-ACK.

[0407] (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.

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

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

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

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

[0412] 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 locations and numbers of the cells and user terminals 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 base station 10.

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

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

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

[0416] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0434] 23 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0451] The transceiver 120 may transmit downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH). The controller 110 may use a specific field included in the DCI to indicate whether the PUSCH is a PUSCH for a single transmission / reception point or a PUSCH for a plurality of spatially multiplexed PUSCHs transmitted in at least the same time domain (first embodiment).

[0452] The transceiver 120 may transmit downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH). The controller 110 may use a specific field included in the DCI to indicate whether the PUSCH is one of multiple PUSCHs transmitted in at least the same time domain using a single frequency network (SFN) or a PUSCH intended for a single transmission / reception point (second embodiment).

[0453] The transceiver 120 may transmit a configuration of physical uplink control channel (PUCCH) resources associated with one or more joint or uplink (UL) Transmission Configuration Indication (TCI) states, and may transmit downlink control information (DCI) including a PUCCH resource indicator (PRI) field. The controller 110 may indicate, based on the number of joint or UL TCI states associated with the PUCCH resource indicated using the PRI field, whether the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using a single frequency network (SFN) (third embodiment).

[0454] The transceiver 120 may transmit a configuration related to a physical uplink control channel (PUCCH) for each cell and may transmit downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH). The control unit 110 may use the PUCCH configuration for a specific cell to instruct a PUCCH for transmitting a hybrid automatic repeat request acknowledgment (HARQ-ACK) corresponding to the PDSCH. The PUCCH configuration for each cell may be any of the following configurations: multiple PUCCHs transmitted in at least the same time domain using a single frequency network (SFN), time-division multiplexed PUCCH repetition, time-division multiplexed PUCCH repetition based on a single DCI, and a PUCCH for a single transmission / reception point (third embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0473] The transceiver 220 may receive downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH). The controller 210 may determine, based on a specific field included in the DCI, whether the PUSCH is a PUSCH for a single transmission / reception point or a PUSCH for a plurality of spatially multiplexed PUSCHs transmitted in at least the same time domain (first embodiment).

[0474] The control unit 210 may determine that, when the code point of the specific field indicates a first value, the PUSH is a PUSH for a transmission / reception point corresponding to a first sounding reference signal (SRS) resource set, and, when the code point of the specific field indicates a second value, the PUSH is a PUSH for a transmission / reception point corresponding to a second SRS resource set (first embodiment).

[0475] If the code point of the specific field indicates a third value or a fourth value, the control unit 210 may determine that the PUSH is a PUSH transmitted in at least the same time domain as the spatial division multiplexed PUSH (first embodiment).

[0476] The control unit 210 may determine the number of layers associated with a first sounding reference signal (SRS) resource set based on a first Transmitted Precoding Matrix Indicator (TPMI) field or a first SRS Resource Indicator (SRI) field, and may determine the number of layers associated with a second SRS resource set based on a second TPMI field or a second SRI field (first embodiment).

[0477] The transceiver 220 may receive downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH). The controller 210 may determine, based on a specific field included in the DCI, whether the PUSCH is one of multiple PUSCHs transmitted in at least the same time domain using a single frequency network (SFN) or a PUSCH intended for a single transmission / reception point (second embodiment).

[0478] The control unit 210 may determine that, when the code point of the specific field indicates a first value, the PUSH is a PUSH for a transmission / reception point corresponding to a first sounding reference signal (SRS) resource set, and, when the code point of the specific field indicates a second value, the PUSH is a PUSH for a transmission / reception point corresponding to a second SRS resource set (second embodiment).

[0479] If the code point of the specific field indicates a third value, the control unit 210 may determine that the PUSH is a plurality of PUSHs transmitted in at least the same time domain using the SFN (second embodiment).

[0480] The control unit 210 may assume that the fourth value is not used for the code point of the specific field (second embodiment).

[0481] The transceiver 220 may receive a configuration of physical uplink control channel (PUCCH) resources associated with one or more joint or uplink (UL) Transmission Configuration Indication (TCI) states, and may receive downlink control information (DCI) including a PUCCH resource indicator (PRI) field. The controller 220 may determine, based on the number of joint or UL TCI states associated with the PUCCH resource indicated using the PRI field, whether the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using a single frequency network (SFN) (third embodiment).

[0482] When the number of joint or UL TCI states associated with the indicated PUCCH resource is plural, the control unit 210 may determine that the PUCCH of the indicated PUCCH resource is plural PUCCHs transmitted in at least the same time domain using the SFN (third embodiment).

[0483] The transceiver 220 may further receive configuration regarding time-division multiplexed PUCCH repetitions or PUCCHs using SFNs using higher layer signaling. When the number of joint or UL TCI states associated with the indicated PUCCH resource is plural, the control unit 210 may further determine, based on the configuration, whether the PUCCH of the indicated PUCCH resource is multiple PUCCHs transmitted in at least the same time domain using the SFN or the time-division multiplexed PUCCH repetitions (third embodiment).

[0484] The transceiver 220 may further receive information regarding the number of PUCCH repetitions. When the number of joint or UL TCI states associated with the indicated PUCCH resource is plural, the control unit 210 may further determine, based on the information, whether the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using the SFN or the time-division multiplexed PUCCH repetitions (third embodiment).

[0485] The transceiver 220 may receive a configuration for a physical uplink control channel (PUCCH) for each cell and may receive downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH). The control unit 210 may determine a PUCCH for transmitting a hybrid automatic repeat request acknowledgment (HARQ-ACK) corresponding to the PDSCH based on the configuration for the PUCCH of a specific cell. The configuration for the PUCCH for each cell may be any of a configuration of multiple PUCCHs transmitted in at least the same time domain using a single frequency network (SFN), time-division multiplexed PUCCH repetition, time-division multiplexed PUCCH repetition based on a single DCI, and a PUCCH for a single transmission / reception point (third embodiment).

[0486] The control unit 210 may determine the PUCCH for transmitting the HARQ-ACK based on the configuration related to the PUCCH in the cell that receives the PDSCH (third embodiment).

[0487] The control unit 210 may determine the PUCCH for transmitting the HARQ-ACK based on the configuration related to the PUCCH in the cell that receives the DCI (third embodiment).

[0488] The control unit 210 may determine the PUCCH for transmitting the HARQ-ACK based on the configuration related to the PUCCH in the cell that transmits the HARQ-ACK (third embodiment).

[0489] (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.

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

[0491] 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. Figure 25 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.

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

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

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

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

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

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

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

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

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

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

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

[0503] (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0521] 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."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0551] 26 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0568] 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."

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

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

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

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

[0573] 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...."

[0574] 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 ...." "does not expect ..." may be interchangeably read as "be not expected ...." 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" (e.g., if apparatus A is a UE, apparatus B may be a base station).

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

[0576] 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."

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

[0578] 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."

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

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

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

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

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

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

[0585] 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 receiver for receiving Physical Uplink Control Channel (PUCCH) resource configurations associated with one or more joint or uplink (UL) Transmission Configuration Indication (TCI) states, information regarding the number of PUCCH repetitions, and Downlink Control Information (DCI) including a PUCCH Resource Indicator (PRI) field; a control unit configured to determine, when a number of joint or UL TCI states associated with a PUCCH resource indicated using the PRI field is plural, whether a PUCCH of the indicated PUCCH resource corresponds to simultaneous UL transmission using multiple panels of PUCCH using a Single Frequency Network (SFN) or corresponds to time-division multiplexed PUCCH repetition based on information about the repetition number; The control unit determines whether the plurality of joint or UL TCI states or the one joint or UL TCI state is associated with the indicated PUCCH resource based on a Radio Resource Control (RRC) parameter.

2. The terminal according to claim 1, wherein the control unit determines, for each setting of the PUCCH resource, whether simultaneous UL transmission using multiple panels of the PUCCH using the SFN is set or whether the time-division multiplexed PUCCH repetition is set.

3. 2. The terminal according to claim 1, wherein the control unit determines to perform the time-division multiplexed PUCCH repetition when the information regarding the number of repetitions indicates a repetition number greater than 1, and determines to perform simultaneous UL transmission using multiple panels of PUCCH using the SFN when the information regarding the number of repetitions indicates a repetition number of 1.

4. Receiving downlink control information (DCI) including a configuration of physical uplink control channel (PUCCH) resources to which one or more joint or uplink (UL) Transmission Configuration Indication (TCI) states are associated, information regarding the number of PUCCH repetitions, and a PUCCH resource indicator (PRI) field; If the number of joint or UL TCI states associated with the PUCCH resource indicated using the PRI field is plural, determining based on information about the repetition number whether the PUCCH of the indicated PUCCH resource corresponds to simultaneous UL transmission using multiple panels of PUCCH using a Single Frequency Network (SFN) or corresponds to time-division multiplexed PUCCH repetition; determining, based on a Radio Resource Control (RRC) parameter, whether the plurality of joint or UL TCI states or the one joint or UL TCI state is associated with the indicated PUCCH resource.

5. A transmitter configured to transmit Physical Uplink Control Channel (PUCCH) resource configurations associated with one or more joint or uplink (UL) Transmission Configuration Indication (TCI) states, information regarding the number of PUCCH repetitions, and Downlink Control Information (DCI) including a PUCCH Resource Indicator (PRI) field; a control unit for indicating, when a number of joint or UL TCI states associated with a PUCCH resource indicated using the PRI field is plural, whether the PUCCH of the indicated PUCCH resource corresponds to simultaneous UL transmission using multiple panels of PUCCH using a Single Frequency Network (SFN) or corresponds to time-division multiplexed PUCCH repetition, according to information on the repetition number; The base station, wherein the control unit indicates, by a Radio Resource Control (RRC) parameter, whether the plurality of joint or UL TCI states or the one joint or UL TCI state is associated with the indicated PUCCH resource.

6. A system having a terminal and a base station, The terminal includes a receiving unit configured to receive downlink control information (DCI) including a configuration of a physical uplink control channel (PUCCH) resource associated with one or more joint or uplink (UL) Transmission Configuration Indication (TCI) states, information on a PUCCH repetition number, and a PUCCH resource indicator (PRI) field; a control unit configured to determine, when a number of joint or UL TCI states associated with a PUCCH resource indicated using the PRI field is plural, whether a PUCCH of the indicated PUCCH resource corresponds to simultaneous UL transmission using multiple panels of PUCCH using a Single Frequency Network (SFN) or corresponds to time-division multiplexed PUCCH repetition based on information about the repetition number; The controller determines whether the plurality of joint or UL TCI states or the one joint or UL TCI state is associated with the indicated PUCCH resource based on a Radio Resource Control (RRC) parameter; The base station includes a transmitter that transmits the PUCCH resource configuration, information related to the number of repetitions, and the DCI; a control unit for indicating, when a number of joint or UL TCI states associated with a PUCCH resource indicated using the PRI field is plural, whether a PUCCH of the indicated PUCCH resource corresponds to simultaneous UL transmission using multiple panels of PUCCH using the SFN or corresponds to the time division multiplexed PUCCH repetition, according to information on the repetition number; The control unit indicates, by the RRC parameter, whether the plurality of joint or UL TCI states or the one joint or UL TCI state is associated with the indicated PUCCH resource.