WO2022114901A1 - 멀티캐스트 전송을 지원하기 위한 방법 및 장치 - Google Patents
멀티캐스트 전송을 지원하기 위한 방법 및 장치 Download PDFInfo
- Publication number
- WO2022114901A1 WO2022114901A1 PCT/KR2021/017787 KR2021017787W WO2022114901A1 WO 2022114901 A1 WO2022114901 A1 WO 2022114901A1 KR 2021017787 W KR2021017787 W KR 2021017787W WO 2022114901 A1 WO2022114901 A1 WO 2022114901A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- harq
- multicast
- pdsch
- ack
- base station
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 286
- 230000005540 biological transmission Effects 0.000 title abstract description 109
- 230000009849 deactivation Effects 0.000 claims abstract description 39
- 230000004913 activation Effects 0.000 claims abstract description 24
- 238000004891 communication Methods 0.000 claims description 74
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 claims description 59
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 claims description 59
- 238000011017 operating method Methods 0.000 abstract description 2
- 230000011664 signaling Effects 0.000 description 49
- 238000010586 diagram Methods 0.000 description 26
- 238000005516 engineering process Methods 0.000 description 23
- 238000012545 processing Methods 0.000 description 21
- 230000008569 process Effects 0.000 description 15
- 230000000737 periodic effect Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000003111 delayed effect Effects 0.000 description 2
- 238000005562 fading Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/30—Resource management for broadcast services
-
- 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/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
-
- 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/1607—Details of the supervisory signal
- H04L1/1614—Details of the supervisory signal using bitmaps
-
- 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
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
-
- 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
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1848—Time-out mechanisms
- H04L1/1851—Time-out mechanisms using multiple timers
-
- 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
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1854—Scheduling and prioritising arrangements
-
- 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
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1861—Physical mapping arrangements
-
- 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
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1864—ARQ related signaling
-
- 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
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1887—Scheduling and prioritising arrangements
-
- 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
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1896—ARQ related signaling
-
- 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
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- 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
-
- 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/1607—Details of the supervisory signal
- H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
-
- 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
- H04L2001/0092—Error control systems characterised by the topology of the transmission link
- H04L2001/0093—Point-to-multipoint
Definitions
- the present invention relates to multicast technology in a communication system, and more particularly, to a technology for transmitting and receiving multicast physical downlink shared channel (PDSCH) and multicast hybrid automatic repeat request (HARQ) feedback.
- PDSCH physical downlink shared channel
- HARQ multicast hybrid automatic repeat request
- LTE long term evolution
- NR new radio
- 3GPP 3rd generation partnership project
- a frequency band of a 4G communication system eg, a frequency band of 6 GHz or less
- a 5G communication system eg, a communication system supporting NR
- the 5G communication system may support enhanced Mobile BroadBand (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and Massive Machine Type Communication (mMTC).
- eMBB enhanced Mobile BroadBand
- URLLC Ultra-Reliable and Low Latency Communication
- mMTC Massive Machine Type Communication
- the base station may transmit a plurality of physical downlink shared channels (PDSCHs) to the terminal, and the terminal may receive a plurality of PDSCHs from the base station.
- PDSCHs physical downlink shared channels
- the priority of each of the plurality of PDSCHs may be different from each other, and the type (eg, multicast or unicast) of each of the plurality of PDSCHs may be different from each other.
- a method of generating a hybrid automatic repeat request (HARQ) codebook for a plurality of PDSCHs and a method of transmitting the HARQ codebook are required.
- HARQ hybrid automatic repeat request
- An object of the present invention to solve the above problems is to provide a method and apparatus for transmitting and receiving multicast physical downlink shared channel (PDSCH) and multicast hybrid automatic repeat request (HARQ) feedback in a communication system.
- PDSCH physical downlink shared channel
- HARQ multicast hybrid automatic repeat request
- a method of operating a terminal includes receiving an RRC message indicating activation of HARQ-ACK feedback from a base station, information indicating deactivation of the HARQ-ACK feedback
- Receiving a first DCI from the base station comprising: receiving a first multicast PDSCH from the base station based on first scheduling information included in the first DCI; Even when deactivation of feedback is indicated, generating a first HARQ-ACK bit for the first multicast PDSCH, generating a HARQ codebook including the first HARQ-ACK bit, and the HARQ codebook and transmitting to the base station through an uplink channel.
- One field or a combination of two or more fields included in the first DCI may be used to indicate the priority of the first HARQ-ACK bit.
- the T1 HARQ codebook including the first HARQ-ACK bit may be generated.
- One field or a combination of two or more fields included in the first DCI may be used to indicate activation or deactivation of the HARQ-ACK feedback.
- At least one of the HARQ RTT timer and the retransmission timer may not be started in the terminal.
- the method of operating the terminal may further include receiving a second DCI from the base station, and receiving a second multicast PDSCH from the base station based on second scheduling information included in the second DCI. and the HARQ codebook may further include a second HARQ-ACK bit for the second multicast PDSCH.
- the HARQ codebook may include a first multicast HARQ subcodebook including the first HARQ-ACK bit and a second multicast HARQ subcodebook including the second HARQ-ACK bit, and the first multicast
- the PDSCH and the second multicast PDSCH may be distinguished by different multicast identifiers.
- the method of operating the terminal may further include receiving a third DCI from the base station, and receiving a unicast PDSCH from the base station based on third scheduling information included in the third DCI,
- the HARQ codebook may further include a third HARQ-ACK bit for the unicast PDSCH.
- the generating of the HARQ codebook may include generating a first multicast HARQ subcodebook including the first HARQ-ACK bit, and generating a unicast HARQ subcodebook including the third HARQ-ACK bit. , and generating the HARQ codebook by concatenating the first multicast HARQ subcodebook and the unicast HARQ subcodebook.
- the type of the first multicast HARQ subcodebook may be set independently of the type of the unicast HARQ subcodebook, and the priority of the first HARQ-ACK bit is the same as the priority of the third HARQ-ACK bit can be set to
- the first multicast HARQ subcodebook and the unicast HARQ subcodebook may be independently generated.
- a method of operating a terminal includes receiving a first DCI including information indicating deactivation of HARQ-ACK feedback from a base station, including in the first DCI Receiving a first multicast PDSCH from the base station based on the first scheduling information, even when the first DCI indicates deactivation of the HARQ-ACK feedback, a first HARQ for the first multicast PDSCH - Generating an ACK bit, generating a HARQ codebook including the first HARQ-ACK bit, and transmitting the HARQ codebook to the base station through an uplink channel, the HARQ-ACK feedback Even when this is deactivated, another HARQ-ACK bit is generated in the terminal, and when the first HARQ-ACK bit can be multiplexed with another HARQ-ACK bit, the first HARQ-ACK bit is generated.
- At least one of the HARQ RTT timer and the retransmission timer may not be used in the terminal.
- the method of operating the terminal may further include receiving a second DCI from the base station, and receiving a second multicast PDSCH from the base station based on second scheduling information included in the second DCI. and the HARQ codebook may further include a second HARQ-ACK bit for the second multicast PDSCH.
- the HARQ codebook may include a first multicast HARQ subcodebook including the first HARQ-ACK bit and a second multicast HARQ subcodebook including the second HARQ-ACK bit, and the first multicast
- the PDSCH and the second multicast PDSCH may be distinguished by different multicast identifiers.
- the first multicast HARQ subcodebook and the second multicast HARQ subcodebook may be concatenated in the order of the different multicast identifiers.
- the method of operating the terminal may further include receiving an RRC message indicating that a NACK-only feedback scheme is supported from the base station, and the first HARQ-ACK bit is set according to the NACK-only feedback scheme. may be generated, and when the first HARQ-ACK bit is multiplexed with the other HARQ-ACK bit, the NACK-only feedback scheme may not be applied.
- the method of operating the terminal may further include receiving a third DCI from the base station, and receiving a unicast PDSCH from the base station based on third scheduling information included in the third DCI,
- the HARQ codebook may further include a third HARQ-ACK bit for the unicast PDSCH.
- the generating of the HARQ codebook may include generating a first multicast HARQ subcodebook including the first HARQ-ACK bit, and generating a unicast HARQ subcodebook including the third HARQ-ACK bit. , and generating the HARQ codebook by concatenating the first multicast HARQ subcodebook and the unicast HARQ subcodebook, wherein the first multicast HARQ subcodebook may be distinguished by a multicast identifier. have.
- the first multicast HARQ subcodebook and the unicast HARQ subcodebook may be independently generated.
- the UE may receive a multicast physical downlink shared channel (PDSCH) and a unicast PDSCH from a base station, and a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) bit for the multicast PDSCH and a unicast PDSCH It is possible to generate a HARQ codebook including the HARQ-ACK bit for , and transmit the HARQ codebook to the base station.
- the UE may generate the HARQ codebook in consideration of the priority.
- the terminal may transmit the HARQ codebook to the base station based on an indication of activation or deactivation of the HARQ-ACK feedback of the base station. In particular, even when HARQ-ACK feedback is deactivated, the UE may transmit the HARQ codebook to the base station as needed. Therefore, the HARQ-ACK feedback procedure can be efficiently performed, and the performance of the communication system can be improved.
- FIG. 1 is a conceptual diagram illustrating a first embodiment of a communication system.
- FIG. 2 is a block diagram showing a first embodiment of a communication node constituting a communication system.
- FIG. 3 is a conceptual diagram illustrating a first embodiment of a multicast transmission method.
- FIG. 4 is a conceptual diagram illustrating a first embodiment of a method for allocating a PDSCH.
- 5A is a conceptual diagram illustrating a second embodiment of a method for allocating a PDSCH.
- 5B is a conceptual diagram illustrating a third embodiment of a method for allocating a PDSCH.
- 6A is a conceptual diagram illustrating a first embodiment of a PUCCH allocation method.
- 6B is a conceptual diagram illustrating a second embodiment of a PUCCH allocation method.
- FIG. 7 is a conceptual diagram illustrating a first embodiment of PUCCH transmission timing.
- FIG. 8 is a conceptual diagram illustrating a first embodiment of the time sequence of PDCCH and PUCCH in unicast/multicast transmission.
- FIG. 9 is a block diagram illustrating a first embodiment of a method for generating an HARQ codebook based on method 4.1-1.
- FIG. 10 is a block diagram illustrating a second embodiment of a method for generating an HARQ codebook based on method 4.1-1.
- 11 is a block diagram illustrating a first embodiment of a method for generating an HARQ codebook based on method 4.1-6.
- first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component.
- the term “and/or” includes a combination of a plurality of related listed items or any of a plurality of related listed items.
- “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B”. Also, in the embodiments of the present application, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B”.
- a communication system to which embodiments according to the present invention are applied will be described.
- the communication system to which the embodiments according to the present invention are applied is not limited to the content described below, and the embodiments according to the present invention can be applied to various communication systems.
- a communication system may be used in the same sense as a communication network (network).
- FIG. 1 is a conceptual diagram illustrating a first embodiment of a communication system.
- the communication system 100 is a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6).
- the communication system 100 is a core network (core network) (eg, S-GW (serving-gateway), P-GW (packet data network (PDN)-gateway), MME (mobility management entity)) may include more.
- core network eg, S-GW (serving-gateway), P-GW (packet data network (PDN)-gateway), MME (mobility management entity)
- the core network is an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc.
- AMF access and mobility management function
- UPF user plane function
- SMF session management function
- SMS session management function
- the plurality of communication nodes 110 to 130 may support a communication protocol (eg, an LTE communication protocol, an LTE-A communication protocol, an NR communication protocol, etc.) defined in a 3rd generation partnership project (3GPP) standard.
- a plurality of communication nodes 110 to 130 are CDMA (code division multiple access) technology, WCDMA (wideband CDMA) technology, TDMA (time division multiple access) technology, FDMA (frequency division multiple access) technology, OFDM (orthogonal frequency division) technology multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA Technology, Non-orthogonal Multiple Access (NOMA) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi
- FIG. 2 is a block diagram showing a first embodiment of a communication node constituting a communication system.
- the communication node 200 may include at least one processor 210 , a memory 220 , and a transceiver 230 connected to a network to perform communication.
- the communication node 200 may further include an input interface device 240 , an output interface device 250 , a storage device 260 , and the like.
- Each of the components included in the communication node 200 may be connected by a bus 270 to communicate with each other.
- each of the components included in the communication node 200 may not be connected to the common bus 270 but to the processor 210 through an individual interface or an individual bus.
- the processor 210 may be connected to at least one of the memory 220 , the transceiver 230 , the input interface device 240 , the output interface device 250 , and the storage device 260 through a dedicated interface. .
- the processor 210 may execute a program command stored in at least one of the memory 220 and the storage device 260 .
- the processor 210 may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods according to embodiments of the present invention are performed.
- Each of the memory 220 and the storage device 260 may be configured as at least one of a volatile storage medium and a non-volatile storage medium.
- the memory 220 may be configured as at least one of a read only memory (ROM) and a random access memory (RAM).
- the communication system 100 includes a plurality of base stations 110 - 1 , 110 - 2 , 110 - 3 , 120 - 1 and 120 - 2 , and a plurality of terminals 130 - 1, 130-2, 130-3, 130-4, 130-5, 130-6).
- Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may form a macro cell.
- Each of the fourth base station 120-1 and the fifth base station 120-2 may form a small cell.
- the fourth base station 120-1, the third terminal 130-3, and the fourth terminal 130-4 may belong to the cell coverage of the first base station 110-1.
- the second terminal 130-2, the fourth terminal 130-4, and the fifth terminal 130-5 may belong to the cell coverage of the second base station 110-2.
- the fifth base station 120-2, the fourth terminal 130-4, the fifth terminal 130-5, and the sixth terminal 130-6 may belong to the cell coverage of the third base station 110-3.
- the first terminal 130-1 may belong to the cell coverage of the fourth base station 120-1.
- the sixth terminal 130-6 may belong to the cell coverage of the fifth base station 120-2.
- each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 is a NodeB (NB), an evolved NodeB (eNB), gNB, an advanced base station (ABS), HR - BS (high reliability-base station), BTS (base transceiver station), radio base station (radio base station), radio transceiver (radio transceiver), access point (access point), access node (node), RAS (radio access station) ), MMR-BS (mobile multihop relay-base station), RS (relay station), ARS (advanced relay station), HR-RS (high reliability-relay station), HNB (home NodeB), HeNB (home eNodeB), It may be referred to as a road side unit (RSU), a radio remote head (RRH), a transmission point (TP), a transmission and reception point (TRP), and the like.
- RSU road side unit
- RRH radio remote head
- TP transmission point
- TRP transmission and
- Each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, 130-6 includes a user equipment (UE), a terminal equipment (TE), an advanced mobile station (AMS), HR-MS (high reliability-mobile station), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable It may be referred to as a portable subscriber station, a node, a device, an on board unit (OBU), and the like.
- UE user equipment
- TE terminal equipment
- AMS advanced mobile station
- HR-MS high reliability-mobile station
- OBU on board unit
- each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may operate in different frequency bands or may operate in the same frequency band.
- Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be connected to each other through an ideal backhaul link or a non-ideal backhaul link.
- information can be exchanged with each other through an ideal backhaul link or a non-ideal backhaul link.
- Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be connected to the core network through an ideal backhaul link or a non-ideal backhaul link.
- Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 transmits a signal received from the core network to the corresponding terminals 130-1, 130-2, 130-3, 130 -4, 130-5, 130-6), and a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) is transmitted to the core network can be sent to
- each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 transmits a multi-input multi-output (MIMO) (eg, single user (SU)- MIMO, multi user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, direct communication between terminals (device) to device communication, D2D) (or Proximity services (ProSe)), Internet of Things (IoT) communication, dual connectivity (DC), and the like may be supported.
- MIMO multi-input multi-output
- SU single user
- MU multi user
- massive MIMO massive MIMO
- CoMP coordinated multipoint
- CA carrier aggregation
- IoT Internet of Things
- DC dual connectivity
- each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, 130-6 is the base station 110-1, 110-2, 110-3, and 120-1. , 120-2) and corresponding operations, and operations supported by the base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be performed.
- the second base station 110-2 may transmit a signal to the fourth terminal 130-4 based on the SU-MIMO method, and the fourth terminal 130-4 may transmit a signal based on the SU-MIMO method.
- a signal may be received from the second base station 110 - 2 .
- the second base station 110 - 2 may transmit a signal to the fourth terminal 130 - 4 and the fifth terminal 130 - 5 based on the MU-MIMO scheme, and the fourth terminal 130 - 4 . and each of the fifth terminals 130 - 5 may receive a signal from the second base station 110 - 2 by the MU-MIMO method.
- Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may transmit a signal to the fourth terminal 130-4 based on the CoMP scheme, and the fourth The terminal 130-4 may receive signals from the first base station 110-1, the second base station 110-2, and the third base station 110-3 by the CoMP method.
- Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 is a terminal 130-1, 130-2, 130-3, 130-4 belonging to its own cell coverage. , 130-5, 130-6) and the CA method can transmit and receive signals.
- Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 controls D2D between the fourth terminal 130-4 and the fifth terminal 130-5. and each of the fourth terminal 130-4 and the fifth terminal 130-5 may perform D2D under the control of the second base station 110-2 and the third base station 110-3, respectively. .
- a corresponding second communication node is a method (eg, a method corresponding to the method performed in the first communication node) For example, reception or transmission of a signal) may be performed. That is, when the operation of the terminal is described, the corresponding base station may perform the operation corresponding to the operation of the terminal. Conversely, when the operation of the base station is described, the corresponding terminal may perform the operation corresponding to the operation of the base station.
- the purpose of the eMBB service may be processing of large-capacity traffic
- the purpose of the URLLC service may be to reduce end-to-end latency and error rate
- the purpose of the mMTC service may be processing of intermittent or periodic traffic in a geographic area with high UE density.
- One communication system can support one or more service scenarios simultaneously.
- one communication system may be operated by variously adjusting configuration parameters (eg, numerology) of the OFDM waveform.
- One neuronology may be used in the LTE communication system, and one or more neuronologies may be applied according to a situation in the NR communication system.
- a time division duplex (TDD)-based communication system may support both an eMBB service and a URLLC service.
- the low-latency performance of the URLLC service may be improved.
- uplink hybrid automatic repeat request-acknowledgement (UL HARQ-ACK) is required to support downlink (DL) traffic
- the delay time experienced by DL traffic may be determined by a period in which the DL slot and the UL slot repeatedly appear.
- the delay time experienced by the UL traffic may be determined by a cycle in which the DL slot and the UL slot are repeated.
- the type of slot may be dynamically converted to suit a situation.
- the UE may know the DL symbol, the UL symbol, or the FL (flexible) symbol in units of symbols.
- the FL symbol may be redirected to a DL symbol or a UL symbol.
- the type of subframe may be converted to suit the situation.
- the type of subframe may be a DL subframe, a UL subframe, and a special subframe. There is no concept of a FL subframe (or FL symbol) in the LTE communication system.
- PUSCH physical uplink shared channel
- PUCCH physical uplink control channel
- PUSCH can be dynamically scheduled. Alternatively, it may be indicated that the PUSCH is periodically transmitted.
- the periodic PUSCH transmission method may be divided into two methods according to a periodic PUSCH transmission indication method.
- UL-DCI downlink control information
- UL-DCI downlink control information
- periodic PUSCH transmission may be indicated only by higher layer signaling instead of UL-DCI.
- a base station may transmit a physical downlink shared channel (PDSCH) to one or more terminals.
- PDSCH physical downlink shared channel
- RRC radio resource control
- the base station uses a UE-specific radio network temporary identifier (RNTI) (eg, C (cell)-RNTI) to scramble the UE-specific PDCCH to the terminal can be sent to
- RNTI radio network temporary identifier
- the UE may obtain a UE-specific PDCCH by using the UE-specific RNTI, and may receive the UE-specific PDSCH based on the UE-specific PDCCH.
- the base station may perform transmission for terminals belonging to one group.
- the base station may transmit a scrambled group-common PDCCH using a group-common RNTI.
- UEs may obtain a group-common PDCCH using a group-common RNTI, and may receive a group-common PDSCH based on the group-common PDCCH.
- PTM method 2 the base station may perform transmission for terminals belonging to one group.
- the base station may transmit a scrambled UE-specific PDCCH to each of the terminals using a UE-specific RNTI (eg, C-RNTI).
- a UE-specific RNTI eg, C-RNTI
- Each of the terminals may obtain a UE-specific PDCCH based on the UE-specific RNTI.
- the UE may receive the group-common PDSCH based on the group-common RNTI.
- the PTM method 1 and/or the PTM method 2 may be set or instructed to the terminal without a separate description.
- a communication node eg, a base station, a terminal
- a sensing procedure eg, LBT (Listen before talk) procedure or CCA (clear channel assessment) procedure
- the sensing procedure may have different set variables according to the importance of data.
- a communication node eg, a base station, a terminal
- a signal and/or a channel may be transmitted without a sensing procedure.
- a beam-based sensing procedure in an unlicensed band can be divided into two types.
- the sensing procedure may be divided into an omni-directional sensing procedure and a directional sensing procedure.
- the base station may not perform a transmission operation when energy is detected in a direction that does not interfere with the terminal. This problem may be referred to as the “exposed node problem”.
- the directional sensing procedure is applied, a hidden node problem may occur. In this case, even if energy is not detected in the sensing procedure of the base station, the transmission of the base station may interfere with other terminals (eg, hidden nodes).
- Uplink control information may include a scheduling request (SR), channel state information (CSI), hybrid automatic repeat request-acknowledgement (HARQ-ACK), and/or link recovery request (LRR).
- SR scheduling request
- CSI channel state information
- HARQ-ACK hybrid automatic repeat request-acknowledgement
- LRR link recovery request
- Each of SR, CSI, HARQ-ACK, and LRR included in UCI may be referred to as a control element. That is, UCI may include one or more control elements (eg, SR, CSI, HARQ-ACK, and/or LRR).
- UCI may be used to manage downlink.
- Information (eg, SR, CSI, HARQ-ACK, and/or LRR) included in UCI may vary according to a UCI type.
- UCI may be transmitted through a physical uplink control channel (PUCCH) and/or a physical uplink shared channel (PUSCH).
- PUCCH and PUSCH overlap in one or more symbols, UCI may be transmitted through PUSCH instead of PUCCH. In this case, the PUCCH may not be transmitted.
- the frequency band (eg, FR1) in which the PUCCH is transmitted is different from the frequency band (eg, FR2) in which the PUSCH is transmitted, the PUSCH and the PUCCH may be transmitted simultaneously.
- the UE may compare the priority of the PUCCH and the priority of the PUSCH. Transmission having a lower priority among PUCCH transmission and PUSCH transmission may be dropped.
- the size of UCI may be expressed as the sum of the number of bits representing the UCI type. The size of the UCI may be used to determine the PUCCH resource.
- One UCI type may correspond to one PUCCH resource on a one-to-one basis.
- the UE may select an appropriate PUCCH resource set again based on the sum of sizes of the corresponding UCI types.
- the UE may apply the PUCCH resource index indicated in downlink control information (DCI).
- DCI downlink control information
- transmission resources of the multiplexed UCI types may be indicated by a PUCCH resource index configured by RRC signaling. This operation may mean that multiplexed UCI types are periodically transmitted.
- the base station may indicate (eg, configure) "multiplexing of UCI types" and/or "PUCCH resource for transmission of UCI type(s)" to the terminal through RRC signaling.
- RRC signaling may mean an RRC message.
- the PUCCH resource may be determined as follows.
- the base station may transmit PUCCH-configCommon and/or PUCCH-config to the terminal through RRC signaling (eg, system information block (SIB)1 transmission or dedicated signaling).
- the PUCCH resource set(s) for the UE may be indicated by PUCCH-configCommon and/or PUCCH-config.
- the UE may select one PUCCH resource set from among the PUCCH resource sets indicated by the base station according to the UCI size.
- the PUCCH resource set may include a plurality of PUCCH resources. Each of the plurality of PUCCH resources may be indicated by a PUCCH resource index.
- the base station may inform the terminal of the PUCCH resource index through DCI or RRC signaling.
- the UE may check the PUCCH resource indicated by the PUCCH resource index received from the base station among the plurality of PUCCH resources.
- a configured grant (CG)-UCI may be used for CG PUSCH transmission in an unlicensed band.
- the CG-UCI may include transport block (TB) information and/or channel occupancy time (COT) information.
- the TB information may include a HARQ process number, a redundancy version (RV), and/or a new data indicator (NDI).
- the COT information may include COT sharing information.
- CG-UCI may be transmitted in PUSCH.
- the UE may transmit UCI and/or CG-UCI.
- the priority of UCI may be different from that of CG-UCI.
- UCI and/or CG-UCI may be used for TB transmission. Therefore, the TB priority may be considered as “UCI priority” or “CG-UCI priority”.
- CPSCH physical downlink shared channel
- PSSCH physical sidelink shared channel
- TB priority may be set, and TB priority is "UCI priority " or "CG-UCI priority”.
- Periodic CSI and/or semi-persistent CSI may have a low priority.
- SR priority and LRR priority may be set by RRC signaling.
- the priority of HARQ-ACK for PSSCH may be set to be the same as TB priority. "When the priority of HARQ-ACK exceeds the threshold of the priority indicated by RRC signaling" is distinguished from "when the priority of HARQ-ACK does not exceed the threshold of the priority indicated by RRC signaling" can be The priority of HARQ-ACK for PSSCH may not correspond to TB priority on a one-to-one basis as an exception. In this case, the TB priority may be derived from the priority of the HARQ-ACK for the PSSCH.
- HARQ-ACK may mean HARQ-ACK bit, HARQ-ACK information, HARQ-ACK feedback, or HARQ-ACK response.
- UCI and CG-UCI having different priorities may not be multiplexed.
- the UE may transmit one piece of control information having a high priority among UCI and CG-UCI (eg, high priority (HP) UCI or HP CG-UCI).
- the UE may transmit one piece of control information (eg, low priority (LP) UCI or LP CG-UCI) having a lower priority among UCI and CG-UCI.
- the UE may assume that HP UCI types are multiplexed, and may generate HP PUCCH (eg, virtual HP PUCCH) based on the assumption.
- the UE may assume that LP UCI types are multiplexed, and may generate an LP PUCCH (eg, a virtual LP PUCCH) based on the assumption.
- the UE may transmit the HP PUCCH including the HP UCI type(s). Therefore, only UCI types having the same priority can be multiplexed.
- one UCI type among UCI types may be dropped as needed.
- the base station may anticipate the UCI type dropped from the terminal. Accordingly, the base station may instruct the terminal to transmit the dropped UCI type (eg, UCI or CG-UCI) by performing a scheduling operation for the dropped UCI type.
- the serving base station may transmit a PDCCH including scheduling information (eg, DCI) of the PDSCH including multicast data to the terminal.
- the UE may receive the PDCCH using a separate radio identifier (eg, a separate RNTI) and may decode the DCI included in the PDCCH.
- the radio identifier for multicast may be referred to as M (multicast)-RNTI, G-RNTI, GS-RNTI, G-CS-RNTI, or MCCH-RNTI.
- broadcast transmission and multicast transmission may be described without distinction from each other. Methods for multicast transmission may be applied for broadcast transmission, and methods for broadcast transmission may be applied for multicast transmission.
- a terminal that has established an RRC connection with a base station may be referred to as an "RRC connected terminal".
- a terminal that does not establish an RRC connection with a base station may be referred to as an "RRC non-connected terminal", "RRC inactive terminal", or "RRC idle terminal”.
- a plurality of RRC-connected terminals may belong to one group (eg, a multicast group). RRC-connected terminals belonging to one group may receive the same multicast data.
- a plurality of RRC unconnected terminals may belong to one group (eg, a multicast group). RRC unconnected terminals belonging to one group may receive the same multicast data.
- a group may mean a multicast group or a multicast identifier. The multicast identifier may be used to distinguish different multicast PDSCHs.
- FIG. 3 is a conceptual diagram illustrating a first embodiment of a multicast transmission method.
- a base station may support multicast transmission (eg, multicast service) to RRC-connected terminals as well as RRC-connected terminals.
- Group(s) including one or more terminals may be configured, and terminals belonging to each group may receive the same data.
- the RRC connected terminal(s) and the RRC unconnected terminal(s) may receive the same broadcast PDSCH.
- An RRC-connected terminal belonging to one group may receive a multicast PDSCH.
- the UE may receive one or more multicast PDSCHs.
- the UE may receive one or more broadcast PDSCHs.
- the base station may allocate a PDSCH to each terminal.
- the base station may allocate a PDSCH (eg, common PDSCH, multicast PDSCH) to terminals belonging to one group. That is, the base station may allocate a PDSCH to each group.
- a PDSCH eg, common PDSCH, multicast PDSCH
- Each of the BWP and PDSCH may be appropriately configured and/or allocated so that all terminals belonging to the group receive the PDSCH.
- the base station must perform a complex scheduling operation. In this case, when the unicast PDSCH is previously allocated to a specific UE, the multicast PDSCH must be allocated from a resource other than the resource to which the unicast PDSCH is allocated. That is, resource allocation of the multicast PDSCH may be delayed.
- the multicast PDSCH may be a common PDSCH transmitted to terminals belonging to the group (eg, all terminals).
- the unicast PDSCH must be allocated from a resource other than the resource to which the multicast PDSCH is allocated. That is, resource allocation of the unicast PDSCH may be delayed.
- the maximum number of PDSCHs that the UE can process in the same slot or the same subslot may be defined as UE capability.
- the terminal capability may be referred to as processing capability.
- FIG. 4 is a conceptual diagram illustrating a first embodiment of a method for allocating a PDSCH.
- the base station may allocate four PDSCHs to one terminal.
- the four PDSCHs may include a multicast PDSCH, a unicast PDSCH, and/or a system information (SI) PDSCH.
- the multicast PDSCH may be a PDSCH including multicast data.
- the unicast PDSCH may be a PDSCH including unicast data.
- the SI PDSCH may be a PDSCH including system information. If reception and decoding of one or more PDSCHs is possible according to the UE capability, the UE may decode some or all PDSCHs in one slot or one subslot.
- the base station may perform scheduling such that more PDSCHs than terminal capability (eg, processing capability) are allocated.
- the UE may select PDSCH(s) that the UE can process in consideration of priority among PDSCHs allocated by the base station.
- priorities may be considered in the configuration of PDSCHs.
- the priority of the PDSCH may be defined based on the RNTI. Alternatively, the priority of the PDSCH may be explicitly indicated.
- Method 2.1-2 The priority of PDSCH processing may follow the priority of PDSCH or RNTI scrambling DCI.
- M-RNTI priority with other RNTIs may be considered.
- MsgB-RNTI, TC-RNTI, RA-RNTI, etc. may be considered in an initial access procedure or a random access procedure.
- C-RNTI may be considered.
- the M-RNTI may have the lowest priority.
- the UE may not receive the multicast PDSCH according to processing capability.
- Method 2.1-3 In method 2.1-2, an M-RNTI may have the lowest priority among RNTIs.
- a priority (eg, a priority of the multicast PDSCH) may be introduced.
- the base station may indicate to the terminal the priority of the corresponding PDSCH in the PDSCH allocation or configuration procedure.
- the RRC message for configuring multicast PDSCH1 may include the priority of multicast PDSCH1.
- DCI for allocating multicast PDSCH2 may include a priority of multicast PDSCH2.
- the value of the priority may be a natural number.
- Priorities between PDSCHs may be determined according to a comparison result between the corresponding priority and a preset boundary. The priority when the priority value falls within the preset boundary may be different from the priority when the priority value deviates from the preset boundary.
- a preset boundary may be determined in a technical standard. Alternatively, the preset boundary may be given by RRC signaling.
- the priority for multicast PDSCH processing may be known to the UE in advance.
- the UE may process the multicast PDSCH before the unicast PDSCH based on the priority.
- the UE may process the unicast PDSCH before the multicast PDSCH based on the priority.
- the UE may determine a priority for multicast PDSCH processing based on a preset boundary.
- the UE may process the multicast PDSCH before the unicast PDSCH based on the priority according to the preset boundary.
- the UE may process the unicast PDSCH before the multicast PDSCH based on the priority according to the preset boundary.
- the above-described operation may be utilized for comparison of the multicast PDSCH and the unicast PDSCH.
- the UE may regard the priority of the multicast PDSCH as the same as the priority of the unicast PDSCH for URLLC traffic.
- the UE may regard the priority of the multicast PDSCH as the same as the priority of the unicast PDSCH for eMBB traffic.
- the priority of the multicast PDSCH may be directly compared with the priority of the unicast PDSCH. In this case, the priority of the multicast PDSCH may be limited to two values. In this case, the priority of the multicast PDSCH may be utilized not only as a priority for decoding the PDSCH but also as a priority for transmitting the HARQ-ACK.
- the priority of the multicast PDSCH may be limited to two values, and may be directly compared with the priority of the unicast PDSCH.
- the UE may compare priorities among the plurality of multicast PDSCHs, and may select a multicast PDSCH to be decoded according to processing capability.
- the plurality of PDSCHs may be allocated in chronological order. 5 and 6 below, the time order of "PDCCH - PDSCH - PUCCH" may be maintained.
- FIG. 5A is a conceptual diagram illustrating a second embodiment of a PDSCH allocation method
- FIG. 5B is a conceptual diagram illustrating a third embodiment of a PDSCH allocation method.
- the order of the PDCCH and the order of the PDSCH may be maintained in in-order scheduling, and the order of the PDCCH and the order of the PDSCH may be different from each other in the out-of-order scheduling.
- FIG. 6A is a conceptual diagram illustrating a first embodiment of a PUCCH allocation method
- FIG. 6B is a conceptual diagram illustrating a second embodiment of a PUCCH allocation method.
- the order of the PDSCH and the order of PUCCH in in-order feedback may be maintained, and the order of PDSCH and order of PUCCH in out-of-order feedback may be different from each other.
- the order of "PDCCH - PDSCH - PUCCH" may be maintained in in-order scheduling and in-order feedback.
- the time interval between the PDCCH and the PDSCH eg, slot offset or subslot offset
- K1 may satisfy the condition of in-order scheduling/feedback (eg, in-order scheduling and/or in-order feedback).
- Some terminals belonging to the group may operate in a power saving mode.
- the base station may set K0 between the PDCCH and the PDSCH to be larger than a preset boundary, and may inform the terminal of K0. Since K0 may be large in the procedure for dynamically allocating the multicast PDSCH, out-of-order scheduling may occur frequently.
- scheduling/feedback other than in-order scheduling/feedback may occur in the UE.
- Out-of-order scheduling/feedback may mean out-of-order scheduling and/or out-of-order feedback.
- the UE may process scheduling for a PDSCH having a high priority.
- the base station may separately provide a priority for the above-described operation to the terminal.
- a specific field of DCI may indicate the priority of the PDSCH.
- the base station may indicate to the terminal the priority of the PDSCH allocated by RRC signaling or the PDSCH activated by DCI.
- the above-mentioned priority may be applied to the processing order of the multicast PDSCH.
- the priority of the unicast PDSCH and the priority of the multicast PDSCH may have different values. If "the priority of the multicast PDSCH is outside the preset boundary" or "the priority of the multicast PDSCH belongs to the preset boundary", the priority of the multicast PDSCH may be compared with the priority of the unicast PDSCH. .
- Method 2.1-7 In high-priority multicast transmission, out-of-order scheduling/feedback for low-priority multicast may be allowed.
- the UE may receive the PDSCH and may transmit the PUCCH when the HARQ-ACK feedback is activated.
- the UE may demodulate a control channel element (CCE) and configure a PDCCH candidate to decode the DCI.
- CCE control channel element
- the maximum number of CCEs and/or the maximum number of PDCCHs that the terminal can process in one slot or one subslot may be defined in the technical standard. The reason why the maximum number of CCEs and/or the maximum number of PDCCHs is limited is that the UE needs to perform a channel estimation operation for CCE reception and a polar code decoding operation for PDCCH reception.
- the base station may appropriately configure the search space to the terminal so as not to exceed the maximum number of CCEs and/or the maximum number of PDCCHs.
- the base station may set the search space to the terminal to exceed the maximum number of CCEs and/or the maximum number of PDCCHs.
- the terminal may not search a part of the search space according to a preset procedure.
- the number of CCEs processed by the terminal may be less than or equal to the maximum number of CCEs
- the number of PDCCHs processed by the terminal may be less than or equal to the maximum number of PDCCHs.
- only a UE-specific search space may be supported in the SCell.
- a common search space as well as a UE-specific search space may be supported in the SCell according to configuration.
- the above-mentioned constraint may be a constraint on the unicast PDCCH. Therefore, it is necessary to improve the above-mentioned restrictions in a scenario in which multicast transmission is additionally considered. There is a need for a method capable of supporting both unicast transmission and multicast transmission while satisfying the constraints of the maximum number of PDCCHs and/or the maximum number of CCEs in each of the PCell and the SCell.
- a search space for multicast may belong to a group common search space.
- the search space for multicast may belong to a UE-specific search space (USS).
- the search space for multicast may belong to a Type3-PDCCH CSS set or a CSS set having a separate type.
- Method 2.2-1 can be applied to both SCell and PCell.
- Method 2.2-1 M-RNTI may be observed in Type3-PDCCH CSS set and/or USS set.
- a control resource set (CORESET) and a search space may be configured in the same carrier so that all terminals belonging to the group monitor the search space using the M-RNTI. Accordingly, the first terminal may interpret the corresponding carrier as a PCell, and the second terminal may interpret the carrier as an SCell.
- a separate CSS set may be set in the terminal as a search space for multicast. Even in this case, the UE may monitor the search space using the M-RNTI.
- the number of each of CCEs and PDCCHs processed by UEs observing the M-RNTI in the SCell may not exceed the maximum number. Accordingly, the base station may properly set the search space set to the terminal(s). However, when many terminals exist, it may be difficult to properly set a search space (or a search space set). Therefore, even in the SCell, a method for the UE to select a part of the search space is required.
- Method 2.2-2 The operation of selecting a partial search space set in order to limit the number of CCEs and/or PDCCHs (eg, the number of receptions) may be applied not only to the PCell but also to the SCell.
- the number of PDCCHs and the number of CCEs may be summed in the order of IDs of the search space set, and the number of CCEs and the number of PDCCHs that the UE should receive in the CSS set and the USS set may be set so as not to be greater than the maximum number.
- a configuration variable (eg, monitoringCapabilityConfig) configured in the PCell may be indicated to the UE as another RRC configuration variable in the SCell. If CORESETPoolIndex is indicated to the terminal, a setting variable (eg, monitoringCapabilityConfig) set to the terminal may be applied only to the first CORESET. Alternatively, a separate RRC configuration variable indicating the first CORESET or the second CORESET may be indicated to the UE.
- monitoringCapabilityConfig may also be set in the SCell.
- Method 2.2-4 An RRC setting variable for selecting the first CORESET or the second CORESET in the PCell or SCell to which monitoringCapabilityConfig is applied may be introduced.
- “Operation in which the terminal receives only a part of the search space set” may be performed according to the instruction of the base station. “Operation in which the terminal receives only a part of the search space set” may be performed only when multicast is supported.
- Method 2.2-5 In method 2.2-2, even when there is no separate RRC signaling of the base station, if M-RNTI is configured in the terminal, the terminal may perform an operation of selecting a search space set.
- Method 2.2-6 In method 2.2-2, the operation of selecting a search space set in the SCell may be enabled by RRC signaling.
- the number of CCEs and/or PDCCHs received by the UE observing the M-RNTI in the SCell may exceed the maximum number supported by the UE. Accordingly, “operation not receiving a part of the search space set” may be enabled or disabled.
- the base station may instruct the terminal to enable or disable "operation not receiving a part of the search space set" using RRC signaling.
- the UE may perform the operation of selecting the USS set in all PDCCH monitoring occasions (MOs). If disabling of "operation not to receive a part of the search space set" is indicated to the terminal, the terminal may expect that the number of CCEs and/or PDCCHs in all search space sets is not greater than the maximum number.
- Method 2.2-7 In method 2.2-6, the operation of selecting a search space set in the SCell may be performed in all PDCCH MOs.
- the operation of counting the number of valid search space sets does not always need to be performed.
- the UE may perform the operation of selecting the search space set only in the time resource for observing the M-RNTI.
- Method 2.2-8 In method 2.2-6, the operation of selecting the search space set in the SCell may be performed only at a time (eg, a slot) when the M-RNTI is observed.
- the DCI format decoded by the UE may be set in various ways. For example, two DCI formats may be configured, and the two DCI formats may be scrambled by M-RNTI. The lengths of the two DCI formats may be different from each other.
- the size of the first DCI format among the two DCI formats may be the same as the size of DCI format 1_0.
- the size of the second DCI format among the two DCI formats may be the same as the size of DCI format 1_1.
- the size of DCI format 1_0 may mean the size of DCI format 1_0 scrambled by C-RNTI received from the CSS set.
- the base station may transmit a multicast PDSCH to the terminal, and the terminal may perform decoding on the multicast PDSCH to derive HARQ-ACK.
- the UE may transmit the PUCCH including the derived HARQ-ACK to the base station.
- HARQ-ACK feedback may be enabled or disabled according to an instruction of the base station. When HARQ-ACK feedback is enabled, a transmission method of PUCCH will be described.
- the PDCCH for multicast may include PUCCH resource information.
- the PUCCH resource set may be identically configured to terminals belonging to the same group (eg, the same multicast group). Alternatively, the PUCCH resource set may be independently configured for each UE. "Even if the same UL BWP and the same PUCCH resource index are set and the first CCE of the PDCCH for which the M-RNTI is searched is the same", if the PUCCH resource sets set in the UE are different, the PUCCH resources indicated by the PDCCH are different PUCCH can be interpreted as resources.
- Method 3-1 The PUCCH resource set in which the HARQ-ACK for the multicast PDSCH is transmitted may be equally indicated to the terminals belonging to the group.
- the PUCCH resource set indicated in PUCCH-configcommon may be used.
- the UE may acquire multicast PDSCH allocation information through DCI scrambled with M-RNTI or DCI scrambled with C-RNTI.
- the PUCCH resource set may be interpreted based on PUCCH-configcommon regardless of the RNTI.
- the UE may transmit one or two HARQ-ACK bit(s) to the base station.
- the UE may transmit one PUCCH including HARQ-ACK bits for the plurality of multicast PDSCHs to the base station.
- the UE may check the PUCCH resource based on the late PDCCH (ie, the late received PDCCH) among the PDCCHs.
- the base station may know that two HARQ-ACK bits will be transmitted for the late PDCCH. Accordingly, the base station may allocate the PUCCH resource in consideration of the two HARQ-ACK bits.
- the UE may transmit HARQ-ACK bits for three or more multicast PDSCHs on the same PUCCH. For example, when "in a communication system supporting time division duplex (TDD), when UL resources are small and multicast PDSCH is periodically transmitted", HARQ-ACK bits for a plurality of multicast PDSCHs are one It can correspond to PUCCH.
- TDD time division duplex
- FIG. 7 is a conceptual diagram illustrating a first embodiment of PUCCH transmission timing.
- two PDSCHs may correspond to one PUCCH.
- the base station may schedule a plurality of PDSCHs to correspond to one PUCCH.
- the UE may reduce the size of the HARQ-ACK. For example, the UE may maintain the size of the HARQ-ACK to 2 bits or less.
- the base station may allocate a PUCCH resource capable of transmitting three or more HARQ-ACK bits.
- the PUCCH resource set is configured by PUCCH-configcommon, only two or less HARQ-ACK bits may be transmitted. In order to support the above-described operation, methods 3-2 and 3-3 below may be considered.
- Method 3-2 The UE may expect not to transmit three or more HARQ-ACK bits.
- Method 3-3 The UE can express three or more HARQ-ACK bits as one HARQ-ACK bit by performing AND bundling on three or more HARQ-ACK bits, and one HARQ-ACK bit It can be transmitted on UCCH.
- AND bundling may be performed.
- the base station may perform many retransmission procedures.
- only two multicast PDSCHs can be selected.
- the UE may select two multicast PDSCHs from among three or more multicast PDSCHs based on the reception time of the multicast PDSCH.
- Method 3-4 UE may select two multicast PDSCHs earlier or two multicast PDSCHs later in the time domain from among three or more multicast PDSCHs, and HARQ-ACK bit for the selected two multicast PDSCHs can only be transmitted. That is, the terminal can expect that the above-described operation is supported.
- the base station may indicate a new PUCCH resource set to the terminal.
- a new PUCCH resource set may be configured independently (eg, differently) for each UE. This operation may be methods 3-5. Alternatively, a new PUCCH resource set may be identically configured for all terminals belonging to the same group. This operation may be methods 3-6.
- Method 3-5 PUCCH resource set for supporting unicast (hereinafter referred to as “unicast PUCCH resource set”) is a PUCCH resource set for supporting multicast (hereinafter referred to as “multicast PUCCH resource set”) can be reused as
- the UE may multiplex three or more HARQ-ACK bits using the PUCCH resource set configured by the base station. This operation may mean "all terminals belonging to the group transmit HARQ-ACK to the base station using a separate PUCCH resource". In multicast transmission, three or more HARQ-ACK bits may not occur frequently. Therefore, the PUCCH resource set may not be set to be shared by the group. Accordingly, the UE may utilize a unicast PUCCH resource set for HARQ-ACK transmission for multicast PDSCH(s).
- the UE In order to use the unicast PUCCH resource set, the UE must establish an RRC connection with the base station and receive PUCCH-config from the corresponding base station. Since the PUCCH resource set supporting the transmission of three or more HARQ-ACK bits is not configured for all terminals, multicast support may have limitations. To solve this problem, a separate PUCCH resource set for multicast may be indicated to UEs. For example, the PUCCH resource set may be included in the RRC configuration variable for configuring multicast transmission to the UE.
- the base station may indicate to the terminals a PUCCH resource set for supporting multicast transmission using RRC signaling.
- the PUCCH resource set may be used differently according to priority (eg, priority of multicast PDSCH). In this case, two multicast PUCCH resource sets may be configured for the UE.
- One or more HARQ-ACK bits may be generated according to the number of multicast PDSCHs.
- a common PUCCH resource set to support this operation may be indicated to the UE(s). Since the PUCCH resource set supports transmission of n HARQ-ACK bits, not only PUCCH formats 0 and 1 but also PUCCH formats 2, 3, and 4 may be used. n may be a natural number.
- PUCCH format 0 or 1 may be used, and a separate PUCCH resource set other than the unicast PUCCH resource set may be used as the multicast PUCCH resource set.
- the separate PUCCH resource set may be one of a plurality of multicast PUCCH resource sets configured in the terminal.
- a case in which two or more multicast transmissions are configured to the terminal may be considered.
- the priority may always be maintained the same.
- Two or more multicast transmissions may have different priorities.
- the base station may indicate different PUCCH timings for two or more multicast transmissions.
- the UE may transmit HARQ-ACK in one PUCCH.
- the UE may transmit only the HARQ-ACK for the multicast PDSCH for one priority.
- the UE may multiplex HARQ-ACK bits for multicast PDSCHs for different priorities in one PUCCH.
- Such an operation may be indicated by a combination of RRC signaling and DCI.
- Method 3.1-1 The base station may instruct the terminal to perform "the operation of multiplexing HARQ-ACK bits for multicast PDSCHs having different priorities" through RRC signaling.
- Method 3.1-2 DCI for allocating the latest DCI or the multicast PDSCH having the highest priority indicates the performance of "the operation of multiplexing HARQ-ACK bits for multicast PDSCHs having different priorities" It may include information or information indicating performance of "selecting one multicast PDSCH without multiplexing HARQ-ACK bits".
- Method 3.1-3 Allowance of "operation of multiplexing HARQ-ACK bits for multicast PDSCHs having different priorities" may be indicated by RRC signaling, and the latest DCI or multicast having the highest priority DCI for allocating the cast PDSCH may indicate “multiplexing of HARQ-ACK bits” or “selection of one multicast PDSCH”.
- the PUCCH resource may be indicated by DCI for allocating one multicast PDSCH.
- the DCI scrambled by M-RNTI in PTM method 1 cannot individually indicate the size of the HARQ-ACK bit of each terminal belonging to the group.
- the HARQ-ACK bit for one multicast PDSCH eg, the multicast PDSCH having the highest priority
- the base station is preferably fed back to the base station.
- the UE may feed back HARQ-ACK bits for all multicast PDSCHs to the base station.
- the PUCCH resource may be indicated by the DCI last received from the terminal.
- the UE may not always report the HARQ-ACK for the multicast PDSCH to the base station.
- the base station may consider that the TB has been transmitted without error.
- the base station may retransmit the TB.
- a NACK-only feedback operation may be used.
- HARQ-ACK feedback for the multicast PDSCH may be activated or deactivated.
- activation of HARQ-ACK feedback may mean enabling of HARQ-ACK feedback
- deactivation of HARQ-ACK feedback may mean disabling HARQ-ACK feedback.
- DCI scheduling multicast PDSCH may include information indicating activation or deactivation of HARQ-ACK feedback.
- Method 3.2-2 Allowing deactivation of HARQ-ACK feedback may be indicated by RRC signaling, and DCI scheduling multicast PDSCH may indicate activation or deactivation of HARQ-ACK feedback.
- RRC signaling for configuring multicast transmission may indicate activation or deactivation of HARQ-ACK feedback.
- the UE may always feed back HARQ-ACK for multicast PDSCH.
- the UE may ignore the deactivation indication of the HARQ-ACK feedback, and HARQ-ACK may be transmitted to the base station. That is, an indication by RRC signaling may take precedence over an indication by DCI.
- the UE may or may not transmit the HARQ-ACK according to a specific field or combination of fields of DCI for allocating the multicast PDSCH.
- the UE when HARQ-ACK feedback for multicast PDSCH is activated by RRC signaling, the UE may or may not feed back HARQ-ACK according to DCI that allocates multicast PDSCH.
- This case may be "a case in which a specific field or a combination of fields included in DCI for allocating multicast PDSCH indicates deactivation of HARQ-ACK feedback". That is, HARQ-ACK feedback may be performed by combining RRC signaling and DCI indication. If the deactivation of HARQ-ACK feedback for the multicast PDSCH is permitted by RRC signaling, the UE may or may not transmit the HARQ-ACK according to a specific field or combination of fields of DCI for allocating the multicast PDSCH.
- Method 3.2-4 when activation of HARQ-ACK feedback is indicated by RRC signaling, even when DCI for allocating multicast PDSCH includes information indicating activation or deactivation of HARQ-ACK feedback , the UE may transmit the HARQ-ACK to the base station according to the DCI indication (ie, the indication for activation or deactivation of the HARQ-ACK feedback).
- the DCI indication ie, the indication for activation or deactivation of the HARQ-ACK feedback.
- DCI for allocating multicast PDSCH may include a specific field, and a specific field set to a first value (eg, 0) may indicate activation of HARQ-ACK feedback, and the second A specific field set to a value (eg, 1) may indicate deactivation of HARQ-ACK feedback.
- a specific field set to a first value eg, 0
- the second A specific field set to a value eg, 1
- a combination of fields included in DCI for allocating the multicast PDSCH may indicate activation or deactivation of HARQ-ACK feedback.
- a specific value of a combination of "a first field indicating HARQ-ACK feedback timing" and a "second field indicating a PUCCH resource index" included in DCI indicates activation or deactivation of HARQ-ACK feedback.
- the specific value of the above-mentioned combination may be predefined in the technical standard.
- the base station may inform the terminal of a specific value of the above-described combination.
- the HARQ codebook may be generated as follows. "When the base station instructs the terminal to generate a T1 (Type1) HARQ codebook and HARQ-ACK feedback is deactivated", the terminal may generate a T1 HARQ codebook including a NACK for the multicast PDSCH. Generation of the T1 HARQ codebook may be indicated by RRC signaling, and deactivation of HARQ-ACK feedback may be indicated by DCI. "When the base station instructs the terminal to generate a T2 (Type2) HARQ codebook and HARQ-ACK feedback is deactivated", the T2 HARQ codebook generated by the terminal may not include HARQ-ACK for multicast PDSCH have.
- T2 HARQ codebook may be indicated by RRC signaling, and deactivation of HARQ-ACK feedback may be indicated by DCI.
- a value of a downlink assignment index (DAI) included in DCI for allocating the multicast PDSCH may satisfy a specific condition. For example, C(counter)-DAI and T(total)-DAI may be the same as the previous values.
- the UE receives information about the multicast PDSCH.
- a HARQ-ACK bit may be generated.
- the UE may generate the HARQ-ACK bit for the multicast PDSCH.
- Another HARQ-ACK bit may be a HARQ-ACK bit for a unicast PDSCH or a HARQ-ACK bit for another multicast PDSCH.
- the UE can generate multiplexed HARQ-ACK bits (eg, HARQ subcodebook or HARQ codebook) by multiplexing the HARQ-ACK bit for the multicast PDSCH and other HARQ-ACK bits, and the multiplexed HARQ-ACK Bits may be transmitted through an uplink channel (eg, PUCCH or PUSCH). That is, the HARQ-ACK bit different from the HARQ-ACK bit for the multicast PDSCH may be transmitted through the same PUCCH.
- an uplink channel eg, PUCCH or PUSCH
- the UE may transmit the PUCCH including the HARQ-ACK for the multicast PDSCH to the base station.
- the terminal may transmit only NACK, not ACK, to the base station according to the configuration of the base station. Specifically, only when the decoding result of the multicast PDSCH is NACK, the terminal may transmit the NACK to the base station through the PUCCH. "If the decoding result of the multicast PDSCH is ACK" or "When DCI for allocating the multicast PDSCH is not received (eg, when DTX occurs)", the terminal responds (eg, ACK or DTX ) may not be transmitted to the base station. Therefore, the base station may not receive the PUCCH from the terminal.
- the UE may generate a HARQ codebook including HARQ-ACK bits, and may transmit the HARQ codebook to the base station.
- different methods may be applied according to the type of the HARQ codebook.
- the method of generating the T1 HARQ codebook according to the PTM method 1 may be different from the method of generating the T1 HARQ codebook according to the PTM method 2.
- existing methods may be reused.
- terminals belonging to a group may receive a common DCI, and since the amount of HARQ-ACK is small, there may be fewer issues with the HARQ codebook.
- PTM method 2 to which the T2 HARQ codebook is applied, the UE receives DCI scrambled by C-RNTI, and thus the T2 HARQ codebook may be appropriately generated.
- the UE may decode the multicast PDSCH (eg, TB), and the decoding result (eg, HARQ-ACK feedback) for the multicast PDSCH may be transmitted according to Table 1 below. According to Table 1, one HARQ-ACK bit may be transmitted.
- the HARQ codebook may include one or more HARQ subcodebooks.
- the UE may regard the preset value as the value of the corresponding HARQ-ACK bit.
- the NACK-only feedback operation may be extended. In this case, NACK and non-NACK (eg, ACK and DTX) may be distinguished. Alternatively, the NACK-only feedback operation may not be applied. That is, the HARQ-ACK feedback may be used as it is. In this case, ACK and non-ACK (eg, NACK and DTX) may be distinguished.
- each bit in the HARQ subcodebook may indicate ACK (eg, non-NACK) or NACK.
- ACK eg, non-NACK
- NACK a bit set to 1 in the HARQ subcodebook
- a bit set to 0 in the HARQ subcodebook may indicate NACK
- a bit set to 1 in the HARQ subcodebook may indicate ACK.
- Method 3.2-6 When the decoding result of the TB is NACK, the corresponding decoding result may be expressed as NACK in the HARQ subcodebook. When the decoding result of the TB is not NACK, the corresponding decoding result may be expressed as ACK in the HARQ subcodebook.
- Method 3.2-7 When the decoding result of the TB is NACK, the corresponding decoding result may be expressed as ACK in the HARQ subcodebook. When the decoding result of the TB is not NACK, the corresponding decoding result may be expressed as NACK in the HARQ subcodebook.
- the base station may determine that NACK has occurred in the PDSCH candidate corresponding to the bit indicating NACK in the HARQ subcodebook. Accordingly, the base station may retransmit the TB corresponding to the NACK.
- the UE may express DTX as ACK in the HARQ subcodebook.
- the base station may not be able to distinguish the occurrence of ACK or DTX for the TB corresponding to the bit indicating the ACK in the HARQ subcodebook.
- the base station instructs the terminal to perform the NACK-only feedback operation, it can only check whether NACK has occurred.
- Table 2 The above-described HARQ-ACK feedback operation may be shown in Table 2 below.
- the base station may determine that NACK has occurred in the PDSCH candidate corresponding to the bit indicating ACK in the HARQ subcodebook. Accordingly, the base station may retransmit the TB corresponding to the bit indicating the ACK in the HARQ subcodebook.
- the base station may only check whether NACK has occurred.
- the base station may only check whether NACK has occurred.
- the corresponding DTX may be expressed as NACK in the HARQ subcodebook. This operation may be the same as the operation of expressing an unassigned PDSCH candidate with NACK.
- the above-described HARQ-ACK feedback operation may be shown in Table 3 below.
- each bit in the HARQ subcodebook may indicate ACK or NACK (eg, non-ACK).
- NACK or DTX may be expressed as NACK in the HARQ subcodebook.
- Method 3.2-8 When the decoding result of the TB is ACK, the corresponding decoding result may be expressed as ACK in the HARQ subcodebook. When the decoding result of the TB is not ACK, the corresponding decoding result may be expressed as NACK in the HARQ subcodebook. Method 3.2-8 can be performed as shown in Table 4 below.
- the UE may decode the multicast PDSCH and may not perform HARQ-ACK feedback according to Table 5 below.
- DCI for allocating multicast PDSCH may deactivate or activate HARQ-ACK feedback.
- the UE may generate a HARQ codebook including HARQ-ACK.
- the UE may generate a T1 HARQ codebook including HARQ-ACK (or known bit) for a PDSCH candidate.
- the UE may regard the preset value as the value of the corresponding HARQ-ACK bit.
- a bit set to 0 in the HARQ subcodebook may indicate ACK, and a bit set to 1 in the HARQ subcodebook may indicate NACK.
- a bit set to 0 in the HARQ subcodebook may indicate NACK, and a bit set to 1 in the HARQ subcodebook may indicate ACK.
- the base station may not receive (eg, decode) the HARQ-ACK. Therefore, the HARQ-ACK bit for the PDSCH candidate in the HARQ subcodebook may be set to an arbitrary value.
- each bit in the HARQ subcodebook may be fixed to an arbitrary value, a value indicating ACK, or a value indicating NACK. Methods 3.2-9 can be performed as shown in Table 6.
- the terminal may transmit one bit of information to the base station. Even when HARQ-ACK feedback is deactivated, the UE may feed back HARQ-ACK using additional information (eg, 1-bit information). Alternatively, the terminal may inform the base station whether or not DTX has occurred by using additional information.
- additional information eg, 1-bit information
- Method 3.2-10 When the decoding result of the TB is ACK, the corresponding decoding result may be expressed as ACK in the HARQ subcodebook. When the decoding result of the TB is not ACK, the corresponding decoding result may be expressed as NACK in the HARQ subcodebook. Method 3.2-10 can be performed as shown in Table 7 below.
- the terminal may inform the base station whether the TB decoding result is ACK.
- the base station may determine whether to retransmit the TB according to the decoding result (ie, ACK or NACK) of the TB.
- Method 3.2-11 When the decoding result of the TB is DTX, the corresponding decoding result may be expressed as NACK in the HARQ subcodebook. When the decoding result of the TB is not DTX, the corresponding decoding result may be expressed as ACK in the HARQ subcodebook. Method 3.2-11 can be performed as shown in Table 8 below.
- the UE may inform the eNB of whether DTX has occurred by transmitting an ACK to the eNB regardless of the decoding result (ie, ACK or NACK) of the corresponding TB.
- the base station may determine whether to retransmit DCI for the TB according to the decoding result (ie, ACK or NACK) of the TB.
- the UE may additionally perform a DRX operation for multicast data (eg, multicast PDSCH) as well as a discontinuous reception (DRX) operation for unicast data (eg, unicast PDSCH).
- a DRX operation for multicast data eg, multicast PDSCH
- a discontinuous reception (DRX) operation for unicast data eg, unicast PDSCH.
- terminals belonging to a group may operate based on information element(s) included in DCI scrambled by M-RNTI. Therefore, all terminals belonging to the group cannot transmit according to the active time.
- PTM method 2 UE(s) may operate based on information element(s) included in DCI scrambled by C-RNTI. Therefore, the corresponding terminal(s) does not need to perform a separate DRX operation.
- the UE may perform two DRX operations.
- One M-RNTI may be configured.
- a plurality of M-RNTIs may be configured.
- the number of M-RNTIs may be set equal to the number of multicast groups or multicast identifiers.
- the DRX operation may be independently performed for each M-RNTI.
- the UE may perform different DRX operations (eg, M-DRX operation and U-DRX operation).
- a timer necessary to perform the DRX operation may be separately set for the UE through RRC signaling.
- DRX for multicast may be expressed as M-DRX
- DRX for unicast may be expressed as U-DRX.
- the corresponding DRX may be expressed as C-DRX.
- the UE may receive the multicast PDSCH at the activation time according to the DRX.
- the base station may allocate the multicast PDSCH to the terminals belonging to the group using DCI scrambled by M-RNTI.
- the base station may allocate a PDSCH (eg, multicast PDSCH) to some terminals using DCI scrambled by C-RNTI.
- the terminal performing the DRX operation may start a timer (eg, a HARQ round trip time (RTT) timer).
- the terminal may assume that the base station can perform retransmission when the HARQ RTT timer expires.
- DRX operation may be limited to long DRX.
- the terminal may start a timer (eg, or a retransmission timer). The UE may assume that the retransmitted data will be received before the corresponding timer expires.
- the above-described operation may be unnecessary.
- the HARQ RTT timer and/or retransmission timer may not be started in the M-DRX operation or the C-DRX operation.
- the HARQ RTT timer and/or retransmission timer may not be set.
- the C-DRX operation is configured for the UE, the HARQ RTT timer and/or the retransmission timer may be configured when DCI scrambled with M-RNTI is received. However, the UE may not start the HARQ RTT timer and/or the retransmission timer.
- the HARQ RTT timer and/or retransmission timer may or may not be initiated.
- the UE may start HARQ RTT timer and/or retransmission timer to perform HARQ-ACK feedback operation.
- the UE may not start the above-described HARQ RTT timer and/or retransmission timer. That is, the HARQ RTT timer and/or the retransmission timer may not be used in the terminal.
- Method 3.2-12 Deactivation of HARQ-ACK feedback may be indicated to the UE.
- the HARQ RTT timer and/or the retransmission timer may not be set in the terminal.
- the UE may not start the HARQ RTT timer and/or the retransmission timer.
- the above-described HARQ RTT timer and/or retransmission timer is started, but when HARQ feedback is deactivated, the above-described HARQ RTT timer and/or retransmission timer may not be applied.
- the UE may generate a HARQ codebook including HARQ-ACK bit(s) for the multicast PDSCH, and may transmit the HARQ codebook in PUCCH or PUSCH.
- the UE may generate a T1 HARQ codebook or a T2 HARQ codebook for the unicast PDSCH.
- the base station may inform the terminal of type information (eg, T1 or T2) of the HARQ codebook for the multicast PDSCH using RRC signaling.
- type information eg, T1 or T2
- the type of the HARQ codebook for unicast PDSCH (hereinafter referred to as "unicast HARQ codebook") and the type of the HARQ codebook for multicast PDSCH (hereinafter referred to as "multicast HARQ codebook”) may be indicated in the same way. .
- the type of the unicast HARQ codebook and the type of the multicast HARQ codebook may be indicated by one RRC signaling.
- the type of the unicast HARQ codebook and the type of the multicast HARQ codebook may be indicated differently. In this case, separate RRC signaling may be used to indicate the type of the multicast
- Method 3.3-1 The type of multicast HARQ codebook may be indicated to the UE by RRC signaling.
- the UE may generate a T1 HARQ codebook or a T2 HARQ codebook for the multicast PDSCH according to the instruction of the base station.
- the UE may determine the amount of HARQ-ACK according to the number of K1 values that the multicast PDSCH may have.
- the UE may estimate the amount of HARQ-ACK based on the value of DAI indicated by DCI to which the multicast PDSCH is allocated.
- the UE may generate different HARQ codebooks for each of the multicast PDSCHs. have.
- the base station may independently set each type of multicast HARQ codebooks to the terminal.
- the base station may set a common type for all multicast HARQ codebooks in the terminal.
- the terminal may generate a T1 HARQ codebook and/or a T2 HARQ codebook according to the configuration of the base station.
- the base station may configure multicast to the terminal in a multicast control channel (MCCH), and may configure a plurality of multicast traffic channels (MTCH) to the terminal. Even when the MTCH is divided into a plurality, the type of the HARQ codebook may be interpreted as one.
- the UE may apply the same type of HARQ codebook to different multicast transmissions.
- the HARQ codebook for the multicast PDSCH may not be separately configured. This operation may mean "the type of unicast HARQ codebook is reused when three or more HARQ-ACK bits are generated".
- DCI scrambled with C-RNTI in PTM method 2 may allocate a multicast PDSCH, and the DCI may independently indicate PUCCH resources for each UE. If the following method 3.3-2 is applied, the UE may multiplex HARQ-ACK bit(s) for the unicast PDSCH as well as the HARQ-ACK bit(s) for the multicast PDSCH.
- the type of the multicast HARQ codebook (eg, subcodebook) may be the same as the type of the unicast HARQ codebook (eg, subcodebook).
- the UE may estimate the type of the unicast HARQ codebook as the type of the multicast HARQ codebook.
- a unicast HARQ codebook or a PUCCH resource set for transmission of three or more HARQ-ACK bits may not be configured in the UE.
- the terminal cannot apply method 3.3-2.
- the UE may not be able to use the multicast HARQ codebook, and only the HARQ-ACK for the multicast PDSCH having the highest priority may be fed back to the base station.
- the above-described operation may be applied to the PTM method 1 and/or the PTM method 2.
- the base station may not set the PUCCH resource set of three or more HARQ-ACK bits to the terminal.
- the terminal may feed back only the HARQ-ACK for the multicast PDSCH having the highest priority to the base station.
- the UE may support both unicast transmission and multicast transmission.
- DCI for allocating multicast PDSCH and DCI for allocating unicast PDSCH may be configured differently.
- DCI scrambled with M-RNTI in PTM method 1 cannot indicate different information for each terminal belonging to a group.
- FIG. 8 is a conceptual diagram illustrating a first embodiment of the time sequence of PDCCH and PUCCH in unicast/multicast transmission.
- the first DCI scrambled with C-RNTI (eg, unicast PDCCH) may be received first by the UE, and the second DCI scrambled with M-RNTI (eg, after the reception of the first DCI)
- multicast DCI may be received by the terminal.
- “unicast HARQ codebook and PUCCH resources for unicast PDSCH allocated by the first DCI” and/or "multicast HARQ codebook and PUCCH resources for multicast PDSCH allocated by second DCI” are appropriate It can be difficult to direct.
- the UE may transmit the HARQ-ACK for the PDSCH having a high priority on the PUCCH based on the priority comparison result.
- a priority may be assigned to each multicast PDSCH, and the priority of multicast transmission may be higher than that of unicast transmission.
- the UE may transmit HARQ-ACK bit(s) for some or all of the multicast PDSCH(s) in the PUCCH.
- the UE may directly compare the priority of multicast transmission (eg, multicast PDSCH) with the priority of unicast transmission. Alternatively, when the priority of multicast transmission exceeds a preset boundary, the terminal may determine that the priority of multicast transmission is higher than that of unicast. The UE may generate HARQ-ACK bit(s) for multicast PDSCH(s) having a higher priority than unicast transmission, and may report the HARQ-ACK bit(s) to the base station. Alternatively, if the priority of multicast transmission is higher than that of unicast, the UE may generate a HARQ-ACK bit for the multicast PDSCH having the highest priority, and transmit the HARQ-ACK bit to the base station. can report
- the second DCI scrambled with the M-RNTI may be first received by the terminal, and the first DCI scrambled with the C-RNTI may be performed by the terminal after the reception of the second DCI.
- an appropriate PUCCH resource may be indicated for each UE.
- the UE can compare the priorities between unicast transmission and multicast transmission, and can multiplex the decoding result (eg, HARQ-ACK bit) of some or all of the PDSCHs for transmission with high priority. have.
- the terminal may regard the priority of the multicast transmission as the same as the priority of unicast transmission for transmitting URLLC traffic.
- the UE may regard the priority of the multicast transmission as the same as the priority of unicast transmission delivering eMBB traffic.
- the terminal When the base station instructs the terminal to multiplex URLLC traffic and eMBB traffic, the terminal receives a HARQ codebook including HARQ-ACK bit(s) for all multicast transmission(s) and/or all unicast transmission(s) can create
- the terminal includes HARQ-ACK bit(s) for multicast transmission(s) and/or unicast transmission(s) having the same priority as URLLC traffic HARQ codebook can be generated. In this case, the terminal may not be able to transmit the HARQ-ACK bit(s) for some of the multicast transmission(s) and/or unicast transmission(s) to the base station.
- the base station may indicate the PUCCH resource to the terminal(s) so that all terminals belonging to the group feed back the same n HARQ-ACK bits.
- n may be a natural number.
- the base station may assume that all terminals belonging to the group receive only the multicast PDSCH, and may allocate multicast PDSCH and PUCCH resources to all terminals.
- control information may be independently indicated for each UE. In this case, it may be assumed that the terminal receives not only the multicast PDSCH but also the unicast PDSCH.
- the UE may receive (eg, decode) a part of the multicast PDSCH and/or unicast PDSCH according to processing capability. In this case, the UE may generate a NACK for the undecoded multicast PDSCH and/or unicast PDSCH.
- the base station cannot indicate to the terminal a PUCCH or PUSCH suitable for transmitting the HARQ subcodebook for a plurality of multicast PDSCHs. Since DCI scrambled with C-RNTI is transmitted in PTM method 2, the base station may indicate to the terminal a PUCCH or PUSCH suitable for transmitting the HARQ codebook.
- the UE may assume that frequency division multiplexing (FDM) scheduling for the multicast PDSCH and the unicast PDSCH is allowed according to RRC signaling. Without the above configuration, the UE may assume that time division multiplexing (TDM) scheduling for the multicast PDSCH and the unicast PDSCH is performed.
- FDM frequency division multiplexing
- TDM time division multiplexing
- a method of generating a HARQ codebook when FDM scheduling is allowed may be distinguished from a method of generating a HARQ codebook when TDM scheduling is used.
- the UE may independently generate the HARQ subcodebook for the multicast PDSCH and the HARQ subcodebook for the unicast PDSCH.
- the UE may generate one HARQ codebook without distinction between the multicast HARQ subcodebook and the unicast HARQ subcodebook.
- Method 4.1-1 The terminal may generate a HARQ subcodebook for each multicast group, and may generate one multicast HARQ subcodebook by concatenating the HARQ subcodebooks, and convert the multicast HARQ subcodebook into a unicast HARQ subcodebook By concatenating with , one HARQ codebook can be generated.
- a UE may receive one or more multicast PDSCHs and a unicast PDSCH.
- the UE may generate an HARQ subcodebook for each of the multicast PDSCH(s) and the unicast PDSCH.
- All HARQ subcodebooks generated by the terminal may have the same type. For example, when a T1 HARQ codebook is configured, the HARQ subcodebooks may be T1 HARQ subcodebooks. When the T2 HARQ codebook is configured, the HARQ subcodebooks may be T2 HARQ subcodebooks.
- FIG. 9 is a block diagram illustrating a first embodiment of a method for generating an HARQ codebook based on method 4.1-1.
- the terminal may receive two multicast PDSCHs and one unicast PDSCH, and may generate three HARQ subcodebooks for three PDSCHs, and by concatenating the three subcodebooks One HARQ codebook can be generated.
- the UE may transmit one HARQ codebook in PUCCH or PUSCH.
- the multicast HARQ subcodebook may be configured for each multicast group, multicast identifier, or multicast PDSCH.
- the size of the HARQ subcodebook may not be dynamically changed. Accordingly, the UE can know the size of the HARQ subcodebook for each of the multicast PDSCHs.
- a separate DAI may be defined for each multicast group or multicast identifier, and each DCI(s) for allocating the multicast PDSCH(s) may include a separate DAI. That is, a separate DAI may be indicated to the UE. A separate DAI may be defined for unicast transmission.
- the size of the HARQ codebook generated by the UE may be the sum of the sizes of the HARQ subcodebooks.
- the size of the HARQ codebook may be indicated by a separate DAI (eg, T-DAI) included in the DCI for allocating the unicast PDSCH.
- DCI for allocating unicast transmission may be received at the same time as DCI for allocating multicast transmission. Alternatively, DCI for allocating unicast transmission may be received after DCI for allocating multicast transmission.
- Method 4.1-2 When the DCI for allocating the unicast PDSCH includes the T-DAI in the T2 HARQ codebook generation procedure, the UE generates a T2 HARQ codebook for both the dynamically allocated multicast PDSCH and unicast PDSCH. can
- the UE may concatenate HARQ subcodebooks according to a preset order.
- the plurality of multicast PDSCHs may be identified by a multicast identifier (eg, a multicast ID or a multicast group ID).
- the base station may indicate the multicast ID or the multicast group ID to the terminal.
- the multicast ID or the multicast group ID may be determined based on the M-RNTI.
- the UE may determine the multicast ID or the multicast group ID according to the M-RNTI order (eg, the DCI reception order associated with the M-RNTI).
- Method 4.1-3 When method 4.1-1 is applied, the UE may generate one multicast HARQ subcodebook by concatenating the HARQ subcodebooks according to the order of the multicast ID or multicast group ID. The UE may generate one HARQ codebook by concatenating the multicast HARQ subcodebook and the unicast HARQ subcodebook.
- the UE may generate one HARQ subcodebook for multicast transmission.
- the UE may receive (eg, decode) some of the multicast PDSCHs based on the priority among the multicast PDSCHs allocated by the base station. Accordingly, the UE may generate a HARQ subcodebook of a small size instead of the HARQ subcodebook of each multicast PDSCH.
- the UE may generate one HARQ subcodebook regardless of the multicast group, and may concatenate one HARQ subcodebook (ie, multicast HARQ subcodebook) with the unicast HARQ subcodebook.
- one HARQ subcodebook ie, multicast HARQ subcodebook
- a PDSCH candidate from which a multicast PDSCH may be received may be determined based on the configuration of time and frequency resources. The reason is that the HARQ-ACK feedback timing and/or TDD slot pattern are fixed by RRC signaling.
- the UE may decode two or more overlapping PDSCHs in the time domain according to processing capability.
- the UE may generate a NACK for the undecoded PDSCH according to the processing capability.
- the UE may arrange the multicast PDSCHs in a preset order regardless of the multicast ID.
- the priority of the multicast PDSCH may not be considered.
- Multicast PDSCH candidates may be arranged in chronological order in the same serving cell. If two or more PDSCH candidates overlap in the time domain, the start and length indicator value (SLIV) of each of the two or more PDSCH candidates may be compared.
- HARQ- for the first PDSCH candidate in the HARQ codebook may be disposed before the HARQ-ACK bit(s) for the second PDSCH candidate.
- HARQ-ACK bits for all PDSCH candidates may be valid.
- HARQ-ACK bit(s) for some PDSCH candidates may be expressed as NACK.
- Two or more PDSCH candidates may be allocated regardless of the processing capability of the UE.
- the HARQ subcodebook may include one HARQ-ACK bit, and the base station may transmit one PDSCH candidate (ie, PDSCH) among two or more PDSCH candidates having the same (r, k, n D ).
- the above-described scheduling operation can be effectively utilized in unicast transmission.
- the UE may receive two or more PDSCH candidates according to processing capability.
- Method 4.1-5 The order j of two or more PDSCH candidates having the same (r, k, n D ) may be expressed differently.
- the order j of two or more PDSCH candidates having the same may increase for each PDSCH candidate.
- This operation may mean "increasing the size of the HARQ subcodebook for the multicast PDSCH by the number of PDSCH candidates".
- the executable code defined in Table 9 below may be considered.
- the order of PDSCH candidates may be determined based on the executable code defined in Table 9.
- the order j of PDSCH candidates does not need to exceed J.
- h may be introduced. h can be used to terminate the while loop if j exceeds J.
- the order of PDSCH candidates may be determined based on the execution code defined in Table 10 below.
- the order of PDSCH candidates may be determined based on the executable code defined in Table 10.
- the amount of HARQ-ACK may be different for each terminal belonging to a group.
- DCI scrambled with M-RNTI may not support scheduling for transmission of HARQ-ACK having different amounts.
- DCI scrambled with C-RNTI or DCI for unicast transmission may include information for multicast transmission.
- the size of the HARQ codebook generated by the UE may include the sum of the sizes of the HARQ subcodebooks.
- the size of the HARQ codebook may be indicated by a DAI (eg, T-DAI) included in DCI for allocating unicast transmission.
- DAI eg, T-DAI
- DCI allocating unicast transmission may be received simultaneously with DCI allocating multicast transmission.
- DCI for allocating unicast transmission may be received after DCI for allocating multicast transmission.
- FIG. 10 is a block diagram illustrating a second embodiment of a method for generating an HARQ codebook based on method 4.1-1.
- a UE may receive a plurality of multicast PDSCHs and may receive a unicast PDSCH.
- the UE may generate one multicast HARQ subcodebook for a plurality of multicast PDSCHs (eg, all received multicast PDSCHs), and may generate a unicast HARQ subcodebook for unicast PDSCH have.
- One multicast HARQ subcodebook may be generated for a multicast group.
- the UE may generate the HARQ codebook by concatenating the multicast HARQ subcodebook and the unicast HARQ subcodebook, and may transmit the HARQ codebook in PUCCH or PUSCH.
- the UE may generate the HARQ codebook without distinction between the multicast PDSCH and the unicast PDSCH.
- the UE may generate HARQ subcodebook(s) for PDSCH(s) regardless of multicast transmission and unicast transmission, and may generate one HARQ codebook by concatenating the HARQ subcodebooks. .
- method 4.1-6 may be the same as method 4.1-4 except that unicast transmission is additionally considered in method 4.1-4.
- Executable code(s) defined in Table 9 and/or Table 10 may be changed for application of Method 4.1-6, and the modified executable code(s) may be easily applied to Method 4.1-6.
- method 4.1-6 may be the same as method 4.1-4 except that unicast transmission is additionally considered in method 4.1-4.
- 11 is a block diagram illustrating a first embodiment of a method for generating an HARQ codebook based on method 4.1-6.
- the UE may generate the HARQ codebook without distinction between the multicast PDSCH and the unicast PDSCH.
- PTM method 1 since DCI for allocating multicast is scrambled with M-RNTI, all terminals belonging to the group can receive DCI scrambled with M-RNTI.
- PTM method 2 DCI scrambled with C-RNTI may be used. That is, DCI scrambled with C-RNTI may be received from one UE.
- the format of DL-related DCI may be reused as a format indicated by a field included in DCI.
- Some fields included in DCI cannot be commonly applied to all terminals belonging to the group.
- a time resource and a frequency resource of the PDSCH may be commonly used.
- the TDRA index eg, K0, SLIV, mapping type
- FDRA FDRA
- Information on DM-RS may be identically configured for all terminals belonging to the group.
- the remaining information element(s) except for the above-described information element eg, TDRA index, FDRA, and/or information on DM-RS may be independently configured for each terminal. .
- a field indicating the number of repetitions (eg, the number of repetitions of the multicast PDSCH) may be included in DCI.
- the terminal In order to secure the reception performance of the multicast PDSCH, it is preferable that the terminal repeatedly receives the PDSCH. Although the number of repetitions may be unnecessarily large for some UEs in the group, repeated transmission of the PDSCH may be required to the remaining UEs in the group.
- the link having the worst quality among the links between the terminals and the base station belonging to the group may be identified, and the number of repetitions may be set based on the link having the worst quality.
- the base station may indicate to the terminal(s) the number of repetitions of the multicast PDSCH by using RRC signaling.
- the base station may indicate to the terminal(s) the number of repetitions of the multicast PDSCH by using DCI.
- a field indicating the number of repetitions of the multicast PDSCH may be included in DCI.
- the link between the terminal and the base station may undergo fading, and method 4.2-1 or method 4.2-2 may be applied according to the time unit of fading. Alternatively, method 4.2-2 may be applied for flexible scheduling.
- the number of repetitions of the multicast PDSCH may be implicitly derived by the TDRA index included in DCI.
- the base station may inform all terminals belonging to the group of the TDRA table using RRC signaling. In this case, the amount of RRC signaling may increase.
- TDRA default A defined in the technical standard may be used. However, since the TDRA default A includes only information element(s) for receiving one PDSCH, the number of repetitions of the PDSCH may not be included in the TDRA default A.
- DCI for allocating multicast PDSCH may be scrambled with C-RNTI, and multicast PDSCH may be scrambled with M-RNTI.
- a method of distinguishing whether the DCI detected using the C-RNTI is a multicast PDSCH or a unicast PDSCH may be required.
- a 1-bit information element may be used.
- Method 4.2-3 When a specific field included in DCI is set to a first value, this may indicate a PDSCH reception operation using C-RNTI. When a specific field included in DCI is set to the second value, this may indicate a PDSCH reception operation using M-RNTI.
- a specific field of DCI for allocating multicast PDSCH may indicate HARQ process ID (HPID) and/or HARQ process number (HPN).
- HPID HARQ process ID
- HPN HARQ process number
- the same HPN may be indicated to all terminals belonging to the group. That HPN may already be allocated for another TB.
- the HPN may be calculated differently depending on the reception time of the PDSCH. Since terminals belonging to a group have different HPNs, the base station can determine an appropriate HPN for each terminal by calculating all HPNs. Alternatively, an offset may be introduced so that each terminal is interpreted as a different HPN.
- the base station may indicate to the terminal the offset (o) to be applied to derive the HPN using RRC signaling.
- the base station may indicate to the terminal the number of HARQ processes allocated to the multicast PDSCH (eg, the maximum number (m)) by using RRC signaling.
- the number of HARQ processes allocated to the multicast PDSCH eg, the maximum number (m)
- the UE can calculate the result of adding the offset (o) to the HPID (h) indicated in the DCI scrambled with M-RNTI, and the remainder divided by the maximum number of HARQ processes (m) can be considered as HPN have. That is, the received PDSCH may be processed in the HARQ process ID in HPN (h+o)%m.
- One terminal may receive a plurality of multicast PDSCHs. Accordingly, the number of HARQ processes (eg, the maximum number (m)) and/or the offset (o) may be indicated for each multicast PDSCH.
- the number of HARQ processes eg, the maximum number (m)
- the offset (o) may be indicated for each multicast PDSCH.
- the priority of the multicast PDSCH may be configured.
- the priority of the multicast PDSCH may be used for PDSCH reception or PUCCH transmission.
- the UE may select some PDSCHs based on the priority of the multicast PDSCH.
- the UE may transmit some PUCCHs or one PUCCH based on the priority of the multicast PDSCH.
- the UE may multiplex the HARQ-ACK in the PUSCH based on the priority of the multicast PDSCH.
- Method 4.2-6 The priority of the multicast PDSCH may be indicated by a field included in the DCI for allocating the multicast PDSCH.
- Two or more priorities for multicast PDSCHs may be configured.
- the base station may inform the terminal of a field representing the number of priorities using RRC signaling.
- the size of the field representing the number of priorities may be 3 bits or more.
- Method 4.2-7 In method 4.2-6, the size of a field expressing the number of priorities may be indicated to the UE by RRC signaling.
- the base station may transmit information indicating activation or deactivation of HARQ-ACK feedback to the terminal.
- Information indicating activation or deactivation of HARQ-ACK feedback may be included in DCI for allocating multicast PDSCH.
- the above-described operation may be applied to both the PTM method 1 and the PTM method 2.
- a specific field of DCI is set to the first value, this may indicate that the UE transmits the PUCCH.
- a specific field of DCI is set to the second value, this may indicate that the UE does not transmit PUCCH.
- the UE may report the HARQ-ACK or HARQ codebook for the corresponding multicast PDSCH to the base station.
- Method 4.2-8 Activation or deactivation of HARQ-ACK feedback for multicast PDSCH may be indicated by a specific field included in DCI for allocating multicast PDSCH.
- the base station may instruct the terminal to generate the T2 HARQ codebook.
- the UE needs to know the number of HARQ-ACKs and/or the size of the HARQ codebook.
- DCI for allocating the multicast PDSCH may include a DAI field. Since DCI scrambled with M-RNTI is used in PTM method 1, the C-DAI field may be used, but the T-DAI field may not be used. Since DCI scrambled with C-RNTI is used in PTM method 2, both the C-DAI field and the T-DAI field may be used.
- the C-DAI field may mean the number of allocated multicast PDSCHs.
- the T-DAI field may mean the sum of the number of allocated multicast PDSCHs and the number of unicast PDSCHs.
- terminals belonging to a group may receive a common DCI. Therefore, DCI for allocating the multicast PDSCH may not include a transmit power control (TPC) PUCCH field.
- the TPC command of PUCCH may be summed as a relay loop control in DCI format 1_x and/or DCI format 2_2.
- the T-DAI field may be managed for each number of multicast IDs.
- DCI may include several T-DAI fields.
- Each T-DAI field may indicate a value of T-DAI for multicast ID.
- terminals belonging to the group may transmit PUCCH, and the base station may receive PUCCH having good quality. Therefore, it is preferable that the UE repeatedly transmits the PUCCH.
- the PUCCH resource set indicated by PUCCH-configcommon may be used in the terminal(s). In this case, the base station may instruct the terminal to repeatedly transmit PUCCH.
- the base station may set the number of repetitions of the PUCCH to the terminal by using RRC signaling.
- the base station may transmit DCI including information indicating the number of repetitions of the PUCCH to the terminal.
- the DCI may be a DCI for allocating the multicast PDSCH.
- the methods according to the present invention may be implemented in the form of program instructions that can be executed by various computer means and recorded in a computer-readable medium.
- the computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination.
- the program instructions recorded on the computer-readable medium may be specially designed and configured for the present invention, or may be known and available to those skilled in the art of computer software.
- Examples of computer-readable media include hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like.
- Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like.
- the hardware device described above may be configured to operate as at least one software module to perform the operations of the present invention, and vice versa.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (20)
- 통신 시스템에서 단말의 동작 방법으로서,HARQ(hybrid automatic repeat request)-ACK(acknowledgement) 피드백의 활성화(enable)를 지시하는 RRC(radio resource control) 메시지를 기지국으로부터 수신하는 단계;상기 HARQ-ACK 피드백의 비활성화(disable)를 지시하는 정보를 포함하는 제1 DCI(downlink control information)를 상기 기지국으로부터 수신하는 단계;상기 제1 DCI에 포함된 제1 스케줄링 정보에 기초하여 제1 멀티캐스트 PDSCH(physical downlink shared channel)를 상기 기지국으로부터 수신하는 단계;상기 제1 DCI가 상기 HARQ-ACK 피드백의 비활성화를 지시하는 경우에도, 상기 제1 멀티캐스트 PDSCH에 대한 제1 HARQ-ACK 비트를 생성하는 단계;상기 제1 HARQ-ACK 비트를 포함하는 HARQ 코드북(codebook)을 생성하는 단계; 및상기 HARQ 코드북을 상향링크 채널을 통해 상기 기지국에 전송하는 단계를 포함하는, 단말의 동작 방법.
- 청구항 1에 있어서,상기 제1 DCI에 포함되는 하나의 필드 또는 둘 이상의 필드들의 조합은 상기 제1 HARQ-ACK 비트의 우선순위를 지시하기 위해 사용되는, 단말의 동작 방법.
- 청구항 1에 있어서,상기 제1 DCI가 상기 HARQ-ACK 피드백의 비활성화를 지시하는 경우에도 T1 HARQ 코드북의 생성이 지시되면, 상기 제1 HARQ-ACK 비트를 포함하는 상기 T1 HARQ 코드북은 생성되는, 단말의 동작 방법.
- 청구항 1에 있어서,상기 제1 DCI에 포함되는 하나의 필드 또는 둘 이상의 필드들의 조합은 상기 HARQ-ACK 피드백의 활성화 또는 비활성화를 지시하기 위해 사용되는, 단말의 동작 방법.
- 청구항 1에 있어서,상기 HARQ-ACK 피드백의 비활성화가 지시되는 경우, 상기 단말에서 HARQ RTT(round trip time) 타이머 또는 재전송 타이머 중에서 적어도 하나는 개시되지 않는, 단말의 동작 방법.
- 청구항 1에 있어서,상기 단말의 동작 방법은,제2 DCI를 상기 기지국으로부터 수신하는 단계; 및상기 제2 DCI에 포함된 제2 스케줄링 정보에 기초하여 상기 기지국으로부터 제2 멀티캐스트 PDSCH를 수신하는 단계를 더 포함하고,상기 HARQ 코드북은 상기 제2 멀티캐스트 PDSCH에 대한 제2 HARQ-ACK 비트를 더 포함하는, 단말의 동작 방법.
- 청구항 6에 있어서,상기 HARQ 코드북은 상기 제1 HARQ-ACK 비트를 포함하는 제1 멀티캐스트 HARQ 서브코드북(subcodebook) 및 상기 제2 HARQ-ACK 비트를 포함하는 제2 멀티캐스트 HARQ 서브코드북을 포함하고, 상기 제1 멀티캐스트 PDSCH와 상기 제2 멀티캐스트 PDSCH는 서로 다른 멀티캐스트 식별자들에 의해 구분되는, 단말의 동작 방법.
- 청구항 1에 있어서,상기 단말의 동작 방법은,제3 DCI를 상기 기지국으로부터 수신하는 단계; 및상기 제3 DCI에 포함된 제3 스케줄링 정보에 기초하여 상기 기지국으로부터 유니캐스트 PDSCH를 수신하는 단계를 더 포함하고,상기 HARQ 코드북은 상기 유니캐스트 PDSCH에 대한 제3 HARQ-ACK 비트를 더 포함하는, 단말의 동작 방법.
- 청구항 8에 있어서,상기 HARQ 코드북을 생성하는 단계는,상기 제1 HARQ-ACK 비트를 포함하는 제1 멀티캐스트 HARQ 서브코드북을 생성하는 단계;상기 제3 HARQ-ACK 비트를 포함하는 유니캐스트 HARQ 서브코드북을 생성하는 단계; 및상기 제1 멀티캐스트 HARQ 서브코드북과 상기 유니캐스트 HARQ 서브코드북을 연접함으로써 상기 HARQ 코드북을 생성하는 단계를 포함하는, 단말의 동작 방법.
- 청구항 9에 있어서,상기 제1 멀티캐스트 HARQ 서브코드북의 타입은 상기 유니캐스트 HARQ 서브코드북의 타입과 독립적으로 설정되고, 상기 제1 HARQ-ACK 비트의 우선순위는 상기 제3 HARQ-ACK 비트의 우선순위와 동일하게 설정되는, 단말의 동작 방법.
- 청구항 9에 있어서,상기 제1 멀티캐스트 PDSCH와 상기 유니캐스트 PDSCH에 대한 FDM(frequency division multiplexing) 스케줄링이 허용되는 경우, 상기 제1 멀티캐스트 HARQ 서브코드북과 상기 유니캐스트 HARQ 서브코드북은 독립적으로 생성되는, 단말의 동작 방법.
- 통신 시스템에서 단말의 동작 방법으로서,HARQ(hybrid automatic repeat request)-ACK(acknowledgement) 피드백의 비활성화(disable)를 지시하는 정보를 포함하는 제1 DCI(downlink control information)를 기지국으로부터 수신하는 단계;상기 제1 DCI에 포함된 제1 스케줄링 정보에 기초하여 제1 멀티캐스트 PDSCH(physical downlink shared channel)를 상기 기지국으로부터 수신하는 단계;상기 제1 DCI가 상기 HARQ-ACK 피드백의 비활성화를 지시하는 경우에도, 상기 제1 멀티캐스트 PDSCH에 대한 제1 HARQ-ACK 비트를 생성하는 단계;상기 제1 HARQ-ACK 비트를 포함하는 HARQ 코드북(codebook)을 생성하는 단계; 및상기 HARQ 코드북을 상향링크 채널을 통해 상기 기지국에 전송하는 단계를 포함하며,상기 HARQ-ACK 피드백이 비활성화되는 경우에도, 상기 단말에서 다른 HARQ-ACK 비트가 발생하고, 상기 제1 HARQ-ACK 비트가 다른 HARQ-ACK 비트와 다중화 가능한 경우, 상기 제1 HARQ-ACK 비트는 생성되는, 단말의 동작 방법.
- 청구항 12에 있어서,상기 HARQ-ACK 피드백의 비활성화가 지시되는 경우, 상기 단말에서 HARQ RTT(round trip time) 타이머 또는 재전송 타이머 중에서 적어도 하나는 사용되지 않는, 단말의 동작 방법.
- 청구항 12에 있어서,상기 단말의 동작 방법은,제2 DCI를 상기 기지국으로부터 수신하는 단계; 및상기 제2 DCI에 포함된 제2 스케줄링 정보에 기초하여 상기 기지국으로부터 제2 멀티캐스트 PDSCH를 수신하는 단계를 더 포함하고,상기 HARQ 코드북은 상기 제2 멀티캐스트 PDSCH에 대한 제2 HARQ-ACK 비트를 더 포함하는, 단말의 동작 방법.
- 청구항 14에 있어서,상기 HARQ 코드북은 상기 제1 HARQ-ACK 비트를 포함하는 제1 멀티캐스트 HARQ 서브코드북(subcodebook) 및 상기 제2 HARQ-ACK 비트를 포함하는 제2 멀티캐스트 HARQ 서브코드북을 포함하고, 상기 제1 멀티캐스트 PDSCH와 상기 제2 멀티캐스트 PDSCH는 서로 다른 멀티캐스트 식별자들에 의해 구분되는, 단말의 동작 방법.
- 청구항 15에 있어서,상기 제1 멀티캐스트 HARQ 서브코드북과 상기 제2 멀티캐스트 HARQ 서브코드북은 상기 서로 다른 멀티캐스트 식별자들의 순서대로 연접되는, 단말의 동작 방법.
- 청구항 12에 있어서,상기 단말의 동작 방법은,NACK-only 피드백 방식이 지원되는 것을 지시하는 RRC(radio resource control) 메시지를 상기 기지국으로부터 수신하는 단계를 더 포함하며,상기 제1 HARQ-ACK 비트는 상기 NACK-only 피드백 방식에 따라 생성되고, 상기 제1 HARQ-ACK 비트가 상기 다른 HARQ-ACK 비트와 다중화 되는 경우에 상기 NACK-only 피드백 방식은 적용되지 않는, 단말의 동작 방법.
- 청구항 13에 있어서,상기 단말의 동작 방법은,제3 DCI를 상기 기지국으로부터 수신하는 단계; 및상기 제3 DCI에 포함된 제3 스케줄링 정보에 기초하여 상기 기지국으로부터 유니캐스트 PDSCH를 수신하는 단계를 더 포함하고,상기 HARQ 코드북은 상기 유니캐스트 PDSCH에 대한 제3 HARQ-ACK 비트를 더 포함하는, 단말의 동작 방법.
- 청구항 18에 있어서,상기 HARQ 코드북을 생성하는 단계는,상기 제1 HARQ-ACK 비트를 포함하는 제1 멀티캐스트 HARQ 서브코드북을 생성하는 단계;상기 제3 HARQ-ACK 비트를 포함하는 유니캐스트 HARQ 서브코드북을 생성하는 단계; 및상기 제1 멀티캐스트 HARQ 서브코드북과 상기 유니캐스트 HARQ 서브코드북을 연접함으로써 상기 HARQ 코드북을 생성하는 단계를 포함하며,상기 제1 멀티캐스트 HARQ 서브코드북은 멀티캐스트 식별자에 의해 구분되는, 단말의 동작 방법.
- 청구항 19에 있어서,상기 제1 멀티캐스트 PDSCH와 상기 유니캐스트 PDSCH에 대한 FDM(frequency division multiplexing) 스케줄링이 허용되는 경우, 상기 제1 멀티캐스트 HARQ 서브코드북과 상기 유니캐스트 HARQ 서브코드북은 독립적으로 생성되는, 단말의 동작 방법.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP21898726.1A EP4255074A1 (en) | 2020-11-27 | 2021-11-29 | Method and device for supporting multicast transmission |
US18/037,484 US20230422275A1 (en) | 2020-11-27 | 2021-11-29 | Method and device for supporting multicast transmission |
CN202180079951.0A CN116530174A (zh) | 2020-11-27 | 2021-11-29 | 支持多播传输的方法及装置 |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR20200163357 | 2020-11-27 | ||
KR10-2020-0163357 | 2020-11-27 | ||
KR10-2021-0150062 | 2021-11-03 | ||
KR20210150062 | 2021-11-03 | ||
KR1020210166606A KR20220074798A (ko) | 2020-11-27 | 2021-11-29 | 멀티캐스트 전송을 지원하기 위한 방법 및 장치 |
KR10-2021-0166606 | 2021-11-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022114901A1 true WO2022114901A1 (ko) | 2022-06-02 |
Family
ID=81756231
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2021/017787 WO2022114901A1 (ko) | 2020-11-27 | 2021-11-29 | 멀티캐스트 전송을 지원하기 위한 방법 및 장치 |
Country Status (2)
Country | Link |
---|---|
US (1) | US20230422275A1 (ko) |
WO (1) | WO2022114901A1 (ko) |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020144261A1 (en) * | 2019-01-10 | 2020-07-16 | Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. | Advanced feedback in sidelink |
-
2021
- 2021-11-29 WO PCT/KR2021/017787 patent/WO2022114901A1/ko active Application Filing
- 2021-11-29 US US18/037,484 patent/US20230422275A1/en active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020144261A1 (en) * | 2019-01-10 | 2020-07-16 | Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. | Advanced feedback in sidelink |
Non-Patent Citations (5)
Title |
---|
ASIA PACIFIC TELECOM: "Enhancements on HARQ in NTN", 3GPP DRAFT; R1-2009059, vol. RAN WG1, 24 October 2020 (2020-10-24), pages 1 - 5, XP051946806 * |
MODERATOR (HUAWEI): "FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs", 3GPP DRAFT; R1-2009654, vol. RAN WG1, 10 November 2020 (2020-11-10), pages 1 - 62, XP051952879 * |
NOKIA, NOKIA SHANGHAI BELL: "HARQ scheduling and feedback for NR-U", 3GPP DRAFT; R1-1904183_HARQ, vol. RAN WG1, 29 March 2019 (2019-03-29), Xian, China, pages 1 - 12, XP051691327 * |
SAMSUNG: "Uu transport and multicasting enhancement for V2X", 3GPP DRAFT; R1-156817-UU-TRANSPORT-AND-MULTICASTING-ENHANCEMENT-FOR-V2X, vol. RAN WG1, 15 November 2015 (2015-11-15), pages 1 - 5, XP051039937, ISBN: Anaheim, USA * |
ZTE CORPORATION, SANECHIPS: "Consideration on SR and DRX in NTN", 3GPP DRAFT; R2-1915422, vol. RAN WG2, 8 November 2019 (2019-11-08), Reno, USA, pages 1 - 9, XP051817218 * |
Also Published As
Publication number | Publication date |
---|---|
US20230422275A1 (en) | 2023-12-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020222575A1 (en) | Method and apparatus for transmission and reception of sidelink feedback in wireless communication system | |
WO2019216599A1 (ko) | 고신뢰 및 저지연 통신을 위한 신호의 송수신 방법 | |
WO2018199685A1 (ko) | 통신 시스템에서 하향링크 채널 및 참조 신호의 송수신 방법 | |
WO2020145613A1 (en) | Method and apparatus for transmitting/receiving control information in wireless communication system | |
WO2020022650A1 (ko) | 무선 통신 시스템에서 자원을 할당하는 방법, 장치 및 시스템 | |
WO2017052193A1 (ko) | 비면허 대역에서 데이터를 송수신하는 방법 및 이를 위한 장치 | |
WO2016122197A1 (ko) | 상향링크 신호를 전송하기 위한 방법 및 이를 위한 장치 | |
WO2016167606A1 (ko) | 무선 통신 시스템에서 단말이 피드백을 수행하는 방법 및 이를 위한 장치 | |
WO2016126063A1 (ko) | 무선 통신 시스템에서 채널 상태 보고 방법 및 이를 위한 장치 | |
WO2012128505A2 (ko) | 장치-대-장치 통신 방법 및 장치 | |
WO2012077971A2 (ko) | 무선 통신 시스템에서 단말 간의 통신 방법 및 장치 | |
WO2016021983A1 (ko) | 단말간 통신을 지원하는 무선 통신 시스템에서 무선 통신 방법 및 장치 | |
WO2018182262A1 (ko) | 무선 통신 시스템에서 v2x 단말에 의해 수행되는 v2x 통신 수행 방법 및 상기 방법을 이용하는 단말 | |
WO2021162423A1 (ko) | 무선 통신 시스템에서 다중 송수신 포인트로부터의 하향링크 채널 송수신 방법 및 장치 | |
EP3777428A1 (en) | Method and apparatus for data transmission | |
WO2021194108A1 (ko) | 비면허 대역에서 urllc를 위한 방법 및 장치 | |
WO2019199051A1 (ko) | 통신 시스템에서 저지연 통신을 위한 방법 및 장치 | |
WO2019088779A1 (ko) | 무선 통신 시스템에서 단말 간 통신을 위한 피드백을 위한 방법 및 이를 위한 장치 | |
WO2017074155A1 (ko) | 무선 통신 시스템에서의 fdr(full duplex radio) 동작 지원 방법 및 이를 위한 장치 | |
WO2019216619A1 (en) | Method and apparatus for data transmission | |
WO2019050143A1 (ko) | 무선 통신 시스템에서 자원 할당 방법 및 상기 방법을 이용하는 장치 | |
WO2019035701A1 (ko) | 무선 통신 시스템에서 단말의 전력 소모 감소를 위한 하향링크 제어채널 설정 방법 및 장치 | |
WO2021162264A1 (ko) | 무선 통신 시스템에서 상향링크 채널 반복 전송 방법 및 장치 | |
WO2017131465A1 (ko) | 비면허대역 통신 시스템에서 신호를 전송하는 방법 및 장치, 상향링크 스케줄링 방법 및 장치, 그리고 채널 상태 측정 구간에 관한 정보를 전송하는 방법 및 장치 | |
WO2019139330A1 (ko) | 상향링크 제어채널 송수신 방법 및 이를 위한 장치 |
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: 21898726 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18037484 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180079951.0 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021898726 Country of ref document: EP Effective date: 20230627 |