Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a reception unit which receives the setting of a physical uplink control channel (PUCCH) resource associated with one or more joint or uplink (UL) transmission setting indication (TCI) states, and which receives downlink control information (DCI) including a PUCCH resource indicator (PRI) field; and a control unit that determines whether or not the PUCCHs of the indicated PUCCH resources are a plurality of PUCCHs transmitted in at least the same time domain using a single frequency network (SFN), on the basis of the number of united or UL TCI states associated with the PUCCH resources indicated using the PRI field. According to one embodiment of the present disclosure, UL transmission using a plurality of panels can be appropriately performed.

Description

Technical Field

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems. Background Technology

[0002] In Universal Mobile Telecommunication System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving the height of LTE (3rd Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] The development of successor systems to LTE is also underway (e.g., also known as the 5th generation mobile communication system (5G), 5G+ (plus), the 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[0005] Non-patent literature

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

[0007] The problem that the invention aims to solve

[0008] In future wireless communication systems, the UE will be able to use one of multiple panels (or multiple beams) for uplink (UL) transmission. Furthermore, since Rel.18, to improve UL throughput / reliability, research is underway on supporting simultaneous transmission across multiple panels (STxMP) for more than one transmission / reception point (TRP).

[0009] However, how to control UL transmissions utilizing multiple panels (e.g., simultaneous UL transmissions) has not been adequately studied. If UL transmissions utilizing multiple panels are not properly implemented, there are concerns about system performance degradation, such as decreased throughput.

[0010] Therefore, one of the objectives of this disclosure is to provide a terminal, wireless communication method, and base station that can properly control UL transmission even when using multiple panels for UL transmission.

[0011] Methods for solving problems

[0012] One aspect of this disclosure relates to a terminal comprising: a receiving unit that receives settings for Physical Uplink Control Channel (PUCCH) resources associated with one or more Associated 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, based on the number of Associated or UL TCI states associated with the PUCCH resources indicated using the PRI field, determines whether the PUCCH of the indicated PUCCH resources is one of multiple PUCCHs transmitted using a single frequency network (SFN) in at least the same time domain.

[0013] Invention Effects

[0014] According to one method of this disclosure, UL transmission utilizing multiple panels can be appropriately performed. Attached Figure Description

[0015] Figure 1A as well as Figure 1B This represents an example of a unified / public TCI framework.

[0016] Figure 2A as well as Figure 2BThis represents an example of a TCI status indication based on DCI.

[0017] Figure 3 This is a diagram illustrating an example of the association between precoder types and TPMI indexes.

[0018] Figure 4A as well as Figure 4B This is a diagram illustrating an example of UL transmission for a single-panel display.

[0019] Figures 5A-5C This diagram illustrates an example of using multiple panels to simultaneously send UL signals in methods 1-3.

[0020] Figures 6A-6C This is a diagram illustrating an example of how PUSCH is sent.

[0021] Figures 7A-7C This is a diagram illustrating other examples of how PUSCH is sent.

[0022] Figure 8 This diagram illustrates an example of UL sending using multiple panels simultaneously.

[0023] Figure 9 This is a diagram illustrating an example of simultaneous transmission of PUSCH and PUCCH.

[0024] Figure 10 This diagram illustrates an example of PUCCH cell handover scheme 1.

[0025] Figure 11 This is a diagram illustrating an example of PUCCH cell handover scheme 2.

[0026] Figure 12 This is a diagram illustrating other examples of PUCCH cell handover scheme 2.

[0027] Figures 13A-13D This is a diagram illustrating an example of the STxMP scheme.

[0028] Figure 14 This is a diagram representing an example of the maximum number of layers.

[0029] Figure 15 This diagram illustrates an example of an application of the TCI status indicator according to the first embodiment.

[0030] Figure 16 This is a diagram illustrating an example of the associations between the TCI status, SRS resource set, and layer involved in option 1-3-1-1.

[0031] Figure 17 This is a diagram illustrating an example of the associations between the TCI status, SRS resource set, and layer involved in option 1-3-2-1.

[0032] Figure 18 This diagram illustrates an example of an application of the TCI status indicator according to the second embodiment.

[0033] Figure 19 This is a diagram illustrating an example of the associations between the TCI status, SRS resource set, and layer involved in option 2-2-1-1.

[0034] Figure 20 This is a diagram illustrating an example of the association between the TCI status, SRS resource set, and layers involved in implementation method 2-2-2.

[0035] Figure 21 This is a diagram illustrating an example of PUCCH transmission according to Implementation Method 3-2.

[0036] Figure 22 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0037] Figure 23 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0038] Figure 24 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0039] Figure 25 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment.

[0040] Figure 26 This is a diagram illustrating an example of a vehicle according to one embodiment. Detailed Implementation

[0041] (Unified / Common TCI Framework)

[0042] According to the unified TCI framework, multiple (UL / DL) channels / RS can be controlled through a common framework. Regarding the unified TCI framework, instead of specifying the TCI state or spatial relationship for each channel as in Rel.15, it can either indicate a common beam (common TCI state) and apply it to all channels of UL and DL, or apply the common beam used by UL to all channels of UL and apply the common beam used by DL to all channels of DL.

[0043] We are researching a common beam for both DL and UL, or a common beam for DL ​​and a common beam for UL (integrated as two common beams).

[0044] The UE can also envision the same TCI state (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set) for both UL and DL. The UE can also envision different TCI states (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) for UL and DL respectively.

[0045] UL and DL default beam alignment can also be achieved through MAC CE-based beam management (MAC CE level beam indication). The default TCI state of the PDSCH can also be updated and matched with the default UL beam (spatial relationship).

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

[0047] A TCI pool (set) can be either multiple TCI states set via RRC parameters, or multiple TCI states activated by MAC CE from among multiple TCI states set via RRC parameters (activating a TCI state, activating a TCI pool, or a set). Each TCI state can also be a QCL type A / D RS. As a QCL type A / D RS, it can also be set as SSB, CSI-RS, or SRS.

[0048] The number of TCI states corresponding to each of more than one TRP can also be specified. For example, the number of TCI states (UL TCI states) applied in the UL channel / RS (N ≥ 1) and the number of TCI states (DL TCI states) applied in the DL channel / RS (M ≥ 1) can also be specified. At least one of N and M can also be notified / set / indicated to the UE via higher-layer signaling / physical layer signaling.

[0049] In this disclosure, when N = M = X (X is any integer), it can also be intended to notify / set / indicate X TCI states (combined TCI states) common to UL and DL (corresponding to X TRPs) to the UE. Furthermore, when N = X (X is any integer) and M = Y (Y is any integer, or Y = X), it can also be intended to notify / set / indicate X UL TCI states (corresponding to X TRPs) and Y DL TCI states (corresponding to Y TRPs) separately to the UE (i.e., independent TCI states).

[0050] For example, when N=M=1 is recorded, it can also mean to notify / set / indicate to the UE a TCI state common to a UL and DL for a single TRP (the joint TCI state for a single TRP).

[0051] Furthermore, for example, when N=1 and M=1 is recorded, it may also mean that the UE is separately notified / set / indicated a UL TCI state and a DL TCI state (an independent TCI state for a single TRP).

[0052] Furthermore, for example, when N=M=2 is recorded, it may also mean to notify / set / indicate to the UE the TCI state common to multiple (two) ULs and DLs for multiple (two) TRPs (joint TCI state for multiple TRPs).

[0053] Furthermore, for example, when N=2 and M=2 are recorded, it may also mean to notify / set / indicate multiple (two) UL TCI states and multiple (two) DL TCI states (independent TCI states for multiple TRPs) to the UE.

[0054] Furthermore, the above example illustrates the case where N and M have values ​​of 1 or 2, but the values ​​of N and M can also be 3 or higher, and N and M can also be different.

[0055] In Rel.17, research is underway to support N=M=1. In Rel.18 and later, research is underway to support other cases.

[0056] exist Figure 1AIn the example, the RRC parameter (information element) sets multiple TCI states for both DL and UL. MACCE can also activate multiple TCI states among the set TCI states. DCI can also indicate one of the activated TCI states. DCI can also be UL / DL DCI. The indicated TCI state can also be applied to at least one (or all) of the UL / DL channel / RS. A DCI can also indicate both UL TCI and DL TCI.

[0057] In the example in the diagram, a point can be either a TCI state applied to both UL and DL, or two TCI states applied to UL and DL respectively.

[0058] At least one of the multiple TCI states set by RRC parameters and the multiple TCI states activated by MAC CE can also be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool). Multiple TCI states activated by MAC CE can also be referred to as an activated TCI pool (activated common TCI pool).

[0059] Furthermore, in this disclosure, the high-level parameters (RRC parameters) for setting multiple TCI states can also be referred to as setting information for setting multiple TCI states, or simply as "setting information". Additionally, in this disclosure, using a DCI to indicate one of multiple TCI states can be either receiving indication information contained in the DCI for indicating one of the multiple TCI states, or simply receiving the "indication information".

[0060] exist Figure 1B In the example, the RRC parameter sets multiple TCI states (joint common TCI pool) for both DL and UL. MAC CE can also activate multiple TCI states among the set TCI states (activate TCI pool). It can also set / activate separate TCI pools for UL and DL respectively.

[0061] The DL DCI or new DCI format can also select (indicate) more than one (e.g., one) TCI state. The selected TCI state can also be applied to more than one (or all) DL channels / RS. The DL channel can also be PDCCH / PDSCH / CSI-RS. The UE can also use the Rel.16 TCI state operation (TCI framework) to determine the TCI state of each DL channel / RS. The UL DCI or new DCI format can also select (indicate) more than one (e.g., one) TCI state. The selected TCI state can also be applied to more than one (or all) UL channels / RS. The UL channel can also be PUSCH / SRS / PUCCH. Thus, different DCIs can separately indicate the UL TCI and the DL DCI.

[0062] From Rel. 17 NR onwards, it is envisioned that support will be provided via MAC CE / DCI for beam activation / indication to TCI states associated with different physical cell identifiers (PCIs). Furthermore, from Rel. 18 NR onwards, it is envisioned that support will be provided via MAC CE / DCI for indicating changes to serving cells with different PCIs.

[0063] [Data using physical layer procedures / antenna port QCL]

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

[0065] If no DLorJointTCIState or UL-TCIState (UL TCI State) setting exists in the BWP within the reference CC, the UE can apply the DLorJointTCIState or UL-TCIState setting from the reference BWP of the reference CC. If the UE has DLorJointTCIState or UL-TCIState set in any CC within the same band domain, it is not assumed that TCI-State, SpatialRelationInfo (spatial relation information), or PUCCH-SpatialRelationInfo (PUCCH spatial relation information) other than SpatialRelationInfoPos (location spatial relation information) within that band domain will be set. The UE is designed such that, if the UE is set to TCI-State within any CC in the CC list via simultaneousTCI-UpdateList1-r16 (simultaneous TCI update list 1), simultaneousTCI-UpdateList2-r16 (simultaneous TCI update list 2), simultaneousSpatial-UpdatedList1-r16 (simultaneous spatial update list 1), or simultaneousSpatial-UpdatedList2-r16 (simultaneous spatial update list 2), the UE is not set to DLorJointTCIState or UL-TCIState within any CC in that CC.

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

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

[0068] (TCI status indication)

[0069] The Rel.17 Unified TCI framework supports the following modes 1 through 3.

[0070] [Mode 1] MAC CE based TCI state indication.

[0071] [Mode 2] DCI-based TCI state indication with DL assignment (DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment).

[0072] [Mode 3] DCI-based TCI state indication without DL assignment (DCI-based TCI state indication by DCI format 1_1 / 1_2 without DL assignment).

[0073] A UE with a TCI state set and activated with a Rel.17 TCI state ID (e.g., tci-StateId_r17) receives DCI format 1_1 / 1_2 as follows: For a single CC, DCI format 1_1 / 1_2 with a Rel.17 TCI state ID is provided; or, for all CCs within the same CC list set via simultaneous TCI update list 1 or simultaneous TCI update list 2 (e.g., simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2), DCI format 1_1 / 1_2 with a Rel.17 TCI state ID is provided. If DL allocation is available, DCI format 1_1 / 1_2 may or may not be accompanied by DL allocation.

[0074] In the absence of DL allocation in DCI format 1_1 / 1_2, the UE can envision (verify) the following for this DCI.

[0075] - CS-RNTI is used for scrambling CRC in DCI.

[0076] - The following DCI field (special field) values ​​are set as follows:

[0077] - The redundant version (RV) field is all '1's.

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

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

[0080] - The frequency domain resource assignment (FDRA) field is all '0's for FDRA type 0, all '1's for FDRA type 1, or all '0's for DynamicSwitch (same as the validation of the released PDCCH for DL ​​semi-persistent scheduling (SPS) or UL license type 2 scheduling).

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

[0082] In Rel.15 / 16, the UE ignores the BWP indicator field if it does not support activation of BWP changes via DCI. The same approach is being investigated regarding the relationship between Rel.17 TCI state support and the interpretation of the TCI field. It is being investigated that, when the UE is configured with the Rel.17 TCI state, the TCI field is always present in DCI format 1_1 / 1_2, and the UE ignores the TCI field if it does not support TCI updates via DCI.

[0083] In Rel.15 / 16, the presence or absence of the TCI field (TCI presence information within DCI, tci-PresentInDCI) is set per CORESET.

[0084] In DCI format 1_1, the TCI field is 0 bits if the higher-layer parameter tci-PresentInDCI is not valid, and 3 bits otherwise. When the BWP indicator field indicates that a BWP other than the active BWP is enabled, the UE follows these steps.

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

[0086] In DCI format 1_2, the TCI field is 0 bits if the higher-layer parameter tci-PresentInDCI-1-2 is not set; otherwise, it is 1, 2, or 3 bits, determined by the higher-layer parameter tci-PresentInDCI-1-2. When the BWP indicator field indicates that a BWP other than BWP is activated, the UE follows the procedure below.

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

[0088] Figure 2A This represents an example of a DCI-based joint DL / UL TCI status indication. The value of the TCI field used for the joint DL / UL TCI status indication is associated with the TCI status ID representing the joint DL / UL TCI status.

[0089] Figure 2B This example illustrates a standalone DL / UL TCI status indication based on DCI. For each TCI field value used in the standalone DL / UL TCI status indication, at least one TCI status ID is associated with: a TCI status ID representing the TCI status only for DL, and a TCI status ID representing the TCI status only for UL. 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.

[0090] (Indicates TCI status / Sets TCI status)

[0091] For Rel.17 TCI states, the unified / common TCI state can also refer to the Rel.17 TCI state indicated by using (Rel.17) DCI / MACCE / RRC (indicated Rel.17 TCI state).

[0092] In this disclosure, the Rel.17 TCI state, the indicated TCI state, the unified / common TCI state, the TCI state applied to multiple signals (channel / RS), and the TCI state used for multiple signals (channel / RS) can also be overwritten with each other.

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

