EP4188023B1 - Verfahren und vorrichtung zum senden und empfangen eines drahtlossignals in einem drahtloskommunikationssystem - Google Patents
Verfahren und vorrichtung zum senden und empfangen eines drahtlossignals in einem drahtloskommunikationssystem Download PDFInfo
- Publication number
- EP4188023B1 EP4188023B1 EP23152669.0A EP23152669A EP4188023B1 EP 4188023 B1 EP4188023 B1 EP 4188023B1 EP 23152669 A EP23152669 A EP 23152669A EP 4188023 B1 EP4188023 B1 EP 4188023B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- nfi
- dci
- harq
- pdsch
- ack information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 130
- 238000004891 communication Methods 0.000 title claims description 87
- 230000005540 biological transmission Effects 0.000 claims description 151
- 230000004044 response Effects 0.000 claims description 28
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 claims 7
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 claims 7
- 238000004590 computer program Methods 0.000 claims 1
- 230000008569 process Effects 0.000 description 54
- 230000015654 memory Effects 0.000 description 37
- 238000011176 pooling Methods 0.000 description 22
- 230000006870 function Effects 0.000 description 18
- 230000008054 signal transmission Effects 0.000 description 17
- 238000005516 engineering process Methods 0.000 description 16
- 239000010410 layer Substances 0.000 description 14
- 230000011664 signaling Effects 0.000 description 14
- 238000013468 resource allocation Methods 0.000 description 12
- 238000012545 processing Methods 0.000 description 10
- 238000012544 monitoring process Methods 0.000 description 9
- 101150116295 CAT2 gene Proteins 0.000 description 6
- 101100392078 Caenorhabditis elegans cat-4 gene Proteins 0.000 description 6
- 101100326920 Caenorhabditis elegans ctl-1 gene Proteins 0.000 description 6
- 101100126846 Neurospora crassa (strain ATCC 24698 / 74-OR23-1A / CBS 708.71 / DSM 1257 / FGSC 987) katG gene Proteins 0.000 description 6
- 238000013473 artificial intelligence Methods 0.000 description 5
- 238000013507 mapping Methods 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 101150071746 Pbsn gene Proteins 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 2
- 239000000969 carrier Substances 0.000 description 2
- 125000004122 cyclic group Chemical group 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 241000760358 Enodes Species 0.000 description 1
- 108700026140 MAC combination Proteins 0.000 description 1
- 101100274486 Mus musculus Cited2 gene Proteins 0.000 description 1
- 101150096622 Smr2 gene Proteins 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000033228 biological regulation Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 230000001276 controlling effect Effects 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 238000005286 illumination Methods 0.000 description 1
- 239000002346 layers by function Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000000873 masking effect Effects 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000010363 phase shift Effects 0.000 description 1
- -1 physical (PHY) Substances 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
Images
Classifications
-
- 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
- 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/1607—Details of the supervisory signal
- H04L1/1664—Details of the supervisory signal the supervisory signal being transmitted together with payload signals; piggybacking
-
- 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/1685—Details of the supervisory signal the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
-
- 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/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
-
- 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/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
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
- H04L1/0026—Transmission of channel quality indication
-
- 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
- H04L2001/125—Arrangements for preventing errors in the return channel
Definitions
- the present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting and receiving a wireless signal.
- a wireless access system is a multiple access system that supports communication of multiple users by sharing available system resources (a bandwidth, transmission power, etc.) among them.
- multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency division multiple access (SC-FDMA) system.
- CDMA code division multiple access
- FDMA frequency division multiple access
- TDMA time division multiple access
- OFDMA orthogonal frequency division multiple access
- SC-FDMA single carrier frequency division multiple access
- WO 2017/085122 A1 discloses a method comprising receiving one or more data packets wirelessly in one or more downlink transmission opportunities on one or more radio carriers, receiving scheduling information comprising an indication of uplink control information to be transmitted related to at least one of the one or more data packets, and causing wireless transmission of the uplink control information in an uplink transmission opportunity.
- US 2017/273056 A1 discloses methods and apparatus for scheduling transmissions of data channels, control channels, or random access channels using downlink control information (DCI) formats.
- DCI downlink control information
- a DCI format can configure a transmission of one or multiple data channels over respective one or multiple transmission time intervals.
- a first DCI format can configure the parameters for a channel transmission and a second DCI format can trigger the channel transmission and indicate respective one or more transmission time intervals.
- a wireless signal may be efficiently transmitted and received in a wireless communication system.
- CDMA code division multiple access
- FDMA frequency division multiple access
- TDMA time division multiple access
- OFDMA orthogonal frequency division multiple access
- SC-FDMA single carrier frequency division multiple access
- CDMA may be implemented as a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
- TDMA may be implemented as a radio technology such as global system for mobile communications (GSM)/general packet radio service (GPRS)/enhanced data rates for GSM evolution (EDGE).
- GSM global system for mobile communications
- GPRS general packet radio service
- EDGE enhanced data rates for GSM evolution
- OFDMA may be implemented as a radio technology such as institute of electrical and electronics engineers (IEEE) 802.11 (wireless fidelity (Wi-Fi)), IEEE 802.16 (worldwide interoperability for microwave access (WiMAX)), IEEE 802.20, evolved UTRA (E-UTRA), and so on.
- IEEE institute of electrical and electronics engineers
- Wi-Fi wireless fidelity
- WiMAX worldwide interoperability for microwave access
- E-UTRA evolved UTRA
- UTRA is a part of universal mobile telecommunications system (UMTS).
- 3 rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA
- LTE-advanced (LTE-A) is an evolution of 3GPP LTE.
- 3GPP new radio or new radio access technology (NR) is an evolved version of 3GPP LTE/LTE-A.
- next-generation radio access technology for enhanced mobile broadband communication (eMBB), massive MTC (mMTC), and ultra-reliable and low latency communication (URLLC) is being discussed.
- eMBB enhanced mobile broadband communication
- mMTC massive MTC
- URLLC ultra-reliable and low latency communication
- a user equipment receives information from a base station (BS) on DL and transmits information to the BS on UL.
- the information transmitted and received between the UE and the BS includes general data and various types of control information.
- FIG. 1 illustrates physical channels and a general signal transmission method using the physical channels in a 3GPP system.
- the UE When a UE is powered on or enters a new cell, the UE performs initial cell search (S101).
- the initial cell search involves acquisition of synchronization to a BS.
- the UE receives a synchronization signal block (SSB) from the BS.
- the SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH).
- PSS primary synchronization signal
- SSS secondary synchronization signal
- PBCH physical broadcast channel
- the UE synchronizes its timing to the BS and acquires information such as a cell identifier (ID) based on the PSS/SSS. Further, the UE may acquire information broadcast in the cell by receiving the PBCH from the BS.
- the UE may also monitor a DL channel state by receiving a downlink reference signal (DL RS).
- DL RS downlink reference signal
- the UE may perform a random access procedure with the BS (S103 to S106). Specifically, the UE may transmit a preamble on a physical random access channel (PRACH) (S103) and may receive a PDCCH and a random access response (RAR) for the preamble on a PDSCH corresponding to the PDCCH (S104). The UE may then transmit a physical uplink shared channel (PUSCH) by using scheduling information in the RAR (S105), and perform a contention resolution procedure including reception of a PDCCH and a PDSCH signal corresponding to the PDCCH (S 106).
- PRACH physical random access channel
- RAR random access response
- the UE may receive a PDCCH and/or a PDSCH from the BS (S107) and transmit a physical uplink shared channel (PUSCH) and/or a physical uplink control channel (PUCCH) to the BS (S108), in a general UL/DL signal transmission procedure.
- Control information that the UE transmits to the BS is generically called uplink control information (UCI).
- the UCI includes a hybrid automatic repeat and request acknowledgement/negative acknowledgement (HARQ-ACK/NACK), a scheduling request (SR), channel state information (CSI), and so on.
- the CSI includes a channel quality indicator (CQI), a precoding matrix index (PMI), a rank indication (RI), and so on.
- UCI is transmitted on a PUCCH.
- control information and data may be transmitted on a PUSCH.
- the UE may transmit the UCI aperiodically on the PUSCH, upon receipt of a request/command from a network.
- FIG. 2 illustrates a radio frame structure
- Each radio frame has a length of 10ms and is divided into two 5-ms half-frames. Each half-frame is divided into five 1-ms subframes. A subframe is divided into one or more slots, and the number of slots in a subframe depends on a subcarrier spacing (SCS).
- SCS subcarrier spacing
- Each slot includes 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP). When a normal CP is used, each slot includes 14 OFDM symbols. When an extended CP is used, each slot includes 12 OFDM symbols.
- a symbol may include an OFDM symbol (or a CP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).
- Table 1 exemplarily illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCSs in a normal CP case.
- Table 2 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCSs in an extended CP case.
- the frame structure is merely an example, and the number of subframes, the number of slots, and the number of symbols in a frame may be changed in various manners.
- different OFDM(A) numerologies may be configured for a plurality of cells aggregated for one UE.
- the (absolute time) duration of a time resource e.g., a subframe, a slot, or a transmission time interval (TTI)
- TTI transmission time interval
- a symbol may include an OFDM symbol (or CP-OFDM symbol) and an SC-FDMA symbol (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).
- FIG. 3 illustrates a resource grid during the duration of one slot.
- a slot includes a plurality of symbols in the time domain. For example, one slot includes 14 symbols in a normal CP case and 12 symbols in an extended CP case.
- a carrier includes a plurality of subcarriers in the frequency domain.
- a resource block (RB) may be defined by a plurality of (e.g., 12) consecutive subcarriers in the frequency domain.
- a bandwidth part (BWP) may be defined by a plurality of consecutive (physical) RBs ((P)RBs) in the frequency domain and correspond to one numerology (e.g., SCS, CP length, and so on).
- a carrier may include up to N (e.g., 5) BWPs. Data communication may be conducted in an active BWP, and only one BWP may be activated for one UE.
- Each element in a resource grid may be referred to as a resource element (RE), to which one complex symbol may be mapped.
- FIG. 4 illustrates a structure of a self-contained slot.
- a frame has a self-contained structure in which a DL control channel, DL or UL data, a UL control channel, and the like may all be contained in one slot.
- the first N symbols (hereinafter, DL control region) in the slot may be used to transmit a DL control channel
- the last M symbols (hereinafter, UL control region) in the slot may be used to transmit a UL control channel.
- N and M are integers greater than or equal to 0.
- a resource region hereinafter, a data region
- a data region that is between the DL control region and the UL control region may be used for DL data transmission or UL data transmission.
- Respective sections are listed in a temporal order.
- FIG. 5 illustrates mapping of physical channels in a self-contained slot.
- the PDCCH may be transmitted in the DL control region, and the PDSCH may be transmitted in the DL data region.
- the PUCCH may be transmitted in the UL control region, and the PUSCH may be transmitted in the UL data region.
- the GP provides a time gap in the process of the UE switching from the transmission mode to the reception mode or from the reception mode to the transmission mode. Some symbols at the time of switching from DL to UL within a subframe may be configured as the GP.
- the PDCCH delivers DCI.
- the PDCCH i.e., DCI
- the PDCCH may carry information about a transport format and resource allocation of a DL shared channel (DL-SCH), resource allocation information of an uplink shared channel (UL-SCH), paging information on a paging channel (PCH), system information on the DL-SCH, information on resource allocation of a higher-layer control message such as an RAR transmitted on a PDSCH, a transmit power control command, information about activation/release of configured scheduling, and so on.
- the DCI includes a cyclic redundancy check (CRC).
- the CRC is masked with various identifiers (IDs) (e.g.
- RNTI radio network temporary identifier
- the CRC is masked by a UE ID (e.g., cell-RNTI (C-RNTI)).
- C-RNTI cell-RNTI
- P-RNTI paging-RNTI
- SIB system information block
- SI-RNTI system information RNTI
- RA-RNTI random access-RNTI
- the PDCCH may include 1, 2, 4, 8, or 16 control channel elements (CCEs) depending on the aggregation level (AL).
- the CCE is a logical allocation unit for providing the PDCCH with a predetermined coding rate based on the state of a radio channel.
- the PDCCH is transmitted in a control resource set (CORESET).
- the CORESET is defined as a set of REGs with a given numerology (e.g., SCS, CP length, etc.).
- a plurality of CORESETs for one UE may overlap in the time/frequency domain.
- the CORESET may be configured by system information (e.g., master information block (MIB)) or UE-specific higher layer signaling (e.g., radio resource control (RRC) layer signaling).
- MIB master information block
- RRC radio resource control
- the numbers of RBs and OFDM symbols (up to three OFDM symbols) in the CORESET may be configured by higher layer signaling.
- a PDCCH candidate refers to CCE(s) that the UE should monitor for PDCCH detection.
- Each PDCCH candidate is defined by 1, 2, 4, 8, or 16 CCEs depending on the AL.
- monitoring includes (blind) decoding of PDCCH candidates.
- a set of PDCCH candidates monitored by the UE are defined as a PDCCH search space (SS).
- the SS may include a common search space (CSS) or a UE-specific search space (USS).
- the UE may obtain DCI by monitoring PDCCH candidates in one or more SSs, which are configured by an MIB or higher layer signaling.
- Each CORESET is associated with one or more SSs, and each SS is associated with one CORESET.
- the SS may be defined based on the following parameters.
- Table 3 shows the characteristics of each SS.
- Type Search Space RNTI Use Case Type0-PDCC H Common SI-RNTI on a primary cell SIB Decoding Type0A-PDC CH Common SI-RNTI on a primary cell SIB Decoding Type 1-PDCC H Common RA-RNTI or TC-RNTI on a primary cell Msg2, Msg4 decoding in RACH Type2-PDCC H Common P-RNTI on a primary cell Paging Decoding Type3-PDCC H Common INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI(s) UE Specific C-RNTI, or MCS-C-RNTI, or CS-RNTI(s) User specific PDSCH decoding
- Table 4 shows DCI formats transmitted on the PDCCH.
- DCI format 0_0 may be used to schedule a TB-based (or TB-level) PUSCH
- DCI format 0_1 may be used to schedule a TB-based (or TB-level) PUSCH or a code block group (CBG)-based (or CBG-level) PUSCH
- DCI format 1_0 may be used to schedule a TB-based (or TB-level) PDSCH
- DCI format 1_1 may be used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH (DL grant DCI).
- DCI format 0_0/0_1 may be referred to as UL grant DCI or UL scheduling information
- DCI format 1_0/1_1 may be referred to as DL grant DCI or DL scheduling information
- DCI format 2_0 is used to deliver dynamic slot format information (e.g., a dynamic slot format indicator (SFI)) to a UE
- DCI format 2_1 is used to deliver DL pre-emption information to a UE.
- DCI format 2_0 and/or DCI format 2_1 may be delivered to a corresponding group of UEs on a group common PDCCH which is a PDCCH directed to a group of UEs.
- DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, whereas DCI format 0_1 and DCI format 1_1 may be referred to as non-fallback DCI formats.
- a DCI size/field configuration is maintained to be the same irrespective of a UE configuration.
- the DCI size/field configuration varies depending on a UE configuration in the non-fallback DCI formats.
- the PDSCH delivers DL data (e.g., a downlink shared channel (DL-SCH) transport block (TB)) and adopts a modulation scheme such as quadrature phase shift keying (QPSK), 16-ary quadrature amplitude modulation (16 QAM), 64-ary QAM (64 QAM), or 256-ary QAM (256 QAM).
- a TB is encoded to a codeword.
- the PDSCH may deliver up to two codewords.
- the codewords are individually subjected to scrambling and modulation mapping, and modulation symbols from each codeword are mapped to one or more layers.
- An OFDM signal is generated by mapping each layer together with a DMRS to resources, and transmitted through a corresponding antenna port.
- the PUCCH delivers uplink control information (UCI).
- UCI uplink control information
- the UCI includes the following information.
- Table 5 illustrates exemplary PUCCH formats.
- PUCCH formats may be divided into short PUCCHs (Formats 0 and 2) and long PUCCHs (Formats 1, 3, and 4) based on PUCCH transmission durations.
- [Table 5] PUCCH format Length in OFDM PUCCH symbols N symb PUCCH Number of bits Usage Etc 0 1 - 2 ⁇ 2 HARQ, SR Sequence select ion 1 4 - 14 ⁇ 2 HARQ, [SR] Sequence modulat ion 2 1 - 2 >2 HARQ, CSI, [SR] CP-OFDM 3 4 - 14 >2 HARQ, CSI, [SR] DFT-s-OFDM (no UE multiplexing) 4 4 14 >2 HARQ, CSI, [SR] DFT-s-OFDM (Pre DFT OCC)
- PUCCH format 0 conveys UCI of up to 2 bits and is mapped in a sequence-based manner, for transmission. Specifically, the UE transmits specific UCI to the BS by transmitting one of a plurality of sequences on a PUCCH of PUCCH format 0. Only when the UE transmits a positive SR, the UE transmits the PUCCH of PUCCH format 0 in PUCCH resources for a corresponding SR configuration.
- PUCCH format 1 conveys UCI of up to 2 bits and modulation symbols of the UCI are spread with an orthogonal cover code (OCC) (which is configured differently whether frequency hopping is performed) in the time domain.
- OCC orthogonal cover code
- the DMRS is transmitted in a symbol in which a modulation symbol is not transmitted (i.e., transmitted in time division multiplexing (TDM)).
- PUCCH format 2 conveys UCI of more than 2 bits and modulation symbols of the DCI are transmitted in frequency division multiplexing (FDM) with the DMRS.
- the DMRS is located in symbols #1, #4, #7, and #10 of a given RB with a density of 1/3.
- a pseudo noise (PN) sequence is used for a DMRS sequence.
- frequency hopping may be activated.
- PUCCH format 3 does not support UE multiplexing in the same PRBS, and conveys UCI of more than 2 bits. In other words, PUCCH resources of PUCCH format 3 do not include an OCC. Modulation symbols are transmitted in TDM with the DMRS.
- PUCCH format 4 supports multiplexing of up to 4 UEs in the same PRBS, and conveys UCI of more than 2 bits.
- PUCCH resources of PUCCH format 3 include an OCC. Modulation symbols are transmitted in TDM with the DMRS.
- the PUSCH delivers UL data (e.g., UL-shared channel transport block (UL-SCH TB)) and/or UCI based on a CP-OFDM waveform or a DFT-s-OFDM waveform.
- UL-SCH TB UL-shared channel transport block
- the UE transmits the PUSCH by transform precoding. For example, when transform precoding is impossible (e.g., disabled), the UE may transmit the PUSCH in the CP-OFDM waveform, while when transform precoding is possible (e.g., enabled), the UE may transmit the PUSCH in the CP-OFDM or DFT-s-OFDM waveform.
- a PUSCH transmission may be dynamically scheduled by a UL grant in DCI, or semi-statically scheduled by higher-layer (e.g., RRC) signaling (and/or Layer 1 (L1) signaling such as a PDCCH) (configured scheduling or configured grant).
- the PUSCH transmission may be performed in a codebook-based or non-codebook-based manner.
- FIG. 6 illustrates an ACK/NACK transmission process.
- the UE may detect a PDCCH in slot #n.
- the PDCCH includes DL scheduling information (e.g., DCI format 1_0 or DCI format 1_1).
- the PDCCH indicates a DL assignment-to-PDSCH offset, K0 and a PDSCH-HARQ-ACK reporting offset, K1.
- DCI format 1_0 or DCI format 1_1 may include the following information.
- the UE may transmit UCI on the PUCCH in slot #(n+K1).
- the UCI includes an HARQ-ACK response to the PDSCH.
- the HARQ-ACK response may be configured in one bit.
- the HARQ-ACK response may be configured in two bits if spatial bundling is not configured and in one bit if spatial bundling is configured.
- slot #(n+K1) is designated as an HARQ-ACK transmission timing for a plurality of PDSCHs
- UCI transmitted in slot #(n+K1) includes HARQ-ACK responses to the plurality of PDSCHs.
- Each DL HARQ process manages state variables related to the transmission number of MAC protocol data units (PDUs) in a buffer, an HARQ feedback for a MAC PDU in the buffer, a current redundancy version, and so on.
- PDUs MAC protocol data units
- Each HARQ process is identified by an HARQ process ID.
- FIG. 7 illustrates an exemplary PUSCH transmission process.
- a UE may detect a PDCCH in slot #n.
- the PDCCH may include UL scheduling information (e.g., DCI format 0_0 or DCI format 0_1).
- DCI format 0_0 and DCI format 0_1 may include the following information.
- the UE may then transmit the PUSCH in slot #(n+K2) according to the scheduling information in slot #n.
- the PUSCH includes a UL-SCH TB.
- FIG. 8 illustrates exemplary multiplexing of UCI in a PUSCH. If a plurality of PUCCH resources overlap with a PUSCH resource in a slot and a PUCCH-PUSCH simultaneous transmission is not configured in the slot, UCI may be transmitted on a PUSCH (UCI piggyback or PUSCH piggyback), as illustrated. In the illustrated case of FIG. 8 , an HARQ-ACK and CSI are carried in a PUSCH resource.
- a NR cell in the unlicensed-band aims to support a stand-alone operation.
- PUCCH, PUSCH, and/or PRACH transmission may be supported in the NR UCell.
- FIG. 9 illustrates an exemplary wireless communication system supporting an unlicensed band applicable to the present disclosure.
- a cell operating in a licensed band is defined as an L-cell, and a carrier of the L-cell is defined as a (DL/UL) LCC.
- a cell operating in an unlicensed band is defined as a U-cell, and a carrier of the U-cell is defined as a (DL/UL) UCC.
- the carrier/carrier-frequency of a cell may refer to the operating frequency (e.g., center frequency) of the cell.
- a cell/carrier e.g., CC
- CC is commonly called a cell.
- one UE may use a plurality of aggregated cells/carriers to exchange a signal with the BS.
- one CC may be set to a primary CC (PCC), and the remaining CCs may be set to secondary CCs (SCCs).
- Specific control information/channels e.g., CSS PDCCH, PUCCH
- FIG. 9 (a) shows a case in which the UE and BS exchange signals on both the LCC and UCC (non-stand-alone (NSA) mode).
- FIG. 10 illustrates an exemplary method of occupying resources in an unlicensed band.
- a communication node in the U-band needs to determine whether a corresponding channel is used by other communication node(s) before transmitting a signal.
- the communication node may perform carrier sensing (CS) before transmitting the signal so as to check whether the other communication node(s) perform signal transmission.
- CS carrier sensing
- the other communication node(s) perform no signal transmission, it is said that clear channel assessment (CCA) is confirmed.
- CCA threshold is predefined or configured by higher layer signaling (e.g., RRC signaling)
- the communication node may determine that the channel is busy.
- the communication node may determine that the channel is idle. When it is determined that the channel is idle, the communication node may start the signal transmission in the UCell.
- the Wi-Fi standard (802.11ac) specifies a CCA threshold of 62 dBm for non-Wi-Fi signals and a CCA threshold of -82 dBm for Wi-Fi signals.
- the sires of processes described above may be referred to as Listen-Before-Talk (LBT) or a channel access procedure (CAP).
- LBT Listen-Before-Talk
- CAP channel access procedure
- the LBT may be interchangeably used with the CAP.
- FBE frame based equipment
- LBE load based equipment
- one fixed frame is made up of a channel occupancy time (e.g., 1 to 10ms), which is a time period during which once a communication node succeeds in channel access, the communication node may continue transmission, and an idle period corresponding to at least 5% of the channel occupancy time
- CCA is defined as an operation of observing a channel during a CCA slot (at least 20us) at the end of the idle period.
- the communication node performs CCA periodically on a fixed frame basis. When the channel is unoccupied, the communication node transmits during the channel occupancy time, whereas when the channel is occupied, the communication node defers the transmission and waits until a CCA slot in the next period.
- the communication node may set q ⁇ 4, 5, ... , 32 ⁇ and then perform CCA for one CCA slot.
- the communication node may secure a time period of up to (13/32)q ms and transmit data in the time period.
- the communication node randomly selects N ⁇ 1, 2, ... , q ⁇ , stores the selected value as an initial value, and then senses a channel state on a CCA slot basis.
- the communication node decrements the stored counter value by 1.
- the communication node may secure a time period of up to (13/32)q ms and transmit data.
- FIG. 11 is a flowchart illustrating UE's Type 1 CAP operation for UL signal transmission.
- the UE checks whether the channel of U-cell(s) is idle (S1550). If the channel is idle (YES in S1550), the UE checks whether the backoff counter value is 0 (S1530). On the contrary, if the channel is not idle in S1550, that is, if the channel is busy (NO in S1550), the UE checks whether the corresponding channel is idle for a defer duration T d (longer than or equal to 25 usec), which is longer than a slot duration (e.g., 9 usec), according to step 5 (S1560). If the channel is idle for the defer duration (YES in S1570), the UE may resume the CAP.
- T d longer than or equal to 25 usec
- a slot duration e.g., 9 usec
- the defer duration may include a duration of 16 usec and m p consecutive slot durations (e.g., 9 usec), which immediately follows the duration of 16 usec. If the channel is busy for the defer duration (NO in S 1570), the UE performs step S 1560 again to check whether the channel is idle for a new defer duration.
- Table 6 shows that the values of m p , a minimum CW, a maximum CW, a maximum channel occupancy time (MCOT), and allowed CW sizes, which are applied to the CAP, vary depending on channel access priority classes.
- Channel Access Priority Class ( p ) m p CW min, p CW max, p T min cot, p allowed CW p sizes 1 2 3 7 2 ms ⁇ 3,7 ⁇ 2 2 7 15 4 ms ⁇ 7,15 ⁇ 3 3 is 1023 6ms or 10 ms ⁇ 15.31,63,127,255,511,1023 ⁇ 4 7 is 1023 6ms or 10 ms ⁇ 15,31,63,127,255,511,1023 ⁇ 4 7 is 1023 6ms or 10 ms ⁇ 15,31,63,127,255,511,1023 ⁇
- the size of a CW applied to the Type 1 UL CAP may be determined in various ways. For example, the CW size may be adjusted depending on whether the value of of a new data indicator (NDI) for at least one HARQ process associated with HARQ_ID_ref, which is the HARQ process ID of a UL-SCH in a predetermined time period (e.g., a reference TU), is toggled.
- NDI new data indicator
- the reference subframe (or slot) n ref is the subframe (or slot) n 0 .
- a UE operation of transmitting an HARQ-ACK feedback based on a U-band PUCCH/PUSCH transmission, in response to a DL data (e.g., PDSCH) reception may be essential (hereinafter, HARQ-ACK is referred to as A/N, for convenience).
- a PUCCH/PUSCH is a PUCCH or a PUSCH.
- the present disclosure proposes a method of transmitting an HARQ-ACK feedback (hereinafter, referred to as A/N) in a U-band.
- A/N HARQ-ACK feedback
- the present disclosure may be applied to a method of transmitting other UCI (e.g., CSI or SR) on a PUCCH/PUSCH, not limited to a method of transmitting an HARQ-ACK feedback on a PUCCH/PUSCH.
- the present disclosure is not limited to an LBT-based U-band operation, and may be applied to an L-band (or U-band) operation without LBT in a similar manner.
- a plurality of CCs may be replaced with a plurality of BWPs (BWP indexes) configured in one (or more) CC(s)/(serving)cell(s) or a plurality of CCs/(serving)cells including a plurality of BWPs (i.e., CC (index)-BWP (index) combinations).
- BWP indexes configured in one (or more) CC(s)/(serving)cell(s) or a plurality of CCs/(serving)cells including a plurality of BWPs (i.e., CC (index)-BWP (index) combinations).
- t-A/N scheme Timing-based A/N feedback method
- A/N information may include response information for reception of a PDSCH in slot #(m-i).
- Slot #(m-i) is a slot corresponding to a candidate HARQ timing.
- the UE may generate/transmit A/N information for PDSCHs received in slots #n to #(n+3) (i.e., A/N feedbacks for all four slots).
- An A/N response for the PDSCH received in slot #n+1 or slot #(n+3) may be processed as NACK.
- a counter downlink assignment index (c-DAI) and/or a total DAI (t-DAI) may also be signaled by (DL grant) DCI.
- the c-DAI may indicate the scheduled number of a PDSCH corresponding to the (DL grant) DCI.
- the t-DAI may indicate the total number of PDSCHs scheduled up to the current slot (or the total number of slots carrying PDSCHs). Accordingly, the UE may operate to transmit A/Ns for PDSCHs corresponding to c-DAI values from an initial c-DAI value to the last (received) t-DAI value at an indicated HARQ timing.
- the c-DAI and the t-DAI may have the same meaning. Accordingly, only when there are a plurality of serving cells, the t-DAI may be included in the (DL grant) DCI.
- the c-DAI may indicate the scheduled number of a PDSCH (or the number of (a serving cell, a slot) carrying the PDSCH), which has first been counted in the cell domain and then in the time domain.
- the t-DAI may indicate the total number of PDSCHs scheduled so far (up to the current slot) (or the total number of (serving cells, slots) carrying PDSCHs).
- the c-DAI/t-DAI may be defined based on a PDCCH.
- a PDSCH may be replaced by a PDCCH
- a slot carrying a PDCCH may be replaced by a PDCCH monitoring occasion in which a PDCCH (or DCI) related to the PDCCH exists, in the above description.
- the c-DAI/t-DAI may be indicated in two bits. A number larger than 4 may be indicated by using a modulo operation, as follows.
- FIG. 13(b) illustrates a case in which a DAI is signaled by (DL grant) DCI in the same situation as illustrated in FIG. 13(a) .
- FIG. 14 Pooling-based A/N feedback method (hereinafter, referred to as p-A/N scheme) (FIG. 14).
- HpIDs HARQ process IDs
- A/N pooling may be defined as pooling of an A/N transmission for a PDSCH corresponding to an HARQ process ID (indicated by pooling DCI) or pooling of an A/N transmission for at least one PDSCH corresponding to a t-DAI value (indicated by pooling DCI).
- the UE may transmit A/N information for reception of PDSCHs corresponding to an initial c-DAI to a t-DAI value at one time.
- a small CWS-based or BO-less type LBT operation is defined as LBT type A (e.g., no LBT or Cat-2 LBT), and a large CWS-based or BO-based LBT operation may be defined as LBT type B (e.g., Cat-4 LBT).
- LBT type A e.g., no LBT or Cat-2 LBT
- LBT type B e.g., Cat-4 LBT
- LBT type A is indicated by A/N triggering DCI
- ⁇ t-A/N feedback type candidate HARQ timing set, candidate PUCCH starting symbol set, A/N PUCCH resource set ⁇ corresponding to/configured for intra-COT A/N transmission may be applied.
- LBT type B When LBT type B is indicated, ⁇ p-A/N feedback type, candidate HARQ timing set, candidate PUCCH starting symbol set, A/N PUCCH resource set ⁇ corresponding to/configured for inter-COT A/N transmission may be applied.
- LBT type X no LBT
- ⁇ t-A/N feedback type candidate HARQ timing set, candidate PUCCH starting symbol set, A/N PUCCH resource set ⁇ corresponding to/configured for intra-COT A/N transmission may be applied.
- LBT type Y When Cat-2 or Cat-4 LBT (hereinafter, LBT type Y) is indicated, (p-A/N feedback type, candidate HARQ timing set, candidate PUCCH starting symbol set, A/N PUCCH resource set ⁇ corresponding to/configured for inter-COT A/N transmission may be applied.
- all or a part of the following UL TX parameters may be configured differently depending on whether 1) LBT type A (or LBT type X) or 2) LBT type B (or LBT type Y) is indicated by A/N triggering DCI.
- LBT type A may mean LBT type A or X
- LBT type B may mean LBT type B or Y.
- An A/N transmission may be triggered by DL grant DCI, UL grant DCI, or common DCI.
- UL data e.g., PUSCH
- a process of transmitting UL grant DCI that schedules a PUSCH for the UE in a COT period occupied by LBT and indicating to the UE to transmit a PUSCH in the same COT period (or a BS-initiated COT period starting with/occupied by a DL transmission) may be considered (intra-COT PUSCH transmission).
- a process of indicating transmission of a PUSCH corresponding to UL grant DCI transmitted in a specific COT period, in another COT period (or a period which does not belong to a BS-initiated COT period) following the COT period because of a UE processing time required for decoding a UL grant DCI signal and encoding a corresponding PUSCH signal may be considered (inter-COT PUSCH transmission).
- intra-COT PUSCH transmission for convenience, referred to as intra-COT
- inter-COT for convenience, referred to as inter-COT
- all or part of the following UL TX parameters may be configured differently.
- a small CWS-based or BO-less type LBT operation is defined as LBT type A (e.g., no LBT or Cat-2 LBT), and a large CWS-based or BO-based LBT operation may be defined as LBT type B (e.g., Cat-4 LBT).
- LBT type A e.g., no LBT or Cat-2 LBT
- LBT type B e.g., Cat-4 LBT
- LBT type A is indicated by UL grant DCI
- ⁇ candidate HARQ timing set, candidate PUSCH starting symbol set, PUSCH resource allocation ⁇ corresponding to/configured for intra-COT PUSCH transmission may be applied.
- LBT type B is indicated, ⁇ candidate HARQ timing set, candidate PUSCH starting symbol set, PUSCH resource allocation ⁇ corresponding to/configured for inter-COT PUSCH transmission may be applied.
- LBT type X when no LBT (hereinafter, LBT type X) is indicated by UL grant DCI, ⁇ candidate HARQ timing set, candidate PUSCH starting symbol set, PUSCH resource allocation ⁇ corresponding to/configured for intra-COT PUSCH transmission may be applied.
- LBT type Y When Cat-2 or Cat-4 LBT (hereinafter, LBT type Y) is indicated, (candidate HARQ timing set, candidate PUSCH starting symbol set, PUSCH resource allocation ⁇ corresponding to/configured for inter-COT PUSCH transmission may be applied.
- all or a part of the following UL TX parameters may be configured differently depending on whether 1) LBT type A (or LBT type X) or 2) LBT type B (or LBT type Y) is indicated by UL grant DCI.
- LBT type A may mean LBT type A or X
- LBT type B may mean LBT type B or Y.
- a field in a PDCCH/PDSCH, indicating a UL grant (DCI)-to-PUSCH transmission (HARQ) timing is defined as a UL HARQ timing indicator (U-HTI) field, for convenience.
- a different number of candidate PUSCH timings (within the timing set configured for each U-HTI state) may be applied according to an LBT type indicated/configured for a PUSCH transmission.
- An A/N feedback in the U-band may fail for various reasons in view of the nature of the unlicensed band.
- the UE may drop/defer an A/N transmission due to LBT failure.
- the BS may fail in A/N reception/detection.
- the A/N may be transmitted on a PUCCH or PUSCH (PUCCH/PUSCH).
- the BS fails to receive an A/N from the UE, the BS may not identify whether the reason for the A/N reception failure is (1) LBT failure of the UE or (2) A/N reception/detection failure of the BS.
- the UE may attempt to retransmit an A/N for previous data at the next transmission opportunity in the case of (1), while the UE may attempt to transmit an A/N for new data in the case of (2).
- the UE may set A/N information corresponding to the new data to NACK or DTX.
- the BS since the BS does not know whether the reason for the A/N reception failure is (1) or (2), the BS may not correctly interpret the A/N transmitted by the UE.
- the p-A/N scheme may be used in the U-band as described above.
- the BS may make the UE defer the A/N transmission for the PDSCH (pending), and then indicate an A/N transmission for a PDSCH corresponding to (i) all DL HARQ process IDs, or (ii) some specific DL HARQ process ID(s) to the UE by DCI (pooling).
- DCI DCI
- FIG. 16 illustrates A/N mismatch between a UE and a BS.
- the HpID may be indicated by DCI that schedules each data.
- the UE then transmits A/N feedback information to the BS (S1604).
- HpID [X, Y, Z] is one HpID group.
- the BS may fail to receive the A/N information. For example, while the UE transmits A/N information on a PUCCH or a PUSCH, the BS may fail to receive the PUCCH or PUSCH.
- the UE may receive a request for A/N pooling from the BS.
- the present disclosure proposes a method of indicating information such as the following option by a 1-bit flag (hereinafter, a new feedback indicator (NFI)) in DCI.
- the NFI may be signaled in the form of toggling.
- the DCI may include AN triggering DCI.
- An A/N transmission may be triggered by DL grant DCI, UL grant DCI, or (UE-)common DCI.
- NFI information may indicate whether the BS has (a) succeeded or (b) failed in detecting/receiving an A/N feedback transmitted at a previous (recent) time point (hereinafter referred to as a previous A/N feedback).
- a previous A/N feedback For example, in the case of (a), an NFI value toggled from an NFI value received in previous (recent) DCI may be indicated by current DCI.
- an NFI value that has not been toggled from the NFI value received in the previous (recent) DCI may be indicated by the current DCI.
- (a) may be indicated by a non-toggled NFI, and (b) may also be indicated by a toggled NFI.
- the previous A/N feedback includes drop of the A/N feedback due to LBT failure during transmission of the UE.
- the BS may indicate to the UE that the BS has not received A/N feedback(s) ((e.g., A/N PUCCH(s)) in previous A/N opportunity(s) by a toggled NFI. Further, the BS may indicate to the UE that the BS has received the A/N feedback(s) ((e.g., A/N PUCCH(s)) in the previous A/N opportunity(s) by a non-toggled NFI.
- A/N feedback(s) (e.g., A/N PUCCH(s)) in previous A/N opportunity(s) by a toggled NFI.
- the UE may configure/transmit (a) an A/N feedback in consideration of only a data reception state after the previous A/N feedback (toggled NFI) or (b) an A/N feedback based on (the data reception state after the previous A/N feedback and the previous A/N feedback) (non-toggled NFI).
- the UE may configure/transmit (a) an updated A/N feedback by processing the remaining A/Ns as NACK and/or DTX except for an A/N corresponding to a PDSCH scheduled after the previous A/N transmission (toggled NFI) or (b) an A/N feedback by maintaining the remaining A/Ns except for the A/N corresponding to the PDSCH scheduled after the previous A/N transmission (non-toggled NFI), based on the NFI in the DCI.
- an updated A/N feedback by processing the remaining A/Ns as NACK and/or DTX except for an A/N corresponding to a PDSCH scheduled after the previous A/N transmission (toggled NFI)
- an A/N feedback by maintaining the remaining A/Ns except for the A/N corresponding to the PDSCH scheduled after the previous A/N transmission (non-toggled NFI), based on the NFI in the DCI.
- FIG. 17 illustrates an A/N feedback process according to the present disclosure.
- the UE may transmit first A/N information (S1702). After the transmission of the first A/N information, the UE may receive one or more data (S1704). The UE may further receive downlink control information (e.g., DCI) including a 1-bit indicator (e.g., NFI) (S1706). Then, the UE may transmit second A/N information including an A/N result for the one or more data based on whether the 1-bit indicator has been toggled (S1708). Whether to transmit the first A/N information and the second A/N information may be determined according to LBT results.
- DCI downlink control information
- NFI 1-bit indicator
- Whether to transmit the first A/N information and the second A/N information may be determined according to LBT results.
- the second A/N information may be generated by reflecting only a data reception state after the transmission of the first A/N information.
- the second A/N information may be generated in consideration of both (i) the first A/N information, and (ii) the data reception state after the transmission of the first A/N information.
- the remaining A/Ns may be set as NACK, except for A/Ns corresponding to the one or more data in the second A/N information.
- the remaining A/Ns may be set as the same as the first A/N information, except for the A/Ns corresponding to the one or more data in the second A/N information.
- Each of the first A/N information and the second A/N information may include a plurality of A/N results for the same HARQ process ID group. Also, each of the first A/N information and the second A/N information may include a plurality of A/N results for the same slot group.
- FIG. 18 illustrates an A/N feedback process according to the present disclosure.
- the basic situation is the same as that of FIG. 16 , and for a description of steps S1802 and S1804, the description of FIG. 16 may be referred to.
- the NFI may be used as follows for the purpose of CWS update for a (BO-based) LBT operation required for an A/N PUCCH (or PUSCH) transmission.
- the CWS update operation includes CWS reset or CWS increase.
- the NFI may indicate whether (a) a CWS for an A/N PUCCH/PUSCH transmission is to be reset to a minimum value, or (b) the CWS is to be increased (by a certain unit). For example, when receiving a toggled NFI, the UE may reset the CWS for the A/N PUCCH (or PUSCH) transmission to the minimum value. When receiving a non-toggled NFI, the UE may increase the CWS value (by the certain unit). When the CWS reset operation is indicated (i.e., a toggled NFI), the UE may configure/transmit an A/N feedback in consideration of only a data reception state after a previous A/N feedback.
- the UE may configure/transmit an A/N feedback based on ⁇ the data reception state after the previous A/N feedback, and the previous A/N feedback ⁇ .
- the CWS reset operation is indicated (i.e., a toggled NFI)
- the UE may configure/transmit an updated A/N feedback by processing the remaining A/Ns as NACK and/or DTX except for an A/N corresponding to a PDSCH scheduled after the previous A/N transmission.
- the UE may configure/transmit an A/N feedback by maintaining the remaining A/Ns except for the A/N corresponding to the PDSCH scheduled after the previous A/N transmission.
- the operation of updating a CWS for an A/N PUCCH/PUSCH transmission based on NFI information may be limited to a case in which the corresponding A/N PUCCH/PUSCH transmission is configured/indicated for the first/starting channel/slot of one UL TX burst. Accordingly, when the corresponding A/N PUCCH/PUSCH transmission is configured/indicated for a channel/slot other than the first/starting channel/slot within the UL TX burst, the UE may not reflect the corresponding NFI information in the CWS update (e.g., the UE may maintain the previous CWS value).
- total CCs may be divided into a plurality of CC groups, and NFI information may be signaled individually/independently for each CC group.
- total HARQ process IDs configured/defined for each CC may be divided into a plurality of HARQ process ID groups, and NFI information may be signaled individually/independently for each HARQ process ID group.
- the NFI information may be signaled by any DCI that triggers an A/N transmission. That is, the NFI information may be signaled by UL grant DCI as well as DL grant DCI. For example, when the NFI information is signaled by UL grant DCI, the UE may configure an A/N feedback (payload) to be piggybacked to a PUSCH based on the NFI information. Further, it may be regulated that all of NFIs signaled by A/N triggering DCI (e.g., DL/UL grant DCI) indicating the same A/N transmission timing have the same value.
- A/N triggering DCI e.g., DL/UL grant DCI
- the UE may operate, assuming/expecting that A/N triggering DCIs indicating the same A/N transmission timing have the same NFI signaling/value. For example, when A/N triggering DCIs indicating the same A/N transmission timing have different NFI values, the UE may discard the A/N triggering DCIs and/or skip the A/N transmission, assuming that there are errors in the A/N triggering DCIs.
- the UE may signal an NFI value indicated/received by/in DCI to the BS on an A/N PUCCH/PUSCH.
- the NFI value may be signaled by a specific bit in UCI payload, by a CRC (masking) added to the UCI payload, or by scrambling/a DMRS applied to the PUSCH transmission.
- a CWS update operation for an A/N PUCCH/PUSCH transmission may be performed based on NDI information in DL grant DCI. For example, for a PDSCH corresponding to a DL HARQ process ID scheduled/transmitted in any CC or a specific CC (e.g., PCell), an ACK may have already been fed back at a previous time. In this situation, since NDI information has not been toggled (for the same DL HARQ process ID), a PDSCH retransmission may be scheduled. The UE may then perform the CWS increase operation for an A/N PUCCH/PUSCH transmission.
- NDI information may be toggled (for the same DL HARQ process ID) so that a new PDSCH may be scheduled.
- the UE may perform the CWS reset operation for the A/N PUCCH/PUSCH transmission.
- the operation of performing CWS update for an A/N PUCCH/PUSCH transmission based on NDI information may be limited to a case in which the A/N PUCCH/PUSCH transmission is configured/indicated for the first/starting channel/slot of a UL TX burst in the A/N PUCCH/PUSCH transmission. Accordingly, when the A/N PUCCH/PUSCH transmission is configured/indicated for a channel/slot other than the first/starting channel/slot within the UL TX burst, the UE may not reflect the corresponding NDI information in the CWS update (e.g., maintain the previous CWS value).
- a plurality of CCs/BWPs may be configured for one UE.
- the UE may perform an NFI-based and/or NDI-based CWS operation, only for a CWS corresponding to a CCBWP in which an A/N PUCCH/PUSCH transmission is configured/indicated.
- the UE may operate, not expecting (reception of) DL grant DCI(s) indicating the specific UL timing as an A/N transmission timing (and/or scheduling the initial transmission of a new TB or indicating a toggled NDI) and assuming that the DCI(s) is absent. Accordingly, upon receipt of DL grant DCI indicating the specific UL timing as an A/N transmission timing, the UE may ignore the corresponding DCI(s).
- the p-A/N scheme may include, for example, an A/N feedback scheme based on an HARQ process ID (group) or an A/N feedback scheme based on a PDSCH (slot) group ID.
- DCI triggering a t-A/N scheme-based A/N feedback and (ii) DCI triggering a p-A/N scheme-based A/N feedback may indicate the same A/N transmission timing.
- the UE may 1) configure/transmit only the p-A/N scheme-based A/N feedback (i.e., skip the t-AN scheme-based A/N feedback transmission), or 2) combine/configure (e.g., concatenate) and transmit the t-A/N scheme-based A/N feedback and the p-A/N scheme-based A/N feedback at the same time (on a single PUCCH/PUSCH).
- DCI that triggers an HARQ process ID (group)-based A/N feedback and (ii) DCI that triggers a PDSCH (slot) group ID-based A/N feedback may indicate the same A/N transmission timing.
- the UE may 1) configure/transmit only the HARQ process ID (group)-based A/N feedback (i.e., skip the PDSCH (slot) group ID-based A/N feedback transmission), or 2) combine/configure (e.g., concatenate) and transmit the HARQ process ID (group)-based A/N feedback and the PDSCH (slot) group ID-based A/N feedback at the same time (on a single PUCCH/PUSCH).
- parameters required for an LBT operation for an initial PUCCH including a UL channel/signal) transmission carrying UCI (e.g., an A/N) (e.g., an LBT priority class, a (maximum) CWS value, and a back-Off counter value) may be configured/indicated for/to the UE by Msg4 (e.g., a contention-resolution message) in an (initial) random access procedure.
- Msg4 e.g., a contention-resolution message
- the UE may perform LBT by applying the parameters, and transmit an A/N PUCCH in response to the Msg4 reception based on the LBT.
- parameters required for an LBT operation for an initial PUSCH may be configured/indicated for/to the UE by an RAR in the (initial) random access procedure.
- the UE may perform LBT by applying the parameters, and transmit an Msg3 PUSCH based on the LBT.
- FIG. 19 illustrates a communication system 1 applied to the present disclosure.
- the communication system 1 applied to the present disclosure includes wireless devices, BSs, and a network.
- a wireless device is a device performing communication using radio access technology (RAT) (e.g., 5G NR (or New RAT) or LTE), also referred to as a communication/radio/5G device.
- RAT radio access technology
- the wireless devices may include, not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device/server 400.
- RAT radio access technology
- XR extended reality
- AI artificial intelligence
- the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of vehicle-to-vehicle (V2V) communication.
- the vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone).
- UAV unmanned aerial vehicle
- the XR device may include an augmented reality (AR)/virtual reality (VR)/mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television (TV), a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and so on.
- AR augmented reality
- VR virtual reality
- MR mixeded reality
- the hand-held device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch or smart glasses), and a computer (e.g., a laptop).
- the home appliance may include a TV, a refrigerator, a washing machine, and so on.
- the IoT device may include a sensor, a smart meter, and so on.
- the BSs and the network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS/network node for other wireless devices.
- the wireless devices 100a to 100f may be connected to the network 300 via the BSs 200.
- An AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300.
- the network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network.
- the wireless devices 100a to 100f may communicate with each other through the BSs 200/network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without intervention of the BSs/network.
- the vehicles 100b-1 and 100b-2 may perform direct communication (e.g.
- V2V/vehicle-to-everything (V2X) communication may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.
- Wireless communication/connections 150a, 150b, and 150c may be established between the wireless devices 100a to 100fBS 200 and between the BSs 200.
- the wireless communication/connections may be established through various RATs (e.g., 5GNR) such as UL/DL communication 150a, sidelink communication 150b (or, D2D communication), or inter-BS communication (e.g. relay or integrated access backhaul (IAB)).
- RATs e.g., 5GNR
- Wireless signals may be transmitted and received between the wireless devices, between the wireless devices and the BSs, and between the BSs through the wireless communication/connections 150a, 150b, and 150c.
- signals may be transmitted and receive don various physical channels through the wireless communication/connections 150a, 150b and 150c.
- various configuration information configuring processes various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocation processes, for transmitting/receiving wireless signals, may be performed based on the various proposals of the present disclosure.
- various signal processing processes e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping
- resource allocation processes for transmitting/receiving wireless signals
- FIG. 20 illustrates wireless devices applicable to the present disclosure.
- a first wireless device 100 and a second wireless device 200 may transmit wireless signals through a variety of RATs (e.g., LTE and NR).
- RATs e.g., LTE and NR
- the first wireless device 100 and the second wireless device 200 ⁇ may correspond to ⁇ the wireless device 100x and the BS 200 ⁇ and/or ⁇ the wireless device 100x and the wireless device 100x ⁇ of FIG. 20 .
- the first wireless device 100 may include one or more processors 102 and one or more memories 104, and further include one or more transceivers 106 and/or one or more antennas 108.
- the processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document.
- the processor(s) 102 may process information in the memory(s) 104 to generate first information/signals and then transmit wireless signals including the first information/signals through the transceiver(s) 106.
- the processor(s) 102 may receive wireless signals including second information/signals through the transceiver(s) 106 and then store information obtained by processing the second information/signals in the memory(s) 104.
- the memory(s) 104 may be connected to the processor(s) 102 and may store various pieces of information related to operations of the processor(s) 102.
- the memory(s) 104 may store software code including instructions for performing all or a part of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document.
- the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR).
- the transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive wireless signals through the one or more antennas 108.
- Each of the transceiver(s) 106 may include a transmitter and/or a receiver.
- the transceiver(s) 106 may be interchangeably used with radio frequency (RF) unit(s).
- the wireless device may be a communication modem/circuit/chip.
- the second wireless device 200 may include one or more processors 202 and one or more memories 204, and further include one or more transceivers 206 and/or one or more antennas 208.
- the processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document.
- the processor(s) 202 may process information in the memory(s) 204 to generate third information/signals and then transmit wireless signals including the third information/signals through the transceiver(s) 206.
- the processor(s) 202 may receive wireless signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204.
- the memory(s) 204 may be connected to the processor(s) 202 and store various pieces of information related to operations of the processor(s) 202.
- the memory(s) 204 may store software code including instructions for performing all or a part of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document.
- the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR).
- the transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive wireless signals through the one or more antennas 208.
- Each of the transceiver(s) 206 may include a transmitter and/or a receiver.
- the transceiver(s) 206 may be interchangeably used with RF unit(s).
- the wireless device may be a communication modem/circuit/chip.
- One or more protocol layers may be implemented by, not limited to, one or more processors 102 and 202.
- the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), RRC, and service data adaptation protocol (SDAP)).
- the one or more processors 102 and 202 may generate one or more protocol data units (PDUs) and/or one or more service data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document.
- PDUs protocol data units
- SDUs service data Units
- the one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document.
- signals e.g., baseband signals
- the one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers.
- the one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGAs field programmable gate arrays
- the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include the modules, procedures, or functions.
- Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be included in the one or more processors 102 and 202 or may be stored in the one or more memories 104 and 204 and executed by the one or more processors 102 and 202.
- the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of code, an instruction, and/or a set of instructions.
- the one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands.
- the one or more memories 104 and 204 may be configured to include read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof.
- the one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202.
- the one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.
- the one or more transceivers 106 and 206 may transmit user data, control information, and/or wireless signals/channels, mentioned in the methods and/or operation flowcharts of this document, to one or more other devices.
- the one or more transceivers 106 and 206 may receive user data, control information, and/or wireless signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document, from one or more other devices.
- the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive wireless signals.
- the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or wireless signals to one or more other devices.
- the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or wireless signals from one or more other devices.
- the one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and/or wireless signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document, through the one or more antennas 108 and 208.
- the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).
- the one or more transceivers 106 and 206 may convert received wireless signals/channels from RF band signals into baseband signals in order to process received user data, control information, and wireless signals/channels using the one or more processors 102 and 202.
- the one or more transceivers 106 and 206 may convert the user data, control information, and wireless signals/channels processed using the one or more processors 102 and 202 from the baseband signals into the RF band signals.
- the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters.
- FIG. 21 illustrates another example of a wireless device applied to the present disclosure.
- the wireless device may be implemented in various forms according to a use case/service (refer to FIG. 19 ).
- wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 19 and may be configured to include various elements, components, units/portions, and/or modules.
- each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140.
- the communication unit 110 may include a communication circuit 112 and transceiver(s) 114.
- the communication circuit 112 may include the one or more processors 102 and 202 and/or the one or more memories 104 and 204 of FIG. 21 .
- the transceiver(s) 114 may include the one or more transceivers 106 and 206 and/or the one or more antennas 108 and 208 of FIG.
- the control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140 and provides overall control to the wireless device. For example, the control unit 120 may control an electric/mechanical operation of the wireless device based on programs/code/instructions/information stored in the memory unit 130.
- the control unit 120 may transmit the information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130, information received through the wireless/wired interface from the outside (e.g., other communication devices) via the communication unit 110.
- the additional components 140 may be configured in various manners according to type of the wireless device.
- the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit.
- the wireless device may be implemented in the form of, not limited to, the robot (100a of FIG. 19 ), the vehicles (100b-1 and 100b-2 of FIG. 19 ), the XR device (100c of FIG. 19 ), the hand-held device (100d of FIG. 19 ), the home appliance (100e of FIG. 19 ), the IoT device (100f of FIG.
- the wireless device may be mobile or fixed according to a use case/service.
- all of the various elements, components, units/portions, and/or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110.
- the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110.
- Each element, component, unit/portion, and/or module in the wireless devices 100 and 200 may further include one or more elements.
- the control unit 120 may be configured with a set of one or more processors.
- control unit 120 may be configured with a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphical processing unit, and a memory control processor.
- the memory 130 may be configured with a RAM, a dynamic RAM (DRAM), a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.
- FIG. 22 illustrates a vehicle or an autonomous driving vehicle applied to the present disclosure.
- the vehicle or autonomous driving vehicle may be implemented as a mobile robot, a car, a train, a manned/unmanned aerial vehicle (AV), a ship, or the like.
- AV manned/unmanned aerial vehicle
- a vehicle or autonomous driving vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d.
- the antenna unit 108 may be configured as a part of the communication unit 110.
- the blocks 110/130/140a to 140d correspond to the blocks 110/130/140 of FIG. 21 , respectively.
- the communication unit 110 may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers.
- the control unit 120 may perform various operations by controlling elements of the vehicle or the autonomous driving vehicle 100.
- the control unit 120 may include an ECU.
- the driving unit 140a may enable the vehicle or the autonomous driving vehicle 100 to drive on a road.
- the driving unit 140a may include an engine, a motor, a powertrain, a wheel, a brake, a steering device, and so on.
- the power supply unit 140b may supply power to the vehicle or the autonomous driving vehicle 100 and include a wired/wireless charging circuit, a battery, and so on.
- the autonomous driving unit 140d may implement technology for maintaining a lane on which the vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a route if a destination is set, and the like.
- the communication unit 110 may transfer information about a vehicle position, the autonomous driving route, and/or the driving plan to the external server.
- the external server may predict traffic information data using AI technology based on the information collected from vehicles or autonomous driving vehicles and provide the predicted traffic information data to the vehicles or the autonomous driving vehicles.
- the embodiments of the present disclosure have been described above, focusing on the signal transmission and reception relationship between a UE and a BS.
- the signal transmission and reception relationship is extended to signal transmission and reception between a UE and a relay or between a BS and a relay in the same manner or a similar manner.
- a specific operation described as performed by a BS may be performed by an upper node of the BS. Namely, it is apparent that, in a network comprised of a plurality of network nodes including a BS, various operations performed for communication with a UE may be performed by the BS, or network nodes other than the BS.
- BS may be replaced with the term fixed station, Node B, enhanced Node B (eNode B or eNB), access point, and so on.
- UE may be replaced with the term terminal, mobile station (MS), mobile subscriber station (MSS), and so on.
- the embodiments of the present disclosure may be implemented in the form of a module, a procedure, a function, etc.
- software code may be stored in a memory unit and executed by a processor.
- the memory unit is located at the interior or exterior of the processor and may transmit and receive data to and from the processor via various known means.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Claims (11)
- Verfahren zum Übertragen eines Physical Uplink Control Channel, PUCCH, durch ein Benutzergerät (100), UE, in einem drahtlosen Kommunikationssystem, wobei das Verfahren umfasst:Empfangen erster Downlink Control Information, DCI, einschließlich eines ersten New Feedback Indicator, NFI;Empfangen eines ersten gemeinsam genutzten physikalischen Downlink-Kanals, PDSCH, auf der Grundlage der ersten DCI;Bestimmen erster HARQ-ACK-Information als Reaktion auf die ersten PDSCH- und zweiten HARQ-ACK-Informationen,wobei die zweite HARQ-ACK-Information als Reaktion auf einen zweiten PDSCH bestimmt wird, der durch eine zweite DCI geplant ist, die vor dem Empfang der ersten DCI empfangen wird, basierend auf dem Wert der ersten NFI, der der gleiche ist wie der Wert einer zweiten NFI, die in der zweiten DCI enthalten ist, undwobei die zweite HARQ-ACK-Information als Negative Acknowledgement, NACK, bestimmt wird, basierend auf dem Wert des ersten NFI, der sich von dem Wert des zweiten NFI unterscheidet; undÜbertragen des PUCCH mit der ersten HARQ-ACK-Information und der zweiten HARQ-ACK-Information,wobei sowohl der erste NFI als auch der zweite NFI ein 1-Bit-Flag ist.
- Verfahren nach Anspruch 1, wobei der erste NFI auf der Grundlage des ersten NFI umgeschaltet wird, der sich von dem zweiten NFI unterscheidet, und
wobei der erste NFI nicht umgeschaltet wird, wenn der erste NFI mit dem zweiten NFI identisch ist. - Verfahren nach Anspruch 1 oder 2, wobei die erste HARQ-ACK-Information als ACK oder NACK basierend auf einem Ergebnis einer Decodierung des ersten PDSCH bestimmt wird.
- Verfahren nach einem der Ansprüche 1 bis 3, wobei die erste DCI und die zweite DCI Downlink, DL, grant DCI sind.
- Benutzergerät (100), UE, zum Übertragen eines Physical Uplink Control Channel, PUCCH, in einem drahtlosen Kommunikationssystem, wobei das UE (100) umfasst:mindestens einen Transceiver (106);mindestens einen Prozessor (102); undmindestens einen Computerspeicher (104), der betriebsfähig mit dem mindestens einen Prozessor (102) verbunden werden kann und Anweisungen speichert, die,wenn sie von dem mindestens einen Prozessor (102) ausgeführt werden,Operationen durchführen, die umfassen:Empfangen, durch den mindestens einen Transceiver (106), einer ersten Downlink Control Information, DCI, einschließlich eines ersten New Feedback Indicator, NFI;Empfangen eines ersten Physical Downlink Shared Channel, PDSCH, auf der Grundlage der ersten DCI über den mindestens einen Transceiver (106);Bestimmen erster HARQ-ACK-Information als Reaktion auf den ersten PDSCH und die zweite HARQ-ACK-Information,wobei die zweite HARQ-ACK-Information als Reaktion auf einen zweiten PDSCH bestimmt wird, der durch eine zweite DCI geplant ist, die vor dem Empfang der ersten DCI empfangen wird, basierend auf dem Wert des ersten NFI, der der gleiche ist wie der Wert eines zweiten NFI, die in der zweiten DCI enthalten ist, undwobei die zweite HARQ-ACK-Information als Negative Acknowledgement, NACK, bestimmt wird, basierend auf dem Wert des ersten NFI, der sich von dem Wert des zweiten NFI unterscheidet; undSenden des PUCCH mit der ersten HARQ-ACK-Information und der zweiten HARQ-ACK-Information über den mindestens einen Transceiver (106),
wobei sowohl die erste NFI als auch die zweite NFI ein 1-Bit-Flag ist. - UE (100) nach einem der Ansprüche 1 bis 5, wobei der erste NFI auf der Grundlage des ersten NFI umgeschaltet wird, der sich vom zweiten NFI unterscheidet, und
wobei der erste NFI nicht umgeschaltet wird, wenn der erste NFI mit dem zweiten NFI identisch ist. - Das UE (100) nach einem der Ansprüche 1 bis 6, wobei die erste HARQ-ACK-Information als ACK oder NACK basierend auf einem Ergebnis der Decodierung des ersten PDSCH bestimmt wird.
- Das UE (100) nach einem der Ansprüche 1 bis 7, wobei die erste DCI und die zweite DCI Downlink, DL, grant DCI sind.
- Ein computerlesbares Speichermedium, das mindestens ein Computerprogramm enthält, das mindestens einen Prozessor veranlasst, Operationen durchzuführen, die umfassen:Empfangen von erster Downlink Control Information, DCI, einschließlich eines ersten New Feedback Indicator, NFI;Empfangen eines ersten gemeinsam genutzten physikalischen Downlink-Kanals, PDSCH, auf der Grundlage des ersten DCI;Bestimmen erster HARQ-ACK-Information als Reaktion auf den ersten PDSCH und zweite HARQ-ACK-Information,wobei die zweite HARQ-ACK-Information als Reaktion auf einen zweiten PDSCH bestimmt wird, der durch eine zweite DCI geplant ist, die vor dem Empfang der ersten DCI empfangen wird, basierend auf dem Wert der ersten NFI, der der gleiche ist wie der Wert eines zweiten NFI, der in der zweiten DCI enthalten ist, undwobei die zweite HARQ-ACK-Information als Negative Acknowledgement, NACK, bestimmt wird, basierend auf dem Wert des ersten NFI, der sich von dem Wert des zweiten NFI unterscheidet; undÜbertragen des PUCCH mit der ersten HARQ-ACK-Information und der zweiten HARQ-ACK-Information,
wobei sowohl der erste NFI als auch der zweite NFI ein 1-Bit-Flag ist. - Ein Verfahren zum Empfangen eines Physical Uplink Control Channel, PUCCH, durch eine Basisstation (200), BS, in einem drahtlosen Kommunikationssystem, wobei das Verfahren umfasst:Übertragen erster Downlink Control Information, DCI, einschließlich eines ersten New Feedback Indicator, NFI;Übertragen eines ersten gemeinsam genutzten physikalischen Downlink Kanals, PDSCH, auf der Grundlage der ersten DCI; undEmpfangen des PUCCH mit erster HARQ-ACK-Information als Reaktion auf den ersten PDSCH und zweite HARQ-ACK-Information undwobei die zweite HARQ-ACK-Information als eine Antwort auf ein zweites PDSCH interpretiert wird, das durch eine zweite DCI geplant ist, die von der BS vor der Übertragung der ersten DCI übertragen wurde, basierend auf dem Wert des ersten NFI, der der gleiche ist wie der Wert eines zweiten NFI, der in der zweiten DCI enthalten ist, undwobei erwartet wird, dass die zweite HARQ-ACK-Information eine Negative Acknowledgement, NACK, ist, basierend auf dem Wert des ersten NFI, der sich von dem Wert des zweiten NFI unterscheidet,wobei sowohl die erste NFI als auch die zweite NFI ein 1-Bit-Flag ist.
- Eine Basisstation (200), BS, zum Empfangen eines Physical Uplink Control Channel, PUCCH, in einem drahtlosen Kommunikationssystem, wobei die BS (200) umfasst:mindestens einen Transceiver (206);mindestens einen Prozessor (202); undmindestens einen Computerspeicher (204), der betriebsfähig mit dem mindestens einen Prozessor (202) verbunden werden kann und Anweisungen speichert, die,wenn sie von dem mindestens einen Prozessor (202) ausgeführt werden,Operationen durchführen, die umfassen:
Senden einer ersten Downlink Control Information, DCI, einschließlich eines ersten New Feedback Indicator, NFI, über den mindestens einen Transceiver (206);Übertragen eines ersten gemeinsam genutzten physikalischen Downlink Kanals, PDSCH, über den mindestens einen Transceiver (206) auf der Grundlage des ersten DCI; undEmpfangen des PUCCH mit erste HARQ-ACK-Information als Reaktion auf den ersten PDSCH und zweite HARQ-ACK-Information über den mindestens einen Transceiver (206), undwobei die zweite HARQ-ACK-Information als eine Antwort auf einen zweiten PDSCH interpretiert wird, der durch eine zweite DCI geplant ist, die von der BS vor der Übertragung der ersten DCI übertragen wurde, basierend auf dem Wert des ersten NFI, der der gleiche ist wie der Wert eines zweiten NFI, der in der zweiten DCI enthalten ist, undwobei erwartet wird, dass die zweite HARQ-ACK-Information eine Negative Acknowledgement, NACK, ist, basierend auf dem Wert des ersten NFI, der sich von dem Wert des zweiten NFI unterscheidet,wobei sowohl der erste NFI als auch der zweite NFI ein 1-Bit-Flag ist.
Applications Claiming Priority (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862716978P | 2018-08-09 | 2018-08-09 | |
KR20190004181 | 2019-01-11 | ||
KR20190009388 | 2019-01-24 | ||
KR20190017657 | 2019-02-15 | ||
KR20190036829 | 2019-03-29 | ||
PCT/KR2019/010053 WO2020032670A1 (ko) | 2018-08-09 | 2019-08-09 | 무선 통신 시스템에서 무선 신호 송수신 방법 및 장치 |
EP19846021.4A EP3817494B1 (de) | 2018-08-09 | 2019-08-09 | Verfahren und vorrichtung zum senden und empfangen eines drahtlossignals in einem drahtloskommunikationssystem |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19846021.4A Division-Into EP3817494B1 (de) | 2018-08-09 | 2019-08-09 | Verfahren und vorrichtung zum senden und empfangen eines drahtlossignals in einem drahtloskommunikationssystem |
EP19846021.4A Division EP3817494B1 (de) | 2018-08-09 | 2019-08-09 | Verfahren und vorrichtung zum senden und empfangen eines drahtlossignals in einem drahtloskommunikationssystem |
Publications (3)
Publication Number | Publication Date |
---|---|
EP4188023A1 EP4188023A1 (de) | 2023-05-31 |
EP4188023A8 EP4188023A8 (de) | 2023-07-19 |
EP4188023B1 true EP4188023B1 (de) | 2024-06-12 |
Family
ID=69414986
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19846021.4A Active EP3817494B1 (de) | 2018-08-09 | 2019-08-09 | Verfahren und vorrichtung zum senden und empfangen eines drahtlossignals in einem drahtloskommunikationssystem |
EP23152669.0A Active EP4188023B1 (de) | 2018-08-09 | 2019-08-09 | Verfahren und vorrichtung zum senden und empfangen eines drahtlossignals in einem drahtloskommunikationssystem |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19846021.4A Active EP3817494B1 (de) | 2018-08-09 | 2019-08-09 | Verfahren und vorrichtung zum senden und empfangen eines drahtlossignals in einem drahtloskommunikationssystem |
Country Status (4)
Country | Link |
---|---|
US (1) | US20210297223A1 (de) |
EP (2) | EP3817494B1 (de) |
CN (1) | CN112534943B (de) |
WO (1) | WO2020032670A1 (de) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110830174B (zh) * | 2018-08-10 | 2020-11-27 | 北京紫光展锐通信技术有限公司 | 半静态harq-ack码本的生成方法、用户终端、可读存储介质 |
CN115085871A (zh) * | 2019-02-15 | 2022-09-20 | 华为技术有限公司 | 发送反馈信息的方法和装置和接收反馈信息的方法和装置 |
US11758580B2 (en) * | 2019-08-14 | 2023-09-12 | Qualcomm Incorporated | Channel access procedures for an unlicensed radio frequency spectrum band |
KR20220075192A (ko) * | 2019-09-30 | 2022-06-07 | 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 | 업링크 정보 생성 방법 및 이의 장치 |
WO2022226987A1 (en) * | 2021-04-30 | 2022-11-03 | Qualcomm Incorporated | Channel sensing during away period |
US20240244658A1 (en) * | 2021-07-01 | 2024-07-18 | Qualcomm Incorporated | Cross-fixed frame period (ffp) scheduling of hybrid automatic repeat request (harq) |
EP4393258A1 (de) * | 2021-08-27 | 2024-07-03 | NEC Corporation | Verfahren, vorrichtung und computerlesbares medium zur kommunikation |
WO2023133902A1 (zh) * | 2022-01-17 | 2023-07-20 | Oppo广东移动通信有限公司 | 一种无线通信方法及装置、终端设备、网络设备 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101998501A (zh) * | 2009-08-18 | 2011-03-30 | 中兴通讯股份有限公司 | Harq失败指示方法、harq失败指示数据帧及服务节点b |
WO2014000221A1 (en) * | 2012-06-28 | 2014-01-03 | Nokia Corporation | Flexible harq ack/nack transmission |
EP3378264A1 (de) * | 2015-11-19 | 2018-09-26 | Nokia Solutions and Networks Oy | Dynamische harq-ack-codebuch-grösse in einem unlizenzierten spektrum |
US10568081B2 (en) * | 2016-03-21 | 2020-02-18 | Samsung Electronics Co., Ltd. | Scheduling uplink transmissions |
CN107734653B (zh) * | 2016-08-10 | 2021-10-26 | ***通信有限公司研究院 | 一种信息反馈方法、基站及用户设备 |
JP6929945B2 (ja) * | 2017-01-15 | 2021-09-01 | エルジー エレクトロニクス インコーポレイティド | 無線通信システムにおいて、harq−ack信号を送信する方法、及びそのための装置 |
US10211955B2 (en) * | 2017-02-02 | 2019-02-19 | Qualcomm Incorporated | Half-duplex operation in new radio systems |
EP4221029A1 (de) * | 2018-05-11 | 2023-08-02 | Telefonaktiebolaget LM Ericsson (publ) | Harq-codebuch für funkzugangsnetz |
US10924225B2 (en) * | 2018-08-03 | 2021-02-16 | Mediatek Inc. | Group-based hybrid automatic repeat request (HARQ) acknowledgement feedback |
-
2019
- 2019-08-09 US US17/265,500 patent/US20210297223A1/en active Pending
- 2019-08-09 EP EP19846021.4A patent/EP3817494B1/de active Active
- 2019-08-09 CN CN201980052197.4A patent/CN112534943B/zh active Active
- 2019-08-09 EP EP23152669.0A patent/EP4188023B1/de active Active
- 2019-08-09 WO PCT/KR2019/010053 patent/WO2020032670A1/ko unknown
Also Published As
Publication number | Publication date |
---|---|
CN112534943B (zh) | 2023-12-15 |
US20210297223A1 (en) | 2021-09-23 |
WO2020032670A1 (ko) | 2020-02-13 |
EP3817494A1 (de) | 2021-05-05 |
EP3817494B1 (de) | 2023-07-12 |
EP4188023A8 (de) | 2023-07-19 |
CN112534943A (zh) | 2021-03-19 |
EP3817494A4 (de) | 2021-09-01 |
EP4188023A1 (de) | 2023-05-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210329703A1 (en) | Method and apparatus for transmitting or receiving wireless signal in wireless communication system | |
EP4188023B1 (de) | Verfahren und vorrichtung zum senden und empfangen eines drahtlossignals in einem drahtloskommunikationssystem | |
EP4057538B1 (de) | Verfahren und vorrichtung zum senden und empfangen eines signals in einem drahtloskommunikationssystem | |
US12022481B2 (en) | Method and device for transmitting and receiving wireless signal in wireless communication system | |
US11902980B2 (en) | Method and device for transmitting/receiving wireless signal in wireless communication system | |
EP4057537A1 (de) | Verfahren und vorrichtung zum senden oder empfangen eines signals in einem drahtloskommunikationssystem | |
US11785639B2 (en) | Method and apparatus for transmitting and receiving signal in wireless communication system | |
US11963228B2 (en) | Method and apparatus for transmitting and receiving wireless signals in wireless communication system | |
EP4057536A1 (de) | Verfahren und vorrichtung zum senden und empfangen eines drahtlossignals in einem drahtloskommunikationssystem | |
US20230043814A1 (en) | Method for transmitting or receiving signal in wireless communication system supporting unlicensed band, and apparatus supporting same | |
US20220201764A1 (en) | Method for transmitting and receiving signal in wireless communication system and apparatus supporting same | |
US12028854B2 (en) | Method and apparatus for transmitting or receiving wireless signal in wireless communication system | |
US20220078822A1 (en) | Method for transmitting and receiving signal in wireless communication system and apparatus supporting same | |
US11871450B2 (en) | Method and apparatus for transmitting or receiving signal in wireless communication system | |
EP4050958A1 (de) | Verfahren und vorrichtung zum senden und empfangen eines signals in einem drahtloskommunikationssystem | |
US20230131373A1 (en) | Method for transmitting or receiving signal in wireless communication system supporting unlicensed band and apparatus for supporting same method | |
EP4047848A1 (de) | Verfahren und vorrichtung zum übertragen oder empfangen eines drahtlossignals in einem drahtloskommunikationssystem | |
US20210320761A1 (en) | Method and apparatus for transmitting and receiving wireless signal in wireless communication system | |
EP4072233A1 (de) | Verfahren und vorrichtung für signalübertragung oder -empfang in einem drahtlosen kommunikationssystem | |
US11800560B2 (en) | Method for transmitting and receiving signal in wireless communication system supporting unlicensed band, and apparatus supporting same | |
EP4266810A1 (de) | Verfahren und vorrichtung zum senden und empfangen eines signals in einem drahtloskommunikationssystem | |
US20220046609A1 (en) | Method for transmitting and receiving signals in wireless communication system and apparatus for supporting same | |
EP4210420B1 (de) | Verfahren zur durchführung einer kanalzugriffsprozedur auf einem gemeinsam genutzten spektrum, computerlesbares medium, benutzergerät, verfahren zum empfang eines signals auf einem gemeinsam genutzten spektrum und basisstation | |
EP4236155A1 (de) | Verfahren und vorrichtung zum senden und empfangen eines signals in einem drahtloskommunikationssystem |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20230120 |
|
AC | Divisional application: reference to earlier application |
Ref document number: 3817494 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 1/00 20060101ALI20231221BHEP Ipc: H04L 1/1607 20230101ALI20231221BHEP Ipc: H04L 1/1822 20230101ALI20231221BHEP Ipc: H04L 1/1867 20230101ALI20231221BHEP Ipc: H04L 1/1829 20230101ALI20231221BHEP Ipc: H04L 1/12 20060101ALI20231221BHEP Ipc: H04L 1/16 20230101ALI20231221BHEP Ipc: H04W 72/04 20230101ALI20231221BHEP Ipc: H04L 5/00 20060101ALI20231221BHEP Ipc: H04L 1/18 20230101ALI20231221BHEP Ipc: H04W 74/08 20090101ALI20231221BHEP Ipc: H04W 72/12 20230101AFI20231221BHEP |
|
INTG | Intention to grant announced |
Effective date: 20240115 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AC | Divisional application: reference to earlier application |
Ref document number: 3817494 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602019053799 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |