WO2024209595A1 - Terminal, procédé de communication sans fil et station de base - Google Patents

Terminal, procédé de communication sans fil et station de base Download PDF

Info

Publication number
WO2024209595A1
WO2024209595A1 PCT/JP2023/014118 JP2023014118W WO2024209595A1 WO 2024209595 A1 WO2024209595 A1 WO 2024209595A1 JP 2023014118 W JP2023014118 W JP 2023014118W WO 2024209595 A1 WO2024209595 A1 WO 2024209595A1
Authority
WO
WIPO (PCT)
Prior art keywords
pucch
pusch
dci
transmission
tci
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2023/014118
Other languages
English (en)
Japanese (ja)
Inventor
祐輝 松村
聡 永田
ウェイチー スン
ジン ワン
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NTT Docomo Inc
Original Assignee
NTT Docomo Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NTT Docomo Inc filed Critical NTT Docomo Inc
Priority to JP2025512295A priority Critical patent/JPWO2024209595A5/ja
Priority to PCT/JP2023/014118 priority patent/WO2024209595A1/fr
Publication of WO2024209595A1 publication Critical patent/WO2024209595A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling

Definitions

  • This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • Non-Patent Document 1 LTE-Advanced (3GPP Rel. 10-14) was specified for the purpose of achieving higher capacity and greater sophistication over LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).
  • LTE 5th generation mobile communication system
  • 5G+ 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • NR New Radio
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • a UE will be able to use one of multiple panels (or multiple beams) for uplink (UL) transmission.
  • UL uplink
  • STxMP simultaneous Multi-panel transmission
  • TRPs Transmission/Reception Points
  • one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control UL transmission, even when UL transmission is performed using multiple panels.
  • a terminal has a receiving unit that receives settings related to a physical uplink control channel (PUCCH) for each cell and receives downlink control information (DCI) that schedules a physical downlink shared channel (PDSCH), and a control unit that determines a PUCCH for transmitting a hybrid automatic repeat request ACKnowledgement (HARQ-ACK) corresponding to the PDSCH based on the settings related to the PUCCH of a specific cell, and the settings related to the PUCCH for each cell are any of settings of multiple PUCCHs transmitted in at least the same time domain using a single frequency network (SFN), time-division multiplexed PUCCH repetition, time-division multiplexed PUCCH repetition based on a single DCI, and a PUCCH for a single transmission/reception point.
  • SFN single frequency network
  • UL transmission can be performed appropriately using multiple panels.
  • FIG. 1A and 1B show an example of a unified/common TCI framework.
  • 2A and 2B show an example of DCI-based TCI status indication.
  • FIG. 3 is a diagram illustrating an example of an association between a precoder type and a TPMI index.
  • 4A and 4B are diagrams showing an example of a single panel UL transmission.
  • 5A to 5C are diagrams showing examples of methods 1 to 3 of simultaneous UL transmission using multiple panels.
  • 6A to 6C are diagrams showing an example of a PUSCH transmission method.
  • 7A to 7C are diagrams showing other examples of the PUSCH transmission method.
  • FIG. 8 is a diagram showing an example of simultaneous UL transmission using multiple panels.
  • FIG. 9 is a diagram showing an example of simultaneous transmission of PUSCH and PUCCH.
  • FIG. 10 is a diagram showing an example of PUCCH cell switching scheme 1.
  • FIG. 11 is a diagram showing an example of PUCCH cell switching scheme 2.
  • FIG. 12 is a diagram showing another example of PUCCH cell switching scheme 2.
  • 13A-13D are diagrams showing an example of an STxMP scheme.
  • FIG. 14 is a diagram showing an example of the maximum number of layers.
  • FIG. 15 is a diagram illustrating an example of application of an indicated TCI state according to the first embodiment.
  • FIG. 16 is a diagram showing an example of association of an indication TCI state, an SRS resource set, and a layer according to option 1-3-1-1.
  • FIG. 17 is a diagram showing an example of association of an indication TCI state, an SRS resource set, and a layer according to option 1-3-2-1.
  • FIG. 18 is a diagram illustrating an example of application of an indicated TCI state according to the second embodiment.
  • FIG. 19 is a diagram showing an example of association of an indication TCI state, an SRS resource set, and a layer according to option 2-2-1-1.
  • FIG. 20 is a diagram showing an example of association between an indication TCI state, an SRS resource set, and a layer according to embodiment 2-2-2.
  • FIG. 21 is a diagram showing an example of transmission of a PUCCH according to embodiment 3-2.
  • FIG. 22 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment.
  • FIG. 23 is a diagram illustrating an example of the configuration of a base station according to an embodiment.
  • FIG. 24 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment.
  • FIG. 25 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment.
  • FIG. 26 is a diagram illustrating an example of a vehicle according to an embodiment.
  • the unified TCI framework does not specify the TCI state or spatial relationship for each channel as in Rel. 15, but instead specifies a common beam (common TCI state) and may apply it to all UL and DL channels, or a common beam for UL may apply to all UL channels and a common beam for DL may apply to all DL channels.
  • a common beam common TCI state
  • One common beam for both DL and UL, or one common beam for DL and one common beam for UL (total of two common beams) are being considered.
  • the UE may assume the same TCI state for UL and DL (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set).
  • the UE may assume different TCI states for UL and DL respectively (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).
  • the UL and DL default beams may be aligned via MAC CE based beam management (MAC CE level beam instructions).
  • the PDSCH default TCI state may be updated to match the default UL beam (spatial relationship).
  • DCI based beam management may indicate a common beam/unified TCI state from the same TCI pool (joint common TCI pool, joint TCI pool, set) for both UL and DL.
  • X (>1) TCI states may be activated by the MAC CE.
  • the UL/DL DCI may select one out of the X active TCI states.
  • the selected TCI state may be applied to both UL and DL channels/RS.
  • the TCI pool (set) may be multiple TCI states set by RRC parameters, or multiple TCI states (active TCI states, active TCI pool, set) activated by the MAC CE among multiple TCI states set by RRC parameters.
  • Each TCI state may be a QCL type A/D RS.
  • SSB, CSI-RS, or SRS may be set as the QCL type A/D RS.
  • the number of TCI states corresponding to each of one or more TRPs may be specified.
  • the number N ( ⁇ 1) of TCI states (UL TCI states) applied to UL channels/RS and the number M ( ⁇ 1) of TCI states (DL TCI states) applied to DL channels/RS may be specified.
  • At least one of N and M may be notified/configured/instructed to the UE via higher layer signaling/physical layer signaling.
  • this may mean that one UL TCI state and one DL TCI state for a single TRP are notified/configured/instructed separately to the UE (separate TCI states for a single TRP).
  • this may mean that multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs are notified/configured/instructed to the UE (separate TCI states for multiple TRPs).
  • N and M are 1 or 2, but the values of N and M may be 3 or more, and N and M may be different.
  • the RRC parameters configure multiple TCI states for both DL and UL.
  • the MAC CE may activate multiple TCI states from the configured multiple TCI states.
  • the DCI may indicate one of the activated multiple TCI states.
  • the DCI may be a UL/DL DCI.
  • the indicated TCI state may apply to at least one (or all) of the UL/DL channels/RS.
  • One DCI may indicate both UL TCI and DL TCI.
  • a point may be one TCI state that applies to both UL and DL, or it may be two TCI states that apply to UL and DL, respectively.
  • At least one of the multiple TCI states configured by the RRC parameters and the multiple TCI states activated by the MAC CE may be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool).
  • the multiple TCI states activated by the MAC CE may be referred to as an active TCI pool (active common TCI pool).
  • the higher layer parameters (RRC parameters) that set multiple TCI states may be referred to as configuration information that sets multiple TCI states, or simply as “configuration information.” Also, in this disclosure, being instructed to set one of multiple TCI states using DCI may mean receiving indication information that indicates one of the multiple TCI states included in DCI, or may simply mean receiving "instruction information.”
  • the RRC parameters configure multiple TCI states for both DL and UL (joint common TCI pool).
  • the MAC CE may activate multiple TCI states (active TCI pools) among the configured multiple TCI states. Separate active TCI pools for each of UL and DL may be configured/activated.
  • the DL DCI or new DCI format may select (indicate) one or more (e.g., one) TCI states.
  • the selected TCI state may apply to one or more (or all) DL channels/RS.
  • the DL channels may be PDCCH/PDSCH/CSI-RS.
  • the UE may determine the TCI state of each DL channel/RS using the TCI state behavior (TCI framework) of Rel. 16.
  • the UL DCI or new DCI format may select (indicate) one or more (e.g., one) TCI states.
  • the selected TCI state may apply to one or more (or all) UL channels/RS.
  • the UL channels may be PUSCH/SRS/PUCCH. Thus, different DCIs may indicate UL TCI and DL DCI separately.
  • the MAC CE/DCI will support beam activation/indication to a TCI state associated with a different physical cell identifier (PCI). Also, in Rel. 18 NR and later, it is assumed that the MAC CE/DCI will support indicative serving cell change to a cell with a different PCI.
  • PCI physical cell identifier
  • the UE can configure a list of up to 128 DLorJointTCIState configurations in PDSCH-Config.
  • the UE may 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 in the same band, it does not assume that TCI-State, SpatialRelationInfo (spatial relation information), or PUCCH-SpatialRelationInfo (PUCCH spatial relation information) in that band are set, except for SpatialRelationInfoPos (spatial relation information for position).
  • SpatialRelationInfo spatial relation information
  • PUCCH-SpatialRelationInfo PUCCH spatial relation information
  • the UE assumes that if the UE has TCI-State in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneousSpatial-UpdatedList1-r16, or simultaneousSpatial-UpdatedList2-r16, the UE does not configure DLorJointTCIState or UL-TCIState in any CC in the CC list.
  • the UE receives an activation command that is used to map up to eight TCI states and/or TCI state pairs, with one TCI state for DL channels/signals and one TCI state for UL channels/signals, to code points of the DCI field 'Transmission Configuration Indication' (TCI) for one of the CC/DL BWPs or for a set of CC/DL BWPs, if available.
  • TCI Transmission Configuration Indication
  • a set of TCI state IDs is activated for a set of CC/DL BWPs and, if available, for one of the CC/DL BWPs, the same set of TCI state IDs applies to all DL and/or UL BWPs in the indicated CC, where the applicable list of CCs is determined by the CCs indicated in the activation command.
  • the UE applies the indicated DLorJointTCIState and/or UL-TCIState to one or a set of CC/DL BWPs, and if the indicated mapping to a single TCI code point applies, the UE applies the indicated DLorJointTCIState and/or UL-TCIState to one or a set of CC/DL BWPs.
  • the UE shall assume that the QCL type A/D source RS is set in the CC/DL BWP to which the TCI state applies.
  • Unified TCI Framework supports the following modes 1 to 3: [Mode 1] MAC CE based TCI state indication [Mode 2] DCI based TCI state indication by DCI format 1_1/1_2 with DL assignment [Mode 3] DCI based TCI state indication by DCI format 1_1/1_2 without DL assignment
  • TCI State ID receives DCI format 1_1/1_2 providing indicated TCI state with Rel.
  • DCI format 1_1/1_2 may or may not be accompanied by DL assignment if one is available.
  • DCI format 1_1/1_2 does not carry a DL assignment
  • the UE can assume (verify) the following for that DCI: -
  • the CS-RNTI is used to scramble the CRC for the DCI.
  • the values of the following DCI fields are set as follows: -
  • the redundancy version (RV) field is all '1's.
  • the modulation and coding scheme (MCS) field is all '1's.
  • NDI new data indicator
  • the frequency domain resource assignment (FDRA) field is all '0's for FDRA type 0 or all '1's for FDRA type 1 or all '0's for Dynamic Switch (similar to PDCCH validation for release of DL semi-persistent scheduling (SPS) or UL grant type 2 scheduling).
  • DCI in the above Mode 2/Mode 3 may be called beam instruction DCI.
  • Rel. 15/16 if the UE does not support active BWP change via DCI, the UE will ignore the BWP indicator field.
  • a similar behavior is considered for the relationship between Rel. 17 TCI state support and the interpretation of the TCI field. It is considered that if the UE is configured with Rel. 17 TCI state, the TCI field will always be present in DCI format 1_1/1_2, and if the UE does not support TCI update via DCI, the UE will ignore the TCI field.
  • the presence or absence of a TCI field (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.
  • the TCI field in DCI format 1_1 is 0 bits if the higher layer parameter tci-PresentInDCI is not enabled, and 3 bits otherwise. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following actions: [Operation] If the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying that DCI format 1_1, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP, otherwise the UE shall assume that tci-PresentInDCI is enabled for all CORESETs in the indicated BWP.
  • the TCI field in DCI format 1_2 is 0 bit if the higher layer parameter tci-PresentInDCI-1-2 is not set, otherwise it is 1, 2 or 3 bits determined by the higher layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following actions.
  • the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP, otherwise the UE shall assume that tci-PresentInDCI-1-2 for all CORESETs in the indicated BWP is set with the same value as tci-PresentInDCI-1-2 set for the CORESET used for the PDCCH carrying that DCI format 1_2.
  • Figure 2A shows an example of a DCI-based joint DL/UL TCI status indication.
  • a TCI status ID indicating the joint DL/UL TCI status is associated with the value of the TCI field for the joint DL/UL TCI status indication.
  • FIG. 2B shows an example of a DCI-based separate DL/UL TCI status indication.
  • At least one TCI status ID is associated with the value of the TCI field for the separate DL/UL TCI status indication: a TCI status ID indicating a DL-only TCI status and a TCI status ID indicating a UL-only TCI status.
  • 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
  • TCI field values 100 to 111 are associated with both one TCI status ID for DL and one TCI status ID for UL.
  • the unified/common TCI state may mean the Rel. 17 TCI state indicated using (Rel. 17) DCI/MAC CE/RRC (indicated Rel. 17 TCI state).
  • TCI state indicates whether or not TCI is mapped to multiple types of signals (channels/RS).
  • unified/common TCI state TCI state applicable to multiple types of signals (channels/RS)
  • TCI state for multiple types of signals channels/RS
  • the indicated Rel. 17 TCI state may be shared with at least one of the UE-specific reception on PDSCH/PDCC (updated using Rel. 17 DCI/MAC CE/RRC), PUSCH of dynamic grant (DCI)/configured grant, and multiple (e.g., all) dedicated PUCCH resources.
  • the TCI state indicated by the DCI/MAC CE/RRC may be referred to as the indicated TCI state, the unified TCI state.
  • a TCI state other than the unified TCI state may refer to a Rel. 17 TCI state configured using the (Rel. 17) MAC CE/RRC (configured Rel. 17 TCI state).
  • the configured Rel. 17 TCI state, the configured TCI state, a TCI state other than the unified TCI state, and a TCI state applied to a specific type of signal (channel/RS) may be read as interchangeable.
  • the configured Rel. 17 TCI state may not be shared with at least one of the UE-specific reception in the PDSCH/PDCC (updated using Rel. 17 DCI/MAC CE/RRC), the PUSCH of the dynamic grant (DCI)/configured grant, and multiple (e.g., all) dedicated PUCCH resources.
  • the configured Rel. 17 TCI state may be configured by the RRC/MAC CE for each CORESET/resource/resource set, and may not be updated even if the indicated Rel. 17 TCI state (common TCI state) described above is updated.
  • the indicated Rel. 17 TCI state will be applied to UE-specific channels/signals (RS). It is also being considered that the UE will be notified using higher layer signaling (RRC signaling) as to whether the indicated Rel. 17 TCI state or the configured Rel. 17 TCI state will be applied to non-UE-specific channels/signals.
  • RS UE-specific channels/signals
  • RRC signaling higher layer signaling
  • the RRC parameters for the configured Rel. 17 TCI state (TCI state ID) will have the same configuration as the RRC parameters for the TCI state in Rel. 15/16. It is being considered that the configured Rel. 17 TCI state will be configured/instructed for each CORESET/resource/resource set using RRC/MAC CE. It is also being considered that the UE will make decisions regarding the configuration/instruction based on specific parameters.
  • the UE will update the indicated TCI state and the configured TCI state separately. For example, if the unified TCI state for the indicated TCI state is updated for the UE, the configured TCI state may not need to be updated. It is also being considered that the UE will make a decision about the update based on a specific parameter.
  • RRC/MAC CE higher layer signaling
  • TCI state indication for intra-cell beam indication (TCI state indication), it is being considered to support Rel. 17 TCI state indication for UE-specific CORESET and PDSCH associated with that CORESET, and non-UE-specific CORESET and PDSCH associated with that CORESET.
  • inter-cell beam indication e.g., L1/L2 inter-cell mobility
  • support for indicating Rel. 17 TCI states for UE-specific CORESETs and PDSCHs associated with the CORESETs is under consideration.
  • the legacy MAC CE/RACH signaling mechanism may be used.
  • the CSI-RS related to the Rel. 17 TCI state applied to CORESET#0 may be QCL'd with the SSB related to the serving cell PCI (physical cell ID) (similar to Rel. 15).
  • CORESETs with a common search space (CSS), and CORESETs with a CSS and a UE-specific search space (USS), whether to follow the indicated Rel. 17 TCI state may be configured for each CORESET by an RRC parameter. If the indicated Rel. 17 TCI state is not configured for that CORESET, the configured Rel. 17 TCI state may be applied to that CORESET.
  • CCS common search space
  • USS UE-specific search space
  • RRC parameters may be configured for each channel/resource/resource set to follow or not follow the indicated Rel. 17 TCI state. If the indicated Rel. 17 TCI state is not configured for that channel/resource/resource set, the configured Rel. 17 TCI state may be applied to that channel/resource/resource set.
  • the indicated TCI state by the MAC CE/DCI may apply to the following channels/RS:
  • CORESET0 If followUnifiedTCIState is set for CORESET0, the indicated TCI state is applied. Otherwise, the Rel. 15 specifications are applied for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCLed with SSB. For a CORESET with index other than 0 with USS/CSS type 3, the indicated TCI state always applies. - For a CORESET with index other than 0, with at least a CSS other than CSS type 3, configured to follow the uniform TCI state, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.
  • [PDSCH] - The indicated TCI state always applies for all UE-dedicated PDSCHs.
  • a non-UE-dedicated PDSCH PDSCH scheduled by a DCI in the CSS
  • followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules the PDSCH)
  • the indicated TCI state may apply. Otherwise, the configured TCI state for the PDSCH applies to the PDSCH.
  • followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state may depend on whether followUnifiedTCIState is set for the CORESET used to schedule the PDSCH.
  • CSI-RS For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for the CORESET of the PDCCH that triggers that A-CSI-RS), the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS applies.
  • PUSCH precoder In NR, it is considered that a UE will support at least one of Codebook (CB)-based transmission and Non-Codebook (NCB)-based transmission.
  • CB Codebook
  • NCB Non-Codebook
  • the UE will use at least a sounding reference signal (SRS) resource indicator (SRI) for measurement to determine a precoder (precoding matrix) for CB-based and/or NCB-based Physical Uplink Shared Channel (PUSCH) transmissions.
  • SRS sounding reference signal
  • SRI resource indicator
  • precoder precoding matrix
  • the UE may determine a precoder for PUSCH transmission based on the SRI, a transmitted rank indicator (Transmitted Rank Indicator (TRI)), a transmitted precoding matrix indicator (Transmitted Precoding Matrix Indicator (TPMI)), etc.
  • a transmitted rank indicator Transmitted Rank Indicator (TRI)
  • a transmitted precoding matrix indicator Transmitted Precoding Matrix Indicator (TPMI)
  • NCB-based transmission the UE may determine a precoder for PUSCH transmission based on the SRI.
  • the SRI, TRI, TPMI, etc. may be notified to the UE using Downlink Control Information (DCI).
  • DCI Downlink Control Information
  • the SRI may be specified by the SRS Resource Indicator field (SRI field) of the DCI, or by the parameter "srs-ResourceIndicator” included in the RRC information element "ConfiguredGrantConfig" of the configured grant PUSCH.
  • the TRI and TPMI may be specified by the "Precoding information and number of layers" field of the DCI.
  • the UE may report UE capability information regarding the precoder type, and the base station may set the precoder type based on the UE capability information through higher layer signaling.
  • the UE capability information may be information on the precoder type used by the UE in PUSCH transmission (which may be represented by the RRC parameter "pusch-TransCoherence").
  • higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or any combination thereof.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • the MAC signaling may be, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc.
  • the broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), etc.
  • MIB Master Information Block
  • SIB System Information Block
  • the UE may determine the precoder to be used for PUSCH transmission based on precoder type information (which may be represented by the RRC parameter "codebookSubset") included in the PUSCH configuration information (the "PUSCH-Config" information element of the RRC signaling) notified by higher layer signaling.
  • the UE may set a subset of the PMI specified by the TPMI by the codebookSubset.
  • the precoder type may be specified by any one of full coherent, partial coherent, and non-coherent, or a combination of at least two of these (e.g., may be expressed by parameters such as "fullyAndPartialAndNonCoherent” or "partialAndNonCoherent”).
  • Fully coherent may mean that all antenna ports used for transmission are synchronized (may be expressed as being able to align the phase, using the same precoder, etc.). Partially coherent may mean that some of the antenna ports used for transmission are synchronized, but those some ports cannot be synchronized with other ports. Non-coherent may mean that the antenna ports used for transmission cannot be synchronized.
  • a UE that supports a fully coherent precoder type may be assumed to support partially coherent and non-coherent precoder types.
  • a UE that supports a partially coherent precoder type may be assumed to support a non-coherent precoder type.
  • the precoder type may be interpreted as coherency, PUSCH transmission coherence, coherent type, coherence type, codebook type, codebook subset, codebook subset type, etc.
  • the UE may determine a precoding matrix from multiple precoders (which may also be called precoding matrices, codebooks, etc.) for CB-based transmission that corresponds to a TPMI index obtained from a DCI (e.g., DCI format 0_1, etc.) that schedules an UL transmission.
  • precoders which may also be called precoding matrices, codebooks, etc.
  • TPMI index obtained from a DCI (e.g., DCI format 0_1, etc.) that schedules an UL transmission.
  • Figure 3 is a diagram showing an example of the association between precoder types and TPMI indexes.
  • Figure 3 corresponds to a table of precoding matrix W for single-layer (rank 1) transmission using four antenna ports in DFT-s-OFDM (Discrete Fourier Transform spread OFDM, where transform precoding is enabled).
  • DFT-s-OFDM Discrete Fourier Transform spread OFDM, where transform precoding is enabled.
  • the UE is notified of a TPMI from 0 to 27 for single layer transmission. Also, if the precoder type is partial and noncoherent (partialAndNonCoherent), the UE is set with a TPMI from 0 to 11 for single layer transmission. If the precoder type is noncoherent (nonCoherent), the UE is set with a TPMI from 0 to 3 for single layer transmission.
  • a precoding matrix in which only one component in each column is not zero may be called a noncoherent codebook.
  • a precoding matrix in which a predetermined number (not all) of components in each column are not zero may be called a partially coherent codebook.
  • a precoding matrix in which all components in each column are not zero may be called a fully coherent codebook.
  • Noncoherent and partially coherent codebooks may be referred to as antenna selection precoders.
  • Fully coherent codebooks may be referred to as non-antenna selection precoders.
  • a codebook precoding matrix
  • RRC parameter "codebookSubset” “fullyAndPartialAndNonCoherent”
  • a terminal (user terminal, User Equipment (UE)) may receive information (SRS configuration information, for example, parameters in the RRC control element "SRS-Config") used to transmit a measurement reference signal (for example, a Sounding Reference Signal (SRS)).
  • SRS configuration information for example, parameters in the RRC control element "SRS-Config"
  • SRS-Config parameters in the RRC control element "SRS-Config”
  • the UE may receive at least one of information regarding one or more SRS resource sets (SRS resource set information, e.g., the RRC control element "SRS-ResourceSet”) and information regarding one or more SRS resources (SRS resource information, e.g., the RRC control element "SRS-Resource”).
  • SRS resource set information e.g., the RRC control element "SRS-ResourceSet
  • SRS resource information e.g., the RRC control element "SRS-Resource”
  • An SRS resource set may relate to (group together) a number of SRS resources.
  • Each SRS resource may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).
  • SRI SRS Resource Indicator
  • ID SRS Resource Identifier
  • the SRS resource set information may include an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type, and information on SRS usage.
  • SRS-ResourceSetId SRS resource set ID
  • SRS-ResourceId SRS resource set ID
  • SRS resource type SRS resource type
  • the SRS resource type may indicate any of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic CSI (A-SRS).
  • P-SRS periodic SRS
  • SP-SRS semi-persistent SRS
  • A-SRS aperiodic CSI
  • the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation) and transmit A-SRS based on an SRS request in the DCI.
  • the usage may be, for example, beam management (beamManagement), codebook (CB), noncodebook (NCB), antenna switching, etc.
  • the SRS for codebook or noncodebook usage may be used to determine a precoder for codebook-based or noncodebook-based uplink shared channel (Physical Uplink Shared Channel (PUSCH)) transmission based on the SRI.
  • PUSCH Physical Uplink Shared Channel
  • the UE may determine a precoder (precoding matrix) for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), and a Transmitted Precoding Matrix Indicator (TPMI) in the case of codebook-based transmission.
  • the UE may determine a precoder for PUSCH transmission based on the SRI in the case of non-codebook-based transmission.
  • the SRS resource information may include an SRS resource ID (SRS-ResourceId), SRS port number, SRS port number, transmit comb, SRS resource mapping (e.g., time and/or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping related information, SRS resource type, sequence ID, spatial relationship information of SRS, etc.
  • SRS resource ID SRS-ResourceId
  • SRS port number SRS port number
  • SRS port number SRS port number
  • transmit comb e.g., transmit comb
  • SRS resource mapping e.g., time and/or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.
  • SRS resource mapping e.g., time and/or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.
  • the spatial relationship information of the SRS may indicate spatial relationship information between a specific reference signal and the SRS.
  • the specific reference signal may be at least one of a Synchronization Signal/Physical Broadcast Channel (SS/PBCH) block, a Channel State Information Reference Signal (CSI-RS), and an SRS (e.g., another SRS).
  • SS/PBCH Synchronization Signal/Physical Broadcast Channel
  • CSI-RS Channel State Information Reference Signal
  • SRS e.g., another SRS.
  • the SS/PBCH block may be referred to as a Synchronization Signal Block (SSB).
  • SSB Synchronization Signal Block
  • the spatial relationship information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the above-mentioned specified reference signal.
  • the SSB index, SSB resource ID, and SSB Resource Indicator may be interchangeable.
  • the CSI-RS index, CSI-RS resource ID, and CSI-RS Resource Indicator (CRI) may be interchangeable.
  • the SRS index, SRS resource ID, and SRI may be interchangeable.
  • the spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc., corresponding to the above-mentioned specified reference signal.
  • the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter for receiving the SSB or CSI-RS (spatial domain receive filter).
  • the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.
  • the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmission filter) as the spatial domain filter (spatial domain transmission filter) for transmitting the reference SRS.
  • the UE may assume that the UE transmission beam of the reference SRS and the UE transmission beam of the target SRS are the same.
  • the UE may determine the spatial relationship of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on the value of a specific field (e.g., an SRS resource identifier (SRI) field) in the DCI. Specifically, the UE may use spatial relationship information of the SRS resource (e.g., the RRC information element "spatialRelationInfo") determined based on the value of the specific field (e.g., SRI) for PUSCH transmission.
  • a specific field e.g., an SRS resource identifier (SRI) field
  • the UE when using codebook-based transmission for PUSCH, the UE is configured by RRC with a codebook-use SRS resource set having up to two SRS resources, and one of the up to two SRS resources may be indicated by DCI (1-bit SRI field).
  • the transmission beam for PUSCH is specified by the SRI field.
  • the UE may determine the TPMI and number of layers (transmission rank) for the PUSCH based on the precoding information and number of layers field (hereinafter also referred to as the precoding information field).
  • the UE may select a precoder based on the TPMI, number of layers, etc. from an uplink codebook for the same number of ports as the number of SRS ports indicated by the upper layer parameter "nrofSRS-Ports" set for the SRS resource specified by the SRI field.
  • the UE when non-codebook-based transmission is used for PUSCH, the UE is configured by RRC with a non-codebook-used SRS resource set having up to four SRS resources, and one or more of the up to four SRS resources may be indicated by DCI (2-bit SRI field).
  • the UE may determine the number of layers (transmission rank) for the PUSCH based on the SRI field. For example, the UE may determine that the number of SRS resources specified by the SRI field is the same as the number of layers for the PUSCH. The UE may also calculate a precoder for the SRS resources.
  • the transmission beam of the PUSCH may be calculated based on (the measurement of) the configured associated CSI-RS. Otherwise, the transmission beam of the PUSCH may be specified by the SRI.
  • the UE may be configured to use codebook-based PUSCH transmission or non-codebook-based PUSCH transmission by a higher layer parameter "txConfig" indicating a transmission scheme.
  • the parameter may indicate a value of "codebook” or "non-codebook.”
  • codebook-based PUSCH (codebook-based PUSCH transmission, codebook-based transmission) may refer to PUSCH when "codebook" is configured as the transmission scheme in the UE.
  • non-codebook-based PUSCH (non-codebook-based PUSCH transmission, non-codebook-based transmission) may refer to PUSCH when "non-codebook" is configured as the transmission scheme in the UE.
  • future wireless communication systems e.g., Rel. 18 NR and later
  • simultaneous UL transmission e.g., simultaneous multi-panel UL transmission (STxMP)
  • STxMP simultaneous multi-panel UL transmission
  • TRPs transmission/reception points
  • Rel. 18 is considering simultaneous UL transmission using up to 2 TRPs/2 panels. Also, taking into account single DCI-based and multi-DCI-based multi-TRP operation, it is expected that the total number of layers will be up to 4 across all panels, and the total number of codewords will be up to 2 across all panels. Of course, the number of TRPs, panels, layers, and codewords are not limited to these.
  • At least one of the following transmission schemes A and B may be applied to the single panel UL transmission scheme or the single panel UL transmission scheme candidate.
  • the panel/UE panel may be read as a UE capability value set (e.g., UE capability value set) reported for each UE capability.
  • UE capability value set e.g., UE capability value set
  • different panels, different spatial relationships, different joint TCI states, different TPC parameters, different antenna ports, etc. may be read as mutually interchangeable terms.
  • ⁇ Transmission method A Single panel, single TRP, UL transmission>
  • a transmission scheme is used in which a UE transmits UL for one TRP from only one beam and panel at one time (FIG. 4A).
  • ⁇ Transmission method B Single panel multi-TRP UL transmission> In Rel. 17, UL transmission from only one beam and panel at one time and repeated transmission to multiple TRPs is considered (FIG. 4B).
  • the UE transmits PUSCH from panel #1 to TRP #1 (switching beams and panels), and then transmits PUSCH from panel #2 to TRP #2.
  • the two TRPs are connected via an ideal backhaul.
  • Multi-panel transmission In Rel. 18 and later, in order to improve UL throughput/reliability, support for simultaneous UL transmission using multiple panels (e.g., simultaneous multi-panel UL transmission (STxMP)) for one or more TRPs is being considered. Also, a multi-panel UL transmission scheme is being considered for a specific UL channel (e.g., PUSCH/PUCCH) etc.
  • STxMP simultaneous multi-panel UL transmission
  • codebooks of existing systems e.g., before Rel. 16
  • multi-panel UL transmission method or a candidate multi-panel UL transmission method at least one of the following methods 1 to 3 (multi-panel UL transmission methods 1 to 3) is being considered. Only one of transmission methods 1 to 3 may be supported. Multiple methods including at least one of transmission methods 1 to 3 may be supported, and one of the multiple transmission methods may be configured in the UE.
  • ⁇ Transmission method 1 Coherent multi-panel UL transmission> Multiple panels may be synchronized with each other. All layers are mapped to all panels. Multiple analog beams are directed.
  • the SRS Resource Indicator (SRI) field may be extended. This scheme may use up to 4 layers for the UL.
  • the UE maps one codeword (CW) or one transport block (TB) to L layers (PUSCH (1, 2, ..., L)) and transmits L layers from each of the two panels.
  • Panel #1 and panel #2 are coherent. Transmission method 1 can obtain diversity gain.
  • the total number of layers in the two panels is 2L. If the maximum total number of layers is 4, the maximum number of layers in one panel is 2.
  • ⁇ Transmission method 2 Non-coherent multi-panel UL transmission of one codeword (CW) or transport block (TB)> Multiple panels may not be synchronized. Different layers are mapped to different panels and one CW or TB for PUSCH from multiple panels. A layer corresponding to one CW or TB may be mapped to multiple panels.
  • the transmission scheme may use up to 4 layers or up to 8 layers for UL. If up to 8 layers are supported, the transmission scheme may support one CW or TB with up to 8 layers.
  • the UE maps 1 CW or 1 TB to k layers (PUSCH(1, 2, ..., k)) and L-k layers (PUSCH(k+1, k+2, ..., L)), transmits k layers from panel #1, and transmits L-k layers from panel #2.
  • Transmission method 2 can obtain gains through multiplexing and diversity. The total number of layers in the two panels is L.
  • ⁇ Transmission method 3 Non-coherent multi-panel UL transmission of two CWs or TBs> Multiple panels may not be synchronized. Different layers are mapped to different panels and two CWs or TBs for PUSCH from multiple panels. Layers corresponding to one CW or TB may be mapped to one panel. Layers corresponding to multiple CWs or TBs may be mapped to different panels. This transmission scheme may use up to 4 layers or up to 8 layers for UL. When supporting up to 8 layers, this transmission scheme may support up to 4 layers per CW or TB.
  • the UE maps CW#1 or TB#1 to k layers (PUSCH (1, 2, ..., k)), maps CW#2 or TB#2 to L-k layers (PUSCH (k+1, k+2, ..., L)), transmits k layers from panel #1, and transmits L-k layers from panel #2.
  • Transmission method 3 can obtain gains through multiplexing and diversity. The total number of layers in the two panels is L.
  • the base station may configure or indicate panel-specific transmission for UL transmission using UL TCI or panel ID.
  • UL TCI (UL TCI state) may be based on signaling similar to DL beam indication supported in Rel. 15.
  • Panel ID may be implicitly or explicitly applied to transmission of at least one of target RS resource or target RS resource set, PUCCH, SRS, and PRACH. If panel ID is explicitly signaled, panel ID may be configured in at least one of target RS, target channel, and reference RS (e.g., DL RS resource configuration or spatial relationship information).
  • multi-panel UL transmission e.g., Simultaneous Transmission across Multiple Panels (STxMP)
  • STxMP Simultaneous Transmission across Multiple Panels
  • ⁇ Single DCI-based STxMP> In simultaneous multi-panel transmission (STxMP) in a single DCI based multi-TRP system, the following scheme may be applied to UL transmission (e.g., PUSCH).
  • SDM Space Division Multiplexing
  • Different layers/DMRS ports of one PUSCH are precoded separately and transmitted simultaneously from different UE beams/panels (see Figures 6A and 6B).
  • - Space Division Multiplexing (SDM repetition) scheme Two PUSCH transmission opportunities with different redundancy versions (RVs) of the same TB are transmitted simultaneously from two different UE beams/panels on the same time and frequency resources (see Figure 6C).
  • RVs redundancy versions
  • Frequency Division Multiplexing (FDM)-A scheme Different portions of the frequency domain resources of one PUSCH transmission occasion (eg, one PUSCH transmission occasion) are transmitted from different UE beams/panels (see FIG. 7A).
  • FDM-B scheme Two PUSCH transmission opportunities with the same/different RV for the same TB are transmitted from different UE beams/panels on non-overlapping frequency domain resources and the same time domain resources (see FIG. 7B).
  • SFN-based transmission scheme all the same layers/DMRS ports of one PUSCH are transmitted simultaneously from two different UE beams/panels (see Fig. 7C).
  • Transmitting multiple TBs may mean transmitting the same TB multiple times, or transmitting different TBs.
  • the UE may assume that the PUSCH repetitive transmissions using Space Division Multiplexing (SDM) are scheduled on the same time and frequency resources. That is, the UE may assume that the PUSCH repetitive transmissions using Space Division Multiplexing (SDM) are scheduled on the same time and frequency resources. When used, repeated PUSCH transmissions using SDM may be transmitted in the same time resource and the same frequency resource.
  • SDM Space Division Multiplexing
  • Figure 6A shows an example of repeated transmission using SDM in one CW.
  • the time and frequency resources of layers #1-2 and #3-4 corresponding to PUSCH/PUCCH are the same.
  • Figure 6B is a diagram showing an example of repeated transmission using SDM in two CWs.
  • the time and frequency resources of CW#1 and CW#2 corresponding to PUSCH/PUCCH are the same.
  • Figure 6C is a diagram showing an example of repeated transmission using SDM.
  • the time and frequency resources for PUSCH/PUCCH repetition #1 and repetition #2 are the same.
  • PUSCH transmission using SDM may be configured such that at least a portion of the time and frequency resources overlap.
  • the UE may assume that PUSCH/PUCCH repeated transmissions using Frequency Division Multiplexing (FDM) are scheduled on the same time resources and different frequency resources.
  • FDM Frequency Division Multiplexing
  • PUSCH/PUCCH repeated transmission using FDM may be transmitted in the same time resource and different frequency resources.
  • FIG. 7A is a diagram showing a first example of repeated transmission using FDM (FDM-A).
  • FDM-A shows an example in which one PUSCH/PUCCH repeated transmission is performed for one TB/UCI.
  • FIG. 7B is a diagram showing a second example of repeated transmission using FDM (FDM-B).
  • FDM-B shows an example in which PUSCH/PUCCH repeated transmission is performed twice per TB/UCI.
  • Figure 7C shows an example of repeated transmission using a single frequency network (SFN).
  • Figure 7C shows an example in which one PUSCH/PUCCH is transmitted using a different beam/panel for one TB/UCI.
  • SRI indication For simultaneous multi-panel transmission based on spatial division multiplexing of non-codebook-based PUSCH, the following two options are assumed as SRI indication (e.g., SRI indication):
  • SRI combinations may be prescribed from non-codebook SRS resources across two panels.
  • SRS combinations may be indicated, where each SRI combination may be indicated from non-codebook SRS resources of one panel (e.g., NCB SRS resources of one panel).
  • non-codebook SRS resources of one panel e.g., NCB SRS resources of one panel.
  • An SRI combination may include one or more SRS resources (e.g., SRS resources for non-codebooks).
  • SRS resources e.g., SRS resources for non-codebooks.
  • one SRI combination (or SRI field) may indicate the SRI/SRS resources corresponding to each panel.
  • An SRI combination may be read as an SRI set or an SRI group.
  • ⁇ Multi-DCI based STxMP> simultaneous transmission of UL channels/UL signals (e.g., PUSCH+PUSCH and PUSCH+PUCCH) is expected to be supported in STxMP in a multi-DCI-based multi-TRP system (see FIG. 8).
  • simultaneous transmission of multiple PUSCHs e.g., PUSCH+PUSCH
  • simultaneous transmission of PUSCH and PUCCH is supported.
  • the multiple PUSCHs may be multiple PUSCHs (related to STxMP) that are transmitted simultaneously.
  • the multiple PUSCHs may each be associated with a different TRP/panel (see Figure 9).
  • dynamically scheduled PUSCH/PUCCH may mean PUSCH/PUCCH scheduled using a dynamic grant, or PUSCH/PUCCH dynamically scheduled using DCI.
  • PUCCH Cell Switching In Rel. 17, PUCCH cell switching between multiple (e.g., two) TDD cells in the same PUCCH cell group is supported to reduce HARQ-ACK feedback delay in TDD operation.
  • one additional SCell may be configured for PUCCH resources/transmission.
  • an additional SCell may be configured for each PUCCH cell group.
  • PUCCH cell switching may be based on dynamic instructions or semi-static settings.
  • the PUCCH cell may be indicated using a new field (PUCCH cell indicator field) included in the DCI.
  • K1 indicated by a field indicating the timing of HARQ-ACK feedback included in the DCI may be interpreted/determined based on the numerology (e.g., subcarrier spacing setting) of the cell after switching (target PUCCH cell).
  • FIG. 10 is a diagram showing an example of PUCCH cell switching scheme 1.
  • a DL CC (cell), PCell, and PUCCH SCell #1 are configured, and DCI and PDSCH are received in the DL CC (cell).
  • the slot length of the DL CC and PCell is different from the slot length of PUCCH SCell#1.
  • the DCI includes a field indicating the timing of HARQ-ACK feedback and a PUCCH cell indicator field.
  • the UE determines that the slot two slots after the slot in which the PDSCH was received in PUCCH SCell #1 (slot #3) is the slot in which to transmit the HARQ-ACK for the PDSCH.
  • the time domain of the PUCCH cell pattern may be configured for each PUCCH cell group with a granularity of one slot of the PCell/PSCell/PUCCH-SCell.
  • K1 indicated by the field indicating the timing of HARQ-ACK feedback included in the DCI may be interpreted/determined based on the numerology of the PCell/PSCell/PUCCH-SCell (e.g., subcarrier spacing setting).
  • Figure 11 is a diagram showing an example of PUCCH cell switching scheme 2.
  • a PDSCH Cell, PCell, and PUCCH SCell #1 are set, and PDSCH #1 and PDSCH #2 are received in the PDSCH Cell.
  • a target PUCCH cell is set for each slot of the PDSCH Cell/PCell (PUCCH cell pattern).
  • the timing of transmission of the HARQ-ACK for PDSCH #1 is the slot (slot #1) in which the SCell in the PUCCH cell pattern is set.
  • the UE transmits (by switching) the HARQ-ACK for PDSCH #1 that is instructed to be transmitted in the PCell, in the PUCCH SCell.
  • the timing of transmission of the HARQ-ACK for PDSCH #2 is the slot (slot #3) to which the PCell is set in the PUCCH cell pattern.
  • the UE transmits the HARQ-ACK for PDSCH #1, which is instructed to be transmitted in the PCell, in the PCell (without switching).
  • FIG. 12 is a diagram showing another example of PUCCH cell switching scheme 2. The example shown in FIG. 12 differs from FIG. 11 above in terms of the slot length of PUCCH SCell #1.
  • the UE may determine that the first slot of the multiple slots is the slot to be used for PUCCH/HARQ-ACK transmission.
  • the UE transmits the HARQ-ACK for PDSCH #1 in slot #2 (by switching) which is the first slot of slots #2 and #3 of PUCCH SCell #1 that overlap with slot #1 in PCell.
  • STxMP Single DCI PUSCH SDM scheme. - Single DCI PUSCH SFN scheme. - Multi-DCI overlapping PUSCH+PUSCH scheme. Single DCI PUCCH SFN scheme.
  • a single DCI PUSCH SDM scheme may mean that different layers/DMRS ports of one PUSCH scheduled/triggered by one DCI are transmitted simultaneously using different panels (for different TRPs) ( Figure 13A).
  • a single DCI PUSCH SFN scheme may mean that multiple (e.g., all) layers/DMRS ports of one PUSCH scheduled/triggered by one DCI are transmitted simultaneously (for different TRPs) using different panels ( Figure 13B).
  • a multi-DCI overlapping PUSCH+PUSCH scheme may mean that multiple (e.g., two) PUSCHs that overlap (at least partially) in the time domain are transmitted simultaneously (for different TRPs) using different panels ( Figure 13C).
  • the single DCI PUCCH SFN scheme may mean that one PUCCH is transmitted simultaneously using different panels (for different TRPs) ( Figure 13D).
  • multiple (e.g., two) SRS resource sets may be configured and multiple (e.g., two) SRI/TPMI fields may be indicated.
  • multiple (e.g., two) SRS resource sets may be configured, and each of the multiple SRS resource sets may be associated with a different CORESET pool index.
  • multiple (e.g., two) TCI states may be associated with one PUCCH resource.
  • multiple (e.g., two) SRS resource sets with CB/NCB usage will be applied to the PUSCH of the SDM/SFN scheme related to STxMP.
  • DCI e.g., SRS resource set indicator
  • the maximum number of layers for single TRP and STxMP SDM may be set separately.
  • the maximum number of layers may be set by the RRC parameter maxRank (or Lmax), as in existing specifications.
  • a maximum number of layers may be set separately for the first SRS resource set and the second SRS resource set (apart from maxRank (or Lmax) in the single TRP case).
  • the setting may be, for example, an RRC parameter (e.g., maxRankPerSRSResourceSet) indicating the maximum number of layers per SRS resource set.
  • FIG. 14 shows an example of the maximum number of layers.
  • the RRC parameter maxRank is set to 4 for the UE.
  • the UE transmits a maximum of 4 layers (layer 1) of PUSCH using a single TRP/single panel (panel #1).
  • an RRC parameter (e.g., maxRankPerSRSResourceSet) that sets the maximum number of layers for the STxMP scheme is configured for the UE. For example, if the parameter is set to 2, the UE transmits PUSCH for a maximum of two layers (layer 1) using the first TRP/panel (panel #1) and the second TRP/panel (panel #2), respectively.
  • FIG. 14 shows an example of dynamic switching between single TRP PUSCH and SDM PUSCH.
  • the TCI state (joint/UL TCI state) to be applied to the PUSCH scheduled/activated by the DCI may be determined based on a specific field (e.g., SRS resource set indicator field) included in the DCI.
  • the DCI may be, for example, DCI format 0_1/0_2, or may be a DCI for at least one of a DL grant (DG) and a type 2 configured grant (CG) that dynamically schedules a PUSCH.
  • DG DL grant
  • CG type 2 configured grant
  • the UE may apply a first indication (joint/UL) TCI state to multiple (e.g., all) PUSCH antenna ports corresponding to the PUSCH transmission opportunity.
  • a first indication join/UL
  • the UE may apply the second indication (joint/UL) TCI state to multiple (e.g., all) PUSCH antenna ports corresponding to the PUSCH transmission opportunity.
  • a second value e.g., "01”
  • a first indication (joint/UL) TCI state may be applied to a PUSCH transmission opportunity associated with a first SRS resource set
  • a second indication (joint/UL) TCI state may be applied to a PUSCH transmission opportunity associated with a second SRS resource set.
  • These SRS resource sets may be SRS resource sets for CB/NCB.
  • the inventors therefore came up with a way to solve these problems.
  • A/B and “at least one of A and B” may be interpreted as interchangeable. Also, in this disclosure, “A/B/C” may mean “at least one of A, B, and C.”
  • Radio Resource Control RRC
  • RRC parameters RRC parameters
  • RRC messages higher layer parameters, fields, information elements (IEs), settings, etc.
  • IEs information elements
  • CE Medium Access Control
  • update commands activation/deactivation commands, etc.
  • the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocols (e.g., NR Positioning Protocol A (NRPPa)/LTE Positioning Protocol (LPP)) messages), or a combination of these.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • LPP LTE Positioning Protocol
  • the MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc.
  • the broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.
  • MIB Master Information Block
  • SIB System Information Block
  • RMSI Remaining Minimum System Information
  • OSI System Information
  • the physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), etc.
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • multi-TRP, multi-TRP system, multi-TRP transmission, multi-PDSCH, channel using multi-TRP, channel using multiple TCI states/spatial relationships, multi-TRP enabled by RRC/DCI, multiple TCI states/spatial relationships enabled by RRC/DCI, and at least one of multi-TRP based on a single DCI and multi-TRP based on multiple DCI may be read as interchangeable.
  • multi-TRP based on multi-DCI, and a CORESETPoolIndex value of 1 is set for the CORESET may be read as interchangeable.
  • multi-TRP based on a single DCI, and at least one code point of the TCI field is mapped to two TCI states may be read as interchangeable.
  • single TRP, single DCI, single PDCCH, multi-TRP based on single DCI, single TRP system, single TRP transmission, single PDSCH, channel using single TRP, channel using one TCI state/spatial relationship, multi-TRP not being enabled by RRC/DCI, multiple TCI states/spatial relationships not being enabled by RRC/DCI, a CORESETPoolIndex value of 1 not being set for any CORESET and no code point in the TCI field being mapped to two TCI states, and two TCI states on at least one TCI code point being activated may be read as interchangeable.
  • panel e.g., UE capability value set
  • TRP UE capability value set
  • SRS resource set e.g., SRS resource set
  • CORESET pool index e.g., beam group
  • beam group e.g., TCI state group
  • spatial relationship group e.g., reference signal group
  • path loss RS group e.g., path loss RS group
  • STxMP simultaneous UL transmission using multi-panel
  • UL transmission multiple UL transmissions
  • UL transmission multiple UL transmissions
  • UL transmission in at least the same time resource/domain using multi-TRP
  • UL transmission in at least the same time resource/domain for multi-TRP
  • ignore, drop, abort, cancel, puncture, rate match, postpone, do not transmit, etc. may be read as interchangeable.
  • PUSCH related to STxMP subjected to SDM PUSCH of STxMP subjected to SDM, STxMP PUSCH SDM, PUSCH SDM, PUSCH subjected to SDM, SDM PUSCH, etc. may be read as interchangeable.
  • PUSCH related to STxMP using SFN PUSCH of STxMP using SFN
  • STxMP PUSCH SFN PUSCH SFN
  • PUSCH using SFN SFN PUSCH, etc.
  • PUCCH related to STxMP using SFN PUCCH of STxMP using SFN
  • STxMP PUCCH SFN PUCCH SFN
  • PUCCH using SFN SFN PUCCH
  • etc. may be read as interchangeable.
  • a UE may use multiple panels to transmit one or more UL signals/channels, at least in the same time domain (eg, same time resource/symbol/slot/sub-slot).
  • Multi-DCI-based PUSCH+PUSCH may be transmitted when the configuration information regarding multi-DCI-based PUSCH+PUSCH is set to enabled/on for the UE and (two) CORESET pool indices are set.
  • the first embodiment relates to TCI conditions that apply to UL signals/channels that utilize SDM.
  • the UL signal/channel in the first embodiment may be, for example, a PUSCH.
  • the PUSCH in the first embodiment may be, for example, STxMP of the SDM-based PUSCH.
  • a PUSCH related to the SDM-based STxMP may be configured for the UE. This configuration may be performed using higher layer signaling (RRC/MAC CE).
  • the PUSCH in the first embodiment may be scheduled by a single DCI.
  • a UE may be configured with multiple (e.g., two) SRS resource sets for a specific purpose (e.g., codebook (CB)/non-codebook (NCB)).
  • the SRS resource set may be an SRS resource set for the specific purpose.
  • the UE may schedule/activate/trigger the PUSCH using a specific DCI.
  • the particular DCI may be, for example, a DCI that schedules a PUSCH (e.g., DCI format 0_1/0_2), or may be a DCI for at least one of a DL grant (DG) and a type 2 configured grant (CG) that dynamically schedules a PUSCH.
  • a DCI that schedules a PUSCH e.g., DCI format 0_1/0_2
  • DG DL grant
  • CG type 2 configured grant
  • the UE may transmit PUSCHs corresponding to different layers at least in the same time domain (e.g., time resources/symbols/slots/subslots).
  • the UE may determine the instruction (joint/UL) TCI state to apply to the PUSCH/PUSCH antenna port/PUSCH transmission opportunity corresponding to different layers based on specific fields included in the DCI.
  • the UE may determine whether the scheduled PUSCH is a single-TRP PUSCH or an SDM STxMP PUSCH based on the specific field. The UE may determine whether to switch between single-TRP PUSCH transmission and SDM STxMP PUSCH transmission based on the specific field.
  • the specific field may be, for example, the SRS resource set indicator field, or a new field defined in Rel. 18 or later.
  • the particular field may be defined as a particular number of bits (e.g., 2 bits).
  • the UE may determine whether to switch between single TRP PUSCH transmission and SDM STxMP PUSCH transmission based on the presence or absence of the specific field with the specific number of bits in the DCI. For example, the UE may make the decision regarding the switch if the specific field with the specific number of bits is present in the DCI. The UE may determine/assume not to make the switch if the specific field with the specific number of bits is not present in the DCI.
  • the UE may apply the first indication (joint/UL) TCI state to multiple (e.g., all) PUSCH antenna ports/layers associated with the first SRS resource set.
  • a first value e.g., "00"
  • the UE may apply the first indication (joint/UL) TCI state to multiple (e.g., all) PUSCH antenna ports/layers associated with the first SRS resource set.
  • the UE may transmit a PUSCH using one TRP (single TRP) associated with the first SRS resource set.
  • TRP single TRP
  • the UE may apply the second indication (joint/UL) TCI state to multiple (e.g., all) PUSCH antenna ports/layers associated with the second SRS resource set.
  • a second value e.g., "01”
  • the UE may apply the second indication (joint/UL) TCI state to multiple (e.g., all) PUSCH antenna ports/layers associated with the second SRS resource set.
  • the UE may transmit a PUSCH using one TRP (single TRP) associated with the second SRS resource set.
  • TRP single TRP
  • the UE may apply a first indication (joint/UL) TCI state to one or more first PUSCH antenna ports/layers associated with a first SRS resource set, and may apply a second indication (joint/UL) TCI state to one or more second PUSCH antenna ports/layers associated with a second SRS resource set.
  • a third value e.g., "10”
  • the UE may transmit a PUSCH related to STxMP that is SDMed.
  • the UE may apply the first indication (joint/UL) TCI state to one or more second PUSCH antenna ports/layers associated with the second SRS resource set, and may apply the second indication (joint/UL) TCI state to one or more first PUSCH antenna ports/layers associated with the first SRS resource set.
  • a fourth value e.g., "11”
  • the UE may transmit a PUSCH related to STxMP that is SDMed.
  • the first PUSCH antenna port/layer may include the 1st layer, ..., the mth layer (m ⁇ n), and the first PUSCH antenna port/layer may include the m+1th layer, ..., the nth layer.
  • the first SRS resource set may be an SRS resource set corresponding to a lower (or higher) SRS resource set ID among SRS resource sets whose usage is CB/NCB.
  • the second SRS resource set may be an SRS resource set corresponding to a higher (or lower) SRS resource set ID among SRS resource sets whose usage is CB/NCB.
  • the operations related to the code points (first to fourth values) of the particular field may be applied to all code points, or only to some code points (e.g., first to third values). For example, if only the first to third code points are used/supported, the fourth code point may be reserved or may be used for other purposes.
  • the UE may determine the association between the SRS resource set and the indicated TCI state based on certain rules (e.g., predefined specifications).
  • the UE may assume/expect that a first SRS resource set is associated with a first indicated TCI state and a second SRS resource set is associated with a second indicated TCI state.
  • the UE may determine the association between the SRS resource set and the indicated TCI state based on higher layer signaling (e.g., RRC/MAC CE).
  • higher layer signaling e.g., RRC/MAC CE
  • information indicating either the first or second indicated TCI state may be included in the RRC parameters of the SRS resource set.
  • the UE may determine the association between the SRS resource set and the indicated TCI state based on the information.
  • FIG. 15 is a diagram showing an example of application of the indicated TCI state according to the first embodiment.
  • 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.
  • the UE when the code point of a specific field included in the DCI indicates "10", the UE applies a first indication TCI state to Layer 1 and a second indication TCI state to Layer 2.
  • the UE when the code point of a specific field included in the DCI indicates "11", the UE applies the second indication TCI state to Layer 1 and the 21st indication TCI state to Layer 2.
  • the UE may determine the association of PUSCH antenna ports/layers with SRS resource sets based on rules predefined in the specification.
  • the UE may assume/determine that the PUSCH antenna ports of the lower (or higher) n ports/layers are associated with the first SRS resource set and the PUSCH antenna ports of the higher (or lower) m ports/layers are associated with the first SRS resource set.
  • n and m may be the same value or different values.
  • the UE may assume that n ⁇ m. Also, for example, the UE may assume that n ⁇ m.
  • the number of ports/layers (n and/or m) associated with the first/second SRS resource set may be determined based on a specific field in the DCI.
  • the DCI may be a DCI that schedules/activates/triggers the PUSCH.
  • n may be determined based on a first TPMI field (e.g., a first TPMI field for the CB) or a first SRI field (e.g., a first SRI field for the NCB).
  • a first TPMI field e.g., a first TPMI field for the CB
  • a first SRI field e.g., a first SRI field for the NCB
  • m may be determined based on a second TPMI field (e.g., a second TPMI field for the CB) or a second SRI field (e.g., a second SRI field for the NCB).
  • a second TPMI field e.g., a second TPMI field for the CB
  • a second SRI field e.g., a second SRI field for the NCB
  • the UE may also be notified/instructed as to which of the lower port/layer PUSCH antenna ports and the higher PUSCH antenna ports are associated with the first/second SRS resource set.
  • the instruction may be made, for example, using a specific field (e.g., SRS resource set indicator field) in the DCI (e.g., scheduling DCI).
  • the UE may be configured/instructed/notified of the association between the PUSCH antenna port/layer and the SRS resource set based on higher layer signaling (RRC/MAC CE)/DCI.
  • RRC/MAC CE higher layer signaling
  • an association with a PUSCH antenna port/layer may be set for each SRS resource set for a particular purpose (e.g., CB/NCB).
  • the association between the SRS resource set and the PUSCH port/layer can be appropriately defined.
  • an SRS resource set index of the SRS resource set
  • a PUSCH port/layer index of the PUSCH port/layer
  • an indication (joint/UL) TCI state index of the indication (joint/UL) TCI state).
  • the UE may determine the mapping/association based on the specific fields in embodiment 1-1 above.
  • the UE may determine the mapping/association in accordance with embodiment 1-3-1/1-3-2 below.
  • a code point of a particular field may indicate a first value (e.g., "00")/a second value (e.g., "01").
  • the UE may assume/determine that the first indicated (joint/UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated.
  • a first value e.g., “00”
  • the UE may assume/determine that the first indicated (joint/UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated.
  • the UE may decide to transmit a single TRP PUSCH.
  • the UE may assume/determine that a second indicated (joint/UL) TCI state, a second SRS resource set, and multiple (e.g., all) layers are associated.
  • a second value e.g., "01”
  • the UE may assume/determine that a second indicated (joint/UL) TCI state, a second SRS resource set, and multiple (e.g., all) layers are associated.
  • the UE may decide to transmit a single TRP PUSCH.
  • FIG. 16 is a diagram showing an example of the association of an indication TCI state, an SRS resource set, and layers related to option 1-3-1-1.
  • the UE determines that the first indication (joint/UL) TCI state, the first SRS resource set, and all PUSCH layers (layers 1 and 2) are associated. Also, when the code point of a specific field indicates "01", the UE determines that the second indication (joint/UL) TCI state, the second SRS resource set, and all PUSCH layers (layers 1 and 2) are associated.
  • the UE may assume/determine that the first indicated (joint/UL) TCI state, the second SRS resource set, and multiple (e.g., all) layers are associated.
  • a first value e.g., “00”
  • the UE may assume/determine that the first indicated (joint/UL) TCI state, the second SRS resource set, and multiple (e.g., all) layers are associated.
  • the UE may decide to transmit a single TRP PUSCH.
  • the UE may assume/determine that the second indicated (joint/UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated.
  • a second value e.g., "01”
  • the UE may decide to transmit a single TRP PUSCH.
  • a code point of a particular field may indicate a third value (eg, "10")/a second value (eg, "11").
  • the UE may assume/determine that a first indicated (joint/UL) TCI state, a first SRS resource set, and a first layer are associated, and a second indicated (joint/UL) TCI state, a second SRS resource set, and a second layer are associated.
  • a third value e.g., “10”
  • the UE may decide to transmit the SDM STxMP PUSCH.
  • the UE may assume/determine that the first indication (joint/UL) TCI state is associated with the first SRS resource set and the second layer, and that the second indication (joint/UL) TCI state is associated with the second SRS resource set and the first layer.
  • a fourth value e.g., "11"
  • the UE may decide to transmit the SDM STxMP PUSCH.
  • FIG. 17 is a diagram showing an example of the association of the indication TCI state, SRS resource set, and layer according to option 1-3-2-1.
  • the UE determines that the first indication (joint/UL) TCI state is associated with the first SRS resource set and PUSCH layer 1, and that the second indication (joint/UL) TCI state is associated with the second SRS resource set and PUSCH layer 2.
  • the UE determines that the first indication (joint/UL) TCI state is associated with the first SRS resource set and PUSCH layer 2, and that the second indication (joint/UL) TCI state is associated with the second SRS resource set and PUSCH layer 1.
  • the UE may assume/determine that a first indicated (joint/UL) TCI state, a first SRS resource set, and a first layer are associated, and a second indicated (joint/UL) TCI state, a second SRS resource set, and a second layer are associated.
  • a third value e.g., “10”
  • the UE may decide to transmit the SDM STxMP PUSCH.
  • the UE may assume/determine that the first indication (joint/UL) TCI state is associated with the second SRS resource set and the first layer, and that the second indication (joint/UL) TCI state is associated with the first SRS resource set and the second layer.
  • a fourth value e.g., "11"
  • the UE may decide to transmit the SDM STxMP PUSCH.
  • the UE may assume/determine that a first indicated (joint/UL) TCI state, a first SRS resource set, and a first layer are associated, and a second indicated (joint/UL) TCI state, a second SRS resource set, and a second layer are associated.
  • a third value e.g., “10”
  • the UE may decide to transmit the SDM STxMP PUSCH.
  • the UE may assume/determine that the first indication (joint/UL) TCI state is associated with the second SRS resource set and the second layer, and that the second indication (joint/UL) TCI state is associated with the first SRS resource set and the first layer.
  • a fourth value e.g., "11"
  • the UE may decide to transmit the SDM STxMP PUSCH.
  • the fourth value (e.g., "11") may be reserved (not used).
  • the association between the SRS resource set, the PUSCH port/layer, and the indication TCI state can be appropriately defined.
  • Second Embodiment A second embodiment relates to the indication of TCI status that applies to UL signals/channels (UL transmissions) that utilize a single frequency network (SFN).
  • SFN single frequency network
  • the UL signal/channel in the second embodiment may be, for example, a PUSCH.
  • a UL transmission using an SFN may mean that the UE transmits the same UL signal/channel on the same resources (resource elements) in each panel using different instructions (joint/UL TCI states). Also, a UL transmission using an SFN may mean a UL transmission in which multiple (e.g., all) DMRS ports/antenna ports for that UL transmission are in a QCL relationship with multiple (e.g., two) TCI states (instruction TCI states).
  • the PUSCH in the second embodiment may be, for example, STxMP of a PUSCH using an SFN.
  • a PUSCH related to STxMP using an SFN may be configured for a UE. This configuration may be performed using higher layer signaling (RRC/MAC CE).
  • the PUSCH in the second embodiment may be scheduled by a single DCI.
  • a UE may be configured with multiple (e.g., two) SRS resource sets for a specific purpose (e.g., codebook (CB)/non-codebook (NCB)).
  • the SRS resource set may be an SRS resource set for the specific purpose.
  • the UE may schedule/activate/trigger the PUSCH using a specific DCI.
  • the particular DCI may be, for example, a DCI that schedules a PUSCH (e.g., DCI format 0_1/0_2), or may be a DCI for at least one of a DL grant (DG) and a type 2 configured grant (CG) that dynamically schedules a PUSCH.
  • a DCI that schedules a PUSCH e.g., DCI format 0_1/0_2
  • DG DL grant
  • CG type 2 configured grant
  • the UE may transmit each PUSCH with different indicated TCI states for the same PUSCH at least in the same time domain (e.g., time resource/symbol/slot/subslot).
  • the UE may determine the instruction (joint/UL) TCI state to apply to the PUSCH/PUSCH antenna port/PUSCH transmission opportunity based on a specific field included in the DCI.
  • the UE may determine whether to switch between single TRP PUSCH transmission and SFN STxMP PUSCH transmission based on this specific field.
  • the specific field may be, for example, the SRS resource set indicator field, or a new field defined in Rel. 18 or later.
  • the particular field may be defined as a particular number of bits (e.g., 2 bits).
  • the UE may determine whether to switch between single TRP PUSCH transmission and SFN STxMP PUSCH transmission based on the presence or absence of the specific field with the specific number of bits in the DCI. For example, the UE may make the decision regarding the switch if the specific field with the specific number of bits is present in the DCI. The UE may determine/assume not to make the switch if the specific field with the specific number of bits is not present in the DCI.
  • the UE may apply the first indication (joint/UL) TCI state to multiple (e.g., all) PUSCH antenna ports/layers associated with the first SRS resource set.
  • a first value e.g., "00"
  • the UE may apply the first indication (joint/UL) TCI state to multiple (e.g., all) PUSCH antenna ports/layers associated with the first SRS resource set.
  • the UE may transmit a PUSCH using one TRP (single TRP) associated with the first SRS resource set.
  • TRP single TRP
  • the UE may apply the second indication (joint/UL) TCI state to multiple (e.g., all) PUSCH antenna ports/layers associated with the second SRS resource set.
  • a second value e.g., "01”
  • the UE may apply the second indication (joint/UL) TCI state to multiple (e.g., all) PUSCH antenna ports/layers associated with the second SRS resource set.
  • the UE may transmit a PUSCH using one TRP (single TRP) associated with the second SRS resource set.
  • TRP single TRP
  • the UE may apply a first indication (joint/UL) TCI state to one or more (e.g., all) PUSCH antenna ports/layers associated with the first SRS resource set, and may apply a second indication (joint/UL) TCI state to one or more (e.g., all) PUSCH antenna ports/layers associated with the second SRS resource set.
  • a first indication joint/UL
  • the UE may apply a first indication (joint/UL) TCI state to one or more (e.g., all) PUSCH antenna ports/layers associated with the first SRS resource set
  • a second indication (joint/UL) TCI state to one or more (e.g., all) PUSCH antenna ports/layers associated with the second SRS resource set.
  • the UE may transmit a PUSCH related to STxMP using the SFN.
  • a third value e.g., "10”
  • the UE may apply the first indication (joint/UL) TCI state to one or more (e.g., all) PUSCH antenna ports/layers associated with the second SRS resource set, and may apply the second indication (joint/UL) TCI state to one or more (e.g., all) PUSCH antenna ports/layers associated with the first SRS resource set.
  • a fourth value e.g., "11"
  • the UE may apply the first indication (joint/UL) TCI state to one or more (e.g., all) PUSCH antenna ports/layers associated with the second SRS resource set, and may apply the second indication (joint/UL) TCI state to one or more (e.g., all) PUSCH antenna ports/layers associated with the first SRS resource set.
  • the UE may transmit a PUSCH related to STxMP using the SFN.
  • a fourth value e.g., "11”
  • the operations related to the code points (first to fourth values) of the particular field may be applied to all code points, or only to some code points (e.g., first to third values). For example, if only the first to third code points are used/supported, the fourth code point may be reserved or may be used for other purposes.
  • the UE may determine the association between the SRS resource set and the indicated TCI state based on certain rules (e.g., predefined specifications).
  • the UE may assume/expect that a first SRS resource set is associated with a first indicated TCI state and a second SRS resource set is associated with a second indicated TCI state.
  • the UE may determine the association between the SRS resource set and the indicated TCI state based on higher layer signaling (e.g., RRC/MAC CE).
  • higher layer signaling e.g., RRC/MAC CE
  • information indicating either the first or second indicated TCI state may be included in the RRC parameters of the SRS resource set.
  • the UE may determine the association between the SRS resource set and the indicated TCI state based on the information.
  • FIG. 18 is a diagram illustrating an example of application of the indicated TCI state according to the second embodiment.
  • the UE transmits layers 1 and 2 of the PUSCH in the same time domain using the SFN.
  • the UE when the code point of a specific field included in the DCI indicates "10"/"11", the UE applies the first and second indicated TCI states to all layers (layers 1 and 2) and transmits PUSCH using the SFN.
  • Emodiment 2-2 At least two mappings/associations are described: SRS resource set (index of SRS resource set), PUSCH port/layer (index of PUSCH port/layer), and indication (joint/UL) TCI state (index of indication (joint/UL) TCI state).
  • the UE may determine the mapping/association based on the specific fields in embodiment 2-1 above.
  • the UE may determine the mapping/association in accordance with embodiment 2-2-1/2-2-2 below.
  • a code point of a particular field may indicate a first value (e.g., "00")/a second value (e.g., "01").
  • the UE may assume/determine that the first indicated (joint/UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated.
  • a first value e.g., “00”
  • the UE may assume/determine that the first indicated (joint/UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated.
  • the UE may decide to transmit a single TRP PUSCH.
  • the UE may assume/determine that a second indicated (joint/UL) TCI state, a second SRS resource set, and multiple (e.g., all) layers are associated.
  • a second value e.g., "01”
  • the UE may assume/determine that a second indicated (joint/UL) TCI state, a second SRS resource set, and multiple (e.g., all) layers are associated.
  • the UE may decide to transmit a single TRP PUSCH.
  • FIG. 19 is a diagram showing an example of the association of an indication TCI state, an SRS resource set, and layers related to option 2-2-1-1.
  • the UE determines that the first indication (joint/UL) TCI state, the first SRS resource set, and all PUSCH layers (layers 1 and 2) are associated. Also, when the code point of a specific field indicates "01", the UE determines that the second indication (joint/UL) TCI state, the second SRS resource set, and all PUSCH layers (layers 1 and 2) are associated.
  • the UE may assume/determine that the first indicated (joint/UL) TCI state, the second SRS resource set, and multiple (e.g., all) layers are associated.
  • a first value e.g., “00”
  • the UE may assume/determine that the first indicated (joint/UL) TCI state, the second SRS resource set, and multiple (e.g., all) layers are associated.
  • the UE may decide to transmit a single TRP PUSCH.
  • the UE may assume/determine that the second indicated (joint/UL) TCI state, the first SRS resource set, and multiple (e.g., all) layers are associated.
  • a second value e.g., "01”
  • the UE may decide to transmit a single TRP PUSCH.
  • a code point of a particular field may indicate a third value (eg, "10")/a second value (eg, "11").
  • the UE may assume/determine that the first indicated (joint/UL) TCI state is associated with the first SRS resource set and multiple (e.g., all) layers, and that the second indicated (joint/UL) TCI state is associated with the second SRS resource set and multiple (e.g., all) layers.
  • a third value e.g., "10”
  • the UE may decide to transmit a STxMP PUSCH using the SFN.
  • the UE may assume/determine that the first indication (joint/UL) TCI state is associated with the second SRS resource set and multiple (e.g., all) layers, and that the second indication (joint/UL) TCI state is associated with the first SRS resource set and multiple (e.g., all) layers.
  • a fourth value e.g., "11"
  • the UE may decide to transmit the SDM STxMP PUSCH.
  • FIG. 20 is a diagram showing an example of the association of an instruction TCI state, an SRS resource set, and layers according to embodiment 2-2-2.
  • the UE determines that the first instruction (joint/UL) TCI state is associated with the first SRS resource set and all layers, and that the second instruction (joint/UL) TCI state is associated with the second SRS resource set and all layers.
  • the code point of the specific field indicates "11”
  • the UE determines that the first instruction (joint/UL) TCI state is associated with the second SRS resource set and all layers, and that the second instruction (joint/UL) TCI state is associated with the first SRS resource set and all layers.
  • the fourth value (e.g., "11") may be reserved (not used).
  • the association between the SRS resource set, the PUSCH port/layer, and the indication TCI state can be appropriately defined.
  • Third Embodiment A third embodiment relates to the indication of TCI status that applies to UL signals/channels (UL transmissions) that utilize a single frequency network (SFN).
  • SFN single frequency network
  • the UL signal/channel in the third embodiment may be, for example, a PUCCH.
  • the PUCCH in the third embodiment may be, for example, STxMP of PUCCH using SFN.
  • a PUCCH related to STxMP using SFN may be configured for the UE. This configuration may be performed using higher layer signaling (RRC/MAC CE).
  • the PUCCH in the third embodiment may be scheduled/triggered by a single DCI.
  • the PUCCH in the third embodiment may be a PUCCH corresponding to a single DCI.
  • the UE may determine the indicated (joint/UL) TCI state to apply to the PUCCH based on higher layer signaling (RRC/MAC CE)/DCI.
  • RRC/MAC CE higher layer signaling
  • the UE may determine whether the PUCCH to be configured/instructed is a PUCCH that uses an SFN based on higher layer signaling (RRC/MAC CE)/DCI.
  • RRC/MAC CE higher layer signaling
  • the UE may determine whether to switch between the STxMP PUCCH using SFN and another PUCCH (e.g., a single TRP PUCCH) based on higher layer signaling (RRC/MAC CE)/DCI.
  • another PUCCH e.g., a single TRP PUCCH
  • RRC/MAC CE higher layer signaling
  • One or more (e.g., two) joint/UL TCI states may be indicated (associated) with one PUCCH resource.
  • a first joint/UL TCI state, a second joint/UL TCI state, or both may be indicated (associated) with one PUCCH resource using RRC signaling.
  • the UE may then determine the PUCCH resource using a specific field (e.g., the PUCCH Resource Indicator (PRI) field) included in the DCI that schedules/activates/trigger the PUCCH.
  • a specific field e.g., the PUCCH Resource Indicator (PRI) field
  • the UE may decide to perform SFN PUCCH transmission or repetition of PUCCH TDM transmission (specified in Rel. 17).
  • the UE may determine to perform transmission related to a single TRP PUCCH.
  • the UE may determine whether to use single TRP PUCCH or single DCI-based PUCCH TDM based on the number of PUCCH repetitions that is set/instructed.
  • the UE may determine whether to perform SFN PUCCH transmission or Rel. 17 PUCCH TDM repetition for each PUCCH resource based on higher layer signaling (RRC/MAC CE).
  • RRC/MAC CE higher layer signaling
  • PUCCH resource setting For example, for each PUCCH resource (PUCCH resource setting), either SFN PUCCH transmission or repetition of PUCCH TDM (specified in Rel. 17) may be set.
  • a specific field e.g., PRI field
  • PRI field may be used to switch PUCCH resources.
  • the UE may determine whether to perform SFN PUCCH transmission or repeated PUCCH TDM transmission (specified in Rel. 17) based on the number of repetitions specified for the PUCCH resource.
  • a specific field e.g., the PRI field
  • the UE may determine to perform SFN PUCCH transmission. If a repetition number greater than 1 is indicated, the UE may determine to perform repetition of PUCCH TDM transmission.
  • the network/base station cannot secure the resources to schedule PUCCH repetition for multiple slots/subslots, it can use SFN PUCCH, making it possible to schedule according to the resource situation.
  • the number of repetitions of the PUCCH may be set for each PUCCH resource. Also, the number of repetitions of the PUCCH may be set commonly for multiple (e.g., all) PUCCH resources in a CC/BWP.
  • the UE may determine whether to perform SFN PUCCH transmission or repeated PUCCH TDM transmission (specified in Rel. 17) based on a specific field included in the DCI (scheduling/triggering DCI). For that specific field, a new field specified in Rel. 18 or later may be used, or an existing field (specified up to Rel. 17) may be reused.
  • the UE may ignore the instruction/configuration of the repetition number and determine/consider the repetition number to be 1.
  • the UE may not assume that a SFN PUCCH is configured and a repetition count greater than 1 is configured/indicated.
  • the UE may perform repeated transmission based on the repetition number for the SFN PUCCH.
  • the UE may be configured with either SFN PUCCH transmission or repetition of PUCCH TDM (as specified in Rel. 17).
  • This setting may be made for each BWP/CC.
  • the UE may decide to perform either single TRP PUCCH or single DCI-based PUCCH TDM. In this case, the UE may not assume/expect to be instructed to have multiple (e.g., two) joint/UL TCI states per PUCCH (resource).
  • the UE may decide to perform either single TRP PUCCH or single DCI-based PUCCH TDM. If multiple (e.g., two) joint/UL TCI states are indicated to the UE, the UE may select a specific indicated TCI state (e.g., the first (or second) indicated (joint/UL) TCI state).
  • a specific indicated TCI state e.g., the first (or second) indicated (joint/UL) TCI state).
  • the UE may support PUCCH cell switching.
  • the PUCCH settings (e.g., SFN PUCCH, (Rel. 17) PUCCH TDM repetition, single DCI-based PUCCH TDM repetition, and single TRP PUCCH settings) may be configured for each cell/CC/BWP/cell group.
  • the UE needs to determine which cell/CC/BWP/cell group settings to follow.
  • the UE may transmit the PUCCH according to the configuration in the cell/CC/BWP/cell group in which the PDSCH is transmitted.
  • FIG. 21 is a diagram showing an example of PUCCH transmission according to embodiment 3-2.
  • a DL CC (cell), a PCell, and a PUCCH SCell #1 are configured, and DCI and PDSCH are received in the DL CC (cell).
  • the DCI includes a field indicating the timing of HARQ-ACK feedback and a PUCCH cell indicator field.
  • the UE determines that the slot two slots after the slot in which the PDSCH was received (slot #3) in PUCCH SCell #1 is the slot in which to transmit HARQ-ACK for the PDSCH.
  • the UE switches the slot in which to transmit the PUCCH from the PCell to PUCCH SCell #1.
  • the UE transmits PUCCH in PUCCH SCell #1 according to the settings in the cell in which the PDSCH is transmitted (i.e., the DL CC).
  • the UE may transmit the PUCCH according to the configuration in the cell/CC/BWP/cell group (triggering cell/CC/BWP/cell group) in which the DCI is transmitted.
  • the UE transmits PUCCH in PUCCH SCell #1 according to the settings in the cell in which the DCI is transmitted (i.e., the DL CC).
  • the UE may transmit the PUCCH according to the configuration in the cell/CC/BWP/cell group in which the PUCCH is triggered (triggered cell/CC/BWP/cell group).
  • the UE transmits PUCCH in PUCCH SCell #1 according to the configuration in the cell where the PUCCH is triggered (i.e., PCell).
  • the UE may transmit the PUCCH according to the configuration in the cell/CC/BWP/cell group in which the PUCCH is (actually) transmitted.
  • the UE transmits PUCCH in PUCCH SCell #1 according to the settings in the cell in which the PUCCH is transmitted (i.e., PUCCH SCell).
  • any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, any information is received by the UE from the BS) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.
  • NW network
  • BS base station
  • the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader that is not specified in existing standards.
  • LCID Logical Channel ID
  • the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.
  • RNTI Radio Network Temporary Identifier
  • CRC Cyclic Redundancy Check
  • notification of any information to the UE in the above-mentioned embodiments may be performed periodically, semi-persistently, or aperiodically.
  • notification of any information from the UE (to the NW) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal/channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.
  • physical layer signaling e.g., UCI
  • higher layer signaling e.g., RRC signaling, MAC CE
  • a specific signal/channel e.g., PUCCH, PUSCH, PRACH, reference signal
  • the MAC CE may be identified by including a new LCID in the MAC subheader that is not specified in existing standards.
  • the notification may be transmitted using PUCCH or PUSCH.
  • notification of any information from the UE may be performed periodically, semi-persistently, or aperiodically.
  • At least one of the above-mentioned embodiments may be applied when a specific condition is satisfied, which may be specified in a standard or may be notified to a UE/BS using higher layer signaling/physical layer signaling.
  • At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.
  • the specific UE capabilities may indicate at least one of the following: Supporting specific processing/operations/control/information for at least one of the above embodiments (e.g. STxMP for PUSCH/PUCCH). Supports STxMP PUSCH SDM. Support STxMP PUSCH SFN. Support STxMP PUCCH SFN. Support PUCCH cell switching. - The number of panels available to support simultaneous transmission.
  • the above-mentioned specific UE capabilities may be capabilities that are applied across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination of a cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities per Feature Set (FS) or Feature Set Per Component-carrier (FSPC).
  • FR1 Frequency Range 1
  • FR2 FR2, FR3, FR4, FR5, FR2-1, FR2-2
  • SCS subcarrier Spacing
  • FS Feature Set
  • FSPC Feature Set Per Component-carrier
  • the specific UE capabilities may be capabilities that are applied across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • the UE configures/activates/triggers specific information related to the above-mentioned embodiments (or performs the operations of the above-mentioned embodiments) by higher layer signaling/physical layer signaling.
  • the specific information may be information indicating that STxMP PUSCH SDM/STxMP PUSCH SFN/STxMP PUCCH SFN are enabled, any RRC parameters for a specific release (e.g., Rel. 18/19), etc.
  • the UE may, for example, apply Rel. 15/16 operations.
  • Appendix A-1 a receiving unit for receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH);
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • a terminal having a control unit that determines, based on a specific field included in the DCI, whether the PUSH is one of multiple PUSHs transmitted in at least the same time domain that are spatially division multiplexed, and a PUSH for a single transmission/reception point.
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • the control unit determines that the PUSH is a PUSH for a transmission/reception point corresponding to a first sounding reference signal (SRS) resource set when the code point of the specific field indicates a first value, and that the PUSH is a PUSH for a transmission/reception point corresponding to a second SRS resource set when the code point of the specific field indicates a second value.
  • SRS sounding reference signal
  • the control unit determines that the PUSH is a PUSH transmitted in at least the same time domain as the spatial division multiplexing when the code point of the specific field indicates a third value or a fourth value.
  • the control unit determines the number of layers associated with a first sounding reference signal (SRS) resource set based on a first Transmitted Precoding Matrix Indicator (TPMI) field or a first SRS Resource Indicator (SRI) field, and determines the number of layers associated with a second SRS resource set based on a second TPMI field or a second SRI field.
  • SRS sounding reference signal
  • TPMI Transmitted Precoding Matrix Indicator
  • SRI SRS Resource Indicator
  • Appendix B With respect to one embodiment of the present disclosure, the following invention is noted.
  • Appendix B-1 a receiving unit for receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH);
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • a terminal having a control unit that determines, based on a specific field included in the DCI, whether the PUSH is one of multiple PUSHs transmitted in at least the same time domain using a single frequency network (SFN) and a PUSH for a single transmission/reception point.
  • SFN single frequency network
  • the control unit determines that the PUSH is a PUSH for a transmission/reception point corresponding to a first sounding reference signal (SRS) resource set when the code point of the specific field indicates a first value, and that the PUSH is a PUSH for a transmission/reception point corresponding to a second SRS resource set when the code point of the specific field indicates a second value.
  • the control unit determines that the PUSH is a plurality of PUSHs transmitted in at least the same time domain using the SFN when the code point of the specific field indicates a third value.
  • [Appendix B-4] The terminal according to any one of Supplementary Note B-1 to Supplementary Note B-3, wherein the control unit assumes that a fourth value is not used for the code point of the specific field.
  • Appendix C-1 a receiver for receiving a configuration of a Physical Uplink Control Channel (PUCCH) resource with which one or more joint or uplink (UL) Transmission Configuration Indication (TCI) states are associated, and for receiving a Downlink Control Information (DCI) including a PUCCH Resource Indicator (PRI) field; and a control unit for determining, based on a number of joint or UL TCI states associated with a PUCCH resource indicated using the PRI field, whether the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain utilizing a single frequency network (SFN).
  • PUCCH Physical Uplink Control Channel
  • TCI Transmission Configuration Indication
  • DCI Downlink Control Information
  • PRI PUCCH Resource Indicator
  • the control unit determines that the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using the SFN when the number of joint or UL TCI states associated with the indicated PUCCH resource is a plurality of PUCCHs.
  • the receiving unit further receives a setting regarding time division multiplexed PUCCH repetition or PUCCH using SFN by using higher layer signaling
  • the control unit further determines, based on the configuration, whether the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using the SFN, or the time division multiplexed PUCCH repetition, when the number of joint or UL TCI states associated with the indicated PUCCH resource is a plurality of PUCCHs, or the time division multiplexed PUCCH repetition, if the number of joint or UL TCI states associated with the indicated PUCCH resource is a plurality of PUCCHs, based on the configuration, the terminal according to Supplementary Note C-1 or Supplementary Note C-2.
  • the receiving unit further receives information regarding the number of repetitions of a PUCCH
  • the control unit further determines, based on the information, whether the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using the SFN, or the PUCCH repetition that is time-division multiplexed, when the number of joint or UL TCI states associated with the indicated PUCCH resource is a plurality of PUCCHs, or the PUCCH repetition is time-division multiplexed, when the number of joint or UL TCI states associated with the indicated PUCCH resource is a plurality of PUCCHs, based on the information, the terminal according to any one of Supplementary Note C-1 to Supplementary Note C-3.
  • a receiving unit that receives a configuration related to a physical uplink control channel (PUCCH) for each cell and receives downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH);
  • a control unit that determines a PUCCH for transmitting a Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) corresponding to the PDSCH based on a setting related to a PUCCH of a specific cell,
  • the setting for the PUCCH for each cell is any one of a plurality of PUCCHs transmitted in at least the same time domain using a single frequency network (SFN), a time-division multiplexed PUCCH repetition, a time-division multiplexed PUCCH repetition based on a single DCI, and a PUCCH for a single transmission/reception point.
  • SFN single frequency network
  • Appendix D-2 The terminal according to Appendix D-1, wherein the control unit determines a PUCCH for transmitting the HARQ-ACK based on a setting for a PUCCH in a cell receiving the PDSCH.
  • Appendix D-3 The terminal according to Supplementary Note D-1 or Supplementary Note D-2, wherein the control unit determines a PUCCH for transmitting the HARQ-ACK based on a setting for a PUCCH in a cell that receives the DCI.
  • Wired communication system A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below.
  • communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination of these.
  • FIG. 22 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.
  • the wireless communication system 1 (which may simply be referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE) specified by the Third Generation Partnership Project (3GPP), 5th generation mobile communication system New Radio (5G NR), or the like.
  • LTE Long Term Evolution
  • 3GPP Third Generation Partnership Project
  • 5G NR 5th generation mobile communication system New Radio
  • the wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)).
  • MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.
  • RATs Radio Access Technologies
  • MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • EN-DC E-UTRA-NR Dual Connectivity
  • NE-DC NR-E-UTRA Dual Connectivity
  • the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN).
  • the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.
  • the wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (e.g., dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).
  • dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).
  • gNBs NR base stations
  • N-DC Dual Connectivity
  • the wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are arranged within the macrocell C1 and form a small cell C2 that is narrower than the macrocell C1.
  • a user terminal 20 may be located within at least one of the cells. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.
  • the user terminal 20 may be connected to at least one of the multiple base stations 10.
  • the user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).
  • CA carrier aggregation
  • CC component carriers
  • DC dual connectivity
  • Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)).
  • Macro cell C1 may be included in FR1
  • small cell C2 may be included in FR2.
  • FR1 may be a frequency band below 6 GHz (sub-6 GHz)
  • FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.
  • the user terminal 20 may communicate using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • the multiple base stations 10 may be connected by wire (e.g., optical fiber conforming to the Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (e.g., NR communication).
  • wire e.g., optical fiber conforming to the Common Public Radio Interface (CPRI), X2 interface, etc.
  • NR communication e.g., NR communication
  • base station 11 which corresponds to the upper station
  • IAB Integrated Access Backhaul
  • base station 12 which corresponds to a relay station
  • the base station 10 may be connected to the core network 30 directly or via another base station 10.
  • the core network 30 may include at least one of, for example, an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), etc.
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the core network 30 may include network functions (Network Functions (NF)) such as, for example, a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM).
  • NF Network Functions
  • UPF User Plane Function
  • AMF Access and Mobility management Function
  • SMF Session Management Function
  • UDM Unified Data Management
  • AF Application Function
  • DN Data Network
  • LMF Location Management Function
  • OAM Operation, Administration and Maintenance
  • the user terminal 20 may be a terminal that supports at least one of the communication methods such as LTE, LTE-A, and 5G.
  • a wireless access method based on Orthogonal Frequency Division Multiplexing may be used.
  • OFDM Orthogonal Frequency Division Multiplexing
  • CP-OFDM Cyclic Prefix OFDM
  • DFT-s-OFDM Discrete Fourier Transform Spread OFDM
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the radio access method may also be called a waveform.
  • other radio access methods e.g., other single-carrier transmission methods, other multi-carrier transmission methods
  • a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.
  • PDSCH Physical Downlink Shared Channel
  • PBCH Physical Broadcast Channel
  • PDCCH Physical Downlink Control Channel
  • an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • PRACH Physical Random Access Channel
  • SIB System Information Block
  • PDSCH User data, upper layer control information, System Information Block (SIB), etc.
  • SIB System Information Block
  • PUSCH User data, upper layer control information, etc.
  • MIB Master Information Block
  • PBCH Physical Broadcast Channel
  • Lower layer control information may be transmitted by the PDCCH.
  • the lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information for at least one of the PDSCH and the PUSCH.
  • DCI Downlink Control Information
  • the DCI for scheduling the PDSCH may be called a DL assignment or DL DCI
  • the DCI for scheduling the PUSCH may be called a UL grant or UL DCI.
  • the PDSCH may be interpreted as DL data
  • the PUSCH may be interpreted as UL data.
  • a control resource set (COntrol REsource SET (CORESET)) and a search space may be used to detect the PDCCH.
  • the CORESET corresponds to the resources to search for DCI.
  • the search space corresponds to the search region and search method of PDCCH candidates.
  • One CORESET may be associated with one or multiple search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.
  • a search space may correspond to PDCCH candidates corresponding to one or more aggregation levels.
  • One or more search spaces may be referred to as a search space set. Note that the terms “search space,” “search space set,” “search space setting,” “search space set setting,” “CORESET,” “CORESET setting,” etc. in this disclosure may be read as interchangeable.
  • the PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.), and a scheduling request (SR).
  • UCI uplink control information
  • CSI channel state information
  • HARQ-ACK Hybrid Automatic Repeat reQuest ACKnowledgement
  • ACK/NACK ACK/NACK
  • SR scheduling request
  • the PRACH may transmit a random access preamble for establishing a connection with a cell.
  • downlink, uplink, etc. may be expressed without adding "link.”
  • various channels may be expressed without adding "Physical” to the beginning.
  • a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted.
  • a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.
  • the synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).
  • a signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for PBCH) may be called an SS/PBCH block, an SS Block (SSB), etc.
  • SS, SSB, etc. may also be called reference signals.
  • a measurement reference signal Sounding Reference Signal (SRS)
  • a demodulation reference signal DMRS
  • UL-RS uplink reference signal
  • DMRS may also be called a user equipment-specific reference signal (UE-specific Reference Signal).
  • the base station 23 is a diagram showing an example of a configuration of a base station according to an embodiment.
  • the base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.
  • this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the base station 10 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.
  • the control unit 110 controls the entire base station 10.
  • the control unit 110 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.
  • the control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc.
  • the control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc.
  • the control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 120.
  • the control unit 110 may perform call processing of communication channels (setting, release, etc.), status management of the base station 10, management of radio resources, etc.
  • the transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123.
  • the baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212.
  • the transceiver unit 120 may be composed of a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on a common understanding in the technical field to which the present disclosure relates.
  • the transceiver unit 120 may be configured as an integrated transceiver unit, or may be composed of a transmission unit and a reception unit.
  • the transmission unit may be composed of a transmission processing unit 1211 and an RF unit 122.
  • the reception unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.
  • the transmitting/receiving antenna 130 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.
  • the transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc.
  • the transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.
  • the transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.
  • digital beamforming e.g., precoding
  • analog beamforming e.g., phase rotation
  • the transceiver 120 may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data and control information obtained from the control unit 110 to generate a bit string to be transmitted.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • HARQ retransmission control HARQ retransmission control
  • the transceiver unit 120 may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • channel coding which may include error correction coding
  • DFT Discrete Fourier Transform
  • IFFT Inverse Fast Fourier Transform
  • the transceiver unit 120 may perform modulation, filtering, amplification, etc., on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.
  • the transceiver unit 120 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 130.
  • the transceiver 120 may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.
  • reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.
  • FFT Fast Fourier Transform
  • IDFT Inverse Discrete Fourier Transform
  • the transceiver 120 may perform measurements on the received signal.
  • the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal.
  • the measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc.
  • RSRP Reference Signal Received Power
  • RSSI Received Signal Strength Indicator
  • the measurement results may be output to the control unit 110.
  • the transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes providing NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.
  • devices included in the core network 30 e.g., network nodes providing NF
  • other base stations 10, etc. may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.
  • the transmitter and receiver of the base station 10 in this disclosure may be configured with at least one of the transmitter/receiver 120, the transmitter/receiver antenna 130, and the transmission path interface 140.
  • the transceiver 120 may transmit downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH).
  • DCI downlink control information
  • the controller 110 may use a specific field included in the DCI to indicate whether the PUSCH is one of multiple PUSCHs that are spatially multiplexed and transmitted in at least the same time domain, or a PUSCH for a single transceiver point (first embodiment).
  • the transceiver 120 may transmit downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH).
  • DCI downlink control information
  • the controller 110 may use a specific field included in the DCI to indicate whether the PUSCH is one of multiple PUSCHs transmitted in at least the same time domain using a single frequency network (SFN) or a PUSCH for a single transmission/reception point (second embodiment).
  • SFN single frequency network
  • second embodiment single transmission/reception point
  • the transceiver 120 may transmit a configuration of a physical uplink control channel (PUCCH) resource with which one or more joint or uplink (UL) Transmission Configuration Indication (TCI) states are associated, and may transmit downlink control information (DCI) including a PUCCH resource indicator (PRI) field.
  • the control unit 110 may indicate 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 using the PRI field (third embodiment).
  • SFN single frequency network
  • the transceiver 120 may transmit a setting for a physical uplink control channel (PUCCH) for each cell and transmit downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH).
  • the control unit 110 may use a setting for the PUCCH of a specific cell to instruct a PUCCH for transmitting a Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) corresponding to the PDSCH.
  • HARQ-ACK Hybrid Automatic Repeat reQuest ACKnowledgement
  • the setting for the PUCCH for each cell may be any of the following settings: multiple PUCCHs transmitted in at least the same time domain using a single frequency network (SFN), time-division multiplexed PUCCH repetition, time-division multiplexed PUCCH repetition based on a single DCI, and a PUCCH for a single transmission/reception point (third embodiment).
  • SFN single frequency network
  • time-division multiplexed PUCCH repetition time-division multiplexed PUCCH repetition based on a single DCI
  • PUCCH for a single transmission/reception point third embodiment
  • the user terminal 24 is a diagram showing an example of the configuration of a user terminal according to an embodiment.
  • the user terminal 20 includes a control unit 210, a transmitting/receiving unit 220, and a transmitting/receiving antenna 230.
  • the control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may each be provided in one or more units.
  • this example mainly shows the functional blocks of the characteristic parts of this embodiment, and the user terminal 20 may also be assumed to have other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.
  • the control unit 210 controls the entire user terminal 20.
  • the control unit 210 can be configured from a controller, a control circuit, etc., which are described based on a common understanding in the technical field to which this disclosure pertains.
  • the control unit 210 may control signal generation, mapping, etc.
  • the control unit 210 may control transmission and reception using the transceiver unit 220 and the transceiver antenna 230, measurement, etc.
  • the control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 220.
  • the transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223.
  • the baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212.
  • the transceiver unit 220 may be composed of a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on a common understanding in the technical field to which the present disclosure relates.
  • the transceiver unit 220 may be configured as an integrated transceiver unit, or may be composed of a transmission unit and a reception unit.
  • the transmission unit may be composed of a transmission processing unit 2211 and an RF unit 222.
  • the reception unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.
  • the transmitting/receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.
  • the transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc.
  • the transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.
  • the transceiver 220 may form at least one of the transmit beam and receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.
  • digital beamforming e.g., precoding
  • analog beamforming e.g., phase rotation
  • the transceiver 220 may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on the data and control information acquired from the controller 210, and generate a bit string to be transmitted.
  • RLC layer processing e.g., RLC retransmission control
  • MAC layer processing e.g., HARQ retransmission control
  • the transceiver 220 may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
  • Whether or not to apply DFT processing may be based on the settings of transform precoding.
  • the transceiver unit 220 transmission processing unit 2211
  • the transceiver unit 220 may perform DFT processing as the above-mentioned transmission processing in order to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, it is not necessary to perform DFT processing as the above-mentioned transmission processing.
  • the transceiver unit 220 may perform modulation, filtering, amplification, etc., on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.
  • the transceiver unit 220 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.
  • the transceiver 220 may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
  • reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
  • the transceiver 220 may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal.
  • the measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc.
  • the measurement results may be output to the control unit 210.
  • the measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources.
  • the channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources.
  • the measurement unit 223 may derive interference measurements for CSI calculation based on interference measurement resources.
  • the interference measurement resources may be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc.
  • CSI-IM may be called CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS.
  • CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be read as interchangeable.
  • the transmitting unit and receiving unit of the user terminal 20 in this disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.
  • the transceiver 220 may receive downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH).
  • DCI downlink control information
  • the controller 210 may determine, based on a specific field included in the DCI, whether the PUSCH is one of multiple PUSCHs that are spatially multiplexed and transmitted in at least the same time domain, or a PUSCH for a single transceiver point (first embodiment).
  • the control unit 210 may determine that the PUSCH is a PUSCH for a transmission/reception point corresponding to a first sounding reference signal (SRS) resource set when the code point of the specific field indicates a first value, and that the PUSCH is a PUSCH for a transmission/reception point corresponding to a second SRS resource set when the code point of the specific field indicates a second value (first embodiment).
  • SRS sounding reference signal
  • control unit 210 may determine that the PUSCH is a PUSCH transmitted in at least the same time domain as the spatial division multiplexing (first embodiment).
  • the control unit 210 may determine the number of layers associated with a first sounding reference signal (SRS) resource set based on a first Transmitted Precoding Matrix Indicator (TPMI) field or a first SRS Resource Indicator (SRI) field, and may determine the number of layers associated with a second SRS resource set based on a second TPMI field or a second SRI field (first embodiment).
  • SRS sounding reference signal
  • TPMI Transmitted Precoding Matrix Indicator
  • SRI SRS Resource Indicator
  • the transceiver 220 may receive downlink control information (DCI) that schedules a physical uplink shared channel (PUSCH).
  • DCI downlink control information
  • the controller 210 may determine, based on a specific field included in the DCI, whether the PUSCH is one of multiple PUSCHs transmitted in at least the same time domain using a single frequency network (SFN) or a PUSCH intended for a single transceiver point (second embodiment).
  • SFN single frequency network
  • second embodiment second embodiment
  • the control unit 210 may determine that the PUSCH is a PUSCH for a transmission/reception point corresponding to a first sounding reference signal (SRS) resource set when the code point of the specific field indicates a first value, and that the PUSCH is a PUSCH for a transmission/reception point corresponding to a second SRS resource set when the code point of the specific field indicates a second value (second embodiment).
  • SRS sounding reference signal
  • control unit 210 may determine that the PUSCH is a plurality of PUSCHs transmitted in at least the same time domain using the SFN (second embodiment).
  • the control unit 210 may assume that the fourth value is not used for the code point of the particular field (second embodiment).
  • the transceiver 220 may receive a configuration of a physical uplink control channel (PUCCH) resource with which one or more joint or uplink (UL) Transmission Configuration Indication (TCI) states are associated, and may receive downlink control information (DCI) including a PUCCH resource indicator (PRI) field.
  • the control unit 220 may determine 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 using the PRI field (third embodiment).
  • PUCCH physical uplink control channel
  • TCI Transmission Configuration Indication
  • PRI PUCCH resource indicator
  • control unit 210 may determine that the PUCCH of the indicated PUCCH resource is multiple PUCCHs transmitted in at least the same time domain using the SFN (third embodiment).
  • the transceiver 220 may further receive settings for time-division multiplexed PUCCH repetitions or PUCCH using SFN using higher layer signaling.
  • the control unit 210 may further determine, based on the settings, whether the PUCCH of the indicated PUCCH resource is a plurality of PUCCHs transmitted in at least the same time domain using the SFN, or the time-division multiplexed PUCCH repetitions, if the number of joint or UL TCI states associated with the indicated PUCCH resource is multiple (third embodiment).
  • the transceiver 220 may further receive information regarding the number of PUCCH repetitions. If the number of joint or UL TCI states associated with the indicated PUCCH resource is multiple, the control unit 210 may further determine, based on the information, whether the PUCCH of the indicated PUCCH resource is multiple PUCCHs transmitted in at least the same time domain using the SFN, or the time-division multiplexed PUCCH repetitions (third embodiment).
  • the transceiver 220 may receive a setting for a physical uplink control channel (PUCCH) for each cell, and may receive downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH).
  • the control unit 210 may determine a PUCCH for transmitting a hybrid automatic repeat request ACKnowledgement (HARQ-ACK) corresponding to the PDSCH based on the setting for the PUCCH of a specific cell.
  • PUCCH physical uplink control channel
  • DCI downlink control information
  • PDSCH physical downlink shared channel
  • the control unit 210 may determine a PUCCH for transmitting a hybrid automatic repeat request ACKnowledgement (HARQ-ACK) corresponding to the PDSCH based on the setting for the PUCCH of a specific cell.
  • HARQ-ACK hybrid automatic repeat request ACKnowledgement
  • the setting for the PUCCH for each cell may be any of the following settings: multiple PUCCHs transmitted in at least the same time domain using a single frequency network (SFN), time-division multiplexed PUCCH repetition, time-division multiplexed PUCCH repetition based on a single DCI, and a PUCCH for a single transmission/reception point (third embodiment).
  • SFN single frequency network
  • time-division multiplexed PUCCH repetition time-division multiplexed PUCCH repetition based on a single DCI
  • PUCCH for a single transmission/reception point third embodiment
  • the control unit 210 may determine the PUCCH for transmitting the HARQ-ACK based on the settings for the PUCCH in the cell that receives the PDSCH (third embodiment).
  • the control unit 210 may determine the PUCCH for transmitting the HARQ-ACK based on the settings for the PUCCH in the cell that receives the DCI (third embodiment).
  • the control unit 210 may determine the PUCCH for transmitting the HARQ-ACK based on the settings for the PUCCH in the cell that transmits the HARQ-ACK (third embodiment).
  • each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (for example, using wires, wirelessly, etc.).
  • the functional blocks may be realized by combining the one device or the multiple devices with software.
  • the functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment.
  • a functional block (component) that performs the transmission function may be called a transmitting unit, a transmitter, and the like. In either case, as mentioned above, there are no particular limitations on the method of realization.
  • a base station, a user terminal, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 25 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment.
  • the above-mentioned base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
  • the terms apparatus, circuit, device, section, unit, etc. may be interpreted as interchangeable.
  • the hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figures, or may be configured to exclude some of the devices.
  • processor 1001 may be implemented by one or more chips.
  • the functions of the base station 10 and the user terminal 20 are realized, for example, by loading specific software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications via the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.
  • the processor 1001 for example, runs an operating system to control the entire computer.
  • the processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, etc.
  • CPU central processing unit
  • control unit 110 210
  • transmission/reception unit 120 220
  • etc. may be realized by the processor 1001.
  • the processor 1001 also reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these.
  • the programs used are those that cause a computer to execute at least some of the operations described in the above embodiments.
  • the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks.
  • Memory 1002 is a computer-readable recording medium and may be composed of at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other suitable storage media. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to one embodiment of the present disclosure.
  • ROM Read Only Memory
  • EPROM Erasable Programmable ROM
  • EEPROM Electrically EPROM
  • RAM Random Access Memory
  • Memory 1002 may also be called a register, cache, main memory, etc.
  • Memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to one embodiment of the present disclosure.
  • Storage 1003 is a computer-readable recording medium and may be composed of at least one of a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium.
  • Storage 1003 may also be referred to as an auxiliary storage device.
  • the communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc.
  • the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • the above-mentioned transmitting/receiving unit 120 (220), transmitting/receiving antenna 130 (230), etc. may be realized by the communication device 1004.
  • the transmitting/receiving unit 120 (220) may be implemented as a transmitting unit 120a (220a) and a receiving unit 120b (220b) that are physically or logically separated.
  • the input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside.
  • the output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside.
  • the input device 1005 and the output device 1006 may be integrated into one structure (e.g., a touch panel).
  • each device such as the processor 1001 and memory 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
  • the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using the hardware.
  • the processor 1001 may be implemented using at least one of these pieces of hardware.
  • a channel, a symbol, and a signal may be read as mutually interchangeable.
  • a signal may also be a message.
  • a reference signal may be abbreviated as RS, and may be called a pilot, a pilot signal, or the like depending on the applied standard.
  • a component carrier may also be called a cell, a frequency carrier, a carrier frequency, or the like.
  • a radio frame may be composed of one or more periods (frames) in the time domain.
  • Each of the one or more periods (frames) constituting a radio frame may be called a subframe.
  • a subframe may be composed of one or more slots in the time domain.
  • a subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.
  • the numerology may be a communication parameter that is applied to at least one of the transmission and reception of a signal or channel.
  • the numerology may indicate, for example, 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 configuration, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.
  • SCS SubCarrier Spacing
  • TTI Transmission Time Interval
  • radio frame configuration a specific filtering process performed by the transceiver in the frequency domain
  • a specific windowing process performed by the transceiver in the time domain etc.
  • a slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.).
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • a slot may also be a time unit based on numerology.
  • a slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot.
  • a PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A.
  • a PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.
  • a radio frame, subframe, slot, minislot, and symbol all represent time units when transmitting a signal.
  • a different name may be used for radio frame, subframe, slot, minislot, and symbol. Note that the time units such as frame, subframe, slot, minislot, and symbol in this disclosure may be read as interchangeable.
  • one subframe may be called a TTI
  • multiple consecutive subframes may be called a TTI
  • one slot or one minislot may be called a TTI.
  • at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms.
  • the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.
  • TTI refers to, for example, the smallest time unit for scheduling in wireless communication.
  • a base station schedules each user terminal by allocating radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units.
  • radio resources such as frequency bandwidth and transmission power that can be used by each user terminal
  • the TTI may be a transmission time unit for a channel-coded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc.
  • the time interval e.g., the number of symbols
  • the time interval in which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
  • one or more TTIs may be the minimum time unit of scheduling.
  • the number of slots (minislots) that constitute the minimum time unit of scheduling may be controlled.
  • a TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc.
  • a TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
  • a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms
  • a short TTI e.g., a shortened TTI, etc.
  • TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
  • a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain.
  • the number of subcarriers included in an RB may be the same regardless of numerology, and may be, for example, 12.
  • the number of subcarriers included in an RB may be determined based on numerology.
  • an RB may include one or more symbols in the time domain and may be one slot, one minislot, one subframe, or one TTI in length.
  • One TTI, one subframe, etc. may each be composed of one or more resource blocks.
  • one or more RBs may be referred to as a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, an RB pair, etc.
  • PRB Physical RB
  • SCG sub-carrier Group
  • REG resource element group
  • PRB pair an RB pair, etc.
  • a resource block may be composed of one or more resource elements (REs).
  • REs resource elements
  • one RE may be a radio resource area of one subcarrier and one symbol.
  • a Bandwidth Part which may also be referred to as partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by an index of the RB relative to a common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within the BWP.
  • the BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL).
  • BWP UL BWP
  • BWP for DL DL BWP
  • One or more BWPs may be configured for a UE within one carrier.
  • At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP.
  • BWP bitmap
  • radio frames, subframes, slots, minislots, and symbols are merely examples.
  • the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, as well as the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.
  • the information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information.
  • a radio resource may be indicated by a predetermined index.
  • the names used for parameters, etc. in this disclosure are not limiting in any respect. Furthermore, the formulas, etc. using these parameters may differ from those explicitly disclosed in this disclosure.
  • the various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any respect.
  • the information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies.
  • the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
  • information, signals, etc. may be output from a higher layer to a lower layer and/or from a lower layer to a higher layer.
  • Information, signals, etc. may be input/output via multiple network nodes.
  • Input/output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input/output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.
  • a specific location e.g., memory
  • Input/output information, signals, etc. may be overwritten, updated, or added to.
  • Output information, signals, etc. may be deleted.
  • Input information, signals, etc. may be transmitted to another device.
  • the notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods.
  • the notification of information in this disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), etc.), Medium Access Control (MAC) signaling), other signals, or a combination of these.
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • RRC Radio Resource Control
  • MIB Master Information Block
  • SIB System Information Block
  • MAC Medium Access Control
  • the physical layer signaling may be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), etc.
  • the RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.
  • the MAC signaling may be notified, for example, using a MAC Control Element (CE).
  • CE MAC Control Element
  • notification of specified information is not limited to explicit notification, but may be implicit (e.g., by not notifying the specified information or by notifying other information).
  • the determination may be based on a value represented by a single bit (0 or 1), a Boolean value represented by true or false, or a comparison of numerical values (e.g., with a predetermined value).
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • Software, instructions, information, etc. may also be transmitted and received via a transmission medium.
  • a transmission medium For example, if the software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and/or wireless technologies (such as infrared, microwave, etc.), then at least one of these wired and wireless technologies is included within the definition of a transmission medium.
  • wired technologies such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)
  • wireless technologies such as infrared, microwave, etc.
  • Network may refer to the devices included in the network (e.g., base stations).
  • the antenna port may be interchangeably read as an antenna port for any signal/channel (e.g., a demodulation reference signal (DMRS) port).
  • the resource may be interchangeably read as a resource for any signal/channel (e.g., a reference signal resource, an SRS resource, etc.).
  • the resource may include time/frequency/code/space/power resources.
  • the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.
  • the above groups may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, etc.
  • CDM Code Division Multiplexing
  • RS Reference Signal
  • CORESET Control Resource Set
  • beam SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable.
  • SRI SRS Resource Indicator
  • CORESET CORESET pool
  • PDSCH PUSCH
  • codeword CW
  • TB transport block
  • RS etc.
  • TCI state downlink TCI state
  • DL TCI state downlink TCI state
  • UL TCI state uplink TCI state
  • unified TCI state common TCI state
  • joint TCI state etc.
  • QCL QCL
  • QCL assumptions QCL relationship
  • QCL type information QCL property/properties
  • specific QCL type e.g., Type A, Type D
  • specific QCL type e.g., Type A, Type D
  • index identifier
  • indicator indication, resource ID, etc.
  • sequence list, set, group, cluster, subset, etc.
  • TCI state ID the spatial relationship information identifier
  • TCI state ID the spatial relationship information
  • TCI state the spatial relationship information
  • TCI state the spatial relationship information
  • TCI state the spatial relationship information
  • Base Station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.
  • a base station can accommodate one or more (e.g., three) cells.
  • a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small base station for indoor use (Remote Radio Head (RRH))).
  • RRH Remote Radio Head
  • the term "cell” or “sector” refers to a part or the entire coverage area of at least one of the base station and base station subsystems that provide communication services in this coverage.
  • a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control/operate based on the information.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
  • At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc.
  • at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.
  • the moving body in question refers to an object that can move, and the moving speed is arbitrary, and of course includes the case where the moving body is stationary.
  • the moving body in question includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, balloons, and objects mounted on these.
  • the moving body in question may also be a moving body that moves autonomously based on an operating command.
  • the moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned).
  • a vehicle e.g., a car, an airplane, etc.
  • an unmanned moving object e.g., a drone, an autonomous vehicle, etc.
  • a robot manned or unmanned
  • at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations.
  • at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
  • IoT Internet of Things
  • FIG. 26 is a diagram showing an example of a vehicle according to an embodiment.
  • the vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.
  • various sensors including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58
  • an information service unit 59 including a communication module 60.
  • the drive unit 41 is composed of at least one of an engine, a motor, and a hybrid of an engine and a motor, for example.
  • the steering unit 42 includes at least a steering wheel (also called a handlebar), and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.
  • the electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (e.g., an Input/Output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle.
  • the electronic control unit 49 may also be called an Electronic Control Unit (ECU).
  • ECU Electronic Control Unit
  • Signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the motor current, a rotation speed signal of the front wheels 46/rear wheels 47 acquired by a rotation speed sensor 51, an air pressure signal of the front wheels 46/rear wheels 47 acquired by an air pressure sensor 52, a vehicle speed signal acquired by a vehicle speed sensor 53, an acceleration signal acquired by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 acquired by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 acquired by a brake pedal sensor 56, an operation signal of the shift lever 45 acquired by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 58.
  • the information service unit 59 is composed of various devices, such as a car navigation system, audio system, speakers, displays, televisions, and radios, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices.
  • the information service unit 59 uses information acquired 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.
  • various information/services e.g., multimedia information/multimedia services
  • the information service unit 59 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that perform output to the outside.
  • input devices e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.
  • output devices e.g., a display, a speaker, an LED lamp, a touch panel, etc.
  • the driving assistance system unit 64 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving load, such as a millimeter wave radar, a Light Detection and Ranging (LiDAR), a camera, a positioning locator (e.g., a Global Navigation Satellite System (GNSS)), map information (e.g., a High Definition (HD) map, an Autonomous Vehicle (AV) map, etc.), a gyro system (e.g., an Inertial Measurement Unit (IMU), an Inertial Navigation System (INS), etc.), an Artificial Intelligence (AI) chip, and an AI processor, and one or more ECUs that control these devices.
  • the driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize a driving assistance function or an autonomous driving function.
  • the communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63.
  • the communication module 60 transmits and receives data (information) via the communication port 63 between the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58 that are provided on the vehicle 40.
  • the communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication.
  • the communication module 60 may be located either inside or outside the electronic control unit 49.
  • the external device may be, for example, the above-mentioned base station 10 or user terminal 20.
  • the communication module 60 may also be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (it may function as at least one of the base station 10 and user terminal 20).
  • the communication module 60 may transmit at least one of the signals from the various sensors 50-58 described above input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication.
  • the electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input.
  • the PUSCH transmitted by the communication module 60 may include information based on the above input.
  • the communication module 60 receives various information (traffic information, signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle.
  • the information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 60).
  • the communication module 60 also stores various information received from external devices in memory 62 that can be used by the microprocessor 61. Based on the information stored in memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided on the vehicle 40.
  • the base station in the present disclosure may be read as a user terminal.
  • each aspect/embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.).
  • the user terminal 20 may be configured to have the functions of the base station 10 described above.
  • terms such as "uplink” and "downlink” may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink").
  • the uplink channel, downlink channel, etc. may be read as the sidelink channel.
  • the user terminal in this disclosure may be interpreted as a base station.
  • the base station 10 may be configured to have the functions of the user terminal 20 described above.
  • operations that are described as being performed by a base station may in some cases also be performed by its upper node.
  • a network that includes one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) or a Serving-Gateway (S-GW)), or a combination of these.
  • MME Mobility Management Entity
  • S-GW Serving-Gateway
  • each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation.
  • the processing procedures, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no inconsistency.
  • the methods described in this disclosure present elements of various steps in an exemplary order, and are not limited to the particular order presented.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-B LTE-Beyond
  • SUPER 3G IMT-Advanced
  • 4th generation mobile communication system 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • xG x is, for example, an integer or decimal
  • Future Radio Access FX
  • GSM Global System for Mobile communications
  • CDMA2000 Code Division Multiple Access
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods, as well as next-generation systems that are expanded, modified,
  • the phrase “based on” does not mean “based only on,” unless expressly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to an element using a designation such as "first,” “second,” etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.
  • determining may encompass a wide variety of actions. For example, “determining” may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking in a table, database, or other data structure), ascertaining, etc.
  • Determining may also be considered to mean “determining” receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.
  • judgment (decision) may be considered to mean “judging (deciding)” resolving, selecting, choosing, establishing, comparing, etc.
  • judgment (decision) may be considered to mean “judging (deciding)” some kind of action.
  • judgment (decision) may be interpreted interchangeably with the actions described above.
  • expect may be read as “be expected”.
  • "expect(s)" ("" may be expressed, for example, as a that clause, a to infinitive, etc.) may be read as “be expected".
  • "does not expect" may be read as "be not expected".
  • "An apparatus A is not expected" may be read as "An apparatus B other than apparatus A does not expect" (for example, if apparatus A is a UE, apparatus B may be a base station).
  • the "maximum transmit power" referred to in this disclosure may mean the maximum value of transmit power, may mean the nominal UE maximum transmit power, or may mean the rated UE maximum transmit power.
  • connection and “coupled,” or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” to each other.
  • the coupling or connection between the elements may be physical, logical, or a combination thereof. For example, "connected” may be read as "accessed.”
  • a and B are different may mean “A and B are different from each other.”
  • the term may also mean “A and B are each different from C.”
  • Terms such as “separate” and “combined” may also be interpreted in the same way as “different.”
  • timing, time, duration, time instance, any time unit e.g., slot, subslot, symbol, subframe
  • period occasion, resource, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un terminal selon un aspect de la présente divulgation comprend une unité de réception qui reçoit une configuration relative à un canal de commande de liaison montante physique (PUCCH) pour chaque cellule et qui reçoit des informations de commande de liaison descendante (DCI) qui planifient un canal partagé de liaison descendante physique (PDSCH) et une unité de commande qui détermine, sur la base de la configuration relative au PUCCH d'une cellule spécifique, un PUCCH pour transmettre un accusé de réception de demande de répétition automatique hybride (HARQ-ACK) correspondant au PDSCH et est caractérisé en ce que la configuration relative au PUCCH pour chaque cellule est une configuration de l'un quelconque parmi : une pluralité de PUCCH qui sont transmis dans au moins le même domaine temporel à l'aide d'un réseau à fréquence unique (SFN) ; une répétition PUCCH multiplexée par répartition dans le temps ; une répétition PUCCH multiplexée par répartition dans le temps sur la base d'une seule DCI ; et un PUCCH pour un seul point d'émission/réception. Selon un aspect de la présente divulgation, une transmission de liaison montante à l'aide d'une pluralité de panneaux peut être réalisée de manière appropriée.