[0094] For Rel.17 TCI states, TCI states other than the unified TCI state can also refer to the Rel.17 TCI state configured using (Rel.17) MAC CE / RRC (configured Rel.17 TCI state). In this disclosure, the configured Rel.17 TCI state, the configured TCI state, the TCI state other than the unified TCI state, and the TCI state applied to a specific type of signal (channel / RS) can also be interchanged.

[0095] Setting the Rel.17 TCI state may not be shared with at least one of the UE-specific receive, dynamically authorized (DCI) / configured authorized PUSCH, and multiple (e.g., all) dedicated PUCCH resources in the PDSCH / PDCCH (updated using Rel.17 DCI / MAC CE / RRC). Setting the Rel.17 TCI state may also be structured such that it is set per CORESET / per resource / per resource set via RRC / MAC CE, and the setting of the Rel.17 TCI state will not be updated even if the aforementioned indication of the Rel.17 TCI state (public TCI state) is updated.

[0096] We are investigating the application of Rel.17 TCI status indications for UE-specific channels / signals (RS). Additionally, we are investigating the use of higher-layer signaling (RRC signaling) to notify the UE of the application of Rel.17 TCI status indications for non-UE-specific channels / signals, and which Rel.17 TCI status is set.

[0097] An investigation is underway to set the RRC parameters associated with setting the Rel.17 TCI state (TCI state ID) to the same structure as the RRC parameters for the TCI state in Rel.15 / 16. An investigation is also underway to investigate using RRC / MAC CE to set / indicate the Rel.17 TCI state per CORESET / per resource / per resource set. Furthermore, an investigation is underway to investigate how the UE will determine this setting / indication based on specific parameters.

[0098] Research is underway to independently update the indicator TCI state and the setting TCI state for the UE. For example, for the UE, if the unified TCI state indicating the TCI state is updated, the setting TCI state update may not be performed. Furthermore, research is underway to allow the UE to determine this update based on specific parameters.

[0099] In addition, research is underway on using higher-layer signaling (RRC / MAC CE) to switch for PDCCH / PDSCH whether to apply the Rel.17 TCI state indication or not (apply the Rel.17 TCI state indication setting, or apply a TCI state that is set separately from the Rel.17 TCI state indication).

[0100] In addition, for intra-cell beam indication (TCI status indication), research is underway to support Rel.17 TCI status indication for UE-specific CORESET and PDSCH associated with that CORESET, as well as non-UE-specific CORESET and PDSCH associated with that CORESET.

[0101] In addition, for inter-cell beam indication (e.g., L1 / L2 inter-cell mobility), research is underway to support indication of Rel.17 TCI status for UE-specific CORESET and PDSCH associated with that CORESET.

[0102] In Rel.15, whether CORESET#0 indicates a TCI state depends on the base station implementation. In Rel.15, for CORESET#0 that is indicated with a TCI state, that indicated TCI state is applied. For CORESET#0 that is not indicated with a TCI state, the QCL of the SSB selected in the most recent (most recent) PRACH transmission is applied.

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

[0104] For example, within the framework of the unified TCI state after Rel.17, the Rel.17 TCI state indication for CORESET#0 can be configured by RRC for each CORESET to determine whether to apply the Rel-17 TCI state associated with the serving cell. If not, the existing MAC CE / RACH signaling mechanism can be utilized.

[0105] Additionally, the CSI-RS associated with the Rel.17 TCI state applied to CORESET#0 can also perform QCL with the SSB associated with the serving cell PCI (physical cell ID) (same as Rel.15).

[0106] Alternatively, for CORESET#0, CORESETs with a common search space (CSS), and CORESETs with both CSS and UE-specific search space (USS), the RRC parameter can be used to set whether to comply with the Rel.17 TCI state instruction. Even if the Rel.17 TCI state instruction is not set for a particular CORESET, the Rel.17 TCI state setting can still be applied to that CORESET.

[0107] Alternatively, the RRC parameter can be used to set whether to follow the Rel.17 TCI state instruction for each channel / resource / resource set (other than CORESET) that is not UE-dedicated.

[0108] (Channel / RS whose TCI status is indicated by the application)

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

[0110] [PDCCH]

[0111] • If `followUnifiedTCIState` is set for CORESET 0, the indicated TCI state is applied. Otherwise, the Rel.15 specification is applied for that CORESET. That is, CORESET 0 follows the TCI state activated by MAC CE, or is QCL-enabled with SSB.

[0112] • For CORESETs with USS / CSS type 3 and index 0 or less, the TCI status is always applied.

[0113] • When a CORESET with at least CSS type 3 or higher and an index other than 0 is configured to conform to a uniform TCI state, an indicative TCI state is applied. Otherwise, the configured TCI state is applied to that CORESET.

[0114] [PDSCH]

[0115] • For all UE-dedicated PDSCHs, the TCI status is always indicated by the application.

[0116] • When a non-UE-dedicated PDSCH (a PDSCH scheduled via DCI within the CSS) has its followUnifiedTCIState set (for the CORESET of the PDCCH that scheduled the PDSCH), the indicator TCI state can also be applied. Otherwise, the set TCI state for that PDSCH is applied to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicator TCI state depends on whether followUnifiedTCIState is set for the CORESET used in the scheduling of that PDSCH.

[0117] [CSI-RS]

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

[0119] [PUCCH]

[0120] • For all dedicated PUCCH resources, the application always indicates the TCI status.

[0121] [PUSCH]

[0122] • For dynamic / configured license PUSCH, the application is always indicated with TCI status.

[0123] [SRS]

[0124] • When the SRS resource sets for A-SRS used for beam management and A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching are configured to follow a unified TCI state, an indication TCI state is applied. For other SRS, the TCI state set within this SRS resource set is applied.

[0125] (PUSCH precoder)

[0126] In NR, research is underway on UE support for at least one of codebook-based (CB) transmission and non-codebook-based (NCB) transmission.

[0127] For example, research is underway to determine the precoder (precoding matrix) used by the UE at least with the Sounding Reference Signal (SRS) Resource Index (SRI) for transmission on at least one of the uplink shared channel (Physical Uplink Shared Channel (PUSCH)) based on CB and NCB.

[0128] In the case of CB-based transmission, the UE can also determine the precoder used for PUSCH transmission based on SRI, Transmitted Rank Indicator (TRI), and Transmitted Precoding Matrix Indicator (TPMI). In the case of NCB-based transmission, the UE can also determine the precoder used for PUSCH transmission based on SRI.

[0129] SRI, TRI, TPMI, etc., can also be notified to the UE using downlink control information (DCI). SRI can be specified either through the SRS resource indicator field (SRI field) of the DCI, or through the parameter "srs-ResourceIndicator" contained in the RRC information element "ConfiguredGrantConfig" of the configured grant PUSCH. TRI and TPMI can also be specified through the precoding information and number of layers field of the DCI.

[0130] The UE can also report UE capability information related to the precoder type, which is configured by the base station through higher-layer signaling based on the UE capability information. This UE capability information can also be information about the precoder type used by the UE in PUSCH transmission (or can be represented by the RRC parameter "pusch-TransCoherence").

[0131] In this disclosure, higher-level signaling may be, for example, any one or a combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc.

[0132] MAC signaling can also use MAC Control Element (MAC CE) or MAC Protocol Data Unit (PDU). Broadcast information can also be in the form of Master Information Block (MIB) or System Information Block (SIB).

[0133] The UE can also determine the precoder to use in PUSCH transmission based on the precoder type information contained in the PUSCH configuration information (the "PUSCH-Config" information element of the RRC signaling) notified via higher-layer signaling (which can also be represented by the RRC parameter "codebookSubset"). The UE can also be configured with a subset of the PMIs specified by the TPMI via codebookSubset.

[0134] In addition, the precoder type can also be specified by any one of full coherent, fully coherent, coherent, partial coherent, and noncoherent, or a combination of at least two of them (for example, it can also be represented by parameters such as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent").

[0135] Fully coherent can also mean that synchronization has been achieved across all antenna ports used in transmission (or that phase consistency and identical precoders are used, etc.). Partially coherent can also mean that synchronization has been achieved among a subset of antenna ports used in transmission, but this subset is not synchronized with the other ports. Incoherent can also mean that synchronization has not been achieved among the antenna ports used in transmission.

[0136] Furthermore, a UE that supports fully coherent precoder types can also be envisioned as supporting partially coherent and non-coherent precoder types. A UE that supports partially coherent precoder types can also be envisioned as supporting non-coherent precoder types.

[0137] The precoder type can also be rewritten as coherency, PUSCH transmission coherency, coherent type, coherent type, codebook type, codebook subset, codebook subset type, etc.

[0138] The UE can also determine the precoding matrix corresponding to the TPMI index obtained from the DCI (e.g., DCI format 0_1, hereinafter the same) obtained from multiple precoders (also referred to as precoding matrices, codebooks, etc.) used for CB-based transmission.

[0139] Figure 3 This is a diagram illustrating an example of the relationship between precoder types and TPMI indexes. Figure 3 This is equivalent to a table of precoding matrices W used for single-layer (rank 1) transmission with 4 antenna ports in DFT-s-OFDM (Discrete Fourier Transform spread OFDM, with transform precoding activated).

[0140] exist Figure 3 In the context of precoder type (codebookSubset) being fully, partially, and noncoherent, for single-layer transmission, the UE is notified of any TPMI from 0 to 27. Furthermore, in the case of precoder type being partially and noncoherent, for single-layer transmission, the UE is set to any TPMI from 0 to 11. In the case of precoder type being noncoherent, for single-layer transmission, the UE is set to any TPMI from 0 to 3.

[0141] In addition, such as Figure 3 As shown, a precoding matrix in which each column has only one non-zero component can be called an incoherent codebook. A precoding matrix in which each column has only a specific number (not all) non-zero components can be called a partially coherent codebook. A precoding matrix in which all components in each column are non-zero can be called a fully coherent codebook.

[0142] Incoherent codebooks and partially coherent codebooks can also be called antenna selection precoders. Fully coherent codebooks can also be called non-antenna selection precoders.

[0143] Additionally, in this disclosure, a partially coherent codebook can also be equivalent to: a codebook (precoding matrix) from the codebook (precoding matrix) corresponding to the TPMI specified by the DCI for codebook-based transmission of a UE with a partially coherent codebook subset (e.g., RRC parameter "codebookSubset" = "partialAndNonCoherent"), excluding the codebook corresponding to the TPMI specified by the UE with an incoherent codebook subset (e.g., RRC parameter "codebookSubset" = "nonCoherent") (that is, if it is a single-layer transmission with 4 antenna ports, it is the codebook from TPMI=4 to TPMI=11).

[0144] Additionally, in this disclosure, a fully coherent codebook can also be equivalent to: a codebook (precoding matrix) from the codebook (precoding matrix) corresponding to the TPMI specified by the DCI for codebook-based transmission by a UE with a fully coherent codebook subset (e.g., RRC parameter "codebookSubset" = "fullyAndPartialAndNonCoherent"), excluding the codebook corresponding to the TPMI specified by the UE with a partially coherent codebook subset (e.g., RRC parameter "codebookSubset" = "partialAndNonCoherent") (that is, for single-layer transmission with 4 antenna ports, the codebook from TPMI=12 to TPMI=27).

[0145] (Control of SRS and PUSCH transmission)

[0146] In Rel.15 NR, the terminal (user terminal, user equipment (UE)) can also receive information for sending measurement reference signals (e.g., sounding reference signals (SRS)) (SRS setting information, e.g., parameters in the "SRS-Config" of the RRC control element).

[0147] Specifically, the UE may also receive at least one of information related to one or more SRS resource sets (SRS resource set information, such as “SRS-ResourceSet” of RRC control elements) and information related to one or more SRS resources (SRS resource information, such as “SRS-Resource” of RRC control elements).

[0148] An SRS resource set can also be associated with a specific number of SRS resources (or grouped together). Each SRS resource can also be identified by an SRS resource identifier (SRS Resource Indicator (SRI)) or an SRS resource ID (Identifier).

[0149] SRS resource set information can also include the SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, the SRS resource type, and the usage of the SRS.

[0150] Here, the SRS resource type can also represent any of the following: Periodic SRS (P-SRS), Semi-Persistent SRS (SP-SRS), and Aperiodic SRS (A-SRS). Additionally, the UE can periodically (or periodically after activation) send P-SRS and SP-SRS, and send A-SRS based on DCI SRS requests.

[0151] Furthermore, the usage (“usage” in the RRC parameter, “SRS-SetUse” in the L1 (Layer-1) parameter) can also be, for example, beam management, codebook (CB) or noncodebook (NCB) or antenna switching. The codebook or noncodebook-based SRS can also be used to determine the precoder for SRI-based or noncodebook-based uplink shared channel (PUSCH) transmission.

[0152] For example, in codebook-based transmission, the UE can determine the precoder (precoding matrix) used for PUSCH transmission based on the SRI, the Transmitted Rank Indicator (TRI), and the Transmitted Precoding Matrix Indicator (TPMI). In non-codebook-based transmission, the UE can also determine the precoder used for PUSCH transmission based on the SRI.

[0153] SRS resource information may also include SRS resource ID (SRS-ResourceId), number of SRS ports, SRS port number, transmission combo, SRS resource mapping (e.g., time and / or frequency resource location, resource offset, resource period, repetition count, number of SRS symbols, SRS bandwidth, etc.), transition association information, SRS resource type, sequence ID, SRS spatial relationship information, etc.

[0154] Spatial Relation Information (SRS) (e.g., “spatialRelationInfo” in RRC information elements) can also represent spatial relationship information between a specific reference signal and an SRS. This specific reference signal can 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., other SRSs). An SS / PBCH block can also be referred to as a Synchronization Signal Block (SSB).

[0155] SRS spatial relationship information may also include at least one of the following: SSB index, CSI-RS resource ID, and SRS resource ID, as an index to the aforementioned specific reference signal.

[0156] Furthermore, in this disclosure, the SSB index, SSB resource ID, and SSB resource indicator (SSB Resource Indicator (SSBRI)) can be overridden. Similarly, the CSI-RS index, CSI-RS resource ID, and CSI-RS resource indicator (CSI-RS Resource Indicator (CRI)) can also be overridden. Additionally, the SRS index, SRS resource ID, and SRI can also be overridden.

[0157] The spatial relationship information of SRS can also include serving cell index, BWP index (BWP ID), etc., corresponding to the specific reference signal mentioned above.

[0158] When spatial relationship information related to an SSB or CSI-RS and an SRS is configured for a specific SRS resource, the UE can also use the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain receive filter) used for receiving that SSB or CSI-RS to transmit that SRS resource. In this case, the UE can also assume that the UE receive beam for the SSB or CSI-RS is the same as the UE transmit beam for the SRS.

