WO2022208877A1 - 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
WO2022208877A1
WO2022208877A1 PCT/JP2021/014363 JP2021014363W WO2022208877A1 WO 2022208877 A1 WO2022208877 A1 WO 2022208877A1 JP 2021014363 W JP2021014363 W JP 2021014363W WO 2022208877 A1 WO2022208877 A1 WO 2022208877A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
pdcch
ack
coreset
dci
Prior art date
Application number
PCT/JP2021/014363
Other languages
English (en)
Japanese (ja)
Inventor
祐輝 松村
聡 永田
ウェイチー スン
ジン ワン
ラン チン
Original Assignee
株式会社Ｎｔｔドコモ
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 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to JP2023510143A priority Critical patent/JPWO2022208877A1/ja
Priority to PCT/JP2021/014363 priority patent/WO2022208877A1/fr
Publication of WO2022208877A1 publication Critical patent/WO2022208877A1/fr

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/04—Wireless resource allocation

Definitions

  • the present disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.
  • LTE Long Term Evolution
  • 3GPP Rel. 10-14 LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).
  • LTE successor systems for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later
  • 5G 5th generation mobile communication system
  • 5G+ 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • NR New Radio
  • PDCCH physical downlink control channel
  • Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) feedback corresponding to PDCCH repetition for example, HARQ-ACK codebook content, resources for transmitting HARQ-ACK
  • one of the purposes of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately cope with repeated PDCCH transmission.
  • a terminal includes a receiving unit that receives settings for two physical downlink control channels (Physical Downlink Control Channel (PDCCH)) candidates that are linked together, and a joint Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ - ACK) a control unit that determines a HARQ-ACK codebook as valid HARQ-ACK information for the HARQ-ACK corresponding to the reference PDCCH candidate of the two PDCCH candidates when feedback is configured.
  • PDCCH Physical Downlink Control Channel
  • HARQ - ACK Hybrid Automatic Repeat reQuest ACKnowledgement
  • FIG. 1 is a diagram illustrating an example where two linked CORESETs are served using different CORESET pool indices.
  • FIG. 2 is a diagram showing an example of the structure of a HARQ-ACK codebook transmitted on PUCCH in FIG.
  • FIG. 3 is a diagram showing an example of the contents of the HARQ-ACK codebook in the second embodiment.
  • FIG. 4 is a diagram showing an example of the contents of the HARQ-ACK codebook in the second embodiment.
  • FIG. 5 is a diagram showing an example of the contents of the HARQ-ACK codebook in the second embodiment.
  • FIG. 6 illustrates the DAI problem when two linked CORESETs are served with different CORESET pool indices.
  • FIG. 7 is a diagram showing an example of DAI numbering in the third embodiment.
  • FIG. 1 is a diagram illustrating an example where two linked CORESETs are served using different CORESET pool indices.
  • FIG. 2 is a diagram showing an example of the structure of a HAR
  • FIG. 8 illustrates the problem of final DCI determination when two linked CORESETs are served with different CORESET pool indices.
  • FIG. 9 is a diagram showing an example of final DCI format determination in the fourth embodiment.
  • FIG. 10 is a diagram showing an example of final DCI format determination in the fourth embodiment.
  • FIG. 11 is a diagram illustrating an example of a schematic configuration of a radio communication system according to an embodiment.
  • FIG. 12 is a diagram illustrating an example of the configuration of a base station according to one embodiment.
  • FIG. 13 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment;
  • FIG. 14 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment.
  • the reception processing e.g., reception, demapping, demodulation, decoding
  • transmission processing e.g, at least one of transmission, mapping, precoding, modulation, encoding
  • the TCI state may represent those that apply to downlink signals/channels.
  • the equivalent of TCI conditions applied to uplink signals/channels may be expressed as spatial relations.
  • the TCI state is information about the pseudo-colocation (QCL) of signals/channels, and may be called spatial reception parameters, spatial relation information, or the like.
  • the TCI state may be set in the UE on a channel-by-channel or signal-by-signal basis.
  • QCL is an index that indicates the statistical properties of a signal/channel. For example, when one signal/channel and another signal/channel have a QCL relationship, Doppler shift, Doppler spread, average delay ), delay spread, spatial parameters (e.g., spatial Rx parameter) are identical (QCL with respect to at least one of these). You may
  • the spatial reception parameters may correspond to the reception beams of the UE (eg, reception analog beams), and the beams may be specified based on the spatial QCL.
  • QCL or at least one element of QCL in the present disclosure may be read as sQCL (spatial QCL).
  • QCL types may be defined for the QCL.
  • QCL types AD may be provided with different parameters (or parameter sets) that can be assumed to be the same, and the parameters (which may be called QCL parameters) are shown below: QCL type A (QCL-A): Doppler shift, Doppler spread, mean delay and delay spread, QCL type B (QCL-B): Doppler shift and Doppler spread, QCL type C (QCL-C): Doppler shift and mean delay; • QCL Type D (QCL-D): Spatial reception parameters.
  • CORESET Control Resource Set
  • QCL QCL type D
  • a UE may determine at least one of a transmit beam (Tx beam) and a receive beam (Rx beam) for a signal/channel based on the TCI conditions or QCL assumptions of that signal/channel.
  • Tx beam transmit beam
  • Rx beam receive beam
  • the TCI state may be, for example, information about the QCL between the channel of interest (in other words, the reference signal (RS) for the channel) and another signal (for example, another RS). .
  • the TCI state may be set (indicated) by higher layer signaling, physical layer signaling or a combination thereof.
  • higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.
  • RRC Radio Resource Control
  • MAC Medium Access Control
  • Broadcast information includes, for example, Master Information Block (MIB), System Information Block (SIB), Remaining Minimum System Information (RMSI), and other system information ( It may be Other System Information (OSI).
  • MIB Master Information Block
  • SIB System Information Block
  • RMSI Remaining Minimum System Information
  • OSI System Information
  • Physical layer signaling may be, for example, downlink control information (DCI).
  • DCI downlink control information
  • target channel/RS target channel/reference signal
  • source RS source RS
  • Channels for which the TCI state or spatial relationship is set are, for example, a downlink shared channel (PDSCH), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel ( Physical Uplink Shared Channel (PUSCH)) and uplink control channel (Physical Uplink Control Channel (PUCCH)).
  • PDSCH downlink shared channel
  • PDCCH Physical Downlink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • RSs that have a QCL relationship with the channel are, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a measurement reference signal (Sounding Reference Signal (SRS)), CSI-RS for tracking (also called Tracking Reference Signal (TRS)), reference signal for QCL detection (also called QRS), reference signal for demodulation (DeModulation Reference Signal (DMRS)), etc. It may be one.
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • SRS Sounding Reference Signal
  • TRS Tracking Reference Signal
  • QRS reference signal for QCL detection
  • DMRS DeModulation Reference Signal
  • An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • PBCH Physical Broadcast Channel
  • An SSB may also be called an SS/PBCH block.
  • a QCL type X RS in a TCI state may mean an RS that has a QCL type X relationship with (the DMRS of) a certain channel/signal, and this RS is called a QCL type X QCL source in that TCI state.
  • Multi-TRP In NR, one or more Transmission/Reception Points (TRP) (Multi-TRP (MTRP)) are considered to perform DL transmission to the UE. It is also being considered for UEs to perform UL transmissions on one or more TRPs.
  • TRP Transmission/Reception Points
  • CORESET pool index higher layer parameter CORESETPoolIndex
  • BWP active downlink Bandwidth Part
  • PDCCH repetition is applied to PDCCH (or DCI) transmitted from one or more TRPs.
  • PDCCHs or DCI transmitted from one or more TRPs.
  • multiple PDCCHs (or DCIs) transmitted from one or more TRPs may be used to schedule or transmit/receive instructions for one or more signals/channels.
  • PDCCH/DCI to which repeated transmission is applied may be called multi-PDCCH/multi-DCI/multi-TRP PDCCH.
  • Repeated transmission of PDCCH may be replaced with PDCCH repetition, multiple transmissions of PDCCH, multi-PDCCH transmission, multiple TRP PDCCH repetition, MTRP PDCCH, and the like.
  • Multi-PDCCH/multi-DCI may be transmitted from different TRPs (in other words, CORESETs corresponding to different CORESET pool indices).
  • the multiple PDCCH/DCI may be multiplexed using time division multiplexing (TDM)/frequency division multiplexing (FDM)/space division multiplexing (SDM) .
  • PDCCH may be transmitted using different time resources from multiple TRPs.
  • PDCCH may be transmitted using different frequency-time resources from multiple TRPs.
  • FDM PDCCH repetition two sets of Resource Element Groups (REG), Control Channel Element (CCE) of the transmitted PDCCH, two transmitted PDCCH repetitions that do not overlap in frequency, At least one of the non-overlapping multi-chance transmitted PDCCHs may be associated with a different TCI state.
  • REG Resource Element Groups
  • CCE Control Channel Element
  • SDM PDCCH repetition PDCCH may be transmitted using the same time/frequency resource from multiple TRPs.
  • the PDCCH DMRS in all REGs/CCEs of that PDCCH may be associated with two TCI states.
  • SDM may be interchangeably read as single frequency network (SFN).
  • the two or more PDCCH candidates are included in two SS sets (two CORESETs).
  • linking (association) of two SS sets may be configured/activated/notified to the UE by higher layer signaling. If PDCCH repetitions are monitored in two linked SS sets, the UE indicates that yet another (third) monitored SS set is linked to at least one of these two linked SS sets. is unexpected.
  • the two linked SS sets may have the same SS set type (eg, common SS, UE-specific SS) and be configured to monitor the same DCI format.
  • SS set type eg, common SS, UE-specific SS
  • the two linked SS sets may have the same period and offset and the same duration.
  • the linked monitoring opportunities across the two SS sets may exist in the same slot.
  • the two sets may have the same number of monitoring opportunities, and the n-th (where n is an integer) monitoring opportunity of one SS set is linked with the n-th monitoring opportunity of the other SS set.
  • two PDCCH candidates in two SS sets may be linked based on having the same Aggregation Level (AL) and the same candidate index.
  • the two linked SS sets may be configured to have the same number of PDCCH candidates for each AL.
  • Multi-TRP HARQ-ACK Separate HARQ-ACK feedback and joint HARQ-ACK feedback are being considered as Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) feedback for multi-PDSCH.
  • HARQ-ACK Hybrid Automatic Repeat reQuest ACKnowledgement
  • Separate HARQ-ACK feedback allows the UE to send HARQ-ACK for each TRP to a separate uplink control channel (Physical Uplink Control Channel (PUCCH)) / uplink shared channel ( Corresponds to feedback sent by Physical Uplink Shared Channel (PUSCH) resource.
  • the multiple PUCCH/PUSCH resources may overlap (may be transmitted simultaneously) or may not overlap (eg, may be TDM/FDM).
  • HARQ-ACK Using separate HARQ-ACK enables independent HARQ-ACK transmission for each TRP. Even if the backhaul delay between TRPs is large (for example, the TRPs are connected by non-ideal backhaul), HARQ delay does not increase.
  • Joint HARQ-ACK feedback (which may also be called joint feedback, joint HARQ-ACK, etc.) corresponds to feedback in which a UE collectively transmits HARQ-ACKs of multiple TRPs on the same PUCCH/PUSCH resource.
  • HARQ-ACK With joint HARQ-ACK, resource overhead can be reduced because one PUCCH/PUSCH transmission is sufficient. Also, when the backhaul delay between TRPs is small (for example, when the TRPs are connected with an ideal backhaul), HARQ-ACK sent to one TRP is transferred to the other TRP with a low delay. can be delivered to
  • the UE uses a higher layer parameter (which may be called "ackNackFeedbackMode”, “ackNackFeedbackMode-r16", ACKNACK feedback mode, etc.) that indicates whether the feedback mode used in one slot is joint feedback or separate feedback, A feedback mode may be set.
  • a higher layer parameter which may be called "ackNackFeedbackMode”, “ackNackFeedbackMode-r16", ACKNACK feedback mode, etc.
  • One or more DCIs that schedule multi-PDSCH may include a PUCCH resource indicator (PRI) field.
  • PRI corresponds to information specifying resources for transmitting HARQ-ACK corresponding to PDSCH, and may be called an ACK/NACK Resource Indicator (ARI).
  • ARI ACK/NACK Resource Indicator
  • the UE may determine PUCCH resources for transmitting HARQ-ACK corresponding to the multi-PDSCH based on the PRI.
  • the UE is a HARQ-ACK codebook unit consisting of bits of one or more acknowledgment information (eg, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK)), HARQ-ACK using one PUCCH resource You may send feedback.
  • the HARQ-ACK bits may also be called HARQ-ACK information, HARQ-ACK information bits, and so on.
  • the HARQ-ACK codebook includes time domain (eg, slot), frequency domain (eg, Component Carrier (CC)), spatial domain (eg, layer), transport block (TB )), and bits for HARQ-ACK in at least one unit of a code block group (CBG) constituting a TB.
  • CBG code block group
  • the number of bits (size) and the like included in the HARQ-ACK codebook may be determined semi-statically or dynamically.
  • a semi-statically sized HARQ-ACK codebook is also called a semi-static HARQ-ACK codebook, a type 1 HARQ-ACK codebook, and so on.
  • a dynamically sized HARQ-ACK codebook is also called a dynamic HARQ-ACK codebook, a type 2 HARQ-ACK codebook, and so on.
  • Whether to use the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook may be configured in the UE using a higher layer parameter (eg, pdsch-HARQ-ACK-Codebook).
  • a higher layer parameter eg, pdsch-HARQ-ACK-Codebook
  • the UE in a certain range (eg, a range configured based on higher layer parameters), regardless of the presence or absence of PDSCH scheduling, the PDSCH candidate corresponding to the range (or PDSCH HARQ-ACK bits for occasions may be fed back.
  • a certain range eg, a range configured based on higher layer parameters
  • the range may be a period of time (e.g., a set of a certain number of candidate PDSCH reception occasions, or a certain number of PDCCH monitoring occasions), the number of CCs configured or activated in the UE. , the number of TBs (the number of layers or ranks), the number of CBGs per TB, and whether or not spatial bundling is applied.
  • the range is also called HARQ-ACK window, HARQ-ACK bundling window, HARQ-ACK feedback window, and so on.
  • the UE reserves bits for the PDSCH in the codebook even if there is no PDSCH scheduling for the UE. If the UE determines that the PDSCH is not actually scheduled, the UE can feed back the bit as a NACK bit.
  • the UE may feed back the HARQ-ACK bits for the scheduled PDSCH in the above range.
  • the UE may determine the number of bits in the Type 2 HARQ-ACK codebook based on a field in the DCI (eg, the DL Assignment Index (Downlink Assignment Indicator (Index) (DAI)) field).
  • the DAI field may include Counter DAI (C-DAI) and Total DAI (T-DAI).
  • the C-DAI may indicate the counter value of downlink transmissions (PDSCH, data, TB) scheduled within a certain period.
  • the C-DAI in the DCI that schedules data in that period may indicate the number counted first in the frequency domain (eg, CC) and then in the time domain within that period.
  • C-DAI receives PDSCH or Semi-Persistent Scheduling (SPS) release in ascending order of serving cell index and then in ascending order of PDCCH monitoring opportunity for one or more DCIs included in the above period. ) may be counted.
  • SPS Semi-Persistent Scheduling
  • C-DAI may mean the cumulative number of ⁇ serving cell, PDCCH monitoring opportunity ⁇ pairs corresponding to each data, up to the current serving cell and current PDCCH monitoring opportunity.
  • T-DAI may indicate the total value (total number) of data scheduled within a certain period of time.
  • T-DAI in DCI that schedules data in a certain time unit (eg, PDCCH monitoring opportunity) within the period is the time unit (also referred to as a point, timing, etc.) within the period
  • Data scheduled by may indicate the total number of
  • T-DAI is the total number of ⁇ serving cell, PDCCH monitoring opportunity ⁇ pairs corresponding to each data up to the current PDCCH monitoring opportunity, and may mean a value that is updated for each PDCCH monitoring opportunity.
  • CORESETs with different CORESET pool indices are used to schedule different PDSCHs (multi-DCI-based multi-TRP).
  • first TRP first TRP
  • TRP1 first CORESET
  • first CORESET may mean one or more first CORESETs.
  • second CORESET may mean one or more second CORESETs.
  • the two CORESETs associated with the two linked SS sets described above are used for repeated transmission of DCI of the same payload. be done.
  • the two linked CORESETs may be used to schedule the same PDSCH.
  • TRP the HARQ-ACK for the PDSCH scheduled on the two linked CORESETs is intended for. That is, when two linked CORESETs are provided with different CORESET pool indices for PDCCH repetition, the DCI transmitted in the two linked PDCCH candidates in the two linked CORESETs is scheduled. What HARQ-ACK is to be generated for the PDSCH, which resource is used to transmit the HARQ-ACK, etc., have not yet been studied.
  • the inventors came up with a method for suitably performing uplink (eg, PUCCH/PUSCH) transmission for PDCCH repeated transmission.
  • uplink eg, PUCCH/PUSCH
  • A/B may mean “at least one of A and B”.
  • activate, deactivate, indicate (or indicate), select, configure, update, determine, etc. may be read interchangeably.
  • RRC RRC parameters
  • RRC messages higher layer parameters
  • information elements (IEs) IEs
  • MAC CE update command
  • activation/deactivation command may be read interchangeably.
  • supporting, controlling, controllable, operating, and capable of operating may be read interchangeably.
  • sequences, lists, sets, groups, groups, etc. may be read interchangeably.
  • Panel, Beam, Panel Group, Beam Group, Uplink (UL) transmitting entity, TRP, Spatial Relationship Information (SRI), Spatial Relationship, Control Resource Set (COntrol Resource SET (CORESET)), Physical Downlink Shared Channel (PDSCH), codeword, base station, predetermined antenna port (e.g., demodulation reference signal (DMRS) port), predetermined antenna port group (e.g., DMRS port group), predetermined group (e.g., Code Division Multiplexing (CDM) group, predetermined reference signal group, CORESET group), predetermined resource (e.g., predetermined reference signal resource), predetermined resource set (e.g., predetermined reference signal resource set) , CORESET pool, PUCCH group (PUCCH resource group), spatial relationship group, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, etc. may be read interchangeably.
  • DMRS demodulation reference signal
  • CORESET Code Division Multiplexing
  • the panel may relate to at least one of the group index of the SSB/CSI-RS group, the group index of the group-based beam reporting, the group index of the SSB/CSI-RS group for the group-based beam reporting.
  • the panel identifier (ID) and the panel may be read interchangeably.
  • ID and the panel may be read interchangeably.
  • TRP ID and TRP, CORESET group ID and CORESET group, etc. may be read interchangeably.
  • indexes, IDs, indicators, and resource IDs may be read interchangeably.
  • sequences, lists, sets, groups, groups, clusters, subsets, etc. may be read interchangeably.
  • single PDCCH may be assumed to be supported when multiple TRPs utilize the ideal backhaul.
  • Multi-PDCCH may be assumed to be supported when inter-multi-TRP utilizes non-ideal backhaul.
  • the ideal backhaul may also be called DMRS port group type 1, reference signal related group type 1, antenna port group type 1, CORESET pool type 1, and so on.
  • Non-ideal backhaul may be referred to as DMRS port group type 2, reference signal associated group type 2, antenna port group type 2, CORESET pool type 2, and so on. Names are not limited to these.
  • multi-TRP multi-TRP system
  • multi-TRP transmission multi-PDSCH
  • single DCI sDCI
  • single PDCCH multi-TRP system based on single DCI
  • sDCI-based MTRP activating two TCI states on at least one TCI codepoint
  • multi-DCI multi-PDCI
  • multi-PDCCH multi-PDCCH
  • multi-TRP system based on multi-DCI
  • the QCL of the present disclosure may be read interchangeably with QCL Type D.
  • Each embodiment may be applied when Multi-DCI based Multi-TRP is used.
  • CORESETPoolIndex upper layer parameter CORESETPoolIndex
  • the first embodiment is roughly divided into the following two: (Embodiment 1.1) The UE does not expect two linked CORESETs for PDCCH repetition to be provided with different CORESET pool indices. (Embodiment 1.2) The UE may expect two linked CORESETs for PDCCH repetition to be provided with the same or different CORESET pool indices.
  • the UE may expect two linked CORESETs for PDCCH repetition to be provided with the same CORESET pool index.
  • the UE determines that the two linked CORESETs are configured with the same CORESET pool index. It can be assumed that
  • the UE may always generate one HARQ-ACK for one TRP for one PDSCH.
  • the UE may always generate two HARQ-ACKs for two TRPs for one PDSCH scheduled by DCI in two linked PDCCH candidates for PDCCCH repetition? Whether or not will be described in a later embodiment.
  • a second embodiment relates to a Type 1 HARQ-ACK codebook.
  • FIG. 1 is a diagram showing an example where two linked CORESETs are provided using different CORESET pool indices.
  • the second embodiment will be described mainly with reference to FIG. 1, but those skilled in the art will understand that the application of this embodiment is not limited to this case.
  • the UE is configured with two serving cells (CC0-CC1).
  • the UE is also configured with a first CORESET and a second CORESET to operate with multiple TRPs (TRP1,2) for each cell.
  • TRP1,2 multiple TRPs
  • slots 0-3 are DL slots and slot 4 is a UL slot. The same applies to subsequent drawings unless otherwise specified.
  • FIG. 1 shows the transmission timing of HARQ-ACK to PDSCH (PDSCH-to-HARQ feedback timing, which may be called K1, etc.).
  • K1 may be identified by the PDSCH-to-HARQ feedback timing indicator field included in the DCI that schedules this PDSCH (eg, DCI format 1_0/1_1/1_2).
  • n be the last slot in which the PDSCH was received, then the UE transmits HARQ-ACK corresponding to the PDSCH in slot n+K1.
  • the UE may transmit HARQ-ACK for the DCI received in slots 0-3 (for the PDSCH scheduled by that DCI) in slot 4 of CC0.
  • the dashed lines shown across the slots indicate the order of the corresponding HARQ-ACK information bits in the HARQ-ACK codebook (described below in FIG. 2).
  • the CC that transmits PUCCH is not limited to CC0, and may be CC1 depending on the settings.
  • the TRP to which the PUCCH is transmitted is not limited to TRP1, and may be TRP2 depending on settings.
  • the DCI-scheduled PDSCH is indicated by a dashed line.
  • the UE In slot 0 of CC0, the UE repeatedly transmits DCI (DCI#1-1 , #1-2).
  • the same PDSCH may mean PDSCHs with the same content, and may be transmitted from different TRPs (using different beams).
  • FIG. 2 is a diagram showing an example of the structure of the HARQ-ACK codebook transmitted on PUCCH in FIG.
  • the HARQ-ACK codebook (which may be referred to as the joint HARQ-ACK codebook) transmitted on PUCCH#1 is for TRP1 (in other words, for the first set of serving cells containing the first CORESET ), followed by the HARQ-ACK codebook for TRP2 (in other words, for the second set of serving cells including the second CORESET).
  • the PDCCH monitoring occasions included in the corresponding periods are first in ascending order of CC index. , and then indexed in descending order of K1, with the HARQ-ACK bits corresponding to each PDCCH monitoring opportunity arranged in that order.
  • the first CORESET Of the PDCCH candidates and the PDCCH candidates of the second CORESET PDCCH candidates corresponding to any of the following or a combination thereof (referred PDCCH candidate, reference PDCCH candidate, as a reference Only HARQ-ACK information corresponding to the treated PDCCH candidate (which may be called PDCCH candidate taken as reference) may be fed back: (2-0) both the PDCCH candidate for the first CORESET and the PDCCH candidate for the second CORESET; (2-1) PDCCH candidate for the first CORESET, (2-2) PDCCH candidate for the second CORESET, (2-3) PDCCH candidates with earlier or later PDCCH monitoring opportunities, (2-4) PDCCH candidates for CORESETs with smaller or larger CORESET IDs, (2-5) PDCCH candidate for CORESET with smaller or larger SS set ID, (2-
  • each of the above (2-0) to (2-6) PDCCH candidates may be one or more.
  • the HARQ-ACK corresponding to the CORESET pool index of the referenced PDCCH candidate is expressed as valid HARQ-ACK information.
  • a HARQ-ACK corresponding to a CORESET pool index that is not may be expressed as non-valid (or invalid) HARQ-ACK information.
  • the above PDSCH HARQ-ACK information may only be reported in the HARQ-ACK codebook for the same CORESET pool index as the referenced PDCCH candidate's CORESET pool index.
  • the HARQ-ACK information (valid HARQ-ACK information) of the PDSCH may be ACK (eg, 1) if the PDSCH is successfully decoded, and NACK (eg, 0) otherwise.
  • the HARQ-ACK information corresponding to the DCI (not valid HARQ-ACK information) is NACK-fixed.
  • ACK may be fixed, or it may depend on the UE implementation.
  • 3 to 5 are diagrams showing an example of the contents of the HARQ-ACK codebook in the second embodiment. Except for the contents of the 0th and 8th bits of the joint HARQ-ACK codebook, they have already been described in FIG. 2, so the description will not be repeated.
  • Figure 3 corresponds to the case according to (2-0) above.
  • the UE selects the 0th bit of the HARQ-ACK codebook for TRP1 (i.e. the 0th bit of the joint HARQ-ACK codebook) and the 0th bit of the HARQ-ACK codebook for TRP2 (i.e. the joint HARQ- 8th bit of the ACK codebook) and both contain the actual HARQ-ACK information for PDSCH#1.
  • Figure 4 corresponds to the case according to (2-1) above.
  • the UE includes the actual HARQ-ACK information for PDSCH#1 for the 0th bit of the HARQ-ACK codebook for TRP1 and the ACK for the 0th bit of the HARQ-ACK codebook for TRP2. Include fixed (or NACK fixed or information depending on UE implementation).
  • Figure 5 corresponds to the case according to (2-2) above.
  • the UE includes the actual HARQ-ACK information for PDSCH#1 for the 0th bit of the HARQ-ACK codebook for TRP2 and the ACK for the 0th bit of the HARQ-ACK codebook for TRP1. Include fixed (or NACK fixed or information depending on UE implementation).
  • the UE can generate a suitable type 1 HARQ-ACK codebook when two linked CORESETs are used for PDCCH repetition.
  • a third embodiment relates to a type 2 HARQ-ACK codebook.
  • FIG. 6 is a diagram showing the DAI problem when two linked CORESETs are provided using different CORESET pool indices. Points that are omitted from description may be the same as those in FIG.
  • the UE detects normal (non-repeated transmission) DCI#2 in slot 0 of CC1 of the first CORESET.
  • the UE detects normal (non-repeated transmission) DCI#2' in slot 0 of CC1 of the second CORESET.
  • DAI corresponds to a value obtained by counting DCI in ascending order of serving cell index and then in ascending order of PDCCH monitoring opportunities, but it is not clear how to handle repeated DCI. Therefore, the C-DAI, T-DAI for each DCI shown cannot be specified (indicated by "?"). Therefore, the present inventors arrived at the third embodiment.
  • the PDCCH candidate of the first CORESET and the 2 CORESET PDCCH candidates, PDCCH candidates corresponding to any of the following or a combination thereof may be configured to indicate the DAI (C-DAI, T-DAI) corresponding to (even if the UE assumes to indicate such a DAI good): (3-1) PDCCH candidate for the first CORESET, (3-2) PDCCH candidate for the second CORESET, (3-3) PDCCH candidates with earlier or later PDCCH monitoring opportunities, (3-4) PDCCH candidates for CORESETs with smaller or larger CORESET IDs, (3-5) PDCCH candidate for CORESET with smaller or larger SS set ID, (3-6) PDCCH candidates for CORESETs included in the same C
  • each of the above (3-1) to (3-6) PDCCH candidates may be one or more.
  • the DAI included in the two (same content) repeated DCIs is derived assuming the CORESET pool index (first/second CORESET) to which the reference PDCCH candidate belongs. is determined to indicate the value of In other words, repeated DCIs may be considered (counted) for C-DAI and T-DAI in DCIs of the same CORESET pool index as the reference PDCCH candidate. For C-DAI and T-DAI in DCIs with different CORESET pool indices than the reference PDCCH candidate, repeated DCIs may be ignored (not counted).
  • the DAI of the repeated DCI indicates the value of DAI assuming the first CORESET, so the UE receives the DCI #1 in FIG. 6 on the PDCCH corresponding to the first CORESET
  • a DAI of ⁇ 1 is assumed to be the correct (or valid) value and used to determine the number of HARQ-ACK bits, and the DAI of DCI#1-2 received on the PDCCH corresponding to the second CORESET is incorrect.
  • a (or invalid) value may be assumed and not used to determine the number of HARQ-ACK bits.
  • the count of DAI based on at least one of (3-1) to (3-6) above may be applied when the two linked PDCCH candidates belong to the same PDCCH monitoring opportunity, or different May be applied when belonging to a PDCCH monitoring occasion. Also, when the two linked PDCCH candidates belong to the same PDCCH monitoring opportunity and when they belong to different PDCCH monitoring opportunities, the count of DAI based on at least one of (3-1) to (3-6) above The methods can be different.
  • FIG. 7 is a diagram showing an example of DAI numbering in the third embodiment. Points that are omitted from description may be the same as those in FIG. 6 .
  • DAI is usually expressed by applying modulo arithmetic (represented by the remainder obtained by dividing the original value by a predetermined number (eg, 4) (that is, the original value mod predetermined number)).
  • modulo arithmetic represented by the remainder obtained by dividing the original value by a predetermined number (eg, 4) (that is, the original value mod predetermined number)).
  • FIG. 7 corresponds to the case according to (3-1) or (3-2) above.
  • TRPs 1 and 2 have a total of four DCIs, but the repeating DCIs DCI #1-1 and DCI #1-2 only count once in the T-DAI, so each DCI indicates T-DAI is 3.
  • the C-DAI of DCI#1-1 (#1-2) is 1
  • the C-DAI of DCI#2 is 2
  • the DCI# The C-DAI of 2' is 3.
  • the third embodiment is applicable when at least one of DCI indicating both C-DAI and T-DAI and DCI indicating only C-DAI (for example, DCI format 1_0) is used.
  • the UE can generate a suitable type 2 HARQ-ACK codebook when two linked CORESETs are used for PDCCH repetition.
  • a fourth embodiment relates to determination of PUCCH resources for transmitting joint HARQ-ACK feedback.
  • a PUCCH resource that transmits HARQ-ACK in a certain slot has a DCI format (for example, DCI format 1_0/1_1/1_2), it is defined to be determined based on the PRI included in the last DCI format (hereinafter also referred to as the last DCI (last DCI)).
  • DCI format 1_0/1_1/1_2 the last DCI format
  • the PUCCH resource determination is based on one PUCCH resource indicator field (if present). where this one PUCCH resource indicator field has a value indicating the same slot for PUCCH transmission, which the UE detects and which DCI format the UE transmits the corresponding HARQ-ACK information on the PUCCH. and included in the last DCI format.
  • the value indicating the same slot is the value of the PDSCH-to-HARQ feedback timing indicator field (PDSCH-to-HARQ_feedback timing indicator field) (if present), or the higher value indicating the period from DL data to UL-ACK. It may be the value of the layer parameter (dl-DataToUL-ACK) or the value of the higher layer parameter (dl-DataToUL-ACKForDCIFormat1_2) indicating the DL data to UL-ACK period for DCI format 1_2.
  • the detected DCI formats are first indexed in ascending order across the serving cell index for the same PDCCH monitoring opportunity, and then ascending order across multiple PDCCH monitoring opportunity indices.
  • detected DCI formats are first indexed in an ascending order across serving cells indexes for a same PDCCH monitoring occurrence and are then indexed in an ascending order across PDCCH monitoring occurrence indexes").
  • the 'last DCI format' means the last (corresponding to the largest index) DCI format indexed according to this rule among detected DCI formats corresponding to PUCCH transmission in the same slot.
  • the DCI of the first CORESET is indexed before the DCI of the second CORESET.
  • FIG. 8 is a diagram illustrating the problem of final DCI determination when two linked CORESETs are provided with different CORESET pool indices. Points that are omitted from description may be the same as those in FIG. 6 .
  • the UE detects normal (non-repeated transmission) DCI#1 in slot 0 of CC0 of the first CORESET.
  • the UE detects normal (non-repeated transmission) DCI #1' in slot 0 of CC0 of the second CORESET, respectively.
  • the UE repeatedly transmits DCI (DCI #2 -1, #2-2).
  • the PDCCH candidate of the first CORESET and the 2 CORESET PDCCH candidates PDCCH candidates corresponding to any of the following or a combination thereof (referred PDCCH candidate, reference PDCCH candidate, PDCCH candidate treated as reference ( PDCCH candidate taken as reference), etc.), it may be used as the “last DCI format” for PUCCH resource determination: (4-0) PDCCH candidate for first CORESET/PDCCH candidate for second CORESET, (4-1) PDCCH candidate for the first CORESET, (4-2) PDCCH candidate for the second CORESET, (4-3) PDCCH candidates with earlier or later PDCCH monitoring opportunities, (4-4) PDCCH candidates for CORESETs with smaller or larger CORESET IDs, (4-5) PDCCH candidate for CORESET with smaller or larger SS set ID, (4-6) PDCCH candidates for CORESETs included in the same C
  • each of the above (4-0) to (4-6) PDCCH candidates may be one or more.
  • repeated DCI can be the 'last DCI format' only if the referenced PDCCH candidates fall under the same CORESET pool index.
  • repeated DCI may be considered (which may be the 'last DCI format') for the determination of PUCCH resources of the same CORESET pool index as the reference PDCCH candidate.
  • Repeated DCI may be ignored (does not result in 'last DCI format') for determination of PUCCH resource with CORESET pool index different from reference PDCCH candidate.
  • the determination of PUCCH resources based on at least one of (4-0) to (4-6) above may be applied when the two linked PDCCH candidates belong to the same PDCCH monitoring opportunity, It may be applied when belonging to different PDCCH monitoring occasions. Also, when the two linked PDCCH candidates belong to the same PDCCH monitoring opportunity and when they belong to different PDCCH monitoring opportunities, the PUCCH resource based on at least one of (4-0) to (4-6) above The determination method may be different.
  • FIG. 9-10 are diagrams showing an example of final DCI format determination in the fourth embodiment. Points that are omitted from description may be the same as those in FIG. 8 .
  • Fig. 9 corresponds to the case according to (4-1) above.
  • the repeating DCI can be the last DCI format for the first CORESET.
  • the last DCI is DCI#2-1.
  • the determination of PUCCH resources may be based on PRI only, or PRI and other parameters (e.g., the CCE index that detected the last DCI, the number of CCEs in the CORESET used to detect the last DCI, etc. at least one of).
  • Fig. 10 corresponds to the case according to (4-2) above.
  • the repeating DCI can be the final DCI format for the second CORESET.
  • the last DCI is DCI#2-2.
  • the determination of the type 1 HARQ-ACK codebook based on at least one of (2-0) to (2-6) above, and the PUCCH resource based on at least one of (4-0) to (4-6) above may be used in any combination.
  • the determination of the type 2 HARQ-ACK codebook based on at least one of (3-1) to (3-6) above, and the PUCCH resource based on at least one of (4-0) to (4-6) above may be used in any combination.
  • the following combinations may be used for HARQ-ACK codebook determination and PUCCH resource determination: (2-0) and (4-0), ⁇ (2-1)/(3-1) and (4-1), ⁇ (2-2)/(3-2) and (4-2), ⁇ (2-3)/(3-3) and (4-3), (2-4) / (3-4) and (4-4), (2-5) / (3-5) and (4-5), (2-6)/(3-6) and (4-6).
  • These combinations correspond to cases where reference PDCCH candidates for HARQ-ACK codebook determination and reference PDCCH candidates for PUCCH resource determination are determined based on the same rule.
  • the UE can determine suitable PUCCH resources for HARQ-ACK transmission when two linked CORESETs are used for PDCCH repetition.
  • the specific UE capabilities may indicate at least one of the following: whether to support multi-TRP PDCCH repetition schemes; Whether to support two (or more) PDCCH repetitions in two (or more) CORESETs with different CORESET pool indices; whether to support two (or more) PDCCH repetitions in two (or more) CORESETs with different CORESET pool indices in case of joint HARQ-ACK feedback; - In case of joint HARQ-ACK feedback for Type 1 (or Type 2) HARQ-ACK codebook, two (or more) in two (or more) CORESETs with different CORESET pool indices. Whether to support PDCCH repetition.
  • the above embodiments may be applied if the UE is configured by higher layer signaling with specific information related to the above embodiments (if not configured, e.g. Rel. 15/ 16 operations apply).
  • the specific information may include information indicating enabling a PDCCH repetition scheme for different CORESET pool indices, information indicating configuring two CORESETs associated with two linked SS sets, a specific release It may be any RRC parameter for (eg, Rel. 17).
  • wireless 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 radio communication methods according to the above embodiments of the present disclosure or a combination thereof.
  • FIG. 11 is a diagram showing an example of a schematic configuration of a wireless communication system according to one embodiment.
  • the wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc. specified by the Third Generation Partnership Project (3GPP). .
  • LTE Long Term Evolution
  • 5G NR 5th generation mobile communication system New Radio
  • 3GPP Third Generation Partnership Project
  • the wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)).
  • RATs Radio Access Technologies
  • MR-DC is 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 is 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.
  • LTE 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 has dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC) in which both MN and SN are NR base stations (gNB) )) may be supported.
  • dual connectivity NR-NR Dual Connectivity (NN-DC) in which both MN and SN are NR base stations (gNB)
  • gNB NR base stations
  • a wireless communication system 1 includes a base station 11 forming a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) arranged in the macrocell C1 and forming a small cell C2 narrower than the macrocell C1. You may prepare.
  • a user terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminals 20 are not limited to the embodiment shown in the figure.
  • the base stations 11 and 12 are collectively referred to as the base station 10 when not distinguished.
  • the user terminal 20 may connect to at least one of the multiple base stations 10 .
  • the user terminal 20 may utilize at least one of carrier aggregation (CA) using a plurality of 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 the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)).
  • Macrocell C1 may be included in FR1, and 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
  • a plurality of base stations 10 may be connected by wire (for example, an optical fiber conforming to Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (for example, NR communication).
  • wire for example, an optical fiber conforming to Common Public Radio Interface (CPRI), X2 interface, etc.
  • NR communication for example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station is an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) is an IAB Also called a node.
  • IAB Integrated Access Backhaul
  • relay station 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, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and the like.
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the user terminal 20 may be a terminal compatible with at least one of communication schemes such as LTE, LTE-A, and 5G.
  • a radio access scheme 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
  • a radio access method may be called a waveform.
  • other radio access schemes for example, other single-carrier transmission schemes and other multi-carrier transmission schemes
  • the UL and DL radio access schemes may be used as the UL and DL radio access schemes.
  • a downlink shared channel Physical Downlink Shared Channel (PDSCH)
  • PDSCH Physical Downlink Shared Channel
  • PBCH Physical Broadcast Channel
  • PDCCH Physical Downlink Control Channel
  • an uplink shared channel (PUSCH) shared by each user terminal 20 an uplink control channel (PUCCH), a random access channel (Physical Random Access Channel (PRACH)) or the like may be used.
  • PUSCH uplink shared channel
  • PUCCH uplink control channel
  • PRACH Physical Random Access Channel
  • User data, upper layer control information, System Information Block (SIB), etc. are transmitted by the PDSCH.
  • User data, higher layer control information, and the like may be transmitted by PUSCH.
  • a Master Information Block (MIB) may be transmitted by the PBCH.
  • Lower layer control information may be transmitted by the PDCCH.
  • the lower layer control information may include, for example, downlink control information (DCI) including scheduling information for at least one of PDSCH and PUSCH.
  • DCI downlink control information
  • the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc.
  • the DCI that schedules PUSCH may be called UL grant, UL DCI, etc.
  • PDSCH may be replaced with DL data
  • PUSCH may be replaced with UL data.
  • a control resource set (CControl Resource SET (CORESET)) and a search space (search space) may be used for PDCCH detection.
  • CORESET corresponds to a resource searching for DCI.
  • the search space corresponds to the search area and search method of PDCCH candidates.
  • a CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with certain search spaces based on the search space settings.
  • One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels.
  • One or more search spaces may be referred to as a search space set. Note that “search space”, “search space set”, “search space setting”, “search space set setting”, “CORESET”, “CORESET setting”, etc. in the present disclosure may be read interchangeably.
  • PUCCH channel state information
  • acknowledgment information for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.
  • SR scheduling request
  • a random access preamble for connection establishment with a cell may be transmitted by the PRACH.
  • downlink, uplink, etc. may be expressed without adding "link”.
  • various channels may be expressed without adding "Physical" to the head.
  • synchronization signals SS
  • downlink reference signals DL-RS
  • the DL-RS includes a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DeModulation Reference Signal (DMRS)), Positioning Reference Signal (PRS)), Phase Tracking Reference Signal (PTRS)), etc.
  • CRS cell-specific reference signal
  • CSI-RS channel state information reference signal
  • DMRS Demodulation reference signal
  • PRS Positioning Reference Signal
  • PTRS Phase Tracking Reference Signal
  • the synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • a signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called SS/PBCH block, SS Block (SSB), and so on.
  • SS, SSB, etc. may also be referred to as reference signals.
  • DMRS may also be called a user terminal-specific reference signal (UE-specific reference signal).
  • FIG. 12 is a diagram illustrating an example of the configuration of a base station according to one embodiment.
  • the base station 10 comprises a control section 110 , a transmission/reception section 120 , a transmission/reception antenna 130 and a transmission line interface 140 .
  • One or more of each of the control unit 110, the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission line interface 140 may be provided.
  • this example mainly shows the functional blocks that characterize the present embodiment, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.
  • the control unit 110 controls the base station 10 as a whole.
  • the control unit 110 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.
  • the control unit 110 may control signal generation, scheduling (eg, resource allocation, mapping), and the like.
  • the control unit 110 may control transmission/reception, measurement, etc. using the transmission/reception unit 120 , the transmission/reception antenna 130 and the transmission line interface 140 .
  • the control unit 110 may generate data to be transmitted as a signal, control information, a sequence, etc., and transfer them to the transmission/reception unit 120 .
  • the control unit 110 may perform call processing (setup, release, etc.) of communication channels, state management of the base station 10, management of radio resources, and the like.
  • the transmitting/receiving section 120 may include a baseband section 121 , a radio frequency (RF) section 122 and a measuring section 123 .
  • the baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212 .
  • the transmitting/receiving unit 120 is configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure. be able to.
  • the transmission/reception unit 120 may be configured as an integrated transmission/reception unit, or may be configured from a transmission unit and a reception unit.
  • the transmission section may be composed of the transmission processing section 1211 and the RF section 122 .
  • the receiving section may be composed of a reception processing section 1212 , an RF section 122 and a measurement section 123 .
  • the transmitting/receiving antenna 130 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.
  • the transmitting/receiving unit 120 may transmit the above-described downlink channel, synchronization signal, downlink reference signal, and the like.
  • the transmitting/receiving unit 120 may receive the above-described uplink channel, uplink reference signal, and the like.
  • the transmitting/receiving unit 120 may form at least one of the transmission beam and the reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.
  • digital beamforming eg, precoding
  • analog beamforming eg, phase rotation
  • the transmission/reception unit 120 (transmission processing unit 1211) performs Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. may be performed to generate a bit string to be transmitted.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • HARQ retransmission control for example, HARQ retransmission control
  • the transmission/reception unit 120 (transmission processing unit 1211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (DFT) on the bit string to be transmitted. Processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, transmission processing such as digital-to-analog conversion may be performed, and the baseband signal may be output.
  • channel coding which may include error correction coding
  • modulation modulation
  • mapping mapping
  • filtering filtering
  • DFT discrete Fourier transform
  • DFT discrete Fourier transform
  • the transmitting/receiving unit 120 may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 130. .
  • the transmitting/receiving unit 120 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 130.
  • the transmission/reception unit 120 (reception processing unit 1212) performs analog-to-digital conversion, Fast Fourier transform (FFT) processing, and Inverse Discrete Fourier transform (IDFT) processing on the acquired baseband signal. )) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing. User data and the like may be acquired.
  • FFT Fast Fourier transform
  • IDFT Inverse Discrete Fourier transform
  • the transmitting/receiving unit 120 may measure the received signal.
  • the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, etc. based on the received signal.
  • the measurement unit 123 measures received power (for example, Reference Signal Received Power (RSRP)), reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)) , signal strength (for example, Received Signal Strength Indicator (RSSI)), channel information (for example, CSI), and the like may be measured.
  • RSRP Reference Signal Received Power
  • RSSQ Reference Signal Received Quality
  • SINR Signal to Noise Ratio
  • RSSI Received Signal Strength Indicator
  • channel information for example, CSI
  • the transmission path interface 140 transmits and receives signals (backhaul signaling) to and from devices included in the core network 30, other base stations 10, etc., and user data (user plane data) for the user terminal 20, control plane data, and the like. Data and the like may be obtained, transmitted, and the like.
  • the transmitter and receiver of the base station 10 in the present disclosure may be configured by at least one of the transmitter/receiver 120, the transmitter/receiver antenna 130, and the transmission line interface 140.
  • the transmitting/receiving unit 120 may transmit to the user terminal 20 the settings for two physical downlink control channel (PDCCH) candidates linked to each other.
  • the configuration may be at least one of information of linking (association) of two SS sets, information of two linked CORESETs, information of two linked PDCCH candidates in two SS sets, and so on.
  • the transmitting/receiving unit 120 treats the HARQ-ACK corresponding to the reference PDCCH candidate among the two PDCCH candidates as valid HARQ-ACK information. It may receive HARQ-ACK information contained in a HARQ-ACK codebook determined by the terminal.
  • HARQ-ACK Hybrid Automatic Repeat reQuest ACKnowledgement
  • Control section 110 converts the information of the downlink assignment index (Downlink Assignment Index (DAI)) included in the downlink control information transmitted using the two PDCCH candidates to the reference PDCCH candidate among the two PDCCH candidates. may be generated to indicate the DAI corresponding to .
  • DAI Downlink Assignment Index
  • the transmitting/receiving section 120 determines based on the downlink control information.
  • Uplink control information (UCI, eg, HARQ-ACK) transmitted using an uplink control channel resource (PUCCH resource) may be received.
  • FIG. 13 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment.
  • the user terminal 20 includes a control section 210 , a transmission/reception section 220 and a transmission/reception antenna 230 .
  • One or more of each of the control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may be provided.
  • this example mainly shows the functional blocks of the features of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.
  • the control unit 210 controls the user terminal 20 as a whole.
  • the control unit 210 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.
  • the control unit 210 may control signal generation, mapping, and the like.
  • the control unit 210 may control transmission/reception, measurement, etc. using the transmission/reception unit 220 and the transmission/reception antenna 230 .
  • the control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transmission/reception unit 220 .
  • the transmitting/receiving section 220 may include a baseband section 221 , an RF section 222 and a measurement section 223 .
  • the baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212 .
  • the transmitting/receiving unit 220 can be configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure.
  • the transmission/reception unit 220 may be configured as an integrated transmission/reception unit, or may be configured from a transmission unit and a reception unit.
  • the transmission section may be composed of a transmission processing section 2211 and an RF section 222 .
  • the receiving section may include a reception processing section 2212 , an RF section 222 and a measurement section 223 .
  • the transmitting/receiving antenna 230 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.
  • the transmitting/receiving unit 220 may receive the above-described downlink channel, synchronization signal, downlink reference signal, and the like.
  • the transmitting/receiving unit 220 may transmit the above-described uplink channel, uplink reference signal, and the like.
  • the transmitter/receiver 220 may form at least one of the transmission beam and the reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.
  • digital beamforming eg, precoding
  • analog beamforming eg, phase rotation
  • the transmission/reception unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (for example, RLC retransmission control), MAC layer processing (for example, for data and control information acquired from the control unit 210, for example , HARQ retransmission control), etc., to generate a bit string to be transmitted.
  • RLC layer processing for example, RLC retransmission control
  • MAC layer processing for example, for data and control information acquired from the control unit 210, for example , HARQ retransmission control
  • the transmitting/receiving unit 220 (transmission processing unit 2211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), and IFFT processing on a bit string to be transmitted. , precoding, digital-analog conversion, and other transmission processing may be performed, and the baseband signal may be output.
  • Whether or not to apply DFT processing may be based on transform precoding settings. Transmitting/receiving unit 220 (transmission processing unit 2211), for a certain channel (for example, PUSCH), if transform precoding is enabled, the above to transmit the channel using the DFT-s-OFDM waveform
  • the DFT process may be performed as the transmission process, or otherwise the DFT process may not be performed as the transmission process.
  • the transmitting/receiving unit 220 may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 230. .
  • the transmitting/receiving section 220 may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 230.
  • the transmission/reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (error correction) on the acquired baseband signal. decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing may be applied to acquire user data and the like.
  • the transmitting/receiving section 220 may measure the received signal.
  • the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal.
  • the measuring unit 223 may measure received power (eg, RSRP), received quality (eg, RSRQ, SINR, SNR), signal strength (eg, RSSI), channel information (eg, CSI), and the like.
  • the measurement result may be output to control section 210 .
  • the transmitter and receiver of the user terminal 20 in the present disclosure may be configured by at least one of the transmitter/receiver 220 and the transmitter/receiver antenna 230 .
  • the transmitting/receiving unit 220 may receive settings for two physical downlink control channel (PDCCH) candidates linked together.
  • the configuration may be at least one of information of linking (association) of two SS sets, information of two linked CORESETs, information of two linked PDCCH candidates in two SS sets, and so on.
  • control unit 210 When joint Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) feedback is configured, control unit 210 performs HARQ-ACK processing of HARQ-ACK corresponding to the reference PDCCH candidate out of the two PDCCH candidates as valid HARQ-ACK information. - May determine the ACK codebook.
  • HARQ-ACK Hybrid Automatic Repeat reQuest ACKnowledgement
  • the control unit 210 uses the downlink assignment index (DAI) information (DAI field, C-DAI, T- DAI, etc.) indicates the DAI corresponding to the reference PDCCH candidate of said two PDCCH candidates.
  • DAI downlink assignment index
  • the control section 210 transmits the downlink control information to the uplink control channel. May be used for resource determination.
  • CORESET Control Resource Set
  • the reference PDCCH candidate may be the PDCCH candidate with the earlier PDCCH monitoring opportunity among the two PDCCH candidates.
  • each functional block may be implemented using one device that is physically or logically coupled, or directly or indirectly using two or more devices that are physically or logically separated (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices.
  • a functional block may be implemented by combining software in the one device or the plurality of devices.
  • function includes judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deem , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc.
  • a functional block (component) that performs transmission may be called a transmitting unit, a transmitter, or the like. In either case, as described above, the implementation method is not particularly limited.
  • a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 14 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment.
  • the base station 10 and user terminal 20 described above 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, and the like. .
  • the hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.
  • processor 1001 may be implemented by one or more chips.
  • predetermined software program
  • the processor 1001 performs calculations, communication via the communication device 1004 and at least one of reading and writing data in the memory 1002 and the storage 1003 .
  • the processor 1001 operates an operating system and controls the entire computer.
  • the processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like.
  • CPU central processing unit
  • control unit 110 210
  • transmission/reception unit 120 220
  • FIG. 10 FIG. 10
  • the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them.
  • programs program codes
  • software modules software modules
  • data etc.
  • the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be similarly implemented.
  • the memory 1002 is a computer-readable recording medium, such as Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or at least any other suitable storage medium. may be configured by one.
  • the memory 1002 may also be called a register, cache, main memory (main storage device), or the like.
  • the memory 1002 can store executable programs (program code), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.
  • the storage 1003 is a computer-readable recording medium, for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, Blu-ray disc), removable disc, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium may be configured by Storage 1003 may also be called an auxiliary storage device.
  • a computer-readable recording medium for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, Blu-ray disc), removable disc, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium may be configured by Storage 1003 may also
  • 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 a network device, a network controller, a network card, a communication module, or the like.
  • the communication device 1004 includes a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order 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 transmitter/receiver 120 (220) may be physically or logically separated into a transmitter 120a (220a) and a receiver 120b (220b).
  • the input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside.
  • the output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).
  • Each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses between devices.
  • the base station 10 and the user terminal 20 include a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. It may be configured including hardware, and a part or all of each functional block may be realized using the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • a signal may also be a message.
  • a reference signal may be abbreviated as RS, and may also be called a pilot, a pilot signal, etc., depending on the applicable standard.
  • a component carrier may also be called a cell, a frequency carrier, a carrier frequency, or the like.
  • a radio frame may consist of one or more periods (frames) in the time domain.
  • Each of the one or more periods (frames) that make up a radio frame may be called a subframe.
  • a subframe may consist of one or more slots in the time domain.
  • a subframe may be a fixed time length (eg, 1 ms) independent of numerology.
  • a numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel.
  • Numerology for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration , a particular filtering process performed by the transceiver in the frequency domain, a particular windowing process performed by the transceiver in the time domain, and/or the like.
  • a slot may consist of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain.
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • a slot may also be a unit of time based on numerology.
  • a slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot.
  • a PDSCH (or PUSCH) transmitted in time units larger than a minislot may be referred to as PDSCH (PUSCH) Mapping Type A.
  • PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (PUSCH) mapping type B.
  • Radio frames, subframes, slots, minislots and symbols all represent time units when transmitting signals. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations. Note that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be read interchangeably.
  • one subframe may be called a TTI
  • a plurality of consecutive subframes may be called a TTI
  • one slot or one minislot may be called a TTI. That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms may be Note that the unit representing the TTI may be called a slot, mini-slot, or the like instead of a subframe.
  • TTI refers to, for example, the minimum scheduling time unit in wireless communication.
  • a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis.
  • radio resources frequency bandwidth, transmission power, etc. that can be used by each user terminal
  • a TTI may be a transmission time unit such as a channel-encoded data packet (transport block), code block, or codeword, or may be a processing unit such as scheduling and link adaptation. Note that when a TTI is given, the time interval (for example, the number of symbols) in which transport blocks, code blocks, codewords, etc. are actually mapped may be shorter than the TTI.
  • one or more TTIs may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the 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, or the like.
  • a TTI that is shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.
  • the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms
  • the short TTI e.g., shortened TTI, etc.
  • a TTI having the above TTI length may be read instead.
  • a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers (subcarriers) in the frequency domain.
  • the number of subcarriers included in the RB may be the same regardless of the neumerology, eg twelve.
  • the number of subcarriers included in an RB may be determined based on neumerology.
  • an RB may contain one or more symbols in the time domain and may be 1 slot, 1 minislot, 1 subframe or 1 TTI long.
  • One TTI, one subframe, etc. may each be configured with one or more resource blocks.
  • One or more RBs are Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB Also called a pair.
  • PRB Physical Resource Block
  • SCG Sub-Carrier Group
  • REG Resource Element Group
  • PRB pair RB Also called a pair.
  • a resource block may be composed of one or more resource elements (Resource Element (RE)).
  • RE resource elements
  • 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
  • a Bandwidth Part (which may also be called a bandwidth part) represents a subset of contiguous common resource blocks (RBs) for a numerology on a carrier.
  • the common RB may be identified by an RB index based on the common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within that BWP.
  • BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL).
  • BWP for UL
  • BWP for DL DL BWP
  • One or multiple 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 channel/signal outside the active BWP.
  • BWP bitmap
  • radio frames, subframes, slots, minislots, symbols, etc. described above are merely examples.
  • the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers and the number of symbols in a TTI, symbol length, cyclic prefix (CP) length, etc. can be varied.
  • the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. may be represented. For example, radio resources may be indicated by a predetermined index.
  • data, instructions, commands, information, signals, bits, symbols, chips, etc. may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of
  • information, signals, etc. can 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 and output through multiple network nodes.
  • Input/output information, signals, etc. may be stored in a specific location (for example, memory), or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated or appended. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to other devices.
  • Uplink Control Information (UCI) Uplink Control Information
  • RRC Radio Resource Control
  • MIB Master Information Block
  • SIB System Information Block
  • SIB System Information Block
  • MAC Medium Access Control
  • the physical layer signaling may also be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), and the like.
  • RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.
  • MAC signaling may be notified using, for example, a MAC Control Element (CE).
  • CE MAC Control Element
  • notification of predetermined information is not limited to explicit notification, but implicit notification (for example, by not notifying the predetermined information or by providing another information by notice of
  • the determination may be made by a value (0 or 1) represented by 1 bit, or by a boolean value represented by true or false. , may be performed by numerical comparison (eg, comparison with a predetermined value).
  • Software whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.
  • software, instructions, information, etc. may be transmitted and received via a transmission medium.
  • the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) , a server, or other remote source, these wired and/or wireless technologies are included within the definition of transmission media.
  • a “network” may refer to devices (eg, base stations) included in a network.
  • precoding "precoding weight”
  • QCL Quality of Co-Location
  • TCI state Transmission Configuration Indication state
  • spatialal patial relation
  • spatialal domain filter "transmission power”
  • phase rotation "antenna port
  • antenna port group "layer”
  • number of layers Terms such as “rank”, “resource”, “resource set”, “resource group”, “beam”, “beam width”, “beam angle”, “antenna”, “antenna element”, “panel” are interchangeable. can be used as intended.
  • base station BS
  • radio base station fixed station
  • NodeB NodeB
  • eNB eNodeB
  • gNB gNodeB
  • Access point "Transmission Point (TP)”, “Reception Point (RP)”, “Transmission/Reception Point (TRP)”, “Panel”
  • a base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.
  • a base station can accommodate one or more (eg, three) cells.
  • the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is assigned to a base station subsystem (e.g., a small indoor base station (Remote Radio)). Head (RRH))) may also provide communication services.
  • a base station subsystem e.g., a small indoor base station (Remote Radio)). Head (RRH)
  • RRH Head
  • the terms "cell” or “sector” refer to part or all of the coverage area of at least one of the base stations and base station subsystems that serve communication within such coverage.
  • MS Mobile Station
  • UE User Equipment
  • Mobile stations include subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals. , a handset, a user agent, a mobile client, a client, or some other suitable term.
  • At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, or the like.
  • At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like.
  • the mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ).
  • at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations.
  • at least one of the base station and mobile station may be an Internet of Things (IoT) device such as a sensor.
  • IoT Internet of Things
  • the base station in the present disclosure may be read as a user terminal.
  • communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.)
  • the user terminal 20 may have the functions of the base station 10 described above.
  • words such as "up” and “down” may be replaced with words corresponding to inter-terminal communication (for example, "side”).
  • uplink channels, downlink channels, etc. may be read as side channels.
  • user terminals in the present disclosure may be read as base stations.
  • the base station 10 may have the functions of the user terminal 20 described above.
  • operations that are assumed to be performed by the base station may be performed by its upper node in some cases.
  • various operations performed for communication with a terminal may involve the base station, one or more network nodes other than the base station (e.g., Clearly, this can be done by a Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. (but not limited to these) or a combination thereof.
  • MME Mobility Management Entity
  • S-GW Serving-Gateway
  • each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching along with execution. Also, the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in the present disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-B LTE-Beyond
  • SUPER 3G IMT-Advanced
  • 4G 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • xG xG (xG (x is, for example, an integer or a decimal number)
  • Future Radio Access FAA
  • RAT New - Radio Access Technology
  • NR New Radio
  • NX New radio access
  • FX Future generation radio access
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi®
  • IEEE 802.16 WiMAX®
  • IEEE 802.20 Ultra-WideBand (UWB), Bluetooth®, or other suitable wireless It may be applied to systems using communication methods, next-generation systems extended based on these, and the like. Also, multiple systems may be applied to systems using communication methods, next-generation systems extended based on these, and the like
  • any reference to elements using the "first,” “second,” etc. designations 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, references to first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.
  • determining includes judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry ( For example, looking up in a table, database, or another data structure), ascertaining, etc. may be considered to be “determining.”
  • determining (deciding) includes receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access ( accessing (e.g., accessing data in memory), etc.
  • determining is considered to be “determining” resolving, selecting, choosing, establishing, comparing, etc. good too. That is, “determining (determining)” may be regarded as “determining (determining)” some action.
  • connection refers to any connection or coupling, direct or indirect, between two or more elements. and can include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” to each other. Couplings or connections between elements may be physical, logical, or a combination thereof. For example, "connection” may be read as "access”.
  • radio frequency domain when two elements are connected, using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-exhaustive examples, radio frequency domain, microwave They can be considered to be “connected” or “coupled” together using the domain, electromagnetic energy having wavelengths in the optical (both visible and invisible) domain, and the like.
  • a and B are different may mean “A and B are different from each other.”
  • the term may also mean that "A and B are different from C”.
  • Terms such as “separate,” “coupled,” etc. may also be interpreted in the same manner as “different.”

Landscapes

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

Abstract

Un terminal selon un mode de réalisation de la présente divulgation comprend : une unité de réception destinée à recevoir des réglages pour deux canaux physiques de contrôle descendant (PDCCH) candidats qui sont mutuellement liés ; et une unité de commande destinée à, lorsqu'une rétroaction d'accusé de réception de demande de répétition automatique hybride (HARQ-ACK) conjoint est réglée, déterminer un livre de codes HARQ-ACK en utilisant, en tant qu'informations HARQ-ACK effectives, un HARQ-ACK qui correspond à un PDCCH candidat de référence parmi les deux PDCCH candidats. Selon un mode de réalisation de la présente divulgation, une transmission de PDCCH répétée peut être traitée de manière appropriée.
PCT/JP2021/014363 2021-04-02 2021-04-02 Terminal, procédé de communication sans fil et station de base WO2022208877A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2023510143A JPWO2022208877A1 (fr) 2021-04-02 2021-04-02
PCT/JP2021/014363 WO2022208877A1 (fr) 2021-04-02 2021-04-02 Terminal, procédé de communication sans fil et station de base

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/014363 WO2022208877A1 (fr) 2021-04-02 2021-04-02 Terminal, procédé de communication sans fil et station de base

Publications (1)

Publication Number Publication Date
WO2022208877A1 true WO2022208877A1 (fr) 2022-10-06

Family

ID=83457461

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/014363 WO2022208877A1 (fr) 2021-04-02 2021-04-02 Terminal, procédé de communication sans fil et station de base

Country Status (2)

Country Link
JP (1) JPWO2022208877A1 (fr)
WO (1) WO2022208877A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020245973A1 (fr) * 2019-06-06 2020-12-10 株式会社Ｎｔｔドコモ Terminal et procédé de communication sans fil

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020245973A1 (fr) * 2019-06-06 2020-12-10 株式会社Ｎｔｔドコモ Terminal et procédé de communication sans fil

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH", 3GPP DRAFT; R1-2101447, vol. RAN WG1, 19 January 2021 (2021-01-19), pages 1 - 28, XP051971612 *

Also Published As

Publication number Publication date
JPWO2022208877A1 (fr) 2022-10-06

Similar Documents

Publication Publication Date Title
JP7227353B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7216201B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7171926B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7313380B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7269333B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7193549B2 (ja) 端末、無線通信方法及びシステム
JP7323629B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7335329B2 (ja) 端末、無線通信方法及びシステム
JP7337848B2 (ja) 端末、無線通信方法及びシステム
JP7305763B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7244545B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7269322B2 (ja) 端末、無線通信方法及びシステム
JP7320857B2 (ja) 端末、無線通信方法及びシステム
JP7308942B2 (ja) 端末、無線通信方法、基地局及びシステム
WO2022163559A1 (fr) Terminal, procédé de communication sans fil et station de base
JP7308926B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7313379B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7269331B2 (ja) 端末、無線通信方法、基地局及びシステム
WO2022215142A1 (fr) Terminal, procédé de communication radio et station de base
US20240089986A1 (en) Terminal, radio communication method, and base station
US20230086798A1 (en) Terminal, radio communication method, and base station
US20230059757A1 (en) Terminal, radio communication method, and base station
JP7230179B2 (ja) 端末、無線通信方法及びシステム
WO2022208877A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2022208818A1 (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: 21935038

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023510143

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: 21935038

Country of ref document: EP

Kind code of ref document: A1