WO2023204683A1 - Procédé et dispositif permettant de transmettre/recevoir des informations de commande de liaison montante dans un système de communication sans fil - Google Patents

Procédé et dispositif permettant de transmettre/recevoir des informations de commande de liaison montante dans un système de communication sans fil Download PDF

Info

Publication number
WO2023204683A1
WO2023204683A1 PCT/KR2023/005502 KR2023005502W WO2023204683A1 WO 2023204683 A1 WO2023204683 A1 WO 2023204683A1 KR 2023005502 W KR2023005502 W KR 2023005502W WO 2023204683 A1 WO2023204683 A1 WO 2023204683A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
ack
information
pdsch
uci
Prior art date
Application number
PCT/KR2023/005502
Other languages
English (en)
Korean (ko)
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 엘지전자 주식회사
Publication of WO2023204683A1 publication Critical patent/WO2023204683A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling

Definitions

  • This disclosure relates to a wireless communication system, and more specifically to a method and device for transmitting and receiving uplink control information in a wireless communication system.
  • Mobile communication systems were developed to provide voice services while ensuring user activity.
  • the mobile communication system has expanded its scope to include not only voice but also data services.
  • the explosive increase in traffic is causing a shortage of resources and users are demanding higher-speed services, so a more advanced mobile communication system is required. there is.
  • next-generation mobile communication system The requirements for the next-generation mobile communication system are to support explosive data traffic, a dramatic increase in transmission rate per user, a greatly increased number of connected devices, very low end-to-end latency, and high energy efficiency.
  • dual connectivity massive MIMO (Massive Multiple Input Multiple Output), full duplex (In-band Full Duplex), NOMA (Non-Orthogonal Multiple Access), and ultra-wideband (Super)
  • massive MIMO Massive Multiple Input Multiple Output
  • full duplex In-band Full Duplex
  • NOMA Non-Orthogonal Multiple Access
  • Super ultra-wideband
  • the technical problem of the present disclosure is to provide a method and device for transmitting and receiving uplink control information.
  • the technical task of the present disclosure is to provide a method and device for performing multiplexing between a PUCCH for HARQ-ACK for group common transmission and a configured grant (CG)/dynamic grant (DG) based PUSCH.
  • CG configured grant
  • DG dynamic grant
  • a method performed by a terminal in a wireless communication system includes receiving configuration information related to multiplexing of a configured grant (CG) and uplink control information (UCI); Receiving a multicast physical downlink shared channel (PDSCH); And it may include transmitting HARQ-ACK (hybrid automatic repeat request-acknowledgement) information for the multicast PDSCH.
  • CG configured grant
  • PDSCH physical downlink shared channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • a method performed by a base station in a wireless communication system includes transmitting configuration information related to multiplexing of CG-UCI; Transmitting a multicast PDSCH; And it may include receiving HARQ-ACK information for the multicast PDSCH.
  • the PUCCH for the HARQ-ACK information and the PUSCH related to the CG-UCI are allocated to the same slot, and based on the multiplexing of the CG-UCI being activated by the configuration information, the HARQ-ACK information is transmitted to the CG.
  • -Whether it is jointly encoded with UCI may depend on the priority between the HARQ-ACK information and the PUSCH.
  • a method and device for transmitting and receiving uplink control information can be provided.
  • a method and apparatus for performing multiplexing between a PUCCH for HARQ-ACK for group common transmission and a configured grant (CG)/dynamic grant (DG) based PUSCH may be provided.
  • whether multiplexing is possible between HARQ-ACK for group common transmission and UCI (e.g., CG-UCI) piggybacked on PUSCH can be made clear between the base station and the terminal.
  • UCI e.g., CG-UCI
  • FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.
  • FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.
  • FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.
  • FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied.
  • FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.
  • Figure 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using them.
  • Figure 7 illustrates a multiple TRP transmission scheme in a wireless communication system to which the present disclosure can be applied.
  • Figure 8 illustrates a HARQ-ACK process for downlink data in a wireless communication system to which the present disclosure can be applied.
  • Figure 9 illustrates a HARQ-ACK transmission and reception procedure for multicast PDSCH according to an embodiment of the present disclosure.
  • FIG. 10 illustrates unicast/multicast PDSCH transmission and HARQ-ACK reporting and PUSCH transmission therefor in a wireless communication system to which the present disclosure can be applied.
  • FIG. 11 is a diagram illustrating a terminal operation for a multiplexing method between multicast HARQ-ACK and CG-UCI according to an embodiment of the present disclosure.
  • FIG. 12 is a diagram illustrating the operation of a base station for the multiplexing method between multicast HARQ-ACK and CG-UCI according to an embodiment of the present disclosure.
  • Figure 13 illustrates a block diagram of a wireless communication device according to an embodiment of the present disclosure.
  • a component when a component is said to be “connected,” “coupled,” or “connected” to another component, this is not only a direct connection relationship, but also an indirect connection relationship where another component exists between them. It may also be included. Additionally, in this disclosure, the terms “comprise” or “having” specify the presence of a referenced feature, step, operation, element, and/or component, but may also specify the presence of one or more other features, steps, operations, elements, components, and/or components. It does not rule out the existence or addition of these groups.
  • first”, second, etc. are used only for the purpose of distinguishing one component from another component and are not used to limit the components, and unless specifically mentioned, the terms There is no limitation on the order or importance between them. Accordingly, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, the second component in one embodiment may be referred to as a first component in another embodiment. It may also be called.
  • This disclosure describes a wireless communication network or wireless communication system, and operations performed in the wireless communication network include controlling the network and transmitting or receiving signals at a device (e.g., a base station) in charge of the wireless communication network. It can be done in the process of receiving, or it can be done in the process of transmitting or receiving signals from a terminal connected to the wireless network to or between terminals.
  • a device e.g., a base station
  • transmitting or receiving a channel includes transmitting or receiving information or signals through the corresponding channel.
  • transmitting a control channel means transmitting control information or signals through the control channel.
  • transmitting a data channel means transmitting data information or signals through a data channel.
  • downlink refers to communication from the base station to the terminal
  • uplink refers to communication from the terminal to the base station
  • DL downlink
  • UL uplink
  • the transmitter may be part of the base station and the receiver may be part of the terminal.
  • the transmitter may be part of the terminal and the receiver may be part of the base station.
  • the base station may be represented as a first communication device
  • the terminal may be represented as a second communication device.
  • a base station (BS) is a fixed station, Node B, evolved-NodeB (eNB), Next Generation NodeB (gNB), base transceiver system (BTS), access point (AP), and network (5G).
  • eNB evolved-NodeB
  • gNB Next Generation NodeB
  • BTS base transceiver system
  • AP access point
  • 5G network
  • the terminal may be fixed or mobile, and may include UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), and AMS (Advanced Mobile).
  • UE User Equipment
  • MS Mobile Station
  • UT user terminal
  • MSS Mobile Subscriber Station
  • SS Subscriber Station
  • AMS Advanced Mobile
  • MTC Machine-Type Communication
  • M2M Machine-to-Machine
  • D2D Device-to-Device
  • vehicle RSU (road side unit)
  • robot AI (Artificial Intelligence) module
  • UAV Unmanned Aerial Vehicle
  • AR Algmented Reality
  • VR Virtual Reality
  • CDMA can be implemented with wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000.
  • TDMA can be implemented with wireless technologies such as Global System for Mobile communications (GSM)/General Packet Radio Service (GPRS)/Enhanced Data Rates for GSM Evolution (EDGE).
  • EDGE Enhanced Data Rates for GSM Evolution
  • OFDMA can be implemented with wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc.
  • UTRA is part of the Universal Mobile Telecommunications System (UMTS).
  • 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA
  • LTE-A (Advanced)/LTE-A pro is an evolved version of 3GPP LTE
  • 3GPP NR New Radio or New Radio Access Technology
  • 3GPP LTE/LTE-A/LTE-A pro is an evolved version of 3GPP LTE/LTE-A/LTE-A pro.
  • LTE refers to technology after 3GPP TS (Technical Specification) 36.xxx Release 8.
  • LTE technology after 3GPP TS 36.xxx Release 10 is referred to as LTE-A
  • LTE technology after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro
  • 3GPP NR refers to technology after TS 38.xxx Release 15.
  • LTE/NR may be referred to as a 3GPP system.
  • “xxx” refers to the standard document detail number.
  • LTE/NR can be collectively referred to as a 3GPP system.
  • terms, abbreviations, etc. used in the description of the present disclosure reference may be made to matters described in standard documents published prior to the present disclosure. For example, you can refer to the following document:
  • TS 36.211 Physical Channels and Modulation
  • TS 36.212 Multiplexing and Channel Coding
  • TS 36.213 Physical Layer Procedures
  • TS 36.300 General Description
  • TS 36.331 Radio Resource Control
  • TS 38.211 physical channels and modulation
  • TS 38.212 multiplexing and channel coding
  • TS 38.213 physical layer procedures for control
  • TS 38.214 physical layer procedures for data
  • TS 38.300 Overall description of NR and NG-RAN (New Generation-Radio Access Network)
  • TS 38.331 Radio Resource Control Protocol Specification
  • channel state information - reference signal resource indicator channel state information - reference signal resource indicator
  • Synchronization signal block (including primary synchronization signal (PSS: primary synchronization signal), secondary synchronization signal (SSS: secondary synchronization signal), and physical broadcast channel (PBCH: physical broadcast channel))
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • PBCH physical broadcast channel
  • NR is an expression representing an example of 5G RAT.
  • the new RAT system including NR uses OFDM transmission method or similar transmission method.
  • the new RAT system may follow OFDM parameters that are different from those of LTE.
  • the new RAT system follows the numerology of existing LTE/LTE-A but can support a larger system bandwidth (for example, 100 MHz).
  • one cell may support multiple numerologies. In other words, terminals operating with different numerologies can coexist within one cell.
  • Numerology corresponds to one subcarrier spacing in the frequency domain.
  • different numerologies can be defined.
  • FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.
  • NG-RAN is a NG-Radio Access (NG-RA) user plane (i.e., a new access stratum (AS) sublayer/Packet Data Convergence Protocol (PDCP)/Radio Link Control (RLC)/MAC/ It consists of gNBs that provide PHY) and control plane (RRC) protocol termination for the UE.
  • the gNBs are interconnected through the Xn interface.
  • the gNB is also connected to NGC (New Generation Core) through the NG interface. More specifically, the gNB is connected to the Access and Mobility Management Function (AMF) through the N2 interface and to the User Plane Function (UPF) through the N3 interface.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.
  • numerology can be defined by subcarrier spacing and Cyclic Prefix (CP) overhead.
  • CP Cyclic Prefix
  • multiple subcarrier spacing can be derived by scaling the basic (reference) subcarrier spacing by an integer N (or ⁇ ).
  • N or ⁇
  • the numerology used can be selected independently of the frequency band.
  • various frame structures according to multiple numerologies can be supported.
  • OFDM numerology and frame structures that can be considered in the NR system.
  • Multiple OFDM numerologies supported in the NR system can be defined as Table 1 below.
  • NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, if SCS is 15kHz, it supports wide area in traditional cellular bands, and if SCS is 30kHz/60kHz, it supports dense-urban, lower latency. And it supports a wider carrier bandwidth, and when the SCS is 60kHz or higher, it supports a bandwidth greater than 24.25GHz to overcome phase noise.
  • SCS subcarrier spacing
  • the NR frequency band is defined as two types of frequency ranges (FR1, FR2).
  • FR1 and FR2 can be configured as shown in Table 2 below. Additionally, FR2 may mean millimeter wave (mmW).
  • mmW millimeter wave
  • ⁇ f max 480 ⁇ 10 3 Hz
  • N f 4096.
  • slots are numbered in increasing order of n s ⁇ ⁇ 0,..., N slot subframe, ⁇ -1 ⁇ within a subframe, and within a radio frame. They are numbered in increasing order: n s,f ⁇ ⁇ 0,..., N slot frame, ⁇ -1 ⁇ .
  • One slot consists of consecutive OFDM symbols of N symb slots , and N symb slots are determined according to CP.
  • the start of slot n s ⁇ in a subframe is temporally aligned with the start of OFDM symbol n s ⁇ N symb slot in the same subframe. Not all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or uplink slot can be used.
  • Table 3 shows the number of OFDM symbols per slot (N symb slot ), the number of slots per wireless frame (N slot frame, ⁇ ), and the number of slots per subframe (N slot subframe, ⁇ ) in the general CP.
  • Table 4 represents the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.
  • 1 subframe may include 4 slots.
  • a mini-slot may contain 2, 4, or 7 symbols, or may contain more or fewer symbols.
  • antenna port for example, antenna port, resource grid, resource element, resource block, carrier part, etc. can be considered.
  • resource grid resource element, resource block, carrier part, etc.
  • carrier part etc.
  • the antenna port is defined so that a channel carrying a symbol on the antenna port can be inferred from a channel carrying another symbol on the same antenna port. If the large-scale properties of the channel carrying the symbols on one antenna port can be inferred from the channel carrying the symbols on the other antenna port, the two antenna ports are quasi co-located or QC/QCL. It can be said that they are in a quasi co-location relationship.
  • the wide range characteristics include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.
  • FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.
  • the resource grid is composed of N RB ⁇ N sc RB subcarriers in the frequency domain, and one subframe is composed of 14 ⁇ 2 ⁇ OFDM symbols, but is limited to this. It doesn't work.
  • the transmitted signal is described by one or more resource grids consisting of N RB ⁇ N sc RB subcarriers and OFDM symbols of 2 ⁇ N symb ( ⁇ ) .
  • N RB ⁇ N RB max, ⁇ represents the maximum transmission bandwidth, which may vary between uplink and downlink as well as numerologies.
  • one resource grid can be set for each ⁇ and antenna port p.
  • Each element of the resource grid for ⁇ and antenna port p is referred to as a resource element and is uniquely identified by an index pair (k,l').
  • l' 0,...,2 ⁇ N symb ( ⁇ ) -1 is the symbol in the subframe. refers to the location of When referring to a resource element in a slot, the index pair (k,l) is used.
  • l 0,...,N symb ⁇ -1.
  • the resource element (k,l') for ⁇ and antenna port p corresponds to the complex value a k,l' (p, ⁇ ) .
  • indices p and ⁇ may be dropped, resulting in the complex value a k,l' (p) or It can be a k,l' .
  • Point A serves as a common reference point of the resource block grid and is obtained as follows.
  • - offsetToPointA for primary cell (PCell: Primary Cell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping with the SS/PBCH block used by the terminal for initial cell selection. It is expressed in resource block units assuming a 15kHz subcarrier spacing for FR1 and a 60kHz subcarrier spacing for FR2.
  • - absoluteFrequencyPointA represents the frequency-position of point A expressed as in ARFCN (absolute radio-frequency channel number).
  • Common resource blocks are numbered upward from 0 in the frequency domain for the subcarrier spacing setting ⁇ .
  • the center of subcarrier 0 of common resource block 0 for the subcarrier interval setting ⁇ coincides with 'point A'.
  • the relationship between the common resource block number n CRB ⁇ and the resource elements (k,l) for the subcarrier interval setting ⁇ is given as Equation 1 below.
  • Physical resource blocks are numbered from 0 to N BWP,i size, ⁇ -1 within the bandwidth part (BWP), where i is the number of the BWP.
  • BWP bandwidth part
  • Equation 2 The relationship between physical resource block n PRB and common resource block n CRB in BWP i is given by Equation 2 below.
  • N BWP,i start, ⁇ is the common resource block from which BWP starts relative to common resource block 0.
  • Figure 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied.
  • Figure 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.
  • a slot includes a plurality of symbols in the time domain. For example, in the case of normal CP, one slot includes 7 symbols, but in the case of extended CP, one slot includes 6 symbols.
  • a carrier wave includes a plurality of subcarriers in the frequency domain.
  • RB Resource Block
  • BWP Bandwidth Part
  • a carrier wave may include up to N (e.g., 5) BWPs. Data communication is performed through an activated BWP, and only one BWP can be activated for one terminal.
  • Each element in the resource grid is referred to as a resource element (RE), and one complex symbol can be mapped.
  • RE resource element
  • the NR system can support up to 400 MHz per one component carrier (CC: Component Carrier). If a terminal operating in such a wideband CC (wideband CC) always operates with the radio frequency (RF) chip for the entire CC turned on, terminal battery consumption may increase.
  • CC Component Carrier
  • RF radio frequency
  • different numerology e.g., subcarrier spacing, etc.
  • the maximum bandwidth capability may be different for each terminal.
  • the base station can instruct the terminal to operate only in a part of the bandwidth rather than the entire bandwidth of the broadband CC, and the part of the bandwidth is defined as a bandwidth part (BWP) for convenience.
  • BWP may be composed of consecutive RBs on the frequency axis and may correspond to one numerology (e.g., subcarrier interval, CP length, slot/mini-slot section).
  • the base station can set multiple BWPs even within one CC set for the terminal. For example, in the PDCCH monitoring slot, a BWP that occupies a relatively small frequency area is set, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, if UEs are concentrated in a specific BWP, some UEs can be set to other BWPs for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, etc., a portion of the spectrum from the entire bandwidth can be excluded and both BWPs can be set within the same slot. That is, the base station can set at least one DL/UL BWP to a terminal associated with a broadband CC.
  • the base station may activate at least one DL/UL BWP(s) among the DL/UL BWP(s) set at a specific time (by L1 signaling or MAC CE (Control Element) or RRC signaling, etc.). Additionally, the base station may indicate switching to another configured DL/UL BWP (by L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, based on a timer, when the timer value expires, it may be switched to a designated DL/UL BWP. At this time, the activated DL/UL BWP is defined as an active DL/UL BWP.
  • the terminal may not receive settings for the DL/UL BWP, so in these situations, the terminal This assumed DL/UL BWP is defined as the first active DL/UL BWP.
  • Figure 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using them.
  • a terminal receives information from a base station through downlink, and the terminal transmits information to the base station through uplink.
  • the information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type/purpose of the information they transmit and receive.
  • the terminal When the terminal is turned on or enters a new cell, it performs an initial cell search task such as synchronizing with the base station (S601). To this end, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell identifier (ID: Identifier). You can. Afterwards, the terminal can receive broadcast information within the cell by receiving a physical broadcast channel (PBCH) from the base station. Meanwhile, the terminal can check the downlink channel status by receiving a downlink reference signal (DL RS) in the initial cell search stage.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • ID cell identifier
  • the terminal can receive broadcast information within the cell by receiving a physical broadcast channel (PBCH) from the base station. Meanwhile, the terminal can check the downlink channel status by receiving a downlink reference signal (DL RS) in the initial cell search stage.
  • PBCH physical broadcast channel
  • the terminal After completing the initial cell search, the terminal acquires more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH: physical downlink control channel) according to the information carried in the PDCCH. You can do it (S602).
  • a physical downlink control channel (PDCCH)
  • a physical downlink shared channel (PDSCH: physical downlink control channel)
  • the terminal may perform a random access procedure (RACH) to the base station (steps S603 to S606).
  • RACH random access procedure
  • the terminal may transmit a specific sequence as a preamble through a physical random access channel (PRACH) (S603 and S605) and receive a response message for the preamble through the PDCCH and the corresponding PDSCH ( S604 and S606).
  • PRACH physical random access channel
  • an additional conflict resolution procedure Contention Resolution Procedure
  • the terminal that has performed the above-described procedure then performs PDCCH/PDSCH reception (S607) and Physical Uplink Shared Channel (PUSCH)/Physical Uplink Control Channel (PUCCH) as a general uplink/downlink signal transmission procedure.
  • Physical Uplink Control Channel) transmission (S608) can be performed.
  • the terminal receives downlink control information (DCI) through PDCCH.
  • DCI includes control information such as resource allocation information for the terminal, and has different formats depending on the purpose of use.
  • the control information that the terminal transmits to the base station through the uplink or that the terminal receives from the base station includes downlink/uplink ACK/NACK (Acknowledgement/Non-Acknowledgement) signals, CQI (Channel Quality Indicator), and PMI (Precoding Matrix). Indicator), RI (Rank Indicator), etc.
  • the terminal can transmit control information such as the above-described CQI/PMI/RI through PUSCH and/or PUCCH.
  • Table 5 shows an example of the DCI format in the NR system.
  • DCI format uses 0_0 Scheduling of PUSCH within one cell 0_1 Scheduling of one or multiple PUSCHs in one cell, or instruction of cell group (CG: cell group) downlink feedback information to the UE.
  • CG cell group
  • 0_2 Scheduling of PUSCH within one cell 1_0 Scheduling of PDSCH within one DL cell 1_1 Scheduling of PDSCH within one cell 1_2 Scheduling of PDSCH within one cell
  • DCI format 0_0, 0_1, and 0_2 include resource information related to scheduling of PUSCH (e.g., UL/SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block ( TB: Transport Block) related information (e.g. MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid - Automatic Repeat and request) related information (e.g.
  • DCI Downlink Assignment Index
  • PDSCH-HARQ feedback timing etc.
  • multi-antenna related information e.g., DMRS sequence initialization information, antenna port, CSI request, etc.
  • power control information e.g., PUSCH power control, etc.
  • control information included in each DCI format may be predefined.
  • DCI format 0_0 is used for scheduling PUSCH in one cell.
  • the information contained in DCI format 0_0 is checked by CRC (cyclic redundancy check) by C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier) or CS-RNTI (Configured Scheduling RNTI) or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI). ) is scrambled and transmitted.
  • CRC cyclic redundancy check
  • C-RNTI Cell RNTI: Cell Radio Network Temporary Identifier
  • CS-RNTI Configured Scheduling RNTI
  • MCS-C-RNTI Modulation Coding Scheme Cell RNTI
  • DCI format 0_1 is used to indicate scheduling of one or more PUSCHs in one cell or configured grant (CG: configure grant) downlink feedback information to the UE.
  • the information included in DCI format 0_1 is transmitted after CRC scrambling by C-RNTI or CS-RNTI or SP-CSI-RNTI (Semi-Persistent CSI RNTI) or MCS-C-RNTI.
  • DCI format 0_2 is used for scheduling PUSCH in one cell.
  • Information included in DCI format 0_2 is transmitted after CRC scrambling by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI.
  • DCI format 1_0, 1_1, and 1_2 are resource information related to scheduling of PDSCH (e.g., frequency resource allocation, time resource allocation, virtual resource block (VRB)-physical resource block (PRB) mapping, etc.), transport block (TB) related information (e.g. MCS, NDI, RV, etc.), HARQ related information (e.g. process number, DAI, PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g. antenna port , transmission configuration indicator (TCI), sounding reference signal (SRS) request, etc.), PUCCH-related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each DCI format is Can be predefined.
  • DCI format 1_0 is used for scheduling PDSCH in one DL cell.
  • Information included in DCI format 1_0 is transmitted after CRC scrambling by C-RNTI, CS-RNTI, or MCS-C-RNTI.
  • DCI format 1_1 is used for scheduling PDSCH in one cell.
  • Information included in DCI format 1_1 is transmitted after CRC scrambling by C-RNTI, CS-RNTI, or MCS-C-RNTI.
  • DCI format 1_2 is used for scheduling PDSCH in one cell.
  • Information included in DCI format 1_2 is transmitted after CRC scrambling by C-RNTI, CS-RNTI, or MCS-C-RNTI.
  • An antenna port is defined so that a channel carrying a symbol on the antenna port can be inferred from a channel carrying another symbol on the same antenna port. If the properties of the channel carrying the symbols on one antenna port can be inferred from the channel carrying the symbols on the other antenna port, the two antenna ports are QC/QCL (quasi co-located or quasi co-location) ) can be said to be in a relationship.
  • QC/QCL quadsi co-located or quasi co-location
  • the channel characteristics include delay spread, Doppler spread, frequency/Doppler shift, average received power, and received timing/average. delay) and spatial Rx parameters.
  • the spatial Rx parameter refers to a spatial (reception) channel characteristic parameter such as angle of arrival.
  • the terminal may be configured with a list of up to M TCI-State settings in the upper layer parameter PDSCH-Config to decode the PDSCH according to the detected PDCCH with the DCI intended for the terminal and a given serving cell.
  • the M depends on UE capabilities.
  • Each TCI-State includes parameters for establishing a quasi co-location relationship between one or two DL reference signals and the DM-RS port of the PDSCH.
  • Quasi co-location relationship is established with upper layer parameters qcl-Type1 for the first DL RS and qcl-Type2 (if set) for the second DL RS.
  • the QCL types are not the same regardless of whether the references are the same DL RS or different DL RSs.
  • the quasi co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type of QCL-Info and can take one of the following values:
  • the corresponding NZP CSI-RS antenna port(s) are connected to a specific TRS from a QCL-Type A perspective and a specific SSB from a QCL-Type D perspective. and QCL can be indicated/set.
  • the terminal that receives these instructions/settings receives the corresponding NZP CSI-RS using the Doppler and delay values measured in the QCL-TypeA TRS, and applies the reception beam used for QCL-TypeD SSB reception to the reception of the corresponding NZP CSI-RS. can do.
  • the UE can receive an activation command by MAC CE signaling used to map up to 8 TCI states to the codepoint of the DCI field 'Transmission Configuration Indication'.
  • Multi-TRP Multi-TRP
  • Coordinated Multi Point is a technique in which multiple base stations exchange channel information (e.g., RI/CQI/PMI/LI (layer indicator), etc.) fed back from the terminal (e.g., This refers to a method of effectively controlling interference by cooperatively transmitting to the terminal (using the X2 interface) or utilizing it.
  • CoMP uses Joint Transmission (JT), Coordinated Scheduling (CS), Coordinated Beamforming (CB), Dynamic Point Selection (DPS), and Dynamic Point Blocking ( It can be divided into DPB (Dynamic Point Blocking), etc.
  • JT Joint Transmission
  • CS Coordinated Scheduling
  • CB Coordinated Beamforming
  • DPS Dynamic Point Selection
  • DPB Dynamic Point Blocking
  • the M-TRP transmission method in which M TRPs transmit data to one terminal is largely divided into i) eMBB M-TRP transmission, which is a method to increase the transmission rate, and ii) URLLC M, a method to increase the reception success rate and reduce latency.
  • eMBB M-TRP transmission which is a method to increase the transmission rate
  • URLLC M a method to increase the reception success rate and reduce latency.
  • -It can be distinguished by TRP transmission.
  • the M-TRP transmission method is i) M-DCI (multiple DCI)-based M-TRP transmission in which each TRP transmits a different DCI and ii) S-DCI in which one TRP transmits a DCI. It can be classified into (single DCI) based M-TRP transmission. For example, in the case of S-DCI-based M-TRP transmission, all scheduling information about data transmitted by the M TRP must be delivered to the terminal through one DCI, so dynamic cooperation between two TRPs is possible. It can be used in a backhaul (ideal BH) environment.
  • the UE recognizes the PUSCH (or PUCCH) scheduled by the DCI received through different control resource sets (CORESET) (or CORESET belonging to different CORESET groups) as a PUSCH (or PUCCH) transmitted through different TRPs.
  • CORESET control resource sets
  • PUSCH or PUCCH
  • PDSCH or PDCCH
  • the method for UL transmission e.g., PUSCH/PUCCH
  • the method for UL transmission e.g., PUSCH/PUCCH
  • the method for UL transmission is similar to the method for UL transmission (e.g., PUSCH/PUCCH) transmitted to different panels belonging to the same TRP. The same can be applied.
  • the CORESET group identifier (group ID) described/mentioned in the present disclosure may mean an index/identification information (e.g., ID) for distinguishing CORESET for each TRP/panel.
  • the CORESET group may be a group/union of CORESETs distinguished by an index/identification information (e.g., ID)/the CORESET group ID, etc. for distinguishing CORESETs for each TRP/panel.
  • CORESET group ID may be specific index information defined within the CORSET configuration.
  • the CORESET group can be set/indicated/defined by the index defined within the CORESET configuration for each CORESET.
  • And/or CORESET group ID may mean an index/identification information/indicator, etc. for distinction/identification between CORESETs set/related to each TRP/panel.
  • the CORESET group ID described/mentioned in this disclosure may be replaced with a specific index/specific identification information/specific indicator for distinction/identification between CORESETs set/related to each TRP/panel.
  • the CORESET group ID that is, a specific index/specific identification information/specific indicator for distinguishing/identifying between CORESETs set/related to each TRP/panel, is provided by higher layer signaling (e.g., RRC signaling)/second It may be configured/instructed to the terminal through layer signaling (L2 signaling, for example, MAC-CE)/first layer signaling (L1 signaling, for example, DCI).
  • L2 signaling for example, MAC-CE
  • L1 signaling for example, DCI
  • PDCCH detection may be set/instructed to be performed for each TRP/panel (i.e., for each TRP/panel belonging to the same CORESET group) in the corresponding CORESET group unit.
  • And/or uplink control information e.g., CSI, HARQ-A/N (ACK/NACK), SR (e.g., CSI, HARQ-A/N (ACK/NACK), SR ( scheduling request)) and/or uplink physical channel resources (e.g., PUCCH/PRACH/SRS resources) may be set/instructed to be managed/controlled separately.
  • uplink physical channel resources e.g., PUCCH/PRACH/SRS resources
  • the ControlResourceSet information element (IE: information element), which is an upper layer parameter, is used to set a time/frequency control resource set (CORESET: control resource set).
  • CORESET control resource set
  • the ControlResourceSet IE is a CORESET-related ID (e.g., controlResourceSetID)/index of the CORESET pool for CORESET (e.g., CORESETPoolIndex)/time/frequency resource settings of CORESET/TCI information related to CORESET, etc. may include.
  • the index of the CORESET pool (e.g., CORESETPoolIndex) may be set to 0 or 1.
  • CORESET group may correspond to CORESET pool
  • CORESET group ID may correspond to CORESET pool index (e.g., CORESETPoolIndex).
  • the following two methods can be considered as transmission and reception methods to improve reliability using transmission in multiple TRPs.
  • Figure 7 illustrates a multiple TRP transmission scheme in a wireless communication system to which the present disclosure can be applied.
  • the layer group may mean a predetermined layer set consisting of one or more layers.
  • the amount of transmission resources increases due to the number of layers, and this has the advantage of being able to use robust channel coding at a low code rate for TB.
  • the channels are different from multiple TRPs, diversity ) Based on the gain, the reliability of the received signal can be expected to improve.
  • FIG. 7(b) an example of transmitting different CWs through layer groups corresponding to different TRPs is shown.
  • the TBs corresponding to CW #1 and CW #2 in the figure are the same.
  • CW #1 and CW #2 mean that the same TB is converted to a different CW by a different TRP through channel coding, etc. Therefore, it can be viewed as an example of repeated transmission of the same TB.
  • the code rate corresponding to TB is higher compared to FIG. 7(a).
  • the code rate can be adjusted by indicating different RV (redundancy version) values for the encoded bits generated from the same TB, or the modulation order of each CW can be adjusted. It has the advantage of being
  • the same TB is repeatedly transmitted through different layer groups, and as each layer group is transmitted by different TRPs/panels, the terminal's data reception You can increase your odds.
  • This is referred to as the SDM (Spatial Division Multiplexing)-based M-TRP URLLC transmission method.
  • Layers belonging to different Layer groups are each transmitted through DMRS ports belonging to different DMRS CDM groups.
  • the content related to the multiple TRPs described above was explained based on the SDM (spatial division multiplexing) method using different layers, but this is FDM based on different frequency domain resources (e.g., RB/PRB (set), etc.)
  • FDM frequency division multiplexing
  • TDM time division multiplexing
  • Multi-TRP scheduled by at least one DCI, may be performed as follows:
  • Each transmission occasion is one layer or set of layers of the same TB, and each layer or layer set is associated with one TCI and one set of DMRS port(s).
  • a single codeword with one redundancy version (RV) is used for all layers or sets of layers. From the UE perspective, different coded bits are mapped to different layers or layer sets with specific mapping rules.
  • Each transmission occasion is one layer or set of layers of the same TB, and each layer or set of layers is associated with one TCI and one set of DMRS port(s).
  • a single codeword with one RV is used for each spatial layer or set of layers. RVs corresponding to each spatial layer or layer set may be the same or different.
  • Each transmission occasion is one layer of the same TB with one DMRS port associated with multiple TCI state indexes, or the same layer with multiple DMRS ports associated with multiple TCI state indexes one by one. It is one layer of TB.
  • n (n is a natural number) TCI states in a single slot in non-overlapping frequency resource allocation. Each non-overlapping frequency resource allocation is associated with one TCI state. The same single/multiple DMRS port(s) are associated with all non-overlapping frequency resource allocations.
  • a single codeword with one RV is used over the entire resource allocation. From the UE perspective, a common RB mapping (layer mapping of codewords) applies across all resource allocations.
  • RVs corresponding to each non-overlapping frequency resource allocation may be the same or different.
  • TDM Technique 3
  • n (n is a natural number) TCI states in a single slot in non-overlapping time resource allocation.
  • Each transmission occasion of TB has one TCI and one RV with time granularity of mini-slot. All transmission occasion(s) within a slot use a common MCS with the same single or multiple DMRS port(s). RV/TCI status may be the same or different among transmission occasions.
  • TDM Technique 4
  • DL MTRP-URLLC refers to the same data (e.g., transport block (TB)/DCI) where M-TRP uses different layer/time/frequency resources.
  • TRP 1 transmits the same data/DCI on resource 1
  • TRP 2 transmits the same data/DCI on resource 2.
  • the UE that has received the DL MTRP-URLLC transmission method is transmitted at a different layer.
  • the base station determines which QCL RS/type (i.e. DL TCI state) the UE should use in the layer/time/frequency resource receiving the same data/DCI.
  • the DL TCI state used in resource 1 and the DL TCI state used in resource 2 are indicated.
  • the UE receives the same data/DCI from resource 2. High reliability can be achieved because it is received through resource 1 and resource 2.
  • This DL MTRP URLLC can be applied to PDSCH/PDCCH.
  • UL MTRP-URLLC means that M-TRP receives the same data/UCI from one UE using different layer/time/frequency resources.
  • TRP 1 receives the same data/UCI from the UE on resource 1
  • TRP 2 receives the same data/UCI from the UE on resource 2, and then shares the received data/UCI through the backhaul link between TRPs.
  • a UE configured with the UL MTRP-URLLC transmission method transmits the same data/UCI using different layer/time/frequency resources.
  • the UE receives instructions from the base station on which Tx beam and which Tx power (i.e., UL TCI state) to use in layer/time/frequency resources transmitting the same data/UCI.
  • UL TCI state used by resource 1 and the UL TCI state used by resource 2 are indicated.
  • This UL MTRP URLLC can be applied to PUSCH/PUCCH.
  • using (/mapping) a specific TCI state (or TCI) when receiving data/DCI/UCI for a certain frequency/time/space resource means that in the case of DL, the frequency/ This may mean estimating a channel from DMRS using the QCL type and QCL RS indicated by the corresponding TCI state in time/space resources, and receiving/demodulating data/DCI through the estimated channel. In the case of UL, this may mean transmitting/modulating DMRS and data/UCI using the Tx beam and/or Tx power indicated by the corresponding TCI state in the frequency/time/space resources.
  • the UL TCI state contains Tx beam and/or Tx power information of the UE, and may be set to the UE through other parameters such as spatial relation information instead of the TCI state.
  • the UL TCI state may be indicated directly in the UL grant DCI or may mean spatial relation info of the SRS resource indicated through the SRS resource indicator (SRI) field of the UL grant DCI. or open loop (OL) Tx power control parameters (j: open loop parameters Po and alpha (up to 32 sets of parameter values per cell) connected to the values indicated through the SRI field of the UL grant DCI.
  • index for, q_d index of DL RS for pathloss (PL: pathloss) measurement) (maximum 3 measurements per cell), l: closed loop power control process index (maximum 2 processes per cell) )).
  • MTRP-eMBB means transmitting other data using different M-TRP layers/time/frequency
  • the UE configured with the MTRP-eMBB transmission method receives multiple TCI states through DCI and receives QCL RS for each TCI state. It is assumed that the data received using is different data.
  • the UE can determine whether it is MTRP URLLC transmission/reception or MTRP eMBB transmission/reception by separately using the RNTI for MTRP-URLLC and RNTI for MTRP-eMBB. In other words, if the DCI's CRC is masked using the RNTI for URLLC, it is identified as URLLC transmission, and if the DCI's CRC is masked using the RNTI for eMBB, it is identified as eMBB transmission.
  • the base station can configure MTRP URLLC transmission/reception or MTRP eMBB transmission/reception to the UE.
  • this disclosure applies the proposed method assuming cooperative transmission/reception between 2 TRPs, but it can be expanded and applied in a multi-TRP environment of 3 or more, and can also be expanded and applied in a multi-panel environment.
  • Different TRPs may be recognized by the UE as different Transmission Configuration Indication (TCI) states.
  • TCI Transmission Configuration Indication
  • the UE receiving/transmitting data/DCI/UCI using TCI state 1 means receiving/transmitting data/DCI/UCI from/to TRP 1.
  • the proposals of this disclosure can be used in situations where MTRP cooperatively transmits PDCCH (repeatedly transmitting or dividing the same PDCCH), and some proposals can also be used in situations where MTRP cooperatively transmits PDSCH or cooperatively receives PUSCH/PUCCH. It can be.
  • the meaning that multiple base stations (i.e., MTRP) repeatedly transmit the same PDCCH may mean that the same DCI is transmitted through multiple PDCCH candidates, and is the same as the meaning that multiple base stations repeatedly transmit the same DCI. do.
  • the same DCI may mean two DCIs with the same DCI format/size/payload. Alternatively, even if the payloads of two DCIs are different, if the scheduling results are the same, they can be said to be the same DCI.
  • the slot/symbol location of data and the slot/symbol location of ACK (acknowledgement)/NACK (non-acknowledgement) based on the DCI reception point by the DCI's TDRA time domain resource allocation) field. is determined relatively.
  • the TDRA fields of the two DCIs are different, and as a result, the DCI payload is bound to be different.
  • the number of repetitions R can be directly instructed by the base station to the UE or mutually agreed upon.
  • the scheduling result of one DCI is a subset of the scheduling result of the other DCI, they can be said to be the same DCI.
  • the same data is TDMed and transmitted repeatedly N times
  • DCI 1 received before the first data indicates data repetition N times
  • DCI 2 received after the first data and before the second data indicates data N-1 times. Repetition is indicated.
  • the scheduling data of DCI 2 is a subset of the scheduling data of DCI 1, and since both DCIs are scheduling for the same data, in this case, they can also be said to be the same DCI.
  • multiple base stations i.e., MTRPs
  • transmitting the same PDCCH separately means transmitting one DCI through one PDCCH candidate, but TRP 1 transmits some resources defined by the PDCCH candidate and transmits the remaining resources.
  • TRP 2 is transmitting.
  • the PDCCH candidate is divided into PDCCH candidate 1 corresponding to aggregation level m1 and PDCCH candidate corresponding to aggregation level m2.
  • Divide by 2 and TRP 1 transmits PDCCH candidate 1 and TRP 2 transmits PDCCH candidate 2 through different time/frequency resources.
  • the UE After receiving PDCCH candidate 1 and PDCCH candidate 2, the UE generates a PDCCH candidate corresponding to aggregation level m1+m2 and attempts DCI decoding.
  • the DCI payload (control information bits + CRC) is encoded through one channel encoder (e.g. polar encoder), and the resulting coded bits are ) can be transmitted by dividing it into two TRPs. In this case, the entire DCI payload may be encoded in the coded bits transmitted by each TRP, or only a portion of the DCI payload may be encoded.
  • the DCI payload (control information bits + CRC) can be divided into two (DCI 1 and DCI 2) and each encoded through a channel encoder (e.g., polar encoder). Afterwards, the two TRPs can transmit coded bits corresponding to DCI 1 and coded bits corresponding to DCI 2, respectively.
  • multiple base stations i.e., MTRP
  • MTRP multiple base stations
  • MO monitoring occasions
  • This may mean that coded DCI bits that encode the entire DCI contents of the corresponding PDCCH are repeatedly transmitted through each MO for each base station (i.e., STRP); or,
  • This may mean dividing the coded DCI bits, which encode the entire DCI contents of the PDCCH, into a plurality of parts, and transmitting different parts for each base station (i.e. STRP) through each MO; or,
  • TO refers to a specific time/frequency resource unit through which PDCCH is transmitted.
  • RB resource block
  • TO may refer to each slot, and the PDCCH may be transmitted in RB set 1.
  • TO may mean each RB set, or if the PDCCH was transmitted multiple times over different times and frequencies, TO represents each time/frequency resource. It can mean.
  • the TCI state used for DMRS channel estimation may be set differently for each TO, and TOs with different TCI states may be assumed to be transmitted by different TRPs/panels.
  • the fact that multiple base stations repeatedly or dividedly transmit the PDCCH means that the PDCCH is transmitted across multiple TOs and the union of the TCI states set in the corresponding TOs consists of two or more TCI states. For example, if PDCCH is transmitted across TO 1, 2, 3, and 4, TCI state 1, 2, 3, 4 may be set in TO 1, 2, 3, and 4, respectively, which means that TRP i is connected to TO i. This means that the PDCCH was cooperatively transmitted.
  • each TO is UL transmitted toward a specific TRP or DL received from a specific TRP.
  • UL TO transmitted toward TRP 1 refers to two spatial relationships indicated to the UE, two UL TCIs, two UL power control parameters, and/or two It refers to TO using the first value among pathloss reference signals (PLRS: pathloss reference signals), and UL TO (or TO of TRP 2) transmitted toward TRP 2 is two spatial relations indicated to the UE, two This means TO using the second value of two UL TCIs, two UL power control parameters and/or two PLRSs.
  • the DL TO (or TO of TRP 1) transmitted by TRP 1 refers to one of the two DL TCI states indicated to the UE (for example, when two TCI states are set in CORESET). This means TO using the first value, and the DL TO transmitted by TRP 2 (or TO of TRP 2) is two of the two DL TCI states indicated to the UE (for example, when two TCI states are set in CORESET). This means TO uses the th value.
  • the proposal of this disclosure can be expanded and applied to various channels such as PUSCH/PUCCH/PDSCH/PDCCH.
  • the proposal of the present disclosure can be extended and applied to both the case of repeatedly transmitting the channel over different time/frequency/space resources and the case of divided transmission.
  • Figure 8 illustrates a HARQ-ACK process for downlink data in a wireless communication system to which the present disclosure can be applied.
  • the UE can detect the PDCCH in slot #n.
  • PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and PDCCH indicates DL assignment-to-PDSCH offset (K0) and PDSCH-HARQ-ACK reporting offset (K1).
  • DCI format 1_0, 1_1 may include the following information.
  • RB resources e.g., one or more (dis)contiguous RBs allocated to PDSCH
  • K0 indicates the start position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH in the slot.
  • PDSCH-to-HARQ_feedback timing indicator indicates K1
  • HARQ process ID (Identity) for data (e.g. PDSCH, TB)
  • - PUCCH resource indicator Indicates the PUCCH resource to be used for UCI transmission among a plurality of PUCCH resources in the PUCCH resource set.
  • the UE may receive the PDSCH in slot #(n+K0) according to the scheduling information in slot #n and then transmit UCI through the PUCCH in slot #(n+K1).
  • UCI includes a HARQ-ACK response to PDSCH.
  • the HARQ-ACK response may consist of 1-bit.
  • the HARQ-ACK response may consist of 2-bits if spatial bundling is not configured, and may consist of 1-bit if spatial bundling is configured.
  • the HARQ-ACK transmission point for multiple PDSCHs is designated as slot #(n+K1)
  • UCI transmitted in slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.
  • MBMS Multimedia Broadcast/Multicast Service
  • MBMS is i) a single frequency network (SFN) method in which multiple base station cells are synchronized and transmit the same data through PMCH (physical multicast channel) and ii) broadcast within the cell coverage through PDCCH/PDSCH channels. It can be divided into SC-PTM (Single Cell Point To Multipoint) method.
  • SFN single frequency network
  • SC-PTM Single Cell Point To Multipoint
  • the SFN method is used to provide broadcasting services to a wide area (e.g., MBMS area) through pre-allocated semi-static resources, while the SC-PTM method is used to provide broadcasting services through dynamic resources. It is mainly used to provide broadcasting services only within coverage.
  • SC-PTM provides one logical channel, SC-MCCH (Single Cell Multicast Control Channel), and one or multiple logical channels, SC-MTCH (Single Cell Multicast Traffic Channel). These logical channels are mapped to the downlink shared channel (DL-SCH), which is a transport channel, and the PDSCH, a physical channel.
  • DL-SCH downlink shared channel
  • group-RNTI group-RNTI
  • TMGI temporary multicast group ID
  • ID identity
  • One or more terminals may perform PDCCH monitoring using a specific G-RNTI to receive a specific service.
  • the DRX on-duration section can be set to SC-PTM only for a specific service/specific G-RNTI.
  • the terminals wake up only for a specific on-duration period and perform PDCCH monitoring for the G-RNTI.
  • Radio resource management Radio resource management
  • Downlink Control Information Downlink Control Information
  • Starting and Length Indicator Value (Starting and Length Indicator Value) (Indicating value for the starting symbol index and number of symbols in the slot of PDSCH and/or PUSCH. Scheduling the corresponding PDSCH and/or PUSCH It can be set as a component of the entry constituting the TDRA field within the PDCCH being scheduled.)
  • BandWidth Part (Can be composed of consecutive resource blocks (RB) on the frequency axis.
  • One numerology e.g., SCS, CP length, slot/ It may correspond to a mini-slot duration (slot/mini-slot duration, etc.).
  • multiple BWPs may be set on one carrier (the number of BWPs per carrier may also be limited), but may be activated ( The number of activated BWPs may be limited to a portion (e.g., 1) per carrier.)
  • Control resource set (COntrol REsourse SET) (refers to the time-frequency resource area in which PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)
  • QCL Quasi-Co-Location
  • RS reference signals
  • QCL parameters such as average spread (delay spread), spatial Rx parameter, etc. can be applied to other RSs (or antenna port(s) of the RS).
  • 'typeA' ⁇ Doppler shift, Doppler spread, average delay, delay spread ⁇
  • 'typeB' ⁇ Doppler shift, Doppler spread ⁇
  • 'typeC ' ⁇ Doppler shift, average delay ⁇
  • 'typeD' ⁇ Spatial Rx parameter ⁇ .
  • TCI state is one of DM-RS ports of PDSCH, DM-RS port of PDCCH, or CSI-RS port(s) of CSI-RS resource, etc. Or, it includes a QCL relationship between multiple DL RSs.
  • TCI state index state index corresponding to each code point constituting the field.
  • CE control element
  • the TCI state setting for each TCI state index is set through RRC signaling.
  • the corresponding TCI state is set between DL RSs.
  • configuration between DL RS and UL RS or between UL RS and UL RS may be permitted.
  • Examples of UL RS include SRS, PUSCH DM-RS, PUCCH DM-RS, etc.
  • SRS resource indicator (SRS resource indicator) (indicates one of the SRS resource index values set in 'SRS resource indicator' among the fields in DCI scheduling PUSCH.
  • SRS resource indicator (indicates one of the SRS resource index values set in 'SRS resource indicator' among the fields in DCI scheduling PUSCH.
  • the terminal When transmitting PUSCH, the terminal is linked to the corresponding SRS resource.
  • PUSCH can be transmitted using the same spatial domain transmission filter used for transmitting and receiving the reference signal.
  • the reference RS is transmitted to RRC signaling through the SRS spatial relationship information (SRS-SpatialRelationInfo) parameter for each SRS resource. It is set by SS/PBCH block, CSI-RS, or SRS, etc. can be set as the reference RS.)
  • PLMN ID Public Land Mobile Network identifier
  • C-RNTI MAC CE or UL-SCH uplink shared channel
  • CCCH common control channel
  • SDU service data unit
  • Special Cell For Dual Connectivity operation, the term Special Cell refers to the PCell of the MCG or the PCell of the SCG, depending on whether the MAC entity is associated with a master cell group (MCG) or a secondary cell group (SCG), respectively. Represents PSCell. Otherwise, the term Special Cell refers to PCell. Special Cell supports PUCCH transmission and contention-based random access and is always active.
  • MCG master cell group
  • SCG secondary cell group
  • PCell PCell, PSCell, and SCell (secondary cell).
  • Type 1 CG or Type 2 CG Type 1 configured grant or Type 2 configured grant
  • Fall-back DCI Indicates the DCI format that can be used for fall-back operation, for example, DCI format 0_0, 1_0.
  • Non-fall-back DCI Indicates a DCI format other than fall-back DCI, for example, DCI format 0_1, 1_1.
  • frequency domain resource allocation (frequency domain resource allocation)
  • A/N acknowledgenowledgement/negative acknowledgment information for data received in Cell A (e.g., PDSCH)
  • - CFR common frequency resource for MBS (multicast and broadcast service).
  • One DL CFR provides group common PDCCH and group common PDSCH transmission resources for MBS transmission and reception.
  • One UL CFR provides HARQ-ACK PUCCH resources for group common PDSCH reception.
  • One CFR is one MBS specific BWP or one UE specific BWP. Alternatively, one or multiple CFRs may be set within one UE specific BWP.
  • One CFR is associated with one UE specific BWP.
  • Temporary Mobile Group Identity This is an MBS service identifier and represents a specific service.
  • G-RNTI Group Radio Network Temporary Identifier. Indicates the terminal group identifier that receives MBS.
  • a base station can set a terminal-specific SPS configuration to a specific terminal and allocate repeated downlink SPS transmission resources according to the set period.
  • the DCI of the UE-only PDCCH may indicate activation (SPS activation) of a specific SPS configuration index, and thus the UE can repeatedly receive SPS transmission resources according to the set period.
  • SPS transmission resources are used for initial HARQ (hybrid automatic repeat request) transmission, and the base station may allocate retransmission resources for a specific SPS configuration index through the DCI of the UE-only PDCCH. For example, when the terminal reports HARQ NACK for SPS transmission resources, the base station can allocate retransmission resources through DCI so that the terminal can receive downlink retransmission.
  • the DCI of the UE-only PDCCH may indicate deactivation (SPS release or SPS deactivation) of a specific SPS configuration index, and the UE that receives this does not receive the indicated SPS transmission resources.
  • the cyclic redundancy check (CRC) of DCI for activation/retransmission/deactivation of the SPS is scrambled with Configured Scheduling-RNTI (CS-RNTI).
  • An improved wireless communication system seeks to introduce a DL broadcast or DL multicast transmission method to support MBS (Multicast Broadcast Service) service, similar to the MBMS described above in LTE.
  • the base station provides a point-to-multipoint (PTM) transmission method and/or a point-to-point (PTP: point-to-point) transmission method for DL broadcast or DL multicast transmission.
  • PTM point-to-multipoint
  • PTP point-to-point
  • the base station can set a common frequency resource (CFR).
  • the base station transmits a group common PDCCH (Group Common PDCCH) and a group common PDSCH (Group Common PDSCH) to a plurality of terminals through the corresponding CFR, and the multiple terminals simultaneously receive the same group common PDCCH and group common PDSCH transmission and use the same MBS data is decoded.
  • group common PDCCH Group Common PDCCH
  • group common PDSCH Group Common PDSCH
  • the base station transmits the terminal-only PDCCH and the terminal-only PDSCH to a specific terminal, and only the terminal receives the terminal-only PDCCH and the terminal-only PDSCH.
  • the base station separately transmits the same MBS data to each terminal through different terminal-only PDCCHs and terminal-only PDSCHs. That is, the same MBS data is provided to a plurality of terminals, but different channels (i.e., PDCCH, PDCCH) are used for each terminal.
  • the base station transmits a plurality of group common PDSCHs to a plurality of terminals.
  • the base station can receive the terminal's HARQ-ACK for the group common PDSCH from a plurality of terminals through the terminal-specific PUCCH resource.
  • the terminal transmits ACK as HARQ-ACK information.
  • the terminal transmits NACK as HARQ-ACK information.
  • This HARQ-ACK transmission method is referred to as an ACK/NACK based HARQ-ACK method (mode).
  • the UE can transmit ACK/NACK based HARQ-ACK using UE-dedicated PUCCH resources.
  • the terminal when the NACK only based HARQ-ACK method (mode) is set for multicast PDSCH (or group common PDSCH), the terminal does not perform PUCCH transmission in case of ACK and transmits PUCCH only in case of NACK. Perform.
  • PUCCH is a group common PUCCH resource, and only NACK can be transmitted as HARQ-ACK information.
  • the DCI format (or PDCCH) that schedules reception of the PDSCH carrying the MBS service may be referred to as the MBS DCI format (or PDCCH) or the multicast DCI format (or PDCCH).
  • MBS DCI format or PDCCH
  • PDCCH multicast DCI format
  • a DCI format (or PDCCH) containing a CRC scrambled by a group-RNTI (G-RNTI) or group-configured scheduling-RNTI (G-CS-RNTI) for scheduling PDSCH reception can be converted to the MBS DCI format (or PDCCH). or PDCCH) or multicast DCI format (or PDCCH).
  • the MBS DCI format (or PDCCH) or multicast DCI format (or PDCCH) is the group common DCI format (or PDCCH) according to the PTM method for MBS and the PTP method for MBS. It may include all UE specific DCI formats (or PDCCH) according to.
  • the MBS PDSCH or multicast PDSCH may include both a group common PDSCH according to the PTM method for MBS and a UE specific PDSCH according to the PTP method for MBS.
  • HARQ-ACK information associated with a multicast (or MBS) DCI format (or PDCCH) or multicast PDSCH may be referred to as MBS HARQ-ACK information or multicast HARQ-ACK information.
  • MBS HARQ-ACK information or multicast HARQ-ACK information may be transmitted through UE specific PUCCH/PUSCH according to the PTP/PTM method, and group common PUCCH/PUSCH according to the PTM method. It may also be transmitted via .
  • PDSCH scheduled by unicast DCI format (or PDCCH) and UE-specific SPS PDSCH are unicast. /Can be collectively referred to as UE-specific PDSCH.
  • the terminal can transmit ACK as HARQ-ACK information.
  • the terminal may transmit NACK as HARQ-ACK information.
  • This HARQ-ACK transmission method is referred to as an ACK/NACK based HARQ-ACK method (mode).
  • the UE may not transmit HARQ-ACK information (i.e., ACK) through PUCCH (or PUSCH).
  • HARQ-ACK information
  • PUCCH or PUSCH
  • the terminal may transmit NACK as HARQ-ACK information.
  • This HARQ-ACK transmission method is referred to as a NACK-based HARQ-ACK method (mode).
  • the terminal when the NACK only based HARQ-ACK method (mode) is set, the terminal does not perform PUCCH (or PUSCH) transmission in the case of ACK, and transmits PUCCH (or PUSCH) only in the case of NACK. It can be done.
  • sub-slot, mini-slot, and symbol slot all refer to time units smaller than one slot, and unless clearly separately described for each in the present disclosure, all of them refer to time units smaller than one slot. It can be interpreted with the same meaning. Additionally, all of the above terms may be considered/interpreted as one or more symbols in a slot.
  • Figure 9 illustrates a HARQ-ACK transmission and reception procedure for multicast PDSCH according to an embodiment of the present disclosure.
  • FIG. 9(a) illustrates a signaling procedure between UE1 and a base station (gNB) (beam/TRP 1)
  • FIG. 9(b) illustrates a signaling procedure between UE2 and a base station (gNB) (beam/TRP 2).
  • Figure 9(a) illustrates a case without PDSCH retransmission
  • Figure 9(b) illustrates a case with PDSCH retransmission.
  • two procedures are illustrated together, but are not limited thereto. That is, UE1 and UE2 are not limited to accessing the same base station (via different beams/TRPs), and the two procedures are not limited to proceed together.
  • FIGS. 9(a) and 9(b) are separate procedures, they are shown together for convenience of explanation, and common explanations are given for common steps.
  • the UE enters the RRC connected mode (RRC_CONNECTED mode) and sends a message/message indicating one or more interested MBS services to the base station. Information can be transmitted.
  • the message/information may be delivered through any one of uplink control information (UCI), MAC control element (CE), and RRC messages.
  • UCI uplink control information
  • CE MAC control element
  • RRC Radio Resource Control
  • the interested MBS service in the message/information may mean either TMGI or G-RNTI included in the DL message received from the base station.
  • the DL message may be a service availability message including TMGI#1, TMGI#3, TMGI#5, and TMGI#10. If the UE is interested in TMGI#5, the UE may indicate the order of TMGI#5 in the message/information. That is, the UE can report '3' to the base station.
  • the DL message may be a service availability message including G-RNTI#1, G-RNTI#3, G-RNTI#5, and G-RNTI#10. If the UE is interested in G-RNTI#10, the UE may indicate the order of G-RNTI#10 in the message/information. That is, the UE can report '4' to the base station.
  • the base station Upon receiving the message/information, the base station sets i) a common frequency resource (CFR), ii) one or more groups containing TCI states for one or more G-RNTI value(s). At least one of common PDSCH settings, iii) search space (SS) settings including TCI status for one or more G-RNTI value(s) may be transmitted to the UE through an RRC message (S901a, S901b).
  • CFR common frequency resource
  • SS search space
  • FIG. 9 illustrates one RRC message, it is not limited thereto, and the settings i) to iii) may be provided to the UE through different (or only partially identical) RRC messages.
  • the UE that receives the RRC message from the base station may set one or more group common PDSCH (eg, group common SPS PDSCH) settings according to the RRC message.
  • group common PDSCH eg, group common SPS PDSCH
  • the RRC message may be a group common message transmitted on a PTM Multicast Control Channel (MCCH) or a UE-specific message transmitted on a UE-specific Dedicated Control Channel (DCCH).
  • MCCH PTM Multicast Control Channel
  • DCCH UE-specific Dedicated Control Channel
  • the UE may set at least a G-RNTI value for each MBS CFR or each serving cell.
  • GC-CS-RNTI group common-configured scheduling-RNTI
  • GC-CS-RNTI group common-configured scheduling-RNTI
  • the UE activates, retransmits or releases one or more group common SPS settings You can use CS-RNTI for this.
  • the base station can associate a list of TMGIs or a list of G-RNTIs with one GC-CS-RNTI.
  • the base station may provide the terminal with a list of TMGIs or a list of G-RNTIs associated with the GC-CS-RNTI value.
  • Each PDSCH configuration (e.g., RRC parameter PDSCH-config) may include information elements (IE: information elements) for multicast and/or broadcast at least as shown in Table 6 below.
  • IE information elements
  • Table 6 illustrates the PDSCH-Config IE used to set PDSCH parameters.
  • PDSCH-Config :: SEQUENCE ⁇ dataScramblingIdentityPDSCH INTEGER (0..1023) OPTIONAL, -- Need S dmrs-DownlinkForPDSCH-MappingTypeA SetupRelease ⁇ DMRS-DownlinkConfig ⁇ OPTIONAL, -- Need M dmrs-DownlinkForPDSCH-MappingTypeB SetupRelease ⁇ DMRS-DownlinkConfig ⁇ OPTIONAL, -- Need M tci-StatesToAddModList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-State OPTIONAL, -- Need N tci-StatesToReleaseList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-StateId OPTIONAL, -- Need N vrb-ToPRB-Interleaver ENUMERATED ⁇ n2, n4 ⁇ OPTIONAL, -- Need S resourceAl
  • Table 7 illustrates the description of the fields of PDSCH-config in Table 6 above.
  • the dataScramblingIdentityPDSCH2 is configured if coresetPoolIndex is configured with 1 for at least one CORESET in the same BWP.
  • mapping type A and B Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B.
  • the field dmrs-DownlinkForPDSCH-MappingTypeA applies to DCI format 1_1 and the field dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 applies to DCI format 1_2.
  • mapping type A and B Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B.
  • the field dmrs-DownlinkForPDSCH-MappingTypeB applies to DCI format 1_1 and the field dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 applies to DCI format 1_2.
  • the UE applies the value 64QAM.
  • the field mcs-Table applies to DCI format 1_0 and DCI format 1_1, and the field mcs-TableDCI-1-2 applies to DCI format 1_2.
  • the UE applies the value 1.
  • pdsch-TimeDomainAllocationList, pdsch-TimeDomainAllocationListDCI-1-2List of time-domain configurations for timing of DL assignment to DL data.
  • the field pdsch-TimeDomainAllocationList (with or without suffix) applies to DCI format 1_0 and DCI format 1_1, and if the field pdsch-TimeDomainAllocationListDCI-1-2 is not configured, to DCI format 1_2. If the field pdsch-TimeDomainAllocationListDCI-1-2 is configured, it applies to DCI format 1_2.
  • the network does not configure the pdsch-TimeDomainAllocationList-r16 simultaneously with the pdsch-TimeDomainAllocationList (without suffix) in the same PDSCH-Config.
  • rateMatchPatternGroup1, rateMatchPatternGroup1DCI-1-2 The IDs of a first group of RateMatchPatterns defined in PDSCH-Config->rateMatchPatternToAddModList (BWP level) or in ServingCellConfig ->rateMatchPatternToAddModList (cell level). These patterns can be activated dynamically by DCI.
  • the field rateMatchPatternGroup1 applies to DCI format 1_1, and the field rateMatchPatternGroup1DCI-1-2 applies to DCI format 1_2.
  • rateMatchPatternGroup2 rateMatchPatternGroup2DCI-1-2
  • BWP level bandwidth-Config->rateMatchPatternToAddModList
  • Cell level bandwidth-toAddModList
  • the field rateMatchPatternGroup2 applies to DCI format 1_1
  • the field rateMatchPatternGroup2DCI-1-2 applies to DCI format 1_2.
  • rateMatchPatternToAddModListResources which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns.
  • resourceAllocationType1 ResourceAllocationType1GranularityDCI-1-2Configure the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 1_2. If this field is absent, the granularity is 1 PRB.
  • TCI Transmission Configuration Indicator
  • vrb-ToPRB-Interleaver, vrb-ToPRB-InterleaverDCI-1-2Interleaving unit configurable between 2 and 4 PRBs. When the field is absent, the UE performs non-interleaved VRB-to-PRB mapping.
  • the UE monitors the PDCCH on the SS configured in the configured CFR to receive the DCI whose CRC is scrambled with G-RNTI or G-CS-RNTI (S902a, S902b ).
  • MTCH Multicast Traffic Channel
  • MBS radio bearer MBS radio bearer
  • the base station transmits DCI to the UE on the PDCCH (S903a, S903b).
  • the CRC of the DCI may be scrambled by G-RNTI, G-CS-RNTI, or CS-RNTI.
  • the PDCCH may be a group common PDCCH or a UE-specific PDCCH.
  • the DCI may include the following information (fields).
  • This information may indicate an MBS-specific DCI format or one of the existing DCI formats for MBS.
  • This information indicates the (serving or MBS-specific) cell of the CFR where the group common PDCCH/PDSCH is transmitted or the serving cell of the active BWP of the UE associated with the CFR.
  • This information indicates the BWP ID assigned to the CFR through which group common PDCCH/PDSCH is transmitted or the BWP ID of the active BWP of the UE associated with the CFR.
  • the DCI includes frequency domain resource assignment, time domain resource assignment, VRB-to-PRB mapping, and PRB bundling size indicator.
  • Rate matching indicator ZP CSI-RS trigger, Modulation and coding scheme, New data indicator (NDI), Redundancy version ), HARQ process number, downlink assignment index, transmit power control (TPC) command for scheduled PUCCH, PUCCH resource indicator (PRI) : PUCCH resource indicator), HARQ feedback timing indicator (PDSCH-to-HARQ_feedback timing indicator), antenna port(s), transmission configuration indication (TCI), SRS request ( It may include information about SRS request, DMRS sequence initialization, and priority indicator.
  • the base station identifies i) by group common or UE-specific RRC message or ii) by group common or UE-specific MAC CE, TMGI or G-RNTI or GC-CS-RNTI.
  • One or more of the following service-to-resource mappings for MBS services may be provided to the UE.
  • Data of the MBS service can be carried through the MBS radio bearer (MRB) of the MTCH associated with the MBS service, which is a multicast traffic logical channel.
  • the RRC message may be a group common message transmitted through a PTM Multicast Control Channel (MCCH) or a UE-specific message transmitted through a UE-specific Dedicated Control Channel (DCCH).
  • the DCI that schedules the PDSCH carrying MBS service data may also indicate one or more of short ID, MTCH ID, MRB ID, G-RNTI value, and TMGI value for the MBS service.
  • the UE receives a DCI with a CRC scrambled by the G-RNTI that it is interested in receiving, i) mapping between MBS services and the HARQ process number (HPN) indicated in the DCI, and/or ii ) Based on the mapping between MBS services (if available) and the short ID(s) indicated in the DCI, the UE determines the short ID, MTCH ID, MRB ID, G-RNTI value and TMGI for each PDSCH opportunity.
  • the MBS service associated with one or more of the values can be determined.
  • the base station transmits a PDSCH carrying the corresponding MBS service data to the UE (S904a, S904b) ( Figure 9 illustrates a case where MBS service data mapped to G-RNTI#1 is transmitted), and the UE transmits the determined MBS service ( If you are interested, you can receive PDSCH transmission scheduled by DCI (S905a, S905b).
  • the UE may not receive the PDSCH transmission scheduled by DCI.
  • the UE transmits HARQ feedback to the base station.
  • the UE that has received the group common DCI indicating the PUCCH resource(s) for MBS HARQ-ACK may transmit HARQ-ACK to the base station through PUCCH after receiving the PDSCH scheduled by the DCI as follows (S906a) .
  • group common DCI may indicate a single PUCCH resource indicator (PRI) and a single PDSCH-to-HARQ_feedback timing indicator (K1) for at least ACK/NACK based HARQ-ACK.
  • PRI PUCCH resource indicator
  • K1 PDSCH-to-HARQ_feedback timing indicator
  • UE-specific PUCCH resource allocation for ACK/NACK based HARQ-ACK for group common DCI different UEs in the group are allocated for multicast or unicast (if PUCCH-config for multicast is not set) Within the UE-specific PUCCH configuration (e.g., PUCCH-config), it may be set to at least a different value of PUCCH resource and candidate DL Data-UL ACK (e.g., dl-DataToUL-ACK).
  • Different PUCCH resources may be allocated to different UEs by the same PUCCH resource indicator (PRI) of the group common DCI and the same PDSCH-to-HARQ_feedback timing indicator (K1).
  • PRI PUCCH resource indicator
  • K1 PDSCH-to-HARQ_feedback timing indicator
  • the PUCCH resource indicator (PRI) and PDSCH-to-HARQ_feedback timing indicator (K1) in the UE-specific DCI are unicast regardless of whether or not the PUCCH setting for multicast (e.g., PUCCH-config) is set. It can be interpreted based on the PUCCH settings (e.g., PUCCH-config) for.
  • D. PRI PUCCH Resource Indicator
  • group common DCI DCI
  • Option 1A-1 A list of UE specific PRIs may be included in the DCI.
  • Each PRI in the list has a candidate PUCCH resource ID (e.g., pucch- You can indicate the entry corresponding to the ResourceId) value.
  • Other PRIs in the DCI may direct other items in the PUCCH configuration (e.g., PUCCH-config).
  • the candidate PUCCH resource ID (e.g., pucch-ResourceId) value is set by the upper layer (e.g., RRC) and is provided to other UEs in the same group at least in the multicast PUCCH configuration (e.g., PUCCH-config).
  • a different PUCCH resource ID (eg, pucch-ResourceId) value may be set.
  • Option 1A-2 group common PRI can be included in DCI.
  • a single group common PRI is assigned to the candidate PUCCH resource ID (e.g., pucch-ResourceId) value in the UE specific PUCCH settings (e.g., PUCCH-config) for allocation of the same or different PUCCH resources for all UEs in the group. You can indicate the corresponding entry.
  • the candidate PUCCH resource ID e.g., pucch-ResourceId
  • the UE specific PUCCH settings e.g., PUCCH-config
  • the candidate PUCCH resource ID (e.g., pucch-ResourceId) value is set by the upper layer (e.g., RRC), and at least in the PUCCH configuration for multicast (e.g., PUCCH-config), other A different PUCCH resource ID (eg, pucch-ResourceId) value may be set for the UE.
  • the upper layer e.g., RRC
  • PUCCH configuration for multicast e.g., PUCCH-config
  • a different PUCCH resource ID (eg, pucch-ResourceId) value may be set for the UE.
  • the UE must set the PRI of the group common DCI to the PUCCH settings for multicast (e.g., PUCCH-config) (e.g., PUCCH-config) for HARQ-ACK for the group common PDSCH scheduled by the group common DCI.
  • PUCCH-config indicates the corresponding entry for the candidate PUCCH resource ID (pucch-ResourceId) value. That is, the PRI value of the group common DCI can be interpreted based on the PUCCH settings (e.g., PUCCH-config) for multicast.
  • the UE will allow the PRI of the group common DCI to perform unicast.
  • the PUCCH configuration indicates the corresponding entry for the candidate PUCCH resource ID (pucch-ResourceId) value. That is, the PRI value of group common DCI can be interpreted based on the PUCCH configuration for unicast (e.g., PUCCH-config).
  • E. K1 (PDSCH-to-HARQ_feedback timing indicator) can be indicated by group common DCI as follows.
  • Option 1B-1 A list of UE specific K1 values may be included in the DCI.
  • Each K1 in the list can indicate the same UL slot or a different UL (sub)slot for other UEs in the group.
  • K1 values may be assigned to different UEs. For example, K1-UE1, K2-UE2, K3-UE3,...
  • the K1 value may be shared among multiple UEs (e.g., K1-UE1/UE2, K2-UE3/UE4).
  • one K1 value may be a reference and another K1 value may be assigned based on the reference.
  • ⁇ K1_ref, list of K1_offset (offset from reference) ⁇ may be indicated in the DCI.
  • UE1 may use K1_ref
  • UE2 may use K1_ref + K1_offest
  • UE3 may use K1_ref + K1_offest2.
  • Option 1B-2 group common K1 value may be included in DCI.
  • a single K1 value is the same for all UEs in the group receiving DCI or the candidate DL data-UL ACK value (e.g. dl -DataToUL-ACK) can indicate the corresponding entry. This may be applied when the DCI format of DCI is set within the UE specific PUCCH configuration (eg, PUCCH-config) for the K1 value.
  • PUCCH-config UE specific PUCCH configuration
  • dl-DataToUL-ACK is set by the upper layer (e.g., RRC), at least in the PUCCH configuration for multicast (e.g., PUCCH-config) It may be different for different UEs in the same group.
  • the UE sets the K1 value of the group common DCI to the PUCCH configuration for multicast. It can be assumed that (e.g., PUCCH-config) indicates the corresponding entry for the candidate DL data-UL ACK value (e.g., dl-DataToUL-ACK). That is, the K1 value of group common DCI can be interpreted based on the PUCCH configuration for multicast (e.g., PUCCH-config).
  • the UE sets the K1 value of the group common DCI.
  • the PUCCH configuration for unicast indicates the corresponding entry for the candidate DL data-UL ACK value (e.g., dl-DataToUL-ACK). That is, the K1 value of group common DCI can be interpreted based on the PUCCH configuration for unicast (e.g., PUCCH-config).
  • the PUCCH-config for multicast and/or PUCCH-config for unicast the PUCCH-config for multicast and/or PUCCH-config for unicast
  • TDRA Time Domain Resource Allocation
  • the UE may transmit HARQ NACK to the base station on the PUCCH resource within the configured UL CFR (S906b).
  • the UE may also transmit HARQ-ACK for other PDSCH transmissions, such as unicast SPS PDSCH, dynamic unicast PDSCH, PTP retransmission, and/or dynamic group common PDSCH.
  • HARQ-ACK for other PDSCH transmissions, such as unicast SPS PDSCH, dynamic unicast PDSCH, PTP retransmission, and/or dynamic group common PDSCH.
  • the UE uses the above In step 7, you can construct a codebook based on one or more options.
  • the UE can use NACK only based HARQ-ACK based on the measured RSRP of the serving cell. For example, if the measured RSRP is higher (or higher) than the threshold, NACK only based HARQ-ACK may be transmitted through the group common PUCCH resource indicated by the DCI's PRI. On the other hand, if the measured RSRP is lower than (or below) the threshold, NACK only based HARQ-ACK is changed to HARQ-ACK based HARQ-ACK and can be transmitted through the UE-specific PUCCH resource indicated by the DCI's PRI. there is.
  • RSRP reference signal received power
  • the PDSCH aggregation factor (pdsch-AggregationFactor) is set for the G-RNTI or the base station indicates the repetition number (repeat_number) in DCI
  • the TB scheduled by group common DCI is set for each PDSCH aggregation factor (pdsch-AggregationFactor).
  • pdsch-AggregationFactor may be repeated for the Nth HARQ transmission of the TB within each symbol allocation among each of the number of consecutive slots or among each of the repetition number (repeat_number) number of consecutive slots.
  • the base station that received the HARQ NACK in the TCI state can retransmit the PDCCH and PDSCH in the TCI state within the DL CFR set for retransmission of the TB.
  • the UE may monitor group common and/or UE-specific PDCCH in TCI status on the search space set in DL CFR to receive retransmission of TB (S907b).
  • the base station may retransmit the TB to only one of the UEs in the group by the UE-specific PDCCH, and other UEs may not receive the retransmission of the TB (e.g., because the other UEs successfully received the TB).
  • the UE can receive the PDSCH scheduled by the DCI of the PDCCH (S909b, S910b).
  • the UE will determine the mapping between the MBS service indicated by the DCI and the HPN (HARQ process number) and/or the MBS service indicated by the DCI and (if available) the short ID(s). ), the decoded TB can be considered to be associated with the MTCH, MRB, TMGI, G-RNTI and/or short ID of the MBS service.
  • the UE can transmit HARQ ACK to the base station through PUCCH resources in the UL CFR set according to step 7.
  • the UE may transmit HARQ NACK to the base station on the PUCCH resource within the configured UL CFR (S911b).
  • the UE may also transmit HARQ-ACK for other PDSCH transmissions, such as unicast SPS PDSCH, dynamic unicast PDSCH, PTP retransmission, and/or dynamic group common PDSCH.
  • HARQ-ACK for other PDSCH transmissions, such as unicast SPS PDSCH, dynamic unicast PDSCH, PTP retransmission, and/or dynamic group common PDSCH.
  • the UE uses the above In step 7, you can construct a codebook based on one or more options.
  • the example in FIG. 9 is for convenience of explanation and does not limit the scope of the present disclosure. Some step(s) illustrated in FIG. 9 may be omitted depending on the situation and/or setting.
  • the base station and terminal in FIG. 9 are just one example and can be implemented with the device illustrated in FIG. 13 below.
  • the processor 102/202 of FIG. 13 can control to transmit and receive channels/signals/data/information, etc. using the transceiver 106/206, and transmits or receives channels/signals/ It can also be controlled to store data/information, etc. in the memory 104/204.
  • Base station may refer to a general term for objects that transmit and receive data with a terminal.
  • the base station may be a concept that includes one or more Transmission Points (TPs), one or more Transmission and Reception Points (TRPs), etc.
  • the TP and/or TRP may include a base station panel, a transmission and reception unit, etc.
  • TRP refers to a panel, antenna array, cell (e.g., macro cell / small cell / pico cell, etc.), It can be applied in place of expressions such as TP (transmission point), base station (gNB, etc.).
  • TRPs may be classified according to information (e.g., index, ID) about the CORESET group (or CORESET pool).
  • one terminal is configured to transmit and receive with multiple TRPs (or cells)
  • this may mean that multiple CORESET groups (or CORESET pools) are configured for one terminal.
  • Configuration of such a CORESET group (or CORESET pool) can be performed through higher layer signaling (e.g. RRC signaling, etc.).
  • signaling between one base station and a terminal is considered, but of course, the signaling method can be extended and applied to signaling between multiple TRPs and multiple UEs.
  • the base station may include multiple TRPs, or may be one cell including multiple TRPs.
  • unicast HARQ-ACK with the same/different priorities, group common HARQ-ACK, and/or scheduling request (SR) It can be assigned to the same UL slot.
  • unicast HARQ-ACK may correspond to HARQ-ACK information on reception of a unicast PDSCH
  • group common HARQ-ACK may correspond to HARQ-ACK information on reception of a group common PDSCH.
  • the terminal can set/receive up to 8 SPS configurations, and each SPS configuration can be set to have a unique SPS configuration index.
  • the base station may allocate/configure some of the eight SPS settings for SPS PDSCH transmission for unicast purposes, and allocate/configure others for SPS PDSCH transmission for group common purposes.
  • the terminal can receive the group common SPS PDSCH based on the PTM transmission method. That is, multiple terminals within the group can receive the group common SPS PDSCH.
  • the terminal can transmit HARQ-ACK for the SPS PDSCH for each SPS setting.
  • the UE can configure/receive PUCCH resources for performing the corresponding HARQ-ACK transmission through higher layer messages (e.g. RRC messages, etc.) for each SPS setting.
  • PTM transmission and multicast HARQ-ACK transmission can be supported in the wireless communication system through the following methods/operations.
  • the UE can configure MBS frequency resources within the DL BWP for PDCCH and PDSCH reception for each DL BWP by cfr-Config-Multicast. If cfr-Config-Multicast does not include locationAndBandwidth-Multicast, the MBS frequency resource is the active DL BWP. The UE does not need to receive PDSCH from two serving cells simultaneously.
  • Multicast PDCCH, PDSCH or SPS if applicable, with respect to upper layer parameter values provided by PDCCH Config/PDSCH Config/SPS Config for DL BWP
  • Corresponding higher layer parameter values for PDSCH reception may be provided.
  • the higher layer parameter values provided by the first or second PUCCH-Config if applicable, the corresponding higher layer parameter values for PUCCH transmission associated with multicast PDCCH or PDSCH reception may be provided.
  • the upper layer parameter values provided by SPS-PUCCH-AN or SPS-PUCCH-AN-List if applicable, the corresponding upper layer parameter values for PUCCH transmission associated with multicast SPS PDSCH reception may be provided.
  • the corresponding upper layer parameter values for the HARQ-ACK codebook associated with the multicast HARQ-ACK information can be provided.
  • the terminal can monitor the PDCCH for activating/deactivating SPS PDSCH reception for the corresponding SPS PDSCH configuration, or for scheduling PDSCH reception.
  • the terminal according to the first HARQ-ACK reporting mode or the second HARQ-ACK reporting mode, provides HARQ-ACK information for reception of a transport block (TB) related to the G-RNTI or G-CS-RNTI, respectively, It can be set by harq-Feedback-Option-Multicast for G-RNTI, or sps-HARQ-Feedback-Option-Multicast for G-CS-RNTI.
  • the terminal may determine the priority for PUCCH transmission including multicast HARQ-ACK information according to any HARQ-ACK reporting mode.
  • the terminal when the terminal accurately decodes the TB or detects a DCI format indicating SPS PDSCH release, the terminal generates HARQ-ACK information as an ACK value. Otherwise, the terminal generates HARQ-ACK information with the NACK value. That is, the first HARQ-ACK reporting mode corresponds to the ACK/NACK-based HARQ-ACK mode.
  • the terminal does not transmit PUCCH, which will only include HARQ-ACK information with an ACK value.
  • the second HARQ-ACK reporting mode is used when the number of HARQ-ACK information bits is more than 4, or for the first SPS PDSCH reception after activation of SPS PDSCH reception for SPS configuration, or associated HARQ-ACK information without scheduling PDSCH reception. It does not apply to DCI formats with .
  • the terminal transmits PUCCH only when the HARQ-ACK information bit has a NACK value.
  • the terminal selects a resource from the resource set for PUCCH transmission based on the value of the HARQ-ACK information bit.
  • it may be indicated by moreThanOneNackOnly-Mode to provide HARQ-ACK information bits in PUCCH according to the first HARQ-ACK reporting mode.
  • the UE When the UE is provided with pucch-Config-Multicast1 or pucch-Config-Multicast2 for PUCCH transmission with a priority value, the UE receives the associated HARQ-ACK according to the first HARQ-ACK reporting mode or the second HARQ-ACK reporting mode. For each G-RNTI or G-CS-RNTI that provides information, the corresponding terminal transmits a PUCCH with a priority value according to pucch-Config-Multicast1 or pucch-Config-Multicast2.
  • Reception of the PDSCH providing the initial transmission of the TB is scheduled only by the multicast DCI format.
  • PDSCH reception providing retransmission of the TB is either a multicast DCI format using the same G-RNTI as the G-RNTI of the TB's initial transmission, or a unicast DCI format using a C-RNTI It can be scheduled by .
  • Activation of SPS PDSCH reception using G-CS-RNTI for the corresponding SPS PDSCH configuration can only be provided by multicast DCI format by replacing CS-RNTI with G-CS-RNTI.
  • Deactivation of SPS PDSCH reception using G-CS-RNTI for the corresponding SPS PDSCH configuration replaces the CS-RNTI with the G-CS-RNTI, providing either a multicast DCI format or a CRC scrambled DCI by the CS-RNTI. It can be provided by format.
  • the PDSCH reception providing retransmission of the TB is the same as the unicast DCI format using CS-RNTI or the G-CS-RNTI of the initial transmission of the TB. It can be scheduled by multicast DCI format using G-CS-RNTI.
  • the UE can be configured for each G-RNTI or G-CS-RNTI by harq-FeedbackEnabler-Multicast with a value set to 'enabled'.
  • the terminal HARQ-ACK information may not be provided.
  • the terminal For G-RNTI or G-CS-RNTI, if the terminal is provided with harq-FeedbackEnabler-Multicast with a value set to 'dci-enabler', the terminal Based on the indication by format, it can be decided whether to provide HARQ-ACK information for PDSCH reception.
  • the terminal may provide HARQ-ACK information according to the first HARQ-ACK mode.
  • the terminal Before multiplexing HARQ-ACK information in PUCCH or PUSCH, in order to resolve overlap between the second PUCCH and other PUCCHs or PUSCHs with HARQ-ACK information according to the second HARQ-ACK reporting mode, the terminal must provide HARQ-ACK information When all values of are 'ACK', the terminal may consider transmitting the second PUCCH.
  • the setting for the HARQ-ACK codebook type can be applied to all G-RNTIs or G-CS-RNTIs.
  • the terminal can generate a Type-1 HARQ-ACK codebook.
  • the terminal is provided with pdsch-HARQ-ACK-Codebook-Multicast set to "semi-static”, the terminal can generate a Type-1 HARQ-ACK codebook.
  • the terminal is provided with pdsch-HARQ-ACK-Codebook-Multicast set to "dynamic”, the terminal can generate a Type-2 HARQ-ACK codebook.
  • the case of multiplexing ACK information may be considered.
  • the terminal can attach the HARQ-ACK codebook for multicast HARQ-ACK information to the HARQ-ACK codebook for unicast HARQ-ACK information. For example, if the value of O_ACK+O_SR+O_CSI is less than or equal to 11, the terminal obtains the power of PUCCH transmission along with HARQ-ACK information by the sum of n_(HARQ-ACK) value and n_(HARQ-ACK) value. n_(HARQ-ACK) can be determined.
  • the UE can determine PUCCH resources for PUCCH transmission with HARQ-ACK information (e.g., see 3GPP TS 38.213 clause 9.2/9.2.1/9.2.5).
  • the last DCI format that the UE uses to determine the PUCCH resource is the last unicast It may be DCI format.
  • the UE sends the first HARQ-ACK information associated with multicast SPS PDSCH reception and the second HARQ-ACK information associated with the multicast DCI format (having the same priority value as the first HARQ-ACK information) to the PUCCH.
  • the terminal can determine the PUCCH resource based on the last multicast DCI format.
  • the terminal sends the first HARQ-ACK information associated with unicast SPS PDSCH reception and the second HARQ-ACK information associated with the multicast DCI format (having the same priority value as the first HARQ-ACK information) to the PUCCH.
  • the terminal can determine the PUCCH resource from SPS-PUCCH-AN-List for unicast SPS PDSCH reception.
  • the terminal sends the first HARQ-ACK information associated with unicast SPS PDSCH reception and the second HARQ-ACK information (having the same priority value as the first HARQ-ACK information) associated with multicast SPS PDSCH reception to PUCCH.
  • the terminal can determine the PUCCH resource from the SPS-PUCCH-AN-List for unicast SPS PDSCH reception.
  • the UE when the UE is provided with subslotLengthForPUCCH for PUCCH transmission with a unicast UCI of a specific priority, the UE multiplexes the multicast HARQ-ACK information of the specific priority and the unicast UCI of the specific priority in the PUCCH. There is no need to.
  • CG (configured grant)-UCI and CG-PUSCH are allocated together to the slot. It can be.
  • CG-UCI may correspond to UCI transmitted and received based on the CG method
  • CG-PUSCH may correspond to PUSCH transmitted and received based on the GC method.
  • CG-UCI reported by the terminal to the base station shares the HARQ process number (4 bits), Redundancy version (RV) (2 bits), New data indicator (NDI) (1 bit), and Channel occupancy time (COT). It may include information, etc.
  • HARQ-ACK according to the NACK-only based HARQ-ACK mode (e.g., the above-described second HARQ-ACK reporting mode) is assigned to the same slot as the PUSCH and overlaps, the HARQ-ACK and the PUSCH may be transmitted together. There is a problem that cannot be resolved.
  • the present disclosure proposes a method of determining whether to multiplex the multicast HARQ-ACK and the PUSCH and perform multiplexing between the multicast HARQ-ACK and the PUSCH.
  • FIG. 10 illustrates unicast/multicast PDSCH transmission and HARQ-ACK reporting and PUSCH transmission therefor in a wireless communication system to which the present disclosure can be applied.
  • the terminal in the same cell/BWP can receive (both) unicast PDSCH and multicast PDSCH transmitted through FDM method or TDM method.
  • the terminal can receive unicast PDSCH#1 (1010) and multicast PDSCH#2 (1020) through the TDM method. Additionally, the terminal can receive unicast PDSCH#1 (1010) and multicast PDSCH#3 (1030) through the FDM method.
  • unicast HARQ-ACK transmission (1015) and multicast for unicast PDSCH Multicast HARQ-ACK transmission (1025, 1035) for PDSCH can be transmitted in the same or different UL slots.
  • the CG-UCI may be piggybacked and transmitted on the corresponding PUSCH. That is, there may be cases where CG-UCI is transmitted on a PUSCH that overlaps with the PUCCH for multicast HARQ-ACK. In this regard, it is not clear whether CG-PUSCH/CG-UCI can be multiplexed with multicast HARQ-ACK.
  • Example 1 may be applied in combination with the method of Example 2, or may be partially replaced and applied, and vice versa.
  • This embodiment relates to a method for determining whether to multiplex when CG-UCI/PUSCH and multicast PUCCH are transmitted overlapping in the same slot.
  • the multicast PUCCH is a PUCCH for HARQ-ACK transmission for the multicast PDSCH. That is, in this embodiment, transmitting/dropping the multicast PUCCH may mean transmitting/dropping the corresponding multicast HARQ-ACK.
  • the CG-UCI multiplexing-related parameter for unicast HARQ-ACK (e.g., upper layer parameter cg-UCI-Multiplexing) may not be set to “enabled.” That is, parameters related to CG-UCI multiplexing for unicast HARQ-ACK can also be applied between multicast HARQ-ACK and CG-UCI multiplexing.
  • CG-UCI multiplexing-related parameter for multicast HARQ-ACK e.g. upper layer parameter cg-UCI-Multiplexing-Multicast
  • the terminal may drop PUSCH (and CG-UCI) transmission and transmit multicast PUCCH.
  • the terminal may multiplex multicast HARQ-ACK information in PUCCH transmission or another PUSCH transmission without transmitting the corresponding PUSCH (and CG-UCI).
  • the UE may always drop the multicast PUCCH and transmit PUSCH (and CG-UCI).
  • the terminal may drop one of the multicast PUCCH and CG-UCI/PUSCH according to conditions and transmit the one that was not dropped.
  • the UE may drop the CG-UCI/PUSCH and transmit NACK-only based HARQ-ACK.
  • the terminal may transmit the multicast HARQ-ACK and drop the CG-UCI/PUSCH.
  • the UE may drop the CG-UCI/PUSCH and transmit NACK-only based HARQ-ACK.
  • the terminal may transmit the multicast HARQ-ACK and drop the CG-UCI/PUSCH.
  • the terminal may drop one and transmit the rest based on the assigned/set/indicated priority.
  • the terminal may transmit a high priority (HP) multicast HARQ-ACK and drop the lower priority (LP) PUSCH (and CG-UCI).
  • the terminal may drop the LP multicast HARQ-ACK and transmit the HP PUSCH (and CG-UCI).
  • the CG-UCI multiplexing-related parameter for unicast HARQ-ACK (e.g., upper layer parameter cg-UCI-Multiplexing) may be set to “enabled.” That is, parameters related to CG-UCI multiplexing for unicast HARQ-ACK can also be applied between multicast HARQ-ACK and CG-UCI multiplexing.
  • the case may correspond to a case where a separate/new CG-UCI multiplexing-related parameter for multicast HARQ-ACK (e.g., upper layer parameter cg-UCI-Multiplexing-Multicast) is set to "enabled". there is. That is, separately from unicast HARQ-ACK, CG-UCI multiplexing-related parameters for multicast HARQ-ACK may be newly defined.
  • a separate/new CG-UCI multiplexing-related parameter for multicast HARQ-ACK e.g., upper layer parameter cg-UCI-Multiplexing-Multicast
  • the terminal can multiplex/joint encode multicast HARQ-ACK with CG-UCI.
  • the terminal can jointly encode the multicast HARQ-ACK with CG-UCI by converting the multicast HARQ-ACK to follow the ACK/NACK-based HARQ-ACK mode. there is.
  • the terminal can jointly encode all unicast HARQ-ACK, multicast HARQ-ACK, and CG-UCI.
  • joint encoding in which unicast HARQ-ACK bit(s) are followed by multicast HARQ-ACK bit(s), and multicast HARQ-ACK bit(s) are followed by CG-UCI bit(s). Based on , one UCI can be generated/determined/encoded.
  • the terminal may drop one based on the priority and transmit the remainder.
  • the terminal may transmit HP multicast HARQ-ACK and drop LP PUSCH (and CG-UCI). Conversely, the terminal may drop the LP multicast HARQ-ACK and transmit the HP PUSCH (and CG-UCI).
  • LP unicast HARQ-ACK transmission also overlaps in the same slot, and if the multicast HARQ-ACK and/or PUSCH are HP, the terminal may drop the unicast HARQ-ACK.
  • the terminal drops the multicast HARQ-ACK or PUSCH (and CG-UCI) that is LP and transmits only information corresponding to HP. You can.
  • the terminal drops information corresponding to LP and unicasts corresponding to HP.
  • HARQ-ACK (and other HP-corresponding information) can be transmitted.
  • unicast HARQ-ACK transmissions that are LP also overlap in the same slot, and when multicast HARQ-ACK and/or PUSCH are LP, or unicast HARQ-ACK transmissions that are HP also overlap in the same slot, and multicast HARQ-ACK and/or PUSCH are also overlapped in the same slot.
  • the case where cast HARQ-ACK and/or PUSCH is HP may also be considered.
  • the terminal can jointly encode (all) unicast HARQ-ACK, multicast HARQ-ACK, and/or CG-UCI for the same priority.
  • one UCI can be generated/determined/encoded based on joint encoding of attaching multicast HARQ-ACK bit(s)/CG-UCI bit(s) to unicast HARQ-ACK bit(s). there is.
  • one UCI can be generated/determined/encoded based on joint encoding of appending multicast HARQ-ACK bit(s)/CG-UCI bit(s) followed by unicast HARQ-ACK bit(s). there is.
  • One UCI can be generated/determined/encoded based on encoding.
  • One UCI can be generated/determined/encoded based on encoding.
  • the terminal when the UE is configured by CG settings (e.g. ConfiguredGrantConfig) and multiplexes multicast HARQ-ACK information in PUSCH transmission including CG-UCI, the UE uses cg-UCI-Multiplexing or cg-UCI-Multiplexing -If multicast is provided, the terminal can multiplex multicast HARQ-ACK information in PUSCH transmission. Otherwise, if the multicast HARQ-ACK information and the PUSCH have the same priority index, the terminal may multiplex the multicast HARQ-ACK information in PUCCH transmission or another PUSCH transmission without transmitting the PUSCH. Additionally, if multicast HARQ-ACK information and PUSCH have different priority indices, the terminal may not transmit a low priority channel.
  • CG settings e.g. ConfiguredGrantConfig
  • This embodiment is about a method of converting NACK-only based HARQ-ACK mode to ACK/NACK based HARQ-ACK mode when multiplexing PUSCH and multicast PUCCH.
  • the multicast PUCCH is a PUCCH for HARQ-ACK transmission for the multicast PDSCH. That is, in this embodiment, transmitting/dropping the multicast PUCCH may mean transmitting/dropping the corresponding multicast HARQ-ACK.
  • the terminal can transmit PUCCH and/or PUSCH through the following methods.
  • the PUSCH by DG is the PUSCH allocated/scheduled by DCI, or the PUSCH in the RACH procedure (e.g., MSGA PUSCH in the 2-step RACH procedure, MSG3 by the UL grant of MSG2 in the 4-step RACH procedure) PUSCH).
  • the terminal can simultaneously transmit PUCCH for multicast HARQ-ACK and PUSCH for CG/DG (hereinafter, Scheme 2-1a).
  • the operation of the terminal may be based on the settings of the base station.
  • the UE transmits the PUCCH and PUSCH for multicast HARQ-ACK simultaneously according to Scheme 2-1a (RRC message). via) can be set.
  • the UE is configured to simultaneously transmit PUCCH and PUSCH for multicast HARQ-ACK according to Scheme 2-1a (via RRC message). It can be.
  • the terminal may transmit UCI for multicast HARQ-ACK by piggybacking on PUSCH (hereinafter, method 2-1b).
  • the terminal can switch to the ACK/NACK based HARQ-ACK mode and transmit the multicast HARQ-ACK by piggybacking on the PUSCH. That is, if PUCCH transmission for one or more NACK-only-based HARQ-ACK transmissions occurs together with PUSCH transmission in the same slot, the terminal transmits all NACK-only-based HARQ-ACK transmissions as ACK/NACK-based HARQ-ACK transmissions. You can configure UCI by switching to , and the UCI can be transmitted by piggybacking on PUSCH.
  • the terminal can transmit multicast HARQ-ACK by selecting method 2-1a or method 2-1b depending on the settings of the base station.
  • the terminal piggybacks the UCI on the PUSCH according to Scheme 2-1b and transmits the overlapping HARQ-ACK.
  • Information e.g., overlapping HARQ-ACK bits
  • the terminal can switch to ACK/NACK based HARQ-ACK and multiplex the multicast HARQ-ACK.
  • the terminal may perform transmission according to Scheme 2-1b, and if PUCCH and PUSCH have different priorities, the terminal may perform transmission according to Scheme 2-1a. Transmission can be performed.
  • the UE can drop PUCCH and transmit PUSCH, or drop PUSCH and transmit PUCCH (hereinafter, Scheme 2-2a).
  • the operation of the terminal may be based on the settings of the base station.
  • the terminal may transmit a channel with high priority among PUCCH and PUSCH and drop a channel with low priority.
  • the UE may drop PUCCH and transmit PUSCH, or drop PUSCH and transmit PUCCH, depending on the settings of the base station.
  • the UE may drop PUCCH for multicast HARQ-ACK and transmit PUSCH.
  • the UE may drop PUCCH for NACK-only based HARQ-ACK and transmit PUSCH.
  • the UE may transmit PUCCH for NACK-only based HARQ-ACK and drop PUSCH.
  • the UE may transmit PUSCH according to DG and drop PUCCH.
  • the UE may drop PUSCH according to CG and transmit PUCCH.
  • PUCCH for multicast SPS HARQ-ACK (i.e., HARQ-ACK for multicast SPS PDSCH) may be dropped and PUSCH may be transmitted.
  • PUCCH for dynamic multicast HARQ-ACK i.e., HARQ-ACK for multicast PDSCH scheduled by DCI
  • PUSCH may be dropped.
  • the UE may drop the PUCCH for the multicast HARQ-ACK and transmit the PUSCH.
  • the operation of the terminal may be performed based on the settings of the base station, or may be performed regardless of the settings of the base station.
  • the terminal may transmit UCI for multicast HARQ-ACK by piggybacking on PUSCH (hereinafter, method 2-2b).
  • the terminal can switch to the ACK/NACK based HARQ-ACK mode and transmit the multicast HARQ-ACK by piggybacking on the PUSCH. That is, if PUCCH transmission for one or more NACK-only-based HARQ-ACK transmissions occurs together with PUSCH transmission in the same slot, the terminal transmits all NACK-only-based HARQ-ACK transmissions as ACK/NACK-based HARQ-ACK transmissions. You can configure UCI by switching to , and the UCI can be transmitted by piggybacking on PUSCH.
  • the terminal can transmit multicast HARQ-ACK by selecting method 2-2a or method 2-2b depending on the settings of the base station.
  • the UE piggybacks UCI on the PUSCH according to scheme 2-2b and transmits the overlapping HARQ-ACK.
  • Information e.g., overlapping HARQ-ACK bits
  • the terminal can switch to ACK/NACK based HARQ-ACK and multiplex the multicast HARQ-ACK.
  • the terminal may perform transmission according to Scheme 2-2b, and if PUCCH and PUSCH have different priorities, the terminal may perform transmission according to Scheme 2-2a. Transmission can be performed.
  • the terminal may piggyback and transmit the UCI for the multicast HARQ-ACK to the PUSCH according to the settings of the base station.
  • the terminal can switch to ACK/NACK based HARQ-ACK and transmit the multicast HARQ-ACK by piggybacking on the PUSCH.
  • the terminal drops the PUCCH for multicast HARQ-ACK according to scheme 2-2a and/or scheme 2-2b, or multicast HARQ -The UCI for ACK can be transmitted by piggybacking on PUSCH.
  • the terminal may transmit the 1st PUCCH according to the settings of the base station. It is possible to determine whether to multiplex between the PUCCH and the second PUCCH. For example, when the terminal is set to perform multiplexing by the base station, the terminal multiplexes HARQ-ACK for MSG4 transmission and multicast HARQ-ACK, and uses the multiplexed information to use resources in the first PUCCH or second PUCCH.
  • the terminal transmits the first PUCCH for transmitting HARQ-ACK for MSG4 transmission, and the second PUCCH for multicast HARQ-ACK. can be dropped.
  • FIG. 11 is a diagram illustrating a terminal operation for a multiplexing method between multicast HARQ-ACK and CG-UCI according to an embodiment of the present disclosure.
  • Figure 11 illustrates the operation of a terminal based on the previously proposed method (eg, one or a combination of Embodiments 1 and 2 and detailed embodiments thereof).
  • the example in FIG. 11 is for convenience of explanation and does not limit the scope of the present disclosure. Some step(s) illustrated in FIG. 11 may be omitted depending on the situation and/or setting.
  • the terminal in FIG. 11 is only an example and may be implemented as a device illustrated in FIG. 13 below.
  • the processor 102/202 of FIG. 13 uses the transceiver 106/206 to perform channel/signal/data/information, etc. (e.g., RRC signaling, MAC CE, UL/DL scheduling).
  • DCI, SRS, PDCCH, PDSCH, PUSCH, PUCCH, etc. can be controlled to transmit and receive, and transmitted or received channels/signals/data/information, etc. can be controlled to be stored in the memory 104/204.
  • the terminal may receive configuration information related to CG-UCI multiplexing.
  • the corresponding configuration information may be received through higher layer signaling (e.g., RRC message, etc.).
  • the corresponding setting information may be set/provided by being included in CG (configured grant) related settings.
  • step S1120 the terminal can receive a multicast PDSCH.
  • the multicast PDSCH may correspond to a PDSCH scheduled/directed by a G-RNTI-based DCI.
  • the terminal may transmit HARQ-ACK information for the multicast PDSCH.
  • the PUCCH for the HARQ-ACK information and the PUSCH related to the CG-UCI may be allocated to the same slot.
  • the PUSCH may correspond to a CG-PUSCH on which the CG-UCI is piggybacked.
  • whether the HARQ-ACK information is jointly encoded with the CG-UCI depends on the priority between the HARQ-ACK information and the PUSCH. It can be decided based on ranking.
  • the setting information may follow one or more of the examples below.
  • the configuration information may be related to multiplexing between the CG-UCI and HARQ-ACK information for unicast PDSCH. That is, the terminal can receive configuration information regarding joint encoding between unicast HARQ-ACK and CG-UCI, and can also apply the configuration information to joint encoding between multicast HARQ-ACK and CG-UCI.
  • the configuration information may indicate whether to enable joint encoding between the CG-UCI and HARQ-ACK information for the multicast PDSCH in the case where the PUSCH overlaps. That is, configuration information related to multiplexing between multicast HARQ-ACK and CG-UCI can be defined, and based on this, the terminal can configure/receive whether to activate joint encoding between multicast HARQ-ACK and CG-UCI. there is.
  • Joint encoding performance according to priority between the above-described HARQ-ACK information and the corresponding PUSCH may be as follows.
  • the HARQ-ACK information and the CG-UCI may be jointly encoded.
  • the HARQ-ACK information when the HARQ-ACK information is set as a HARQ-ACK mode based on the NACK value (e.g., NACK-only based HARQ-ACK mode), the HARQ-ACK information is configured as an ACK value and another HARQ based on the NACK value.
  • one or more bits corresponding to the CG-UCI may be attached subsequently to one or more bits corresponding to the HARQ-ACK information.
  • HARQ-ACK information for the multicast PDSCH and HARQ-ACK information for a unicast PDSCH having the same priority as the PUSCH and the PUCCH for HARQ-ACK information for the unicast PDSCH is described above. Can be assigned to the same slot. That is, PUCCH for multicast HARQ-ACK and PUCCH and PUSCH for unicast HARQ-ACK with the same priority can be allocated to the same slot.
  • one or more bits corresponding to HARQ-ACK information for the above-described multicast PDSCH may be attached subsequent to one or more bits corresponding to unicast HARQ-ACK.
  • the terminal performs transmission of the corresponding HARQ-ACK information and transmits the PUSCH (i.e., CG-UCI) can be dropped.
  • any one of the HARQ-ACK information and the PUSCH having the same priority may be dropped.
  • FIG. 12 is a diagram illustrating the operation of a base station for the multiplexing method between multicast HARQ-ACK and CG-UCI according to an embodiment of the present disclosure.
  • Figure 12 illustrates the operation of a base station based on the previously proposed method (eg, one or a combination of Embodiments 1 and 2 and detailed embodiments thereof).
  • the example in FIG. 12 is for convenience of explanation and does not limit the scope of the present disclosure. Some step(s) illustrated in FIG. 12 may be omitted depending on the situation and/or setting.
  • the base station in FIG. 12 is only an example and may be implemented as a device illustrated in FIG. 13 below.
  • the processor 102/202 of FIG. 13 uses the transceiver 106/206 to perform channel/signal/data/information, etc. (e.g., RRC signaling, MAC CE, UL/DL scheduling).
  • DCI, SRS, PDCCH, PDSCH, PUSCH, PUCCH, etc. can be controlled to transmit and receive, and transmitted or received channels/signals/data/information, etc. can be controlled to be stored in the memory 104/204.
  • the base station may transmit configuration information related to CG-UCI multiplexing.
  • the corresponding configuration information may be transmitted through higher layer signaling (e.g., RRC message, etc.).
  • the base station may configure/provide the corresponding configuration information to the terminal by including it in CG (configured grant)-related settings.
  • the base station may transmit a multicast PDSCH.
  • the multicast PDSCH may correspond to a PDSCH scheduled/directed by a G-RNTI-based DCI.
  • the base station may receive HARQ-ACK information for the multicast PDSCH.
  • the PUCCH for the HARQ-ACK information and the PUSCH related to the CG-UCI may be allocated to the same slot.
  • the PUSCH may correspond to a CG-PUSCH on which the CG-UCI is piggybacked.
  • whether the HARQ-ACK information is jointly encoded with the CG-UCI depends on the priority between the HARQ-ACK information and the PUSCH. It can be decided based on ranking.
  • Embodiment 1 and/or Embodiment 2 described above in this disclosure may be applied.
  • a method of performing multiplexing between a PUCCH for HARQ-ACK for group common transmission and a configured grant (CG)/dynamic grant (DG)-based PUSCH can be clarified.
  • whether multiplexing is possible between HARQ-ACK for group common transmission and UCI (e.g., CG-UCI) piggybacked on PUSCH can be made clear between the base station and the terminal. there is.
  • UCI e.g., CG-UCI
  • Figure 13 illustrates a block diagram of a wireless communication device according to an embodiment of the present disclosure.
  • the first wireless device 100 and the second wireless device 200 may transmit and receive wireless signals through various wireless access technologies (eg, LTE, NR).
  • various wireless access technologies eg, LTE, NR.
  • the first wireless device 100 includes one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and/or one or more antennas 108.
  • Processor 102 controls memory 104 and/or transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this disclosure.
  • the processor 102 may process information in the memory 104 to generate first information/signal and then transmit a wireless signal including the first information/signal through the transceiver 106.
  • the processor 102 may receive a wireless signal including the second information/signal through the transceiver 106 and then store information obtained from signal processing of the second information/signal in the memory 104.
  • the memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, memory 104 may perform some or all of the processes controlled by processor 102 or instructions for performing the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this disclosure. Software code containing them can be stored.
  • the processor 102 and memory 104 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR).
  • Transceiver 106 may be coupled to processor 102 and may transmit and/or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and/or receiver. The transceiver 106 can be used interchangeably with an RF (Radio Frequency) unit.
  • a wireless device may mean a communication modem/circuit/chip.
  • the second wireless device 200 includes one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and/or one or more antennas 208.
  • Processor 202 controls memory 204 and/or transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this disclosure.
  • the processor 202 may process the information in the memory 204 to generate third information/signal and then transmit a wireless signal including the third information/signal through the transceiver 206.
  • the processor 202 may receive a wireless signal including the fourth information/signal through the transceiver 206 and then store information obtained from signal processing of the fourth information/signal in the memory 204.
  • the memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, memory 204 may perform some or all of the processes controlled by processor 202 or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this disclosure. Software code containing them can be stored.
  • the processor 202 and memory 204 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR).
  • Transceiver 206 may be coupled to processor 202 and may transmit and/or receive wireless signals via one or more antennas 208. Transceiver 206 may include a transmitter and/or receiver. Transceiver 206 may be used interchangeably with an RF unit.
  • a wireless device may mean a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors 102, 202.
  • one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP).
  • One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this disclosure. can be created.
  • PDUs Protocol Data Units
  • SDUs Service Data Units
  • One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this disclosure.
  • One or more processors 102, 202 may process signals (e.g., baseband signals) containing PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and/or methods disclosed in this disclosure. It can be generated and provided to one or more transceivers (106, 206).
  • One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and may use the descriptions, functions, procedures, suggestions, methods, and/or methods disclosed in this disclosure.
  • PDU, SDU, message, control information, data or information can be obtained according to the operation flow charts.
  • One or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer.
  • One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • the descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc.
  • Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this disclosure may be included in one or more processors (102, 202) or stored in one or more memories (104, 204). It may be driven by the above processors 102 and 202.
  • the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions, and/or sets of instructions.
  • One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, codes, instructions, and/or instructions.
  • One or more memories 104, 204 may consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and/or combinations thereof.
  • One or more memories 104, 204 may be located internal to and/or external to one or more processors 102, 202. Additionally, one or more memories 104, 204 may be connected to one or more processors 102, 202 through various technologies, such as wired or wireless connections.
  • One or more transceivers 106 and 206 may transmit user data, control information, wireless signals/channels, etc. mentioned in the methods and/or operation flowcharts of the present disclosure to one or more other devices.
  • One or more transceivers 106, 206 may receive user data, control information, wireless signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods and/or operational flow charts, etc. disclosed in this disclosure from one or more other devices. there is.
  • one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and may transmit and receive wireless signals.
  • one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. In addition, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be connected to the one or more antennas (108, 208) according to the description and functions disclosed in the present disclosure. , may be set to transmit and receive user data, control information, wireless signals/channels, etc.
  • the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports).
  • One or more transceivers (106, 206) process the received user data, control information, wireless signals/channels, etc. using one or more processors (102, 202), and convert the received wireless signals/channels, etc. from the RF band signal. It can be converted to a baseband signal.
  • One or more transceivers (106, 206) may convert user data, control information, wireless signals/channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals.
  • one or more transceivers 106, 206 may comprise (analog) oscillators and/or filters.
  • the scope of the present disclosure is software or machine-executable instructions (e.g., operating system, application, firmware, program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or computer, and such software or It includes non-transitory computer-readable medium in which instructions, etc. are stored and can be executed on a device or computer. Instructions that may be used to program a processing system to perform the features described in this disclosure may be stored on/in a storage medium or computer-readable storage medium and may be viewed using a computer program product including such storage medium. Features described in the disclosure may be implemented.
  • Storage media may include, but are not limited to, high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or It may include non-volatile memory, such as other non-volatile solid state storage devices.
  • Memory optionally includes one or more storage devices located remotely from the processor(s).
  • the memory, or alternatively the non-volatile memory device(s) within the memory includes a non-transitory computer-readable storage medium.
  • Features described in this disclosure may be stored on any one of a machine-readable medium to control the hardware of a processing system and to enable the processing system to interact with other mechanisms utilizing results according to embodiments of the present disclosure. May be integrated into software and/or firmware.
  • Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments/containers.
  • the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include Narrowband Internet of Things for low-power communication as well as LTE, NR, and 6G.
  • NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2, and is limited to the above-mentioned names. no.
  • the wireless communication technology implemented in the wireless device (XXX, YYY) of the present disclosure may perform communication based on LTE-M technology.
  • LTE-M technology may be an example of LPWAN technology, and may be called various names such as enhanced Machine Type Communication (eMTC).
  • eMTC enhanced Machine Type Communication
  • LTE-M technologies include 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine. It can be implemented in at least one of various standards such as Type Communication, and/or 7) LTE M, and is not limited to the above-mentioned names.
  • the wireless communication technology implemented in the wireless device (XXX, YYY) of the present disclosure may include at least ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication. It may include any one, and is not limited to the above-mentioned names.
  • ZigBee technology can create personal area networks (PAN) related to small/low-power digital communications based on various standards such as IEEE 802.15.4, and can be called by various names.

Landscapes

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

Abstract

Un procédé et un dispositif de transmission/réception d'informations de commande de liaison montante dans un système de communication sans fil sont divulgués. Le procédé mis en œuvre par un terminal dans un système de communication sans fil, selon un mode de réalisation de la présente divulgation, peut comprendre les étapes consistant à : recevoir des informations de configuration relatives au multiplexage de CG-UCI ; recevoir un PDSCH de multidiffusion ; et transmettre des informations HARQ-ACK concernant le PDSCH de multidiffusion. Dans la présente divulgation, un PUCCH pour les informations HARQ-ACK et un PUSCH associé aux CG-UCI sont attribués au même créneau, et si les informations HARQ-ACK sont codées conjointement aux CG-UCI, ces derniers peuvent se conformer à la priorité entre les informations HARQ-ACK et le PUSCH sur la base du fait que le multiplexage des CG-UCI est activé par les informations de configuration.
PCT/KR2023/005502 2022-04-22 2023-04-21 Procédé et dispositif permettant de transmettre/recevoir des informations de commande de liaison montante dans un système de communication sans fil WO2023204683A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263334058P 2022-04-22 2022-04-22
US63/334,058 2022-04-22

Publications (1)

Publication Number Publication Date
WO2023204683A1 true WO2023204683A1 (fr) 2023-10-26