[0159] When spatial relationship information related to other SRSs (reference SRSs) and the target SRS is set for a specific SRS (target SRS), the UE can also use the same spatial domain filter (spatial domain transmission filter) as the one used for transmitting the reference SRS to transmit the target SRS resource. That is, in this case, the UE can also assume that the UE transmission beam for the reference SRS is the same as the UE transmission beam for the target SRS.

[0160] The UE can also determine the spatial relationship of the PUSCH scheduled through the DCI based on the value of a specific field (e.g., the SRS Resource Identifier (SRI) field) within the DCI (e.g., DCI format 0_1). Specifically, the UE can also use the spatial relationship information of the SRS resources determined based on the value of the specific field (e.g., SRI) (e.g., the "spatialRelationInfo" of the RRC information element) for PUSCH transmission.

[0161] In Rel.15 / 16 NR, for PUSCH, when using codebook-based transmission, the UE can also be configured via RRC to have a set of SRS resources with a maximum of 2 SRS resources for codebook purposes, indicated by DCI (1-bit SRI field). The transmission beam of PUSCH is specified by the SRI field.

[0162] The UE can also determine the TPMI and layer number (transmission rank) used for PUSCH based on precoding information and layer number fields (hereinafter also referred to as the precoding information field). The UE can also select a precoder from the codebook used for the uplink based on the above TPMI, layer number, etc., which is the same as the number of SRS ports indicated by the higher-layer parameter "nrofSRS-Ports", where the higher-layer parameter "nrofSRS-Ports" is set for the SRS resources specified by the above SRI field.

[0163] In Rel.15 / 16 NR, for PUSCH, when using non-codebook-based transmission, the UE can also be configured via RRC to have a set of non-codebook SRS resources with a maximum of 4 SRS resources, and one or more of these maximum 4 SRS resources can be indicated via DCI (2-bit SRI field).

[0164] The UE can also determine the number of layers (transmission rank) used for PUSCH based on the SRI field mentioned above. For example, the UE can also determine that the number of SRS resources specified by the SRI field is the same as the number of layers used for PUSCH. In addition, the UE can also calculate the precoder for the SRS resources mentioned above.

[0165] When a CSI-RS (also known as an associated CSI-RS) is configured at a higher level to be associated with the SRS resource (or the SRS resource set to which the SRS resource belongs), the PUSCH transmit beam can also be calculated based on the measurements of that configured associated CSI-RS. Otherwise, the PUSCH transmit beam can be specified by the SRI.

[0166] Additionally, the UE can be configured via the high-level parameter "txConfig," which represents the transmission scheme, to use either codebook-based or non-codebook-based PUSCH transmission. This parameter can also represent the value of "codebook" or "non-codebook."

[0167] In this disclosure, codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) can also refer to PUSCH when the UE is configured with a "codebook" as the transmission scheme. In this disclosure, non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission) can also refer to PUSCH when the UE is configured with a "non-codebook" as the transmission scheme.

[0168] However, in future wireless communication systems (e.g., Rel.18 NR and beyond), it is envisioned that simultaneous UL transmission using multiple beams / panels / TRPs will be supported for more than one transmission / reception point (TRP) (e.g., simultaneous multi-panel UL transmission (STxMP)).

[0169] For example, in Rel.18, simultaneous UL transmission is being studied up to a maximum of 2 TRPs / 2 panels. Furthermore, considering multi-TRP operations based on single DCI and multi-DCI, it is envisioned that the total number of layers across all panels is a maximum of 4 layers, and the total number of codewords across all panels is a maximum of 2. Of course, the number of TRPs, panels, layers, and codewords are not limited to these.

[0170] (Single panel sending)

[0171] The single-panel UL transmission method or single-panel UL transmission method candidate can also apply at least one of the following transmission methods A and B (single-panel UL transmission methods A and B). Additionally, in this disclosure, the panel / UE panel can also be rewritten as a set of UE capability values ​​reported per UE capability (e.g., a UE capability value set). Furthermore, in this disclosure, different panels, different spatial relationships, different joint TCI states, different TPC parameters, different antenna ports, etc., can also be mutually rewritten.

[0172] <Sending Method A: Single-panel single-TRP UL sending>

[0173] In Rel.15 and Rel.16, the UE uses the following transmission method: at any given time, UL is transmitted from only one beam and panel to one TRP (Ultra-Low Voltage Receipt). Figure 4A ).

[0174] <Transmission Method B: Single-panel multi-TRP UL transmission>

[0175] In Rel.17, the following is being studied: at one moment, performing UL transmission from only one beam and panel, and performing repeated transmissions for multiple TRPs. Figure 4B ).exist Figure 4B In this example, after the UE sends a PUSCH from panel #1 to TRP #1 (switching beams and panels), it sends a PUSCH from panel #2 to TRP #2. The two TRPs are connected via the ideal backhaul link.

[0176] (Multi-panel delivery)

[0177] Following Rel.18, to improve UL throughput / reliability, research is underway to support simultaneous UL transmission using multiple panels for more than one TRP (e.g., simultaneous multi-panel UL transmission (STxMP)). Furthermore, multi-panel UL transmission methods are being researched for specific UL channels (e.g., PUSCH / PUCCH).

[0178] For example, it is also possible to support a maximum of X (e.g., X=2) and a maximum of Y (e.g., Y=2) panels as multi-panel UL transmissions. In multi-panel UL transmissions, if UL precoding instructions for PUSCH are supported, codebooks supporting existing systems (e.g., Rel. 16 and earlier) can also be transmitted simultaneously for multiple panels. Considering multi-TRP operations based on single DCI and multiple DCIs, it is also possible that the number of layers is a maximum of x (e.g., x=4) across all panels, and the number of codewords (CWs) is a maximum of y (e.g., y=2) across all panels.

[0179] Regarding multi-panel UL transmission methods or multi-panel UL transmission method candidates, at least one of the following methods 1 to 3 (multi-panel UL transmission methods 1 to 3) is being investigated. Alternatively, only one of transmission methods 1 to 3 may be supported. Multiple methods including at least one of transmission methods 1 to 3 may also be supported, with one of the multiple transmission methods being assigned to the UE.

[0180] <Transmission Method 1: Coherent Multi-Panel UL Transmission>

[0181] Multiple panels can also be synchronized with each other. All layers are mapped to all panels. Multiple analog beams are indicated. The SRS Resource Indicator (SRI) field can also be extended. This method can also use up to 4 layers for UL.

[0182] exist Figure 5A In the example, the UE maps a codeword (CW) or a transport block (TB) to L layers (PUSCH(1, 2, ..., L)), transmitting L layers from each of the two panels. Panel #1 and panel #2 are coherent. Transmission mode 1 can achieve diversity-based gain. The total number of layers in the two panels is 2L. With a maximum total number of layers of 4, the maximum number of layers in one panel is 2.

[0183] <Transmission Method 2: Incoherent Multi-Panel UL Transmission of a Codeword (CW) or Transport Block (TB)>

[0184] Multiple panels can also be asynchronous. Different layers are mapped to different panels and a CW or TB for PUSCH from multiple panels. The layer corresponding to a CW or TB can also be mapped to multiple panels. This transmission method can also use a maximum of 4 layers or a maximum of 8 layers for UL. If a maximum of 8 layers is supported, this transmission method can also support a CW or TB with a maximum of 8 layers.

[0185] exist Figure 5B In the example, the UE maps a CW or a TB to k layers (PUSCH(1, 2, ..., k)) and Lk layers (PUSCH(k+1, k+2, ..., L)), transmitting k layers from panel #1 and Lk layers from panel #2. Transmission mode 2 can achieve gains based on multiplexing and diversity. The total number of layers in the two panels is L.

[0186] <Transmission Method 3: Incoherent Multi-Panel UL Transmission from Two CW or TB Panels>

[0187] Multiple panels can also be asynchronous. Different layers are mapped to different panels and two CWs or TBs for the PUSCH from multiple panels. A layer corresponding to one CW or TB can also be mapped to one panel. Layers corresponding to multiple CWs or TBs can also be mapped to different panels. This transmission method can also use a maximum of 4 layers or a maximum of 8 layers for UL. When supporting a maximum of 8 layers, this transmission method can also support a maximum of 4 layers per CW or TB.

[0188] exist Figure 5C In the example, the UE maps CW#1 or TB#1 from two CWs or two TBs to k layers (PUSCH(1, 2, ..., k)), and maps CW#2 or TB#2 to Lk layers (PUSCH(k+1, k+2, ..., L)). It transmits k layers from panel #1 and Lk layers from panel #2. Transmission method 3 achieves gain based on multiplexing and diversity. The total number of layers in the two panels is L.

[0189] In the aforementioned transmission methods, the base station may also use UL TCI or panel ID to set or indicate panel-specific transmissions for UL transmission. UL TCI (UL TCI status) may also be based on signaling similar to DL beam indication supported in Rel.15. Panel ID may also be implicitly or explicitly applied to the transmission of at least one of the following: target RS resource or target RS resource set, PUCCH, SRS, and PRACH. When panel ID is explicitly notified, it may also be set in at least one of the following: target RS, target channel, and reference RS (e.g., DL RS resource settings or spatial relationship information).

[0190] (Send to multiple panels simultaneously)

[0191] Among the above-mentioned transmission methods / modes, the following are being studied: scheduling of PUSCH based on a single DCI (single DCI) / scheduling of PUSCH based on multiple DCIs (multiple DCIs) for multiple panels (e.g., simultaneous transmission across multiple panels (STxMP)).

[0192] <STxMP based on a single DCI>

[0193] In simultaneous multi-panel transmission (STxMP) in a single DCI-based multi-TRP system, the following approach can also be applied to UL transmission (e.g., PUSCH).

[0194] • Space Division Multiplexing (SDM) mode: Different layers / DMRS ports of a PUSCH are precoded separately and transmitted simultaneously from different UE beams / panels (see reference). Figure 6A , Figure 6B ).

[0195] • Spatial Division Multiplexing Repetition (SDM repetition): Simultaneously transmitting two PUSCH transmission opportunities with different Redundancy Versions (RVs) of the same TB from two different UE beams / panels on the same time and frequency resources (see reference). Figure 6C ).

[0196] • Frequency Division Multiplexing (FDM)-A mode: Different portions of the frequency domain resources for transmitting a PUSCH from different UE beams / panels (e.g., one PUSCH transmission occasion) (see reference) Figure 7A ).

[0197] • FDM-B mode: Two PUSCH transmission opportunities with the same TB and the same / different RV are transmitted from different UE beams / panels on non-overlapping frequency domain resources and the same time domain resources (see reference). Figure 7B ).

[0198] • SFN-based transmission method: Simultaneous transmission of all identical layer / DMRS ports of a PUSCH from two different UE beams / panels (see reference) Figure 7C ).

[0199] Furthermore, in this disclosure, repeated sending and sending can be interchanged. Sending multiple TBs can also mean sending multiple identical TBs or sending different TBs.

[0200] Space Division Multiplexing (SDM)

[0201] The UE can also envision repeated transmissions of PUSCH using Space Division Multiplexing (SDM) scheduled within the same time and frequency resources. That is, when using multiple coherent panels, the UE can also repeatedly transmit SDM-enabled PUSCH within the same time and frequency resources.

[0202] Figure 6A This diagram illustrates an example of repeated transmissions of SDM applied through a CW. In Figure 6A In this context, the time and frequency resources of layers #1-2 and layers #3-4 corresponding to PUSCH / PUCCH are the same.

[0203] Figure 6B This diagram illustrates an example of repeated transmissions of SDM applied through two CWs. Figure 6B In this context, the time and frequency resources of CW#1 and CW#2 corresponding to PUSCH / PUCCH are the same.

[0204] Figure 6C This diagram illustrates an example of repeated transmissions using SDM. Figure 6C In this context, the time and frequency resources for repetition #1 and repetition #2 of PUSCH / PUCCH are the same.

[0205] In addition, PUSCH transmission using SDM (e.g., repeated PUSCH transmission) can also be a structure that repeats at least a portion of time and frequency resources.

[0206] Frequency Division Multiplexing (FDM)

[0207] The UE can also envision repeated transmissions of PUSCH / PUCCH using Frequency Division Multiplexing (FDM) scheduled within the same time resources but different frequency resources. That is, when using multiple coherent panels, the UE can also repeatedly transmit FDM-enabled PUSCH / PUCCH within the same time resources but different frequency resources.

[0208] Figure 7A This diagram represents the first example of repeated transmissions using FDM (FDM-A). Figure 7AAn example is shown where PUSCH / PUCCH is repeatedly sent once for each TB / UCI.

[0209] Figure 7B This is a diagram illustrating the second example of repeated transmissions using FDM (FDM-B). Figure 7B An example is shown where two PUSCH / PUCCH repetitive transmissions are performed for each TB / UCI.

[0210] Figure 7C This is a diagram illustrating an example of repeated transmission using a single-frequency network (SFN). Figure 7C An example is shown of transmitting a PUSCH / PUCCH using a different beam / panel for each TB / UCI.

[0211] like Figure 6A , Figure 6B As shown, in the case of simultaneous multi-panel transmission based on spatial multiplexing for non-codebook PUSCH transmission (STxMP SDM scheme), different layer / DMRS ports of a PUSCH can be precoded separately and transmitted simultaneously from different UP panels.

[0212] For simultaneous multi-panel transmission based on spatial multiplexing according to non-codebook-based PUSCH, as an SRI indication (e.g., SRI indication), consider the following two options.

[0213] Option 1

[0214] A combination of SRIs can be indicated (e.g., one SRI combination). Combinations of SRIs can also be indicated from non-codebook SRS resources spanning two panels (e.g., NCB SRS resources across two panels).

[0215] Option 2

[0216] Multiple (e.g., 2) SRS combinations (e.g., two SRI combinations) can be indicated. Combinations of SRIs can also be indicated from non-codebook SRS resources of a panel (e.g., NCB SRS resources of one panel).

[0217] An SRI combination can also contain one or more SRS resources (e.g., SRS resources not used in the codebook). For example, an SRI combination (or an SRI field) can also indicate the SRI / SRS resources corresponding to each panel individually. An SRI combination can also be rewritten as an SRI set or SRI group.

[0218] <STxMP based on multi-DCI>

[0219] Following Rel.18, it is envisioned that in STxMP within a multi-DCI-based multi-TRP system, simultaneous transmission of UL channels / UL signals (e.g., PUSCH+PUSCH and PUSCH+PUCCH) will be supported (see reference). Figure 8 As an example, it is envisioned that at least one of the following is supported: simultaneous transmission of multiple PUSCHs (e.g., PUSCH+PUSCH), and simultaneous transmission of PUSCH and PUCCH.