PCT/JP2023/014118 2023-04-05 2023-04-05 Terminal, procédé de communication sans fil et station de base Ceased WO2024209595A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2025512295A JPWO2024209595A5 (ja) 2023-04-05 端末、無線通信方法、基地局及びシステム
PCT/JP2023/014118 WO2024209595A1 (fr) 2023-04-05 2023-04-05 Terminal, procédé de communication sans fil et station de base

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/014118 WO2024209595A1 (fr) 2023-04-05 2023-04-05 Terminal, procédé de communication sans fil et station de base

Publications (1)

Publication Number Publication Date
WO2024209595A1 true WO2024209595A1 (fr) 2024-10-10

Family

ID=92971436

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/014118 Ceased WO2024209595A1 (fr) 2023-04-05 2023-04-05 Terminal, procédé de communication sans fil et station de base

Country Status (1)

Country Link
WO (1) WO2024209595A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022220028A1 (fr) * 2021-04-13 2022-10-20 株式会社Ｎｔｔドコモ Terminal et système de communication sans fil

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022220028A1 (fr) * 2021-04-13 2022-10-20 株式会社Ｎｔｔドコモ Terminal et système de communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "HARQ-ACK Enhancements for IIoT/URLLC", 3GPP DRAFT; R1-2111188, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20211111 - 20211119, 6 November 2021 (2021-11-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052074727 *

Also Published As

Publication number Publication date
JPWO2024209595A1 (fr) 2024-10-10

Similar Documents

Publication Publication Date Title
WO2024195103A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024042924A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024069810A1 (fr) Terminal, procédé de communication sans fil et station de base
JP7846490B2 (ja) 端末、無線通信方法、基地局及びシステム
WO2024209595A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209597A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209598A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024209596A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2025069244A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2025041757A1 (fr) Terminal, procédé de communication radioélectrique et station de base
WO2025041756A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024195102A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024247812A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024219413A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024236654A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025088800A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2025017930A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2024069808A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2025017931A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2024247108A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2025041764A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024069809A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2024176454A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2024176455A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2025041763A1 (fr) Terminal, procédé de communication sans fil, et station de base

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23932006

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2025512295

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2025512295

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23932006

Country of ref document: EP

Kind code of ref document: A1