Family

ID=88420342

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/005502 WO2023204683A1 (fr) 2022-04-22 2023-04-21 Procédé et dispositif permettant de transmettre/recevoir des informations de commande de liaison montante dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2023204683A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210051702A1 (en) * 2019-08-13 2021-02-18 Qualcomm Incorporated Configured grant uplink control information (uci) multiplexing for new radio-unlicensed (nr-u)
WO2022030828A1 (fr) * 2020-08-03 2022-02-10 Samsung Electronics Co., Ltd. Procédé et dispositif d'émission et de réception
CN114285534A (zh) * 2020-09-28 2022-04-05 维沃移动通信有限公司 传输信息确定方法、装置和终端

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210051702A1 (en) * 2019-08-13 2021-02-18 Qualcomm Incorporated Configured grant uplink control information (uci) multiplexing for new radio-unlicensed (nr-u)
WO2022030828A1 (fr) * 2020-08-03 2022-02-10 Samsung Electronics Co., Ltd. Procédé et dispositif d'émission et de réception
CN114285534A (zh) * 2020-09-28 2022-04-05 维沃移动通信有限公司 传输信息确定方法、装置和终端

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
MODERATOR (VIVO): "Feature lead summary of [100b-e-NR-unlic-NRU-CG-01] Email discussion", 3GPP DRAFT; R1-2002982, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200420 - 20200430, 1 May 2020 (2020-05-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051879544 *
ZTE: "Discussion on HARQ-ACK multiplexing on PUSCH", 3GPP DRAFT; R1-2201146, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220221 - 20220303, 14 February 2022 (2022-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052109209 *

Similar Documents

Publication Publication Date Title
WO2022145882A1 (fr) Procédé et appareil pour transmettre et recevoir un pdcch dans un système de communication sans fil
WO2021157938A1 (fr) Procédé et dispositif permettant de transmettre/recevoir des informations de commande de liaison descendante dans un système de communication sans fil
WO2021162423A1 (fr) Procédé et dispositif de transmission pour transmettre/recevoir un canal de liaison montante provenant de multiples points de transmission/réception dans un système de communication sans fil
WO2021187966A1 (fr) Procédé et dispositif de transmission/réception en liaison montante ou liaison descendante prenant en charge une planification multi-cellules dans un système de communication sans fil
WO2021162483A1 (fr) Procédé et appareil pour la transmission ou la réception d'un canal de liaison descendante depuis de multiples points de transmission/réception dans un système de communication sans fil
WO2021210881A1 (fr) Procédé et dispositif d'émission et de réception de liaison montante dans un système de communication sans fil
WO2022211539A1 (fr) Procédé et appareil de transmission et de réception d'informations de commande dans un système de communication sans fil
WO2021206446A1 (fr) Procédé et dispositif basés sur un décodage aveugle pour la transmission et la réception d'un canal de liaison descendante dans un système de communication sans fil
WO2023003295A1 (fr) Procédé et dispositif d'émission/réception d'informations d'état de canal dans un système de communication sans fil
WO2022131872A1 (fr) Procédé et dispositif de transmission/réception d'un pdcch dans un système de communication sans fil
WO2022240178A1 (fr) Procédé et dispositif pour réaliser une transmission ou une réception en liaison montante dans un système de communication sans fil
WO2022015061A1 (fr) Procédé et dispositif de transmission et de réception en fonction d'un paramètre spatial par défaut dans un système de communication sans fil
WO2022010314A1 (fr) Procédé et appareil permettant de transmettre et de recevoir des données dans un système de communication sans fil
WO2023136562A1 (fr) Procédé et dispositif de transmission/réception d'informations harq-ack dans un système de communication sans fil
WO2023014152A1 (fr) Procédé et dispositif pour émettre ou recevoir des informations de commande dans un système de communication sans fil
WO2023153860A1 (fr) Procédé et dispositif de transmission/réception d'informations harq-ack dans un système de communication sans fil
WO2022240198A1 (fr) Procédé et dispositif de transmission ou de réception d'informations de harq-ack dans un système de communication sans fil
WO2022240200A1 (fr) Procédé et dispositif d'émission et de réception d'informations de harq-ack dans un système de communication sans fil
WO2023014138A1 (fr) Procédé et appareil d'émission ou de réception commune à un groupe et spécifique à un terminal de données de liaison descendante dans un système de communication sans fil
WO2022240180A1 (fr) Procédé et dispositif pour réaliser une émission et une réception en liaison montante dans un système de communication sans fil
WO2022211472A1 (fr) Procédé et dispositif de transmission et de réception en liaison montante dans un système de communication sans fil
WO2021194217A1 (fr) Procédé et appareil de transmission ou de réception en liaison montante d'après un paramètre spécial dans un système de communication sans fil
WO2023204683A1 (fr) Procédé et dispositif permettant de transmettre/recevoir des informations de commande de liaison montante dans un système de communication sans fil
WO2023204681A1 (fr) Procédé et dispositif pour transmettre et recevoir des informations de commande de liaison montante dans un système de communication sans fil
WO2023204685A1 (fr) Procédé et dispositif de transmission et de réception d'informations de commande de liaison montante dans un système de communication sans fil

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

Country of ref document: EP

Kind code of ref document: A1