[0220] Following Rel.18, research is underway on UCI multiplexing / mapping methods in cases where a PUCCH overlaps with multiple PUSCHs during simultaneous transmission of PUSCH and PUCCH. These multiple PUSCHs can also be multiple PUSCHs transmitted simultaneously (as involved in STxMP).

[0221] In this case, the multiple PUSCHs can also be associated with different TRPs / panels (see reference). Figure 9 ).

[0222] In existing specifications (up to Rel.17), for multiple DCI and multiple TRP, when the RRC parameter "ackNackFeedbackMode" is set to "separate", the UE does not expect dynamically scheduled PUSCH / PUCCH to overlap with other dynamically scheduled PUSCH / PUCCH in the time domain (see reference). Figure 8 ).

[0223] This is because when the RRC parameter “ackNackFeedbackMode” is set to “separate”, a non-ideal backhaul is assumed between two TRPs, and each TRP cannot identify the dynamic scheduling of other TRPs in a timely manner.

[0224] Additionally, in this disclosure, dynamically scheduled PUSCH / PUCCH can also refer to PUSCH / PUCCH scheduled using dynamic licensing or PUSCH / PUCCH dynamically scheduled using DCI.

[0225] (PUCCH cell handover)

[0226] In Rel.17, in order to reduce the HARQ-ACK feedback delay in TDD operations, handover between PUCCH cells of multiple (e.g., 2) TDD cells within the same PUCCH cell group is supported.

[0227] In addition to PCell / PSCell / PUCCH-SCell, an append SCell can also be set for PUCCH resources / transmission.

[0228] When two PUCCH cell groups are configured, additional SCells can also be configured for each PUCCH cell group.

[0229] PUCCH cell handover can also be based on dynamic indications or semi-static settings.

[0230] In the case of PUCCH cell handover based on dynamic indication (also known as Scheme 1), the PUCCH cell can also be indicated using a new field (PUCCH cell indicator field) included in the DCI. In this case, K1, indicated by the timing field of the HARQ-ACK feedback included in the DCI, can also be interpreted / determined based on the parameter set of the handover cell (target PUCCH cell) (e.g., subcarrier spacing settings).

[0231] Figure 10 This diagram illustrates an example of PUCCH cell handover scheme 1. Figure 10 In the example shown, DL CC (cell), PCell, and PUCCH SCell#1 are configured, and DCI and PDSCH are received in DL CC (cell).

[0232] exist Figure 10 In the example shown, the length of the DL CC and PCell time slots is different from the length of the PUCCH SCell#1 time slot.

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

[0234] At this time, the UE determines that: starting from the time slot of receiving the PDSCH, the time slot after the second time slot in PUCCH SCell#1 (time slot #3) is the time slot for sending HARQ-ACK for the PDSCH.

[0235] In the case of PUCCH cell handover based on semi-static settings (also known as Scheme 2), the time domain of the PUCCH cell mode can also be set at the granularity of 1 time slot of PCell / PSCell / PUCCH-SCell, per PUCCH cell group. In this case, K1, indicated by the timing field of the HARQ-ACK feedback included in the DCI, can also be interpreted / determined based on the parameter set of PCell / PSCell / PUCCH-SCell (e.g., subcarrier spacing settings).

[0236] Figure 11 This diagram illustrates an example of PUCCH cell handover scheme 2. Figure 11 In the example shown, the PDSCH Cell, PCell, and PUCCH SCell#1 are configured, and PDSCH#1 and PDSCH#2 are received within the PDSCH Cell. Furthermore, in each time slot of the PDSCH Cell / PCell, the target PUCCH cell is configured (PUCCH cell mode).

[0237] exist Figure 11 In the example shown, the HARQ-ACK for PDSCH#1 is sent at the time slot (slot #1) of the configured SCell in the PUCCH cell mode. At this time, the UE sends the HARQ-ACK for PDSCH#1 in the PUCCH SCell (during the handover) as instructed to be sent in the PCell.

[0238] exist Figure 11 In the example shown, the HARQ-ACK for PDSCH#2 is sent at the time slot (slot #3) of the configured PCell in the PUCCH cell mode. At this time, the UE sends the HARQ-ACK for PDSCH#1 that was instructed to be sent in the PCell (without handover) in the PCell.

[0239] Figure 12 This is a diagram illustrating other examples of PUCCH cell handover scheme 2. In Figure 12 In the example shown, similar to the above Figure 11 The difference lies in the length of the time slot in PUCCH SCell#1.

[0240] When the time slots of PCell / PSCell / PUCCH-SCell overlap with multiple time slots of the target PUCCH cell, the UE can also determine the first time slot among these multiple time slots as the time slot used for PUCCH / HARQ-ACK transmission.

[0241] Figure 12In the example shown, the UE switches and sends a HARQ-ACK for PDSCH #1 in slot #2 and slot #3 of PUCCH SCell #1, which overlaps with slot #1 in PCell.

[0242] (analyze)

[0243] As mentioned above, in future wireless communication systems (Rel.18 and later), simultaneous UL transmission utilizing multiple beams / panels / TRPs in the UE is being studied (e.g., it can also be called simultaneous multi-panel UL transmission (STxMP)).

[0244] Specifically, for STxMP, at least one of the following is being investigated.

[0245] • Single DCI PUSCH SDM solution.

[0246] • Single DCI PUSCH SFN scheme.

[0247] • Multi-DCI overlapping PUSCH+PUSCH scheme.

[0248] • Single DCI PUCCH SFN scheme.

[0249] A single DCI PUSCH SDM scheme can also mean that different layers / DMRS ports of a PUSCH scheduled / triggered by a single DCI are simultaneously transmitted using different panels (towards different TRPs). Figure 13A ).

[0250] The Single DCI PUSCH SFN scheme can also mean that multiple (e.g., all) Layer / DMRS ports of a PUSCH scheduled / triggered by a single DCI are simultaneously transmitted using different panels (towards different TRPs). Figure 13B ).

[0251] The multi-DCI overlapping PUSCH+PUSCH scheme can also mean that multiple (e.g., two) PUSCHs that overlap in the time domain (at least partially) are transmitted simultaneously using different panels (oriented towards different TRPs). Figure 13C ).

[0252] The Single DCI PUCCH SFN scheme can also mean that a single PUCCH is transmitted simultaneously using different panels (facing different TRPs). Figure 13D ).

[0253] In this disclosure, the above scheme names are used for convenience, but this is only one example and is not limited to these examples.

[0254] Additionally, a maximum of n layers (e.g., n=4) can be sent across m panels (e.g., m=2).

[0255] Furthermore, following Rel.18, research is underway on extending and applying the unified TCI state framework for beam indication.

[0256] In a single DCI PUSCH SDM / SFN scheme, multiple (e.g., 2) SRS resource sets can also be configured, and multiple (e.g., 2) SRI fields / TPMI fields can be indicated.

[0257] In a multi-DCI PUSCH+PUSCH scheme, multiple (e.g., 2) SRS resource sets can also be configured, with each SRS resource set associated with a different CORESET pool index.

[0258] In a single DCI PUCCH SFN scheme, multiple (e.g., two) TCI states can also be associated with a single PUCCH resource.

[0259] Investigating: Multiple (e.g., 2) SRS resource sets with usage of CB / NCB are applied to the PUSCH of the SDM / SFN scheme involved in STxMP.

[0260] As with STxMP's dynamic handover, handover between the STxMP-based SDM / SFN scheme and the TDM scheme utilizing multiple TRPs specified in Rel. 17 is not supported. On the other hand, support for handover between the STxMP-based SDM / SFN scheme and the single TRP scheme is under investigation.

[0261] Investigating: Utilizing specific fields within the DCI (e.g., SRS resource set indicator) during the switch between STxMP (schema) and single TRP based on a single DCI.

[0262] The maximum number of layers used by a single TRP and STxMP SDM can also be set separately.

[0263] In the case of a single TRP transmission, the maximum number of layers can also be set in the same way as the existing specifications, through the RRC parameter maxRank (or Lmax).

[0264] In the case of the SDM STxMP scheme, (unlike the maxRank (or Lmax) in the case of a single TRP) a maximum number of layers can also be set separately for the first SRS resource set and the second SRS resource set. This setting can be, for example, an RRC parameter representing the maximum number of layers for each SRS resource set (e.g., maxRankPerSRSResourceSet).

[0265] Figure 14 This is a diagram representing an example of the maximum number of layers. In Figure 14 In the example shown, in the case of a single TRP, the RRC parameter maxRank is set to 4 for the UE. The UE uses a single TRP / single panel (panel #1) to send a maximum of 4 layers (layer 1) of PUSCH.

[0266] In addition, Figure 14 In the example shown, for the UE, the RRC parameter (e.g., maxRankPerSRSResourceSet) for setting the maximum number of layers used in the STxMP scheme is set. For example, when this parameter is set to 2, the UE uses the first TRP / panel (panel #1) and the second TRP / panel (panel #2) to send a maximum of 2 layers (layer 1) of PUSCH.

[0267] exist Figure 14 The example shown illustrates a dynamic switching between these single TRP PUSCH and SDM PUSCH.

[0268] Furthermore, since Rel.18, research is underway to apply / extend the unified TCI state framework for PUSCH transmission that utilizes multiple TRPs based on a single DCI.

[0269] When multiple (e.g., 2) SRS resource sets are configured for CB / NCB, the TCI state (joint / UL TCI state) applied for a PUSCH that is scheduled / activated via DCI can also be determined based on a specific field contained in the DCI (e.g., SRS resource set indicator field).

[0270] Alternatively, the DCI can be, for example, a DCI format 0_1 / 0_2, or a DCI of at least one of a DL license (DG) for dynamic scheduling of PUSCH and a type 2 setting license (CG).

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

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

[0273] For example, if the code point of a particular field indicates a third value (e.g., "10") / a fourth value (e.g., "11"), and the PUSCH transmission is based on TDM, a first indication (joint / UL) TCI state can be applied to the PUSCH transmission opportunity associated with the first SRS resource set, and a second indication (joint / UL) TCI state can be applied to the PUSCH transmission opportunity associated with the second SRS resource set. These SRS resource sets can also be SRS resource sets used for CB / NCB.

[0274] On the other hand, for the case where the code point of this particular field shows a third value (e.g., "10") / fourth value (e.g., "11"), and it is a PUSCH transmission based on SDM / SFN, there has been no progress in research on how to apply the TCI state.

[0275] As mentioned above, since Rel.18, research is underway on applying / extending the unified TCI state framework to various STxMP schemes.

[0276] However, research on this application method is insufficient. More specifically, research on how to indicate the TCI state and the correlation between the indicated TCI state and the PUSCH / PUCCH in SDM / SFN-based STxMP is insufficient.

[0277] In the absence of sufficient research, proper transmission of overlapping UL channels / signals is not possible, raising concerns about system performance degradation such as reduced throughput.

[0278] Therefore, the inventors of this invention conceived of methods to solve these problems.

[0279] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods involved in each embodiment can be used individually or in combination.

[0280] In this disclosure, "A / B" and "at least one of A and B" may be rewritten as each other. In addition, in this disclosure, "A / B / C" may also mean "at least one of A, B and C".

[0281] In this disclosure, terms such as notification, activation, deactivation, indication (or indication), selection, configuration, update, and determination can be overridden. Similarly, terms such as support, control, ability to control, operation, and ability to operate can also be overridden.

[0282] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, fields, Information Elements (IE), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) elements (MAC ControlElement (CE)), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

[0283] In this disclosure, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., any one of positioning protocols (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP))) or combinations thereof).

[0284] In this disclosure, MAC signaling may also use, for example, a MAC Control Element (MACCE) or a MAC Protocol Data Unit (PDU). Broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), a Minimum System Information (Remaining Minimum System Information (RMSI)), or Other System Information (OSI).

[0285] In this disclosure, physical layer signaling may also be, for example, downlink control information (DCI), uplink control information (UCI), etc.

[0286] In this disclosure, the following can also be rewritten as: multiple TRP, multiple TRP system, multiple TRP transmission, multiple PDSCH, channel using multiple TRP, channel using multiple TCI state / spatial relationships, multiple TRP activated by RRC / DCI, multiple TCI state / spatial relationships activated by RRC / DCI, at least one of single DCI-based multiple TRP and multiple DCI-based multiple TRP. In this disclosure, for multiple DCI-based multiple TRP, the CORESET pool index value set to 1 for CORESET can also be rewritten as. In this disclosure, for single DCI-based multiple TRP, at least one code point of the TCI field is mapped to two TCI states, which can also be rewritten as.

[0287] In this disclosure, single TRP, single DCI, single PDCCH, multiple TRP based on single DCI, single TRP system, single TRP transmission, single PDSCH, channel using single TRP, channel using one TCI state / spatial relationship, multiple TRP not activated by RRC / DCI, multiple TCI state / spatial relationships not activated by RRC / DCI, CORESET pool index (CORESETPoolIndex) value not set to 1 for any CORESET and no code point of TCI field is mapped to 2 TCI states, and 2 TCI states on at least one activated TCI code point can also be rewritten to each other.

[0288] In this disclosure, the panel, UE capability value set (e.g., UE capability value set), TRP, SRS resource set, CORESET pool index, beam group, TCI state group, spatial relationship group, reference signal group, and path loss RS group can also be rewritten to each other.

[0289] In this disclosure, STxMP, simultaneous UL transmission using multiple panels, UL transmission using at least the same time resources / time domain of multiple panels (multiple UL transmissions), UL transmission using at least the same time resources / time domain of multiple TRPs (multiple UL transmissions), and UL transmission oriented towards multiple TRPs (multiple UL transmissions) can also be rewritten to each other.

[0290] In this disclosure, terms such as ignore, drop, abort, cancel, puncture, rate match, postpone, and do not send can also be rewritten.

[0291] In this disclosure, PUSCH involved in STxMP of SDM, PUSCH of STxMP of SDM, STxMP PUSCHSDM, PUSCH SDM, PUSCH of SDM, SDM PUSCH, etc. can also be rewritten to each other.

[0292] In this disclosure, PUSCH involving STxMP using SFN, PUSCH using STxMP using SFN, STxMPPUSCH SFN, PUSCH SFN, PUSCH using SFN, SFN PUSCH, etc. can also be rewritten to each other.

[0293] In this disclosure, PUCCH involving STxMP using SFN, PUCCH using STxMP using SFN, STxMPPUCCH SFN, PUCCH SFN, PUCCH using SFN, SFN PUCCH, etc. can also be rewritten to each other.

[0294] (Wireless communication method)

[0295] The UE can also use multiple panels to transmit more than one UL signal / channel in at least the same time domain (e.g., the same time resources / symbols / time slots / sub-time slots).

[0296] The various embodiments of this disclosure can also be appropriately applied to STxMP based on multi-DCI PUSCH+PUSCH. When the configuration information related to multi-DCI PUSCH+PUSCH is set to active / on, and (2) CORESET pool indexes are set, multi-DCI PUSCH+PUSCH can also be transmitted to the UE.

[0297] <First Implementation Method>

[0298] The first implementation relates to the TCI state applied in a UL signal / channel utilizing SDM.

[0299] The UL signal / channel in the first embodiment can also be, for example, a PUSCH.

[0300] In the first embodiment, the PUSCH can also be, for example, an STxMP of the SDM PUSCH. The PUSCH involved in the SDM STxMP can also be configured for the UE. This configuration can also be performed using higher-layer signaling (RRC / MAC CE).

[0301] In the first embodiment, PUSCH can also be scheduled via a single DCI.

[0302] Multiple (e.g., two) SRS resource sets for a specific purpose (e.g., codebook (CB) / non-codebook (NCB)) can also be configured for the UE. In this embodiment, the SRS resource set can also be an SRS resource set used for that specific purpose.

[0303] Implementation Method 1-1

[0304] UEs can also be scheduled / activated / triggered using specific DCIs for PUSCH.

[0305] The specific DCI can be, for example, a DCI for scheduling PUSCH (e.g., DCI format 0_1 / 0_2), or a DCI for at least one of a DL license (DG) and a type 2 setting license (CG) for dynamically scheduling PUSCH.

[0306] The UE can also transmit PUSCH corresponding to different layers in at least the same time domain (e.g., time resources / symbols / time slots / sub-time slots).

[0307] The UE can also determine the indication (joint / UL) TCI status applied in the PUSCH / PUSCH antenna port / PUSCH transmission opportunity corresponding to different layers based on specific fields contained in the DCI.

[0308] The UE can also use this specific field to determine whether the scheduled PUSCH is a single TRP PUSCH or an SDM STxMP PUSCH. The UE can also use this specific field to determine the handover between single TRP PUSCH transmission and SDM STxMP PUSCH transmission.

[0309] This specific field can be, for example, an SRS resource set indicator field or a new field defined after Rel.18.

[0310] This particular field can also be specified by a specific number of bits (e.g., 2 bits).

[0311] The UE can also determine whether to switch between single TRP PUSCH transmission and SDM STxMP PUSCH transmission based on the presence or absence of a specific field within a specific number of bits in the DCI. For example, if the specific field within the specific number of bits exists in the DCI, the UE can perform the necessary checks for the switch. If the specific field within the specific number of bits does not exist in the DCI, the UE can also determine / presume not to perform the switch.

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

[0313] For example, if the code point of that particular field shows a first value (e.g., "00"), the UE may also transmit a PUSCH using a TRP (single TRP) associated with the first SRS resource set.

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

[0315] For example, if the code point of that particular field shows a second value (e.g., "01"), the UE can also transmit a PUSCH using a TRP (single TRP) associated with the second SRS resource set.

[0316] For example, if the code point of the particular field indicates a third value (e.g., "10"), the UE may also apply a first indication (joint / UL) TCI state for more than one first PUSCH antenna port / layer associated with the first SRS resource set, and a second indication (joint / UL) TCI state for more than one second PUSCH antenna port / layer associated with the second SRS resource set.

[0317] For example, if the code point of that particular field shows a third value (e.g., "10"), the UE can also transmit the PUSCH involved in the STxMP of the SDM.

[0318] For example, if the code point of the particular field indicates a fourth value (e.g., "11"), the UE may also apply a first indication (joint / UL) TCI state for more than one second PUSCH antenna port / layer associated with the second SRS resource set, and a second indication (joint / UL) TCI state for more than one first PUSCH antenna port / layer associated with the first SRS resource set.

[0319] For example, if the code point of that particular field shows a fourth value (e.g., "11"), the UE can also transmit the PUSCH involved in the STxMP of the SDM.

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

[0321] Furthermore, in the present disclosure, the first SRS resource set may also be the SRS resource set corresponding to a lower (or higher) SRS resource set ID in the SRS resource sets with usage of CB / NCB. In the present disclosure, the second SRS resource set may also be the SRS resource set corresponding to a higher (or lower) SRS resource set ID in the SRS resource sets with usage of CB / NCB.

[0322] Regarding the operations related to the code points (first - fourth values) of this specific field, the operations for all code points can be applied, or the operations for only a part of the code points (e.g., the first - third values) can be applied. For example, when only the code points of the first - third values are utilized / supported, the code point of the fourth value can be either reserved or used for other purposes.

[0323] For example, when only the operations for a part of the code points are applied, an association between the SRS resource set and the indicated TCI state is required.

[0324] The UE can also determine the association between the SRS resource set and the indicated TCI state based on specific rules (e.g., pre - defined specifications).

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

[0326] The UE can also determine the association between the SRS resource set and the indicated TCI state based on higher - layer signaling (e.g., RRC / MAC CE).

[0327] For example, the RRC parameters of the SRS resource set may also include information indicating either the first or the second indicated TCI state. The UE can also determine the association between the SRS resource set and the indicated TCI state based on this information.

[0328] Figure 15 It is a diagram showing an example of the application of the indicated TCI state related to the first embodiment. In Figure 15 In the example shown, 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.

[0329] In Figure 15In the example shown, when the code point of a specific field contained in the DCI shows "10", the UE applies the first indication TCI state for layer 1 and the second indication TCI state for layer 2.

[0330] exist Figure 15 In the example shown, when the code point of a specific field contained in the DCI shows "11", the UE applies the second indication TCI state for layer 1 and the first indication TCI state for layer 2.

[0331] According to implementation method 1-1, it is possible to appropriately switch between a single TRP PUSCH and an STxMP PUSCH that is SDMed.

[0332] Implementation Methods 1-2

[0333] In embodiments 1-2, the association between the PUSCH antenna port / layer and the SRS resource set is explained.

[0334] [Options 1-2-1]

[0335] The UE can also determine the association between the PUSCH antenna port / layer and the SRS resource set based on the rules predefined in the specification.

[0336] For example, the UE may also 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.

[0337] The values ​​of n and m can be the same or different.

[0338] For example, UE can also be conceived as n≤m. Furthermore, for example, UE can also be conceived as n≥m.

[0339] The port / layer number (at least one of n and m) associated with the first / second SRS resource set can also be determined based on a specific field within the DCI. This DCI can also be the DCI that schedules / activates / triggers the PUSCH.

[0340] For example, n can also be determined based on the first TPMI field (e.g., the first TPMI field used by CB) or the first SRI field (e.g., the first SRI field used by NCB).

[0341] For example, m can also be determined based on a second TPMI field (e.g., the second TPMI field used by CB) or a second SRI field (e.g., the second SRI field used by NCB).

[0342] Furthermore, the UE can also be notified / indicated which of the lower port / layer PUSCH antenna ports and the higher PUSCH antenna ports are associated with the first / second SRS resource set. This indication can also be made, for example, using a specific field (e.g., the SRS resource set indicator field) within the DCI (e.g., the scheduling DCI).

[0343] [Options 1-2-2]

[0344] The UE can also be configured / indicated / notified of the association between the PUSCH antenna port / layer and the SRS resource set based on higher-layer signaling (RRC / MAC CE) / DCI.

[0345] For example, each SRS resource set can also be associated with a PUSCH antenna port / layer for a specific purpose (e.g., CB / NCB).

[0346] According to implementation methods 1-2, the association between the SRS resource set and the port / layer of PUSCH can be appropriately specified.

[0347] Implementation Methods 1-3

[0348] In embodiments 1-3, the mapping / association of at least two of the following is described: SRS resource set (index of SRS resource set), PUSCH port / layer (index of PUSCH port / layer), and indicator (joint / UL) TCI status (index of indicator (joint / UL) TCI status).

[0349] The UE can also determine the mapping / association based on the specific fields in Implementation Method 1-1 above.

[0350] The UE can also determine the mapping / association by following the implementation methods 1-3-1 / 1-3-2 below.

[0351] [Implementation Method 1-3-1]

[0352] The code point of a specific field can also indicate a first value (e.g., "00") / a second value (e.g., "01").

[0353] [[Options 1-3-1-1]]

[0354] When the code point of a specific field shows a first value (e.g., "00"), the UE may also assume / determine that: a first indication (joint / UL) TCI state, a first SRS resource set, and multiple (e.g., all) layers are associated.

[0355] At this point, the UE can also determine that a single TRP PUSCH has been sent.

[0356] When a code point in a specific field indicates a second value (e.g., "01"), the UE may also assume / determine that: a second indication (joint / UL) TCI state, a second SRS resource set, and multiple (e.g., all) layers are associated.

[0357] At this point, the UE can also determine that a single TRP PUSCH has been sent.

[0358] Figure 16 This is a diagram illustrating an example of the TCI status, SRS resource set, and layer associations involved in option 1-3-1-1. Figure 16 In the example shown, when the code point of a specific field shows "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. Furthermore, when the code point of a specific field shows "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.

[0359] [[Options 1-3-1-2]]

[0360] When the code point of a specific field shows a first value (e.g., "00"), the UE may also assume / determine that: a first indication (joint / UL) TCI state, a second SRS resource set, and multiple (e.g., all) layers are associated.

[0361] At this point, the UE can also determine that a single TRP PUSCH has been sent.

[0362] When a code point in a specific field indicates a second value (e.g., "01"), the UE may also assume / determine that: a second indication (joint / UL) TCI state, a first SRS resource set, and multiple (e.g., all) layers are associated.

[0363] At this point, the UE can also determine that a single TRP PUSCH has been sent.

[0364] [Implementation Method 1-3-2]

[0365] The code point of a specific field can also indicate a third value (e.g., "10") / a second value (e.g., "11").

[0366] [[Options 1-3-2-1]]

[0367] When the code point of a specific field shows a third value (e.g., "10"), the UE may also assume / determine that: the first indication (joint / UL) TCI state, the first SRS resource set, and the first layer are associated, and the second indication (joint / UL) TCI state, the second SRS resource set, and the second layer are associated.

[0368] At this point, the UE can also determine that the STxMP PUSCH being sent by SDM is being sent.

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

[0370] At this point, the UE can also determine that the STxMP PUSCH being sent by SDM is being sent.

[0371] Figure 17 This is a diagram illustrating an example of the TCI status, SRS resource set, and layer associations involved in option 1-3-2-1. Figure 17 In the example shown, when the code point of a specific field shows "01", the UE determines that: the first indication (joint / UL) TCI state, the first SRS resource set, and PUSCH layer 1 are associated; and the second indication (joint / UL) TCI state, the second SRS resource set, and PUSCH layer 2 are associated. Furthermore, when the code point of a specific field shows "11", the UE determines that: the first indication (joint / UL) TCI state, the first SRS resource set, and PUSCH layer 2 are associated; and the second indication (joint / UL) TCI state, the second SRS resource set, and PUSCH layer 1 are associated.

[0372] [[Options 1-3-2-2]]

[0373] When the code point of a specific field shows a third value (e.g., "10"), the UE may also assume / determine that: the first indication (joint / UL) TCI state, the first SRS resource set, and the first layer are associated, and the second indication (joint / UL) TCI state, the second SRS resource set, and the second layer are associated.

[0374] At this point, the UE can also determine that the STxMP PUSCH being sent by SDM is being sent.

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

[0376] At this point, the UE can also determine that the STxMP PUSCH being sent by SDM is being sent.

[0377] [[Options 1-3-2-3]]

[0378] When the code point of a specific field shows a third value (e.g., "10"), the UE may also assume / determine that: the first indication (joint / UL) TCI state, the first SRS resource set, and the first layer are associated, and the second indication (joint / UL) TCI state, the second SRS resource set, and the second layer are associated.

[0379] At this point, the UE can also determine that the STxMP PUSCH being sent by SDM is being sent.

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

[0381] At this point, the UE can also determine that the STxMP PUSCH being sent by SDM is being sent.

[0382] Additionally, in at least one option of implementation 1-3-2, the fourth value (e.g., "11") may also be reserved (or may not be used).

[0383] According to implementation methods 1-3, the associations of SRS resource sets, PUSCH ports / layers, and TCI status indicators can be appropriately specified.

[0384] According to the first embodiment described above, the transmission of the STxMP PUSCH of the SDM can be performed appropriately.

[0385] <Second Implementation Method>

[0386] The second embodiment relates to the indication of TCI status applied in UL signals / channels (UL transmissions) using a single frequency network (SFN).

[0387] In the second embodiment, the UL signal / channel can also be, for example, a PUSCH.

[0388] In this disclosure, UL transmission using SFN can also mean that the UE transmits the same UL signal / channel in the same resource (resource element) in each panel using different indications (joint / ULTCI states). Furthermore, UL transmission using SFN can also mean UL transmission in which multiple (e.g., all) DMRS ports / antenna ports of the UL transmission are in a QCL relationship with multiple (e.g., 2) TCI states (indicating TCI states).

[0389] In the second embodiment, the PUSCH can also be, for example, an STxMP using the SFN's PUSCH. The PUSCH involved in the STxMP using the SFN can also be configured for the UE. This configuration can also be performed using higher-layer signaling (RRC / MAC CE).

[0390] In the second embodiment, PUSCH can also be scheduled via a single DCI.

[0391] Multiple (e.g., two) SRS resource sets for a specific purpose (e.g., codebook (CB) / non-codebook (NCB)) can also be configured for the UE. In this embodiment, the SRS resource set can also be an SRS resource set used for that specific purpose.

[0392] Implementation Method 2-1

[0393] UEs can also be scheduled / activated / triggered using specific DCIs for PUSCH.

[0394] The specific DCI can be, for example, a DCI for scheduling PUSCH (e.g., DCI format 0_1 / 0_2), or a DCI for at least one of a DL license (DG) and a type 2 setting license (CG) for dynamically scheduling PUSCH.

[0395] For the same PUSCH, the UE can also transmit PUSCHs with different TCI states applied in at least the same time domain (e.g., time resources / symbols / time slots / sub-time slots).

[0396] The UE can also determine the indication (joint / UL) TCI status applied in the PUSCH / PUSCH antenna port / PUSCH transmission opportunity based on specific fields contained in the DCI.

[0397] The UE can also use this specific field to determine the switching between single TRP PUSCH transmission and SFN STxMP PUSCH transmission.

[0398] This specific field can be, for example, an SRS resource set indicator field or a new field defined after Rel.18.

[0399] This particular field can also be specified by a specific number of bits (e.g., 2 bits).

[0400] The UE can also determine whether to switch between single TRP PUSCH transmission and SFN STxMP PUSCH transmission based on the presence or absence of a specific field within a specific number of bits in the DCI. For example, if the specific field within the specific number of bits exists in the DCI, the UE can perform the necessary checks for the switch. If the specific field within the specific number of bits does not exist in the DCI, the UE can also determine / presume not to perform the switch.

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

[0402] For example, if the code point of that particular field shows a first value (e.g., "00"), the UE may also transmit a PUSCH using a TRP (single TRP) associated with the first SRS resource set.

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

[0404] For example, if the code point of that particular field shows a second value (e.g., "01"), the UE can also transmit a PUSCH using a TRP (single TRP) associated with the second SRS resource set.

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

[0406] For example, if the code point of a particular field shows a third value (e.g., "10"), the UE can also transmit the PUSCH involved in STxMP using SFN.

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

[0408] For example, if the code point of that particular field shows a fourth value (e.g., "11"), the UE can also transmit the PUSCH involved in STxMP using SFN.

[0409] Operations relating to the code points (first to fourth values) of this particular field can be applied to all code points or only to a subset of code points (e.g., first to third values). For example, if only the code points of the first to third values ​​are used / supported, the code point of the fourth value can be reserved or used for other purposes.

[0410] For example, when only a subset of code points are applied, an association between the SRS resource set and the TCI status indicator is required.

[0411] The UE can also determine the association between the SRS resource set and the TCI indication state based on specific rules (e.g., predefined specifications).

[0412] For example, the UE may also envision / expect the first SRS resource set to be associated with the first indication TCI state, and the second SRS resource set to be associated with the second indication TCI state.

[0413] The UE can also determine the association between the SRS resource set and the TCI indication state based on higher-layer signaling (e.g., RRC / MAC CE).

[0414] For example, the RRC parameters of the SRS resource set may also contain information indicating either the first or second TCI indication state. The UE may also use this information to determine the association between the SRS resource set and the TCI indication state.

[0415] Figure 18 This diagram illustrates an example of an application for indicating the TCI status according to the second embodiment. Figure 18 In the example shown, the UE uses SFN to transmit layer 1 and 2 of PUSCH in the same time domain.

[0416] exist Figure 18In the example shown, when the code point of a specific field contained in the DCI is “10” / “11”, the UE applies the first indication TCI state and the second indication TCI state for all layers (layer 1 and 2) and uses SFN to send PUSCH.

[0417] According to implementation method 2-1, it is possible to appropriately switch between a single TRP PUSCH and a PUSCH utilizing SFN and STxMP.

[0418] Implementation Method 2-2

[0419] In implementation 2-2, the mapping / association of at least two of the following is described: SRS resource set (index of SRS resource set), PUSCH port / layer (index of PUSCH port / layer), and indicator (joint / UL) TCI status (index of indicator (joint / UL) TCI status).

[0420] The UE can also determine the mapping / association based on the specific fields in Implementation Method 2-1 above.

[0421] The UE can also determine the mapping / association by following the implementation methods 2-2-1 / 2-2-2 below.

[0422] [Implementation Method 2-2-1]

[0423] The code point of a specific field can also indicate a first value (e.g., "00") / a second value (e.g., "01").

[0424] [[Option 2-2-1-1]]

[0425] When the code point of a specific field shows a first value (e.g., "00"), the UE may also assume / determine that: a first indication (joint / UL) TCI state, a first SRS resource set, and multiple (e.g., all) layers are associated.

[0426] At this point, the UE can also determine that it is sending a single TRP PUSCH.

[0427] When a code point in a specific field indicates a second value (e.g., "01"), the UE may also assume / determine that: a second indication (joint / UL) TCI state, a second SRS resource set, and multiple (e.g., all) layers are associated.

[0428] At this point, the UE can also determine that a single TRP PUSCH has been sent.

[0429] Figure 19 This is a diagram illustrating an example of the TCI status, SRS resource set, and layer associations involved in option 2-2-1-1. Figure 19In the example shown, when the code point of a specific field shows "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. Furthermore, when the code point of a specific field shows "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.

[0430] [[Options 2-2-1-2]]

[0431] When the code point of a specific field shows a first value (e.g., "00"), the UE may also assume / determine that: a first indication (joint / UL) TCI state, a second SRS resource set, and multiple (e.g., all) layers are associated.

[0432] At this point, the UE can also determine that a single TRP PUSCH has been sent.

[0433] When a code point in a specific field indicates a second value (e.g., "01"), the UE may also assume / determine that: a second indication (joint / UL) TCI state, a first SRS resource set, and multiple (e.g., all) layers are associated.

[0434] At this point, the UE can also determine that it is sending a single TRP PUSCH.

[0435] [Implementation Method 2-2-2]

[0436] The code point of a specific field can also indicate a third value (e.g., "10") / a fourth value (e.g., "11").

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

[0438] At this point, the UE can also determine to send a PUSCH using STxMP with SFN.

[0439] When the code point of a specific field shows a fourth value (e.g., "11"), the UE may also assume / determine that: the first indication (joint / UL) TCI state, the second SRS resource set, and multiple (e.g., all) layers are associated, and the second indication (joint / UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated.

[0440] At this point, the UE can also determine that the STxMP PUSCH being sent by SDM is being sent.

[0441] Figure 20 This is a diagram illustrating an example of the association between the TCI status, SRS resource set, and layers involved in implementation method 2-2-2. Figure 20 In the example shown, when the code point of a specific field shows "10", the UE determines that: the first indication (joint / UL) TCI state, the first SRS resource set, and all layers are associated; the second indication (joint / UL) TCI state, the second SRS resource set, and all layers are associated. Furthermore, when the code point of a specific field shows "11", the UE determines that: the first indication (joint / UL) TCI state, the second SRS resource set, and all layers are associated; the second indication (joint / UL) TCI state, the first SRS resource set, and all layers are associated.

[0442] Additionally, in at least one option of implementation 2-2-2, the fourth value (e.g., "11") may also be reserved (or may not be used).

[0443] According to implementation method 2-2, the associations of SRS resource set, PUSCH port / layer and TCI status can be appropriately specified.

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

[0445] <Third Implementation Method>

[0446] The third implementation relates to the indication of TCI status applied in UL signals / channels (UL transmissions) utilizing a single frequency network (SFN).

[0447] In the third embodiment, the UL signal / channel can also be, for example, a PUCCH.

[0448] In the third embodiment, the PUCCH can also be, for example, an STxMP of the PUCCH using SFN. The PUCCH involved in the STxMP using SFN can also be configured for the UE. This configuration can also be performed using higher-layer signaling (RRC / MAC CE).

[0449] In the third embodiment, the PUCCH can also be scheduled / triggered by a single DCI. The PUCCH in the third embodiment can also be a PUCCH corresponding to a single DCI.

[0450] Implementation Method 3-1

[0451] The UE can also determine the TCI status of the indication (joint / UL) applied in the PUCCH based on higher-layer signaling (RRC / MAC CE) / DCI.

[0452] The UE can also determine whether the PUCCH that is set / indicated is a PUCCH that utilizes SFN based on higher-layer signaling (RRC / MAC CE) / DCI.

[0453] In other words, the UE can also determine the handover between the STxMP PUCCH using SFN and other PUCCHs (e.g., single TRP PUCCH) based on higher-layer signaling (RRC / MAC CE) / DCI.

[0454] For a PUCCH resource, one or more (e.g., two) combined / UL TCI states can also be indicated (or associated). For example, for a PUCCH resource, a first combined / UL TCI state, a second combined / UL TCI state, and either of the two can also be indicated (or associated) using RRC signaling.

[0455] Then, the UE can also use specific fields contained in the DCI that schedules / activates / triggers the PUCCH (e.g., the PUCCH Resource Indicator (PRI) field) to determine the PUCCH resource.

[0456] At this time, if the UE is indicated (associated) with multiple (e.g., 2) combined / ULTCI states in the PUCCH resources used for UCI transmission, the UE may also determine to perform SFN PUCCH transmission or (as specified in Rel.17) repetition of PUCCH TDM transmission.

[0457] Furthermore, if a combined / UL TCI state is indicated (associated) in the PUCCH resource used by the UE for UCI transmission, the UE can also determine whether to perform the transmission involved in a single TRP PUCCH.

[0458] At this time, the UE can also determine either a single TRP PUCCH or a single DCI-based PUCCH TDM based on the number of repetitions of the set / indicated PUCCH.

[0459] In cases where SFN PUCCH transmission and (dynamic) switching of PUCCH TDM repetition (as specified in Rel.17) are supported, it is necessary to determine which one to perform.

[0460] For example, the UE can also determine whether to send SFNPUCCH or repetition of Rel.17 PUCCH TDM based on higher-layer signaling (RRC / MAC CE) for each PUCCH resource.

[0461] For example, each PUCCH resource (PUCCH resource settings) can be configured to either SFN PUCCH transmission or (as specified in Rel. 17) PUCCH TDM repetition. Switching of PUCCH resources can also be done using specific fields (e.g., the PRI field).

[0462] Furthermore, for example, the UE can also determine whether to perform an SFN PUCCH transmission or a repetition of PUCCH TDM (as specified in Rel. 17) based on the number of repetitions indicated for the PUCCH resource. Switching of PUCCH resources can also use specific fields (e.g., the PRI field).

[0463] For example, the UE can determine to perform SFN PUCCH transmission even without being instructed to repeat. The UE can also determine to perform PUCCH TDM repetition even when instructed to repeat a number greater than 1.

[0464] Therefore, when it is impossible to ensure the repeated use of PUCCH for scheduling multiple time slots / sub-time slots for NW / base station scheduling, SFN PUCCH can be used to perform scheduling that matches the resource status.

[0465] In this disclosure, the repetition count of a PUCCH can also be set per PUCCH resource. Furthermore, the repetition count of a PUCCH can also be set publicly for multiple (e.g., all) PUCCH resources within a CC / BWP.

[0466] Furthermore, for example, the UE can also determine whether to perform SFNPUCCH transmission or repetition of PUCCH TDM (as specified in Rel. 17) based on specific fields contained in the DCI (Scheduling / Triggering DCI). Regarding this specific field, either new fields specified after Rel. 18 can be used, or existing fields (as specified up to Rel. 17) can be reused.

[0467] Furthermore, for example, for a UE, if a repeat count greater than 1 is indicated / set and an SFN PUCCH is set, the UE may ignore the indication / setting of the repeat count and determine / treat it as a repeat count of 1.

[0468] Furthermore, for example, the UE may not assume that the SFN PUCCH is set and that the number of repetitions is set / indicated to be greater than 1.

[0469] Furthermore, for example, if a repetition number greater than 1 is set / indicated and an SFN PUCCH is set, the UE can also perform repeated transmissions for the SFN PUCCH based on that repetition number.

[0470] It may also not support SFN PUCCH transmission and (dynamic) switching of PUCCH TDM repetition (as specified in Rel.17).

[0471] In this case, either SFN PUCCH transmission or (as specified in Rel. 17) PUCCH TDM repetition can also be configured for the UE.

[0472] This setting can also be done per BWP / CC.

[0473] Even without this setting, the UE can determine whether to perform a single TRP PUCCH or a single DCI-based PUCCH TDM. In this case, the UE may not expect to be indicated with multiple (e.g., 2) combined / UL TCI states in each PUCCH (resource).

[0474] Even without this setting, the UE can determine whether to perform a single TRP PUCCH or a single DCI-based PUCCH TDM. When multiple (e.g., two) combined / UL TCI states are indicated to the UE, the UE can also select a specific indication TCI state (e.g., the first (or second) indication (combined / UL) TCI state).

[0475] According to implementation method 3-1, it is possible to appropriately switch between PUCCH transmissions using STxMP of SFN and other PUCCH transmissions.

[0476] Implementation Method 3-2

[0477] The UE can also support PUCCH cell handover.

[0478] The settings involved in PUCCH (e.g., SFN PUCCH, (Rel.17) PUCCH TDM repeat, PUCCH TDM repeat based on single DCI, and any of the settings for single TRP PUCCH) can also be set per cell / CC / BWP / cell group.

[0479] When the settings involved in PUCCH differ for each cell / CC / BWP / cell group, if a PUCCH cell handover is performed, it is necessary to determine which cell / CC / BWP / cell group settings the UE should follow.

[0480] [Option 3-2-1]

[0481] The UE can also send PUCCH according to the settings in the cell / CC / BWP / cell group where the PDSCH is sent.

[0482] Figure 21 This diagram illustrates an example of PUCCH transmission according to Implementation Method 3-2. Figure 21 In the example shown, DL CC (cell), PCell, and PUCCH SCell#1 are configured, and DCI and PDSCH are received in DL CC (cell).

[0483] exist Figure 21 In the example shown, the DCI includes a field indicating the timing of HARQ-ACK feedback and a PUCCH cell indicator field. The field indicating the timing of HARQ-ACK feedback shows K1=2, and the PUCCH cell indicator field shows PUCCHSCell#1 as the target cell.

[0484] At this point, the UE determines that the time slot following the second time slot (time slot #3) in PUCCH SCell #1, starting from the time slot where the PDSCH is received, is the time slot for transmitting HARQ-ACK for the PDSCH. The UE then switches the time slot for transmitting the PUCCH from PCell to PUCCH SCell #1.

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

[0486] [Option 3-2-2]

[0487] The UE can also send PUCCH according to the settings in the cell / CC / BWP / cell group (triggering cell / CC / BWP / cell group) where the DCI is sent.

[0488] exist Figure 21 In the example shown, in option 3-2-2, the UE transmits the PUCCH in PUCCH SCell#1 according to the settings in the cell where the DCI is transmitted (i.e., DL CC).

[0489] [Option 3-2-3]

[0490] The UE can also send PUCCH according to the settings in the cell / CC / BWP / cell group where PUCCH is triggered.

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

[0492] [Options 3-2-4]

[0493] The UE can also send PUCCH according to the settings in the cell / CC / BWP / cell group where the PUCCH is actually sent.

[0494] exist Figure 21 In the example shown, in option 3-2-4, the UE transmits the PUCCH in PUCCH SCell#1 according to the settings in the cell (i.e., PUCCH SCell) where the PUCCH is transmitted.

[0495] In addition, PUCCH cell handover scheme 1 was used as an example in the above options, but PUCCH cell handover scheme 2 can also be applied appropriately.

[0496] According to implementation method 3-2, PUCCH transmission can be performed appropriately even during PUCCH cell handover.

[0497] According to the third embodiment described above, the operations involved in the PUCCH using STxMP of SFN can be performed appropriately.

[0498] <Supplement>

[0499] [Information notification to UE]

[0500] The notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE in the above-described embodiments (in other words, the reception of any information from the BS in the UE) can also be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals) or combinations thereof.

[0501] In the case where the above notification is made through MAC CE, the MAC CE can also be identified by including a new Logical Channel ID (LCID) that is not specified in the existing specifications in the MAC subheader.

[0502] When the above notification is made through a DCI, the notification may also be made through specific fields of the DCI, the scrambled Radio Network Temporary Identifier (RNTI) used to assign Cyclic Redundancy Check (CRC) bits to the DCI, the format of the DCI, etc.

[0503] Furthermore, the notification of any information to the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0504] [Notification from UE]

[0505] The notification of any information from the UE (to the NW) in the above embodiments (in other words, the transmission / reporting of any information from the UE to the BS) can also be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MACCE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals) or combinations thereof.

[0506] In the case where the above notification is made through a MAC CE, the MAC CE can also be identified by including a new LCID that is not specified in the existing specification in the MAC subheader.

[0507] In the case where the above notification is made through UCI, the above notification may also be sent using PUCCH or PUSCH.

[0508] Furthermore, the notification of any information from the UE in the above embodiments can also be performed periodically, semi-persistently, or non-periodically.

[0509] [Regarding the application of each implementation method]

[0510] At least one of the above-described implementation methods can also be applied to situations where specific conditions are met. These specific conditions can be specified in the specification or notified to the UE / BS using higher-layer signaling / physical layer signaling.

[0511] At least one of the above-described implementation methods may also be applied only to UEs that have reported a specific UE capability or support that specific UE capability.

[0512] This specific UE capability can also represent at least one of the following:

[0513] • Supports specific processing / operation / control / information for at least one of the above implementations (e.g., STxMP related to PUSCH / PUCCH);

[0514] • Supports STxMP PUSCH SDM;

[0515] • Supports STxMP PUSCH SFN;

[0516] • Supports STxMP PUCCH SFN;

[0517] • Supports PUCCH cell handover;

[0518] • The number of panels that can be sent simultaneously.

[0519] Furthermore, the aforementioned specific UE capabilities can be capabilities that are applied across the entire frequency range (commonly regardless of frequency), capabilities that are applied to each frequency (e.g., one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), capabilities that are applied to each frequency range (e.g., Frequency Range 1 (FR1)), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities that are applied to each subcarrier spacing (SCS) or capabilities that are applied to each feature set (FS) or feature set per component-carrier (FSPC)

[0520] Furthermore, the aforementioned specific UE capabilities can be either capabilities that are applied across all duplex modes (common regardless of the duplex mode) or capabilities for each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0521] Furthermore, at least one of the above-described embodiments can also be applied to situations where the UE is set / activated / triggered by higher-layer signaling / physical layer signaling to specific information associated with the above-described embodiments (or to perform actions of the above-described embodiments). For example, this specific information may be information indicating the activation of STxMP PUSCH SDM / STxMP PUSCH SFN / STxMP PUCCH SFN operations, arbitrary RRC parameters for a specific version (e.g., Rel. 18 / 19), etc.

[0522] The UE may also apply Rel.15 / 16 operations if it does not support at least one of the above-mentioned specific UE capabilities or if the above-mentioned specific information is not set.

[0523] (Note A)

[0524] With respect to one embodiment of this disclosure, the following invention is noted.

[0525] [Note A-1]

[0526] A terminal having:

[0527] The receiving unit receives downlink control information (DCI) from the Physical Uplink Shared Channel (PUSCH); and

[0528] The control unit determines, based on specific fields contained in the DCI, which of the following is the PUSCH: multiple PUSCHs that are spatially multiplexed and transmitted in at least the same time domain, and a PUSCH oriented towards a single transmit / receive point.

[0529] [Note A-2]

[0530] The terminal as described in Appendix A-1, wherein,

[0531] When the code point of the specific field shows a first value, the control unit determines that the PUSCH is a PUSCH oriented towards the transmit / receive point corresponding to the first SRS resource set. When the code point of the specific field shows a second value, the control unit determines that the PUSCH is a PUSCH oriented towards the transmit / receive point corresponding to the second SRS resource set.

[0532] [Note A-3]

[0533] The terminal as described in Appendix A-1 or Appendix A-2, wherein,

[0534] If the code point of the specific field shows a third or fourth value, the control unit determines that the PUSCH is the PUSCH that is spatially multiplexed and transmitted in at least the same time domain.

[0535] [Note A-4]

[0536] The terminal as described in any of Notes A-1 to A-3, wherein,

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

[0538] (Note B)

[0539] With respect to one embodiment of this disclosure, the following invention is noted.

[0540] [Note B-1]

[0541] A terminal having:

[0542] The receiving unit receives downlink control information (DCI) from the Physical Uplink Shared Channel (PUSCH); and

[0543] The control unit determines, based on specific fields contained in the DCI, which of the following is the PUSCH: multiple PUSCHs transmitted in at least the same time domain using a single frequency network (SFN), and a PUSCH oriented towards a single transmit / receive point.

[0544] [Postscript B-2]

[0545] The terminal as described in Appendix B-1, wherein,

[0546] When the code point of the specific field shows a first value, the control unit determines that the PUSCH is a PUSCH oriented towards the transmit / receive point corresponding to the first SRS resource set. When the code point of the specific field shows a second value, the control unit determines that the PUSCH is a PUSCH oriented towards the transmit / receive point corresponding to the second SRS resource set.

[0547] [Note B-3]

[0548] The terminal as described in Appendix B-1 or Appendix B-2, wherein,

[0549] If the code point of the specific field shows a third value, the control unit determines that the PUSCH is a plurality of PUSCHs that are transmitted using the SFN in at least the same time domain.

[0550] [Postscript B-4]

[0551] The terminal as described in any of Notes B-1 to B-3, wherein,

[0552] The control unit is envisioned to be such that, for the code point of the specific field, the fourth value is not used.

[0553] (Note C)

[0554] With respect to one embodiment of this disclosure, the following invention is noted.

[0555] [Note C-1]

[0556] A terminal having:

[0557] The receiving unit receives the settings 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

[0558] The control unit determines, based on the number of joint or ULTCI states associated with the PUCCH resource indicated using the PRI field, whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted in at least the same time domain using a single-frequency network (SFN).

[0559] [Note C-2]

[0560] The terminal as described in Appendix C-1, wherein,

[0561] If there are multiple unions or UL TCI states associated with the indicated PUCCH resource, the control unit determines that the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted using SFN in at least the same time domain.

[0562] [Note C-3]

[0563] The terminal as described in Appendix C-1 or Appendix C-2, wherein,

[0564] The receiving unit also uses higher-layer signaling to receive settings related to time-division multiplexed PUCCH cycles or PUCCHs using SFN.

[0565] The control unit, when there are multiple unions or UL TCI states associated with the indicated PUCCH resource, determines, based on the settings, whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted using SFN in at least the same time domain, or a repeated PUCCH that is time-division multiplexed.

[0566] [Note C-4]

[0567] The terminal as described in any of Notes C-1 to C-3, wherein,

[0568] The receiving unit also receives information related to the repetition count of the PUCCH.

[0569] If the number of joint or UL TCI states associated with the indicated PUCCH resource is multiple, the control unit, based on the information, determines whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted using SFN in at least the same time domain, or a repeated PUCCH that is time-division multiplexed.

[0570] (Note D)

[0571] With respect to one embodiment of this disclosure, the following invention is noted.

[0572] [Postscript D-1]

[0573] A terminal having:

[0574] The receiving unit receives the settings related to the Physical Uplink Control Channel (PUCCH) for each cell, and receives downlink control information (DCI) for scheduling the Physical Downlink Shared Channel (PDSCH); and

[0575] The control unit, based on the specific cell's PUCCH-related settings, determines the PUCCH used to send the Hybrid Automatic Repeat reQuest ACK (HARQ-ACK) corresponding to the PDSCH.

[0576] The PUCCH-related settings for each cell are any of the following: multiple PUCCHs transmitted in at least the same time domain using a single-frequency network (SFN), repeated time-division multiplexed PUCCHs, repeated time-division multiplexed PUCCHs based on a single DCI, and PUCCHs oriented towards a single transmit / receive point.

[0577] [Postscript D-2]

[0578] The terminal as described in Appendix D-1, wherein,

[0579] The control unit determines the PUCCH used to send the HARQ-ACK based on the PUCCH-related settings in the cell receiving the PDSCH.

[0580] [Postscript D-3]

[0581] The terminal as described in Appendix D-1 or Appendix D-2, wherein,

[0582] The control unit determines the PUCCH used to send the HARQ-ACK based on the PUCCH-related settings in the cell receiving the DCI.

[0583] [Postscript D-4]

[0584] The terminal as described in any of notes D-1 to D-3, wherein,

[0585] The control unit determines the PUCCH used to send the HARQ-ACK based on the PUCCH-related settings in the cell that sends the HARQ-ACK.

[0586] (Wireless communication system)

[0587] The structure of a wireless communication system according to one embodiment of this disclosure will now be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0588] Figure 22This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 (also referred to simply as System 1) may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5GNR) as standardized by the Third Generation Partnership Project (3GPP).

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

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

[0591] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0592] The wireless communication system 1 may also include a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration and number of each cell and the user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0593] User terminal 20 may also connect to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0594] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands, definitions, etc. of FR1 and FR2 are not limited to these; for example, FR1 can also correspond to a frequency band higher than FR2.

[0595] In addition, in each CC, the user terminal 20 may also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) for communication.

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

[0597] Base station 10 may also be connected to core network 30 via other base stations 10 or directly. Core network 30 may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0598] The core network 30 may also include, for example, user plane functions (UPF), access and mobility management functions (AMF), session management functions (SMF), unified data management (UDM), application functions (AF), data network (DN), location management functions (LMF), and network functions (NF) such as operation, administration and maintenance (OAM). Alternatively, a single network node may provide multiple functions. Furthermore, communication with external networks (e.g., the Internet) may also be conducted via the DN.

[0599] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0600] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0601] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be used in the wireless access methods of UL and DL.

[0602] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0603] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0604] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via the PDSCH. User data and high-level control information can also be transmitted via the PUSCH. In addition, Master Information Blocks (MIBs) can also be transmitted via the PBCH.

[0605] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0606] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

[0607] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0608] A search space can also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" etc. disclosed herein can be rewritten interchangeably.

[0609] The PUCCH can also transmit uplink control information (uplink control information (UCI)) that includes at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat Request ACK Knowledge (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). The PRACH can also transmit random access preambles used for establishing connections with the cell.

[0610] Additionally, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, it may be stated that the word "physical" is not included at the beginning of various channels.

[0611] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. In wireless communication system 1, DL-RS can also transmit cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), and phase tracking reference signals (PTRS).

[0612] Synchronization signals can be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0613] Furthermore, as an uplink reference signal (UL-RS), measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS) can also be transmitted in the wireless communication system 1. Additionally, DMRS can also be referred to as a user terminal-specific reference signal (UE-specific reference signal).

[0614] (Base station)

[0615] Figure 23 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0616] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the base station 10 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0617] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0618] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0619] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 can be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0620] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0621] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0622] The transmitting / receiving unit 120 can also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 can also receive the aforementioned uplink channel, uplink reference signal, etc.

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

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

[0625] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing (filtering processing), Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0626] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0627] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, and demodulate the signals of the wireless frequency band received through the transmitting and receiving antenna 130 into the baseband signal.

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

[0629] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal-to-Interference plus Noise Ratio (SINR), Signal-to-Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results can also be output to the control unit 110.

[0630] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30 (e.g., the network node providing the NF), other base stations 10, etc., and can also acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

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

[0632] The transmit / receive unit 120 may also transmit downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH). The control unit 110 may also use specific fields contained in the DCI to indicate which of the following the PUSCH is: multiple PUSCHs that are spatially multiplexed and transmitted in at least the same time domain, and a PUSCH oriented towards a single transmit / receive point (first embodiment).

[0633] The transmitting / receiving unit 120 may also transmit downlink control information (DCI) for scheduling the Physical Uplink Shared Channel (PUSCH). The control unit 110 may also use specific fields contained in the DCI to indicate which of the following the PUSCH is: multiple PUSCHs transmitted in at least the same time domain using a single frequency network (SFN), and a PUSCH oriented towards a single transmitting / receiving point (second embodiment).

[0634] The transmitting / receiving unit 120 may also transmit settings for Physical Uplink Control Channel (PUCCH) resources associated with one or more Associated or Uplink (UL) Transmission Configuration Indication (TCI) states, and transmit Downlink Control Information (DCI) including a PUCCH Resource Indicator (PRI) field. The control unit 110 may also indicate, based on the number of Associated or UL TCI states associated with the PUCCH resources indicated using the PRI field, whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted in at least the same time domain using a single-frequency network (SFN) (third embodiment).

[0635] The transmit / receive unit 120 may also transmit settings related to the Physical Uplink Control Channel (PUCCH) for each cell and transmit Downlink Control Information (DCI) that schedules the Physical Downlink Shared Channel (PDSCH). The control unit 110 may also use the PUCCH-related settings of a specific cell to instruct the transmission of a PUCCH corresponding to the PDSCH using a Hybrid Automatic Repeat reQuest ACK knowledgement (HARQ-ACK). The PUCCH-related settings for each cell may also be any of the following: 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 PUCCH oriented towards a single transmit / receive point (third embodiment).

[0636] (User terminal)

[0637] Figure 24This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided as one or more.

[0638] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0639] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

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

[0641] The transmitting / receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0642] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0643] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0644] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

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

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

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

[0648] Furthermore, whether or not to apply DFT processing can be based on the settings of transform precoding. For a certain channel (e.g., PUSCH), if transform precoding is enabled, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above in order to transmit the channel using the DFT-s-OFDM waveform. If not, the transmit / receive unit 220 (transmit processing unit 2211) can perform the above transmission processing without performing DFT processing.

[0649] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0650] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

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

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

[0653] Additionally, the measurement unit 223 can also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources can be, for example, non-zero power (NZP) CSI-RS resources. Furthermore, the measurement unit 223 can also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources can be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. Additionally, CSI-IM can also be referred to as CSI-Interference Management (IM), and can be interchanged with zero power (ZP) CSI-RS. Furthermore, in this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

[0654] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one transmitting / receiving unit 220 and transmitting / receiving antenna 230.

[0655] The transmitting and receiving unit 220 can also receive downlink control information (DCI) that schedules the Physical Uplink Shared Channel (PUSCH). The control unit 210 can also determine, based on specific fields contained in the DCI, which of the following is the PUSCH: multiple PUSCHs that are spatially multiplexed and transmitted in at least the same time domain, and a PUSCH oriented towards a single transmitting and receiving point (first embodiment).

[0656] When the code point of the specific field shows a first value, the control unit 210 can also determine that the PUSCH is a PUSCH for the transmit / receive point corresponding to the first probe reference signal (SRS) resource set. When the code point of the specific field shows a second value, the control unit 210 can also determine that the PUSCH is a PUSCH for the transmit / receive point corresponding to the second SRS resource set (first embodiment).

[0657] If the code point of the specific field shows a third or fourth value, the control unit 210 may also determine that the PUSCH is the PUSCH that is spatially multiplexed and transmitted in at least the same time domain (first embodiment).

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

[0659] The transmitting and receiving unit 220 can also receive downlink control information (DCI) that schedules the Physical Uplink Shared Channel (PUSCH). The control unit 210 can also determine, based on specific fields contained in the DCI, which of the following is the PUSCH: multiple PUSCHs transmitted in at least the same time domain using a single frequency network (SFN), and a PUSCH oriented towards a single transmitting and receiving point (second embodiment).

[0660] When the code point of the specific field shows a first value, the control unit 210 can also determine that the PUSCH is a PUSCH for the transmit / receive point corresponding to the first probe reference signal (SRS) resource set. When the code point of the specific field shows a second value, the control unit 210 can also determine that the PUSCH is a PUSCH for the transmit / receive point corresponding to the second SRS resource set (second embodiment).

[0661] If the code point of the specific field shows a third value, the control unit 210 may also determine that the PUSCH is a plurality of PUSCHs that are transmitted using the SFN in at least the same time domain. (Second embodiment).

[0662] The control unit 210 can also be conceived as follows: for the code point of the specific field, the fourth value is not used. (Second embodiment).

[0663] The transmit / receive unit 220 can also receive settings for Physical Uplink Control Channel (PUCCH) resources associated with one or more Associated or Uplink (UL) Transmission Configuration Indication (TCI) states, and receive Downlink Control Information (DCI) including a PUCCH Resource Indicator (PRI) field. The control unit 220 can also determine, based on the number of Associated or UL TCI states associated with the PUCCH resources indicated using the PRI field, whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted in at least the same time domain using a single-frequency network (SFN) (third embodiment).

[0664] If there are multiple unions or UL TCI states associated with the indicated PUCCH resource, the control unit 210 may also determine that the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted using SFN in at least the same time domain (third embodiment).

[0665] The transmit / receive unit 220 can also use higher-layer signaling to receive settings related to time-division multiplexed PUCCH repetitions or PUCCHs utilizing SFN. The control unit 210 can also, based on the settings, determine whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted in at least the same time domain using SFN, or a time-division multiplexed PUCCH repetition (third embodiment), when there are multiple union or UL TCI states associated with the indicated PUCCH resource.

[0666] The transmitting and receiving unit 220 can also receive information related to the number of repetitions of the PUCCH. The control unit 210 can also, based on the information, determine whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted using SFN in at least the same time domain, or a repetition of the time-division multiplexed PUCCH (third embodiment), when there are multiple unions or UL TCI states associated with the indicated PUCCH resource.

[0667] The transmit / receive unit 220 can also receive the settings related to the Physical Uplink Control Channel (PUCCH) for each cell, and receive downlink control information (DCI) for scheduling the Physical Downlink Shared Channel (PDSCH). The control unit 210 can also determine, based on the PUCCH-related settings of a specific cell, the PUCCH to be transmitted for the Hybrid Automatic Repeat reQuest ACK knowledgement (HARQ-ACK) corresponding to the PDSCH. The PUCCH-related settings for each cell can also be any of the following: multiple PUCCHs transmitted in at least the same time domain using a single frequency network (SFN), repeated time-division multiplexed PUCCHs, repeated time-division multiplexed PUCCHs based on a single DCI, and PUCCHs oriented towards a single transmit / receive point (third embodiment).

[0668] The control unit 210 may also determine the PUCCH for sending the HARQ-ACK based on the PUCCH-related settings in the cell receiving the PDSCH (third embodiment).

[0669] The control unit 210 may also determine the PUCCH for sending the HARQ-ACK based on the PUCCH-related settings in the cell receiving the DCI (third embodiment).

[0670] The control unit 210 may also determine the PUCCH used to send the HARQ-ACK based on the PUCCH-related settings in the cell that sends the HARQ-ACK (third embodiment).

[0671] (Hardware structure)

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

[0673] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. Each of these, as described above, is not particularly limited in its implementation method.

[0674] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 25 This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0675] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit can be interchanged. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0676] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

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

[0678] The processor 1001 enables the operating system to operate and control the computer as a whole. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a portion of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0679] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks.

[0680] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to an embodiment of this disclosure.

[0681] Storage device 1003 may also be a computer-readable recording medium, such as a flexible disc, floppy disk, optical disk (e.g., a compact disc ROM), digital multifunction disk, Blu-ray disc, removable disk, hard disk drive, smart card, flash memory device (e.g., a card, stick, key drive), magnetic stripe, database, server, or at least one other suitable storage medium. Storage device 1003 may also be referred to as an auxiliary storage device.

[0682] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmit / receive unit 120 (220) and transmit / receive antenna 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be implemented by physically or logically separating the transmit unit 120a (220a) and the receive unit 120b (220b).

[0683] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

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

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

[0686] (Modified example)

[0687] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be interchanged. Additionally, a signal may also be a message. A reference signal can also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0688] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitute a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

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

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

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

[0692] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols in this disclosure can be interchanged.

[0693] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0694] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0695] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0696] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0697] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in 3GPPRel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0698] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

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

[0700] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0701] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0702] In addition, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0703] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0704] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0705] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Additionally, terms such as "cell" and "carrier" in this disclosure may be replaced with "BWP".

[0706] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0707] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0708] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0709] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

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

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

[0712] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB) etc.), medium access control (MAC) signaling), other signals, or combinations thereof.

[0713] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0714] Furthermore, notification of specific information (e.g., a notification of “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0715] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0716] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

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

[0718] The terms “system” and “network” as used in this disclosure are interchangeable. “Network” may also mean devices included in a network (e.g., base stations).

[0719] In this disclosure, the terms “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”, “beamwidth”, “beam angle”, “antenna”, “antenna element”, “panel”, “UE panel”, “transmitting entity”, and “receiving entity” are used interchangeably.

[0720] Furthermore, in this disclosure, the antenna port can also be rewritten with an antenna port used for any signal / channel (e.g., a DeModulation Reference Signal (DMRS) port). In this disclosure, resources can also be rewritten with resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.). Additionally, resources can also include time / frequency / symbol / space / power resources. Moreover, the spatial domain transmission filter can also include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0721] The aforementioned groups may include, for example, at least one of the following: spatial relation group, code division multiplexing (CDM) group, reference signal (RS) group, control resource set (CORESET) group, PUCCH group, antenna port group (e.g., DMRS port group), layer group, resource group, beam group, antenna group, panel group, etc.

[0722] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., can also be rewritten to each other.

[0723] Furthermore, in this disclosure, the TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state can also be rewritten to each other.

[0724] Furthermore, in this disclosure, terms such as "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", and "specific QCL type (e.g., type A, type D)" can be rewritten interchangeably.

[0725] In this disclosure, indexes, identifiers (IDs), indicators, indications, resource IDs, etc., can be interchanged. Sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0726] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) can be interchanged. "Spatial relationship information (TCI state)" can also be interchanged with "a set of spatial relationship information (TCI states)," "one or more spatial relationship information," etc. TCI state and TCI can also be interchanged. Spatial relationship information and spatial relationships can also be interchanged.

[0727] In this disclosure, the terms "Base Station (BS)", "Wireless Base Station", "Fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access Point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell Group", "Carrier", and "Component Carrier" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0728] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its overall coverage area can be divided into several smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0729] In this disclosure, the act of a base station sending information to a terminal can also be rewritten in relation to the act of the base station instructing the terminal to perform control / operation based on that information.

[0730] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0731] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0732] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a moving object, the moving object itself, etc.

[0733] The term "mobile body" refers to a movable object whose speed is arbitrary, including situations where the body is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, hot air balloons, and objects carried on them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

[0734] The mobile entity can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile entity moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0735] Figure 26This is a diagram illustrating an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a speed sensor 51, a 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.

[0736] The drive unit 41 is comprised of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also called a steering handle) that steers at least one of the front wheels 46 and the rear wheels 47 based on operation of the steering wheel by the user.

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

[0738] The signals from various sensors 50-58 include the following: current signal from current sensor 50 sensing the current of the motor; rotational speed signal of front wheel 46 / rear wheel 47 obtained by speed sensor 51; air pressure signal of front wheel 46 / rear wheel 47 obtained by air pressure sensor 52; vehicle speed signal obtained by vehicle speed sensor 53; acceleration signal obtained by acceleration sensor 54; accelerator pedal 43 depress amount signal obtained by accelerator pedal sensor 55; brake pedal 44 depress amount signal obtained by brake pedal sensor 56; shift lever 45 operation signal obtained by shift lever sensor 57; and detection signal obtained by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0739] The information service unit 59 consists of various devices for providing (outputting) various information such as driving information, traffic information, and entertainment information, including navigation systems, audio systems, speakers, displays, televisions, and radios, as well as one or more ECUs for controlling these devices. The information service unit 59 uses information obtained from external devices via the communication module 60, etc., to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

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

[0741] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning detectors (e.g., Global Navigation Satellite System (GNSS), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS), etc.), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[0743] The communication module 60 can be controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 60 can be located both inside and outside the electronic control unit 49. The external device can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or it can function as at least one of the base station 10 and user terminal 20).

[0744] The communication module 60 can also wirelessly transmit at least one of the signals input to the electronic control unit 49 from the various sensors 50-58 described above, the information obtained based on these signals, and the information based on input from an external (user) source obtained via the information service unit 59 to an external device. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 can also contain information based on the aforementioned inputs.

[0745] The communication module 60 receives various information (traffic information, signal information, workshop information, etc.) sent from external devices and displays it on the vehicle's information service unit 59. The information service unit 59 can also be referred to as an output unit that outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH).

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

[0747] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be rewritten as terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[0748] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0749] In this disclosure, actions are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. In a network containing one or more network nodes having a base station, the various operations performed for communication with a terminal can obviously be performed by the base station, one or more network nodes other than the base station (e.g., consider a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0750] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched as needed during execution. Furthermore, the processing procedures, timing sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, for the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0751] The various methods / implementations described in this disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG, where x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Futuregeneration Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from, modified, generated, or specified based on these methods. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0752] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise specified. In other words, the term "based on" means both "based on only" and "based on at least".

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

[0754] The term "determining" as used in this disclosure can encompass a wide variety of operations. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database or other data structure), and ascertaining.

[0755] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0756] That is, "judgment (decision)" can also refer to situations in which certain actions are considered as making a "judgment (decision)". Furthermore, "judgment (decision)" can also be rewritten as "assuming", "expecting", "considering", etc. In this disclosure, "judgment (decision)" can also be rewritten interchangeably with the operations described above.

[0757] Furthermore, in this disclosure, "determine / determining" can also be interchanged with "assume / assuming," "expect / expecting," "consider / considering," etc. Additionally, in this disclosure, "not assuming to proceed..." can also be interchanged with "assuming not to proceed..."

[0758] In this disclosure, "expect" can also be interchanged with "be expected." For example, "expect(s) ..." ("..." can also be expressed using a "that" clause, an indefinite "to", etc.) can be interchanged with "be expected ...." "Does not expect..." can also be interchanged with "be not expected...". Furthermore, "An apparatus A is not expected..." can also be interchanged with "Apparatus B other than apparatus A does not expect..." (for example, if apparatus A is a UE, apparatus B can also be a base station).

[0759] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0760] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connection” can also be rewritten as “access.”

[0761] In this disclosure, when two elements are connected, it is possible to consider using more than one wire, cable, printed electrical connection, etc. to be "connected" or "combined" with each other, and as several non-limiting and non-exclusive examples, to use electromagnetic energy with wavelengths having wireless frequency domain, microwave region, light (both visible and invisible) region to be "connected" or "combined" with each other.

[0762] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0763] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0764] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0765] In this disclosure, words such as "below," "less than," "above," "more," and "equal to" can be interchanged. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative degrees, and can be interchanged. Additionally, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., as expressions appended with "the i-th" (where i is any integer), are not limited to the positive, comparative, and superlative degrees, and can be interchanged (for example, "highest" can also be interchanged with "the i-th highest").

[0766] In this disclosure, "of", "for", "regarding", "related to", "associated with", etc., can also be rewritten interchangeably.

[0767] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "in response to A", "based on A", "during / while A", "before A", "at the same time as / on A", "after A", "since A", and "until A" can be rewritten interchangeably. Furthermore, A and B can be replaced with nouns, gerunds, or ordinary sentences, depending on the context. Additionally, the time difference between A and B can be approximately 0 (immediately after or immediately before). Moreover, a time offset can be applied to the time A occurs. For example, "A" can be rewritten as "before / after the time offset of A". This time offset (e.g., more than one symbol / slot) can be predetermined or determined by the UE based on the information provided.

[0768] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, occasion, resource, etc., can also be overridden.

[0769] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The description herein is for illustrative purposes only and is not intended to limit the inventions disclosed herein in any way.

Claims

1. A terminal, comprising: The receiving unit receives the configuration of Physical Uplink Control Channel (PUCCH) resources associated with one or more Joint or Uplink (UL) Transmit Configuration Indicator (TCI) states, and receives Downlink Control Information (DCI) including a PUCCH Resource Indicator (PRI) field; and The control unit determines, based on the number of joint or UL TCI states associated with the PUCCH resource indicated by the PRI field, whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted in at least the same time domain using a single-frequency network (SFN).

2. The terminal as described in claim 1, wherein, If there are multiple unions or UL TCI states associated with the indicated PUCCH resource, the control unit determines that the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted using SFN in at least the same time domain.

3. The terminal as described in claim 1, wherein, The receiving unit also uses higher-layer signaling to receive settings related to time-division multiplexed PUCCH cycles or PUCCHs using SFN. The control unit, when there are multiple unions or UL TCI states associated with the indicated PUCCH resource, determines, based on the settings, whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted using SFN in at least the same time domain, or a repeated PUCCH that is time-division multiplexed.

4. The terminal as described in claim 1, wherein, The receiving unit also receives information related to the repetition count of the PUCCH. If the number of joint or UL TCI states associated with the indicated PUCCH resource is multiple, the control unit, based on the information, determines whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted using SFN in at least the same time domain, or a repeated PUCCH that is time-division multiplexed.

5. A wireless communication method for a terminal, comprising: The steps of receiving the setting of Physical Uplink Control Channel (PUCCH) resources associated with one or more Joint or Uplink (UL) Transmit Configuration Indicator (TCI) states, and receiving Downlink Control Information (DCI) including a PUCCH Resource Indicator (PRI) field; and The step of determining 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) based on the number of joint or UL TCI states associated with the PUCCH resource indicated by the PRI field.

6. A base station, comprising: The transmitting unit transmits the settings of Physical Uplink Control Channel (PUCCH) resources associated with one or more Joint or Uplink (UL) Transmit Configuration Indicator (TCI) states, and transmits Downlink Control Information (DCI) including a PUCCH Resource Indicator (PRI) field; and The control unit, based on the number of joint or UL TCI states associated with the PUCCH resource indicated by the PRI field, indicates whether the PUCCH of the indicated PUCCH resource is one of multiple PUCCHs transmitted in at least the same time domain using a single-frequency network (SFN).

Images