HARQ-ACK information disabling in a communication system

Abstract

The disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system and a Internet of Things (IoT) technology beyond a 4th-Generation (4G) system supporting a higher data rate. The disclosure can be applied to intelligent services based on 5G communication technologies and IoT-related technologies, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. The disclosure relates to a method and apparatus for disabling Hybrid Automatic Repeat reQuest-ACKnowledgement (HARQ-ACK) information in a communication system.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to disabling hybrid automatic repeat request-acknowledgement (HARQ-ACK) messages in communication systems. Background Technology

[0002] To meet the increased demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as 'beyond 4G networks' or 'post-LTE systems'. 5G communication systems are considered to be implemented in higher frequency (millimeter wave (mmWave)) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies have been discussed in 5G communication systems. Furthermore, in 5G communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The internet, a human-centric network of connections where humans generate and consume information, is now evolving into the Internet of Things (IoT), where distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), combining IoT technology with big data processing, has emerged through connectivity to cloud servers. Recent research has focused on sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC), as technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology are required for IoT implementation. Such an IoT environment can provide intelligent internet technology services, creating new value for human life by collecting and analyzing data generated between connected objects. Through the convergence and integration of existing information technology (IT) and various industrial applications, IoT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Correspondingly, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented using beamforming, MIMO, and array antennas. Cloud radio access networks (RAN), as an application of the aforementioned big data processing technologies, can also be considered an example of the convergence between 5G and IoT technologies.

[0005] Fifth-generation (5G), or new radio (NR) mobile communications, is gaining increasing momentum recently amid global technological activity surrounding a wide range of candidate technologies from industry and academia. Candidate enablers for 5G / NR mobile communications include massive MIMO technologies that provide beamforming gain and support increased capacity, ranging from traditional cellular bands to higher frequencies; new waveforms that flexibly adapt to various services / applications with different needs (e.g., new radio access technologies (RATs)); and new multiple access schemes that support massive connectivity. Summary of the Invention

[0006] Technical issues

[0007] Non-terrestrial networks (NTNs) refer to networks or network segments that use airborne or space-based vehicles to carry transmission equipment, relay nodes, or base stations. Compared to traditional terrestrial networks, NTNs can provide ubiquitous coverage and are less susceptible to disasters. There is growing interest in supporting NTNs in Narrowband Internet of Things (NB-IoT), enhanced machine-type communications (eMTC), LTE, and 5G systems.

[0008] Due to the long distance between satellites and users, the propagation delay in NTN is much greater than in traditional terrestrial networks. In NR systems, there are up to 16 HARQ processes. Because of the long HARQ round-trip time in NTN, HARQ stalling will occur if enhanced support for regular HARQ operations is not provided. This enhancement is based on disabling HARQ-ACK feedback for each HARQ process using UE-specific RRC signaling.

[0009] Problem Solution

[0010] This disclosure relates to wireless communication systems, and more specifically, to the disabling of HARQ-ACK information in communication systems.

[0011] In one embodiment, a method for providing HARQ-ACK information is provided. The method includes receiving information about a set of HARQ processes without HARQ-ACK information and transport blocks (TBs). The TBs include a first number of TBs not associated with HARQ processes in the set of HARQ processes and a second number of TBs associated with HARQ processes in the set of HARQ processes. The method also includes determining a HARQ-ACK information codebook for the TBs and, based on the first number of TBs but not the second number of TBs, a power for transmitting the Physical Uplink Control Channel (PUCCH) with the HARQ-ACK information codebook. The method further includes transmitting the PUCCH using this power.

[0012] In another embodiment, a user equipment (UE) is provided. The UE includes a transceiver configured to receive information about a set of HARQ processes without HARQ-ACK information and transport blocks (TBs). The TBs include a first number of TBs not associated with HARQ processes in the set of HARQ processes and a second number of TBs associated with HARQ processes in the set of HARQ processes. The UE also includes a processor operatively connected to the transceiver. The processor is configured to determine a HARQ-ACK information codebook for the TBs and a power for transmitting a PUCCH with the HARQ-ACK information codebook based on the first number of TBs but not the second number of TBs. The transceiver is also configured to use this power to transmit the PUCCH.

[0013] In another embodiment, a base station is provided. The base station includes a transceiver configured to transmit information about a set of HARQ processes without HARQ-ACK information and a TB (Base Transaction). The TB includes a first number of TBs not associated with HARQ processes in the set of HARQ processes and a second number of TBs associated with HARQ processes in the set of HARQ processes. The transceiver is also configured to receive a HARQ-ACK information codebook for the TBs. The base station also includes a processor operatively connected to the transceiver. The processor is configured to determine HARQ-ACK information from the HARQ-ACK information codebook. When the HARQ-ACK information codebook is type-1, the HARQ-ACK information is used only for TBs from the first number of TBs. When the HARQ-ACK information codebook is type-2, the HARQ-ACK information is used for TBs from both the first and second number of TBs.

[0014] Other technical features will be apparent to those skilled in the art from the following figures, description and claims.

[0015] Beneficial effects of the invention

[0016] This disclosure provides various embodiments associated with disabling HARQ-ACK information reporting for HARQ processes corresponding to PDSCH reception scheduled via DCI format in PDCCH reception or for semi-persistent scheduling (SPS) PDSCH, based on configuration via RRC signaling and possible additional activation / deactivation via DCI format. In the following, for brevity, HARQ-ACK information in response to PDSCH reception is considered, but HARQ-ACK information may also be provided for detecting DCI format, such as detecting a DCI format indicating SPS PDSCH release or a DCI format indicating SCell sleep, without scheduling PDSCH. Furthermore, this disclosure considers enhancements to HARQ-ACK codebook construction and DCI format design when HARQ-ACK information reporting for HARQ processes can be enabled or disabled. Attached Figure Description

[0017] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein like reference numerals denote like parts:

[0018] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0019] Figure 2 An example gNB according to an embodiment of the present disclosure is shown.

[0020] Figure 3An example UE according to an embodiment of the present disclosure is shown;

[0021] Figure 4 and Figure 5 An example wireless transmission and reception path according to this disclosure is shown;

[0022] Figure 6 A flowchart is shown for a method for disabling HARQ-ACK information reporting and corresponding DCI format indication according to an embodiment of the present disclosure;

[0023] Figure 7 Another flowchart of a method for configuring HARQ-ACK information for a corresponding HARQ process, according to an embodiment of the present disclosure, is shown.

[0024] Figure 8 A flowchart is shown illustrating a method for configuring and transmitting a Type-1 HARQ-ACK codebook according to an embodiment of this disclosure;

[0025] Figure 9A An exemplary type-1 HARQ-ACK codebook according to embodiments of this disclosure is shown; and

[0026] Figure 9B Another type-1 HARQ-ACK codebook according to an embodiment of this disclosure is shown. Detailed Implementation

[0027] Before proceeding with the detailed description below, it may be advantageous to clarify the definitions of certain words and phrases used throughout this disclosure. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are physically in contact with each other. The terms “send,” “receive,” and “communicate,” and their derivatives include both direct and indirect communication. The terms “include” and “contain,” and their derivatives mean, but are not limited to, including. The term “or” is inclusive, meaning “and / or.” The phrase “associated with” and its derivatives mean to include, contain, interconnect, contain, enclose, connected to or linked with, coupled to or coupled with, communicate with, cooperate with, interweave with, juxtapose with, proximate with, bind to or bind with, possess, have its attributes, associate with or be associated with, or similar meanings. The term “controller” refers to any device, system, or part thereof that controls at least one operation. Such controllers may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, either locally or remotely. When used with a series of items, the phrase “at least one of…” means that different combinations of one or more of the listed items may be used, and that only one of the listed items may be required. For example, “at least one of A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0028] Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed by computer-readable program code and implemented in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, programs, functions, objects, classes, instances, associated data, or portions thereof implemented in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data and media that can store data and later overwrite said data, such as rewritable optical discs or erasable storage devices.

[0029] This patent document provides definitions for certain other words and phrases. It will be understood by one of ordinary skill in the art that, in many cases, if not most, these definitions apply to the prior and future use of the defined words and phrases.

[0030] The following discussion Figures 1 to 9B The various embodiments used to describe the principles of this disclosure in this patent document are merely exemplary and should not be construed in any way as limiting the scope of this disclosure. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0031] The following documents are incorporated herein by reference as if fully set forth herein: 3GPP, TR 38.811 v15.3.0, “Study on NR Supporting Non-Terrestrial Networks”; 3GPP, TR 38.821 v16.6.0, “Scheme for NR Supporting Non-Terrestrial Networks (NTNs)”; 3GPP TS 38.212 v16.3.0, “NR; Multiplexing and Channel Coding”; 3GPP TS 38.213 v16.3.0, “NR; Physical Layer Procedures for Control”; 3GPP TS 38.214 v16.3.0, “NR; Physical Layer Procedures for Data”; 3GPP TS 38.321 v16.2.0, “NR; Medium Access Control (MAC) Protocol Specification”; and 3GPP TS 38.331 v16.2.0, “NR; Radio Resource Control (RRC) Protocol Specification”.

[0032] The following Figure 1-3 Various embodiments of communication technologies, such as orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), are described in wireless communication systems. Figure 1-3 The description does not imply any physical or architectural limitation on the ways in which different embodiments may be implemented. Different embodiments of this disclosure can be implemented in any suitably arranged communication system.

[0033] Figure 1 An example wireless network according to an embodiment of this disclosure is shown. Figure 1 The embodiments of the wireless network shown are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0034] like Figure 1 As shown, the wireless network includes gNB 101 (e.g., a base station, BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0035] gNB 102 provides wireless broadband access to network 130 to a first plurality of user equipments (UEs) within its coverage area 120. The first plurality of UEs includes UE 111, which may be located in a small business; UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M), such as a cellular phone, wireless laptop computer, wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 to a second plurality of UEs within its coverage area 125. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, LTE, LTE-A, WiMAX, WiFi or other wireless communication technologies.

[0036] Depending on the network type, the term "gNB" can refer to any component (or set of components) configured to provide wireless access to a network to a remote terminal, such as a base transceiver station, radio base station, transmitting point (TP), transmitting-receiving point (TRP), terrestrial gateway, airborne gNB, satellite system, mobile base station, macro cell, femtocell, WiFi access point (AP), etc. Furthermore, depending on the network type, other well-known terms such as "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," or "user equipment" may be used, in addition to "user equipment" or "UE." For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to a device that wirelessly accesses a gNB. A UE can be a mobile device or a fixed device. For example, a UE can be a mobile phone, smartphone, monitoring equipment, alarm equipment, fleet management equipment, asset tracking equipment, automobile, desktop computer or entertainment device, infotainment device, vending machine, electricity meter, water meter, gas meter, safety device, sensor device, home appliance, etc.

[0037] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles, the coverage areas associated with the gNB (such as coverage areas 120 and 125) may have other shapes, including irregular shapes.

[0038] As described in more detail below, one or more of UEs 111-116 include circuitry, procedures, or combinations thereof for disabling HARQ-ACK information in a wireless communication system. In some embodiments, one or more of gNBs 101-103 include circuitry, procedures, or combinations thereof for disabling HARQ-ACK information in a wireless communication system.

[0039] although Figure 1 An example of a wireless network is shown, but more can be found on... Figure 1 Various modifications can be made. For example, the wireless network can include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 can communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide the UEs with direct wireless broadband access to network 130. Additionally, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0040] Figure 2 An example gNB 102 according to an embodiment of the present disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustrative purposes only. Figure 1 gNBs 101 and 103 can have the same or similar configurations. However, gNBs come in a wide variety of configurations, and Figure 2 This disclosure is not intended to be limited to any particular implementation of gNB.

[0041] like Figure 2 As shown, gNB 102 includes multiple antennas 205a-205n, multiple RF transceivers 210a-210n, transmit (TX) processing circuitry 215, and receive (RX) processing circuitry 220. gNB 102 also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0042] RF transceivers 210a-210n receive input RF signals, such as signals transmitted by a UE in network 100, from antennas 205a-205n. RF transceivers 210a-210n down-convert the input RF signals to generate an IF or baseband signal. The IF or baseband signal is sent to RX processing circuitry 220, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 220 sends the processed baseband signal to controller / processor 225 for further processing.

[0043] The TX processing circuit 215 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from the controller / processor 225. The TX processing circuit 215 encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband or IF signal. RF transceivers 210a-210n receive the processed baseband or IF signal from the TX processing circuit 215 and up-convert the baseband or IF signal into an RF signal, which is then transmitted via antennas 205a-205n.

[0044] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the reception of forward channel signals and the transmission of reverse channel signals via RF transceivers 210a-210n, RX processing circuitry 220, and TX processing circuitry 215, based on well-known principles. The controller / processor 225 may also support additional functions, such as more advanced wireless communication capabilities. For example, the controller / processor 225 may support beamforming or directional routing operations, wherein the output signals from multiple antennas 205a-205n / input signals arriving at multiple antennas 205a-205n are weighted differently to effectively direct the output signals in a desired direction. The controller / processor 225 may support any of a variety of other functions in the gNB 102.

[0045] The controller / processor 225 is also capable of executing programs and other processes, such as an operating system, residing in the memory 230. The controller / processor 225 can move data into or out of the memory 230 as needed during execution.

[0046] The controller / processor 225 is also coupled to the backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or network. Interface 235 can support communication via any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G / NR, LTE, or LTE-A), interface 235 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, interface 235 can allow the gNB 102 to communicate with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. Interface 235 includes any suitable architecture supporting communication over wired or wireless connections, such as Ethernet or RF transceivers.

[0047] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, while another portion of memory 230 may include flash memory or other ROM.

[0048] although Figure 2 An example of gNB 102 is shown, but it is possible to compare it with other models. Figure 2 Various changes can be made. For example, gNB 102 can include... Figure 2 Each component can be any number shown. As a particular example, an access point may include multiple interfaces 235, and the controller / processor 225 may support HARQ-ACK information disabling in a wireless communication system. As another particular example, although shown as a single instance including TX processing circuitry 215 and a single instance including RX processing circuitry 220, gNB 102 may include multiple instances of each (e.g., one per RF transceiver). Furthermore, Figure 2 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0049] Figure 3 An example UE 116 according to an embodiment of the present disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3 This disclosure is not intended to limit the scope to any particular implementation of the UE.

[0050] like Figure 3 As shown, UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a TX processing circuit 315, a microphone 320, and a receive (RX) processing circuit 325. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, a touchscreen 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0051] RF transceiver 310 receives an input RF signal transmitted by a gNB of network 100 from antenna 305. RF transceiver 310 down-converts the input RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 325 sends the processed baseband signal to speaker 330 (e.g., for voice data) or processor 340 for further processing (e.g., for web browsing data).

[0052] The TX processing circuit 315 receives analog or digital voice data from the microphone 320, or other output baseband data (such as web data, email, or interactive video game data) from the processor 340. The TX processing circuit 315 encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband or IF signal. The RF transceiver 310 receives the processed baseband or IF signal from the TX processing circuit 315 and up-converts the baseband or IF signal into an RF signal, which is then transmitted via the antenna 305.

[0053] Processor 340 may include one or more processors or other processing devices and execute OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor 340 may control the reception of forward channel signals and the transmission of reverse channel signals through RF transceiver 310, RX processing circuitry 325 and TX processing circuitry 315 according to well-known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.

[0054] Processor 340 is also capable of executing other processes and programs residing in memory 360, such as a process for disabling HARQ-ACK information in a wireless communication system. Processor 340 can move data into or out of memory 360 as needed for the execution of the process. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from a gNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0055] The processor 340 is also coupled to the touchscreen 350 and the display 355. The operator of the UE 116 can use the touchscreen 350 to input data into the UE 116. The display 355 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text and / or at least limited graphics (such as from a website).

[0056] The memory 360 is coupled to the processor 340. A portion of the memory 360 may include random access memory (RAM), while another portion of the memory 360 may include flash memory or other read-only memory (ROM).

[0057] although Figure 3 An example of UE 116 is shown, but it is possible to modify it. Figure 3 Make various changes. For example, Figure 3The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although... Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.

[0058] To meet the increased demand for wireless data traffic since the deployment of 4G communication systems and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are considered to be implemented in higher frequency (mmWave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (e.g., 6 GHz) to achieve robust coverage and mobility support. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G / NR communication systems.

[0059] In addition, in 5G / NR communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation.

[0060] The discussion of 5G systems and their associated frequency bands is for reference only, as some embodiments of this disclosure can be implemented in 5G systems. However, this disclosure is not limited to 5G systems or their associated frequency bands, and embodiments of this disclosure can be used in conjunction with any frequency band. For example, aspects of this disclosure can also be applied to 5G communication systems, 6G, or even higher deployments that can use terahertz (THz) bands.

[0061] A communication system includes a downlink (DL) and an uplink (UL). The downlink refers to the transmission from the base station or one or more transmitting points to the UE, while the uplink refers to the transmission from the UE to the base station or one or more receiving points.

[0062] The time unit used for DL ​​or UL signaling on a cell is called a time slot, and it may include one or more symbols. Symbols can also be used as additional time units. The frequency (or bandwidth (BW)) unit is called a resource block (RB). An RB includes multiple subcarriers (SCs). For example, a time slot may have a duration of 0.5 milliseconds or 1 millisecond, include 14 symbols, and an RB may include 12 SCs with an inter-SC spacing of 15 kHz or 30 kHz, etc.

[0063] DL signals include data signals that transmit information content, control signals that transmit DL control information (DCI), and reference signals (RS), also known as pilot signals. The gNB transmits data information or DCI via the corresponding Physical DL Shared Channel (PDSCH) or Physical DL Control Channel (PDCCH). PDSCH or PDCCH can be transmitted on a variable number of time slot symbols, each consisting of one time slot symbol. For simplicity, the DCI format used to schedule UE PDSCH reception is referred to as the DL DCI format, and the DCI format used to schedule transmission from the UE's Physical Uplink Shared Channel (PUSCH) is referred to as the ULDCI format.

[0064] The gNB transmits one or more of various RSs, including Channel State Information RS (CSI-RS) and Demodulation RS (DMRS). CSI-RS is primarily used by the UE to perform measurements and provide CSI to the gNB. For channel measurements, the Non-Zero Power CSI-RS (NZPCSI-RS) resource is used. For Interference Measurement Reporting (IMR), the CSI Interference Measurement (CSI-IM) resource associated with the Zero Power CSI-RS (ZP CSI-RS) configuration is used. The CSI process includes both NZP CSI-RS and CSI-IM resources.

[0065] The UE can determine CSI-RS transmission parameters via DL control signaling or higher-level signaling (such as Radio Resource Control (RRC) signaling) from the gNB. The transmission instance of CSI-RS can be indicated by DL control signaling or configured by higher-level signaling. DM-RS is transmitted only in the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.

[0066] Figure 4 and Figure 5Example wireless transmit and receive paths according to this disclosure are illustrated. In the following description, transmit path 400 may be described as being implemented in a gNB (e.g., gNB 102), while receive path 500 may be described as being implemented in a UE (e.g., UE 116). However, it will be understood that receive path 500 may be implemented in a gNB, and transmit path 400 may be implemented in a UE. In some embodiments, receive path 500 is configured to support codebook designs and structures for systems with 2D antenna arrays, as described in embodiments of this disclosure.

[0067] like Figure 4 The transmission path 400 shown includes a channel coding and modulation block 405, a serial-to-parallel (SP) block 410, an N-size inverse fast Fourier transform (IFFT) block 415, a parallel-to-serial (PS) block 420, a cyclic prefix addition block 425, and an up-converter (UC) 430. For example... Figure 5 The receiver path 500 shown includes a downconverter (DC) 555, a cyclic prefix removal block 560, a serial-to-parallel (S-to-P) block 565, a fast Fourier transform (FFT) block of size N, a parallel-to-serial (P-to-S) block 575, and a channel decoding and demodulation block 580.

[0068] like Figure 4 As shown, the channel coding and modulation block 405 receives a set of information bits, applies coding (such as low-density parity-check (LDPC) coding), and modulates the input bits (such as using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a frequency domain modulation symbol sequence.

[0069] Serial-to-parallel block 410 converts (e.g., demultiplexes) serial modulated symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in gNB 102 and UE 116. IFFT block 415 of size N performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial block 420 converts (e.g., multiplexes) the parallel time-domain output symbols from IFFT block 415 of size N to generate a serial time-domain signal. Cyclic prefix addition block 425 inserts a cyclic prefix into the time-domain signal. Upconverter 430 modulates (e.g., upconverts) the output of cyclic prefix addition block 425 to an RF frequency for transmission via a wireless channel. The signal may also be filtered in baseband before conversion to the RF frequency.

[0070] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and UE 116 performs the opposite operation to that at gNB 102.

[0071] like Figure 5As shown, downconverter 555 downconverts the received signal to the baseband frequency, and cyclic prefix removal block 560 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 565 converts the time-domain baseband signal into a parallel time-domain signal. FFT block 570 of size N executes the FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial block 575 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 580 demodulates and decodes the modulated symbols to recover the original input data stream.

[0072] Each gNB in ​​gNBs 101-103 can achieve the following: Figure 4 The transmission path 400 shown is similar to transmission to UEs 111-116 in the downlink, and can achieve the following: Figure 5 The received path 500 shown is similar to receiving from UEs 111-116 in the uplink. Similarly, each UE in UEs 111-116 can implement a transmitted path 400 for transmitting to gNBs 101-103 in the uplink, and can implement a received path 500 for receiving from gNBs 101-103 in the downlink.

[0073] Figure 4 and Figure 5 Each component in the system can be implemented using only hardware or a combination of hardware and software / firmware. As a specific example, Figure 4 and Figure 5 At least some components can be implemented in software, while others can be implemented in configurable hardware or a hybrid of software and configurable hardware. For example, FFT block 570 and IFFT block 515 can be implemented as configurable software algorithms, where the value of size N can be modified according to the implementation.

[0074] Furthermore, although described as using FFT and IFFT, this is merely exemplary and should not be construed as limiting the scope of this disclosure. Other types of transforms, such as the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It will be understood that for the DFT and IDFT functions, the value of the variable N can be any integer (such as 1, 2, 3, 4, etc.), while for the FFT and IFFT functions, the value of the variable N can be any integer that is a power of 2 (such as 1, 2, 4, 8, 16, etc.).

[0075] although Figure 4 and Figure 5 An example of a wireless transmit and receive path is shown, but it is possible to modify it further. Figure 4 and Figure 5 Make various changes. For example, Figure 4 and Figure 5The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. Furthermore, Figure 4 and Figure 5 This example aims to illustrate the types of send and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0076] The UL signal also includes data signals for transmitting information content, control signals for transmitting UL control information (UCI), DMRS associated with data or UCI demodulation, probe RS (SRS) enabling the gNB to perform UL channel measurements, and a random access (RA) preamble enabling the UE to perform random access. The UE transmits data information or UCI via the corresponding PUSCH or PUCCH. The PUSCH or PUCCH can be transmitted on a variable number of time slot symbols, each including one time slot symbol. When the UE transmits both data information and UCI simultaneously, it can multiplex both in the PUSCH, or, depending on the UE's capabilities, at least when transmitting on different cells, it can transmit a PUSCH with data information and a PUCCH with UCI.

[0077] UCI includes HARQ-ACK information indicating correct or incorrect detection of data transfer blocks (TBs) or code block groups (CBGs) in the PDSCH, a scheduling request (SR) indicating whether the UE has data to transmit in the buffer, and a CSI report enabling the gNB to select appropriate parameters for PDSCH or PDCCH transmission to the UE. The CSI report may include: a Channel Quality Indicator (CQI) informing the gNB of the maximum modulation and coding scheme (MCS) used by the UE to detect data TBs at a predetermined block error rate (BLER) (such as 10% BLER); a Precoding Matrix Indicator (PMI) informing the gNB how to combine signals from multiple transmitter antennas according to MIMO transmission principles; a CSI-RS Resource Indicator (CRI) for obtaining the CSI report; and a Rank Indicator (RI) indicating the transmission rank of the PDSCH. UL RS includes DMRS and SRS. DMRS is typically transmitted within the BW of the corresponding PUSCH or PUCCH. The gNB can use DMRS to demodulate information in the corresponding PUSCH or PUCCH. The SRS is sent by the UE to provide the UL CSI to the gNB, and for TDD systems, it also provides the PMI for DL ​​transmission. Additionally, the UE may send the Physical Random Access Channel (PRACH) as part of the random access procedure or for other purposes.

[0078] DL and UL transmissions can be based on OFDM waveforms, which include variants using DFT precoding, known as DFT extended OFDM.

[0079] Non-terrestrial networks (NTNs) refer to networks or network segments that use airborne or space-based vehicles to carry transmission equipment, relay nodes, or base stations. Compared to traditional terrestrial networks, NTNs can provide ubiquitous coverage and are less susceptible to disasters. There is growing interest in supporting NTNs in Narrowband Internet of Things (NB-IoT), enhanced machine-type communications (eMTC), LTE, and 5G systems.

[0080] Due to the long distance between satellites and users, the propagation delay in NTN is much greater than in traditional terrestrial networks. In NR systems, there are up to 16 HARQ processes. Because of the long HARQ round-trip time in NTN, HARQ stalling will occur if enhanced support for regular HARQ operations is not provided. This enhancement is based on disabling HARQ-ACK feedback for each HARQ process using UE-specific RRC signaling.

[0081] This disclosure provides various embodiments associated with disabling HARQ-ACK information reporting for HARQ processes corresponding to PDSCH reception scheduled via DCI format in PDCCH reception or for semi-persistent scheduling (SPS) PDSCH, based on configuration via RRC signaling and possible additional activation / deactivation via DCI format. Hereinafter, for brevity, HARQ-ACK information in response to PDSCH reception is considered, but HARQ-ACK information may also be provided for detecting DCI format, such as detecting a DCI format indicating SPS PDSCH release or a DCI format indicating SCell sleep without scheduling PDSCH, as described in TS 38.213v16.3.0, “NR; Physical Layer Procedures for Control”. Furthermore, this disclosure considers enhancements to HARQ-ACK codebook construction and DCI format design when HARQ-ACK information reporting for HARQ processes can be enabled or disabled.

[0082] In the NR system, there are three types of codebooks: Type-1, Type-2, and Type-3 HARQ-ACK codebooks.

[0083] The size of the Type-1 HARQ-ACK codebook depends on the configured maximum and minimum HARQ timing, the configured number of component carriers (CCs) or cells, and other parameters as described in TS 38.213v16.3.0, “NR; Physical Layer Procedures for Control”. A Type-1 HARQ-ACK codebook considering all possible PDSCH receptions will include HARQ-ACK information for HARQ processes where HARQ-ACK information reporting is disabled, allowing the corresponding HARQ-ACK information to be multiplexed in the same PUCCH transmission. A significant drawback of the Type-1 HARQ-ACK codebook is its size. Since it includes HARQ-ACK information for all PDSCH receptions with corresponding HARQ-ACK information that can be provided in the same PUCCH, it is beneficial to avoid including unnecessary HARQ-ACK information. Therefore, when HARQ-ACK information reporting for a HARQ process is configured to be disabled, corresponding enhancements are needed to the Type-1 HARQ-ACK codebook determination.

[0084] The Type-2 HARQ-ACK codebook includes HARQ-ACK information only for UE identification as received by a scheduled or configured PDSCH, regardless of whether the UE actually receives the PDSCH. This function is enabled by the downlink assignment index (DAI) counter, and, where applicable, by the total DAI in the DCI format of the scheduled PDSCH reception, such as for operations with DL CA. When HARQ-ACK information reporting for a HARQ process is disabled, the UE can ignore the value of the DAI field in the DCI format, which has a HARQ process number (HPN) field indicating the HARQ process, and the Type-2 HARQ-ACK codebook can include only HARQ-ACK information for HARQ processes with HARQ-ACK information reporting enabled. The DAI value can only be changed / incremented when the TB in a subsequent corresponding PDSCH is associated with a HARQ process with HARQ-ACK information reporting enabled.

[0085] The Type-3 HARQ-ACK codebook, also known as the one-time codebook, can include HARQ-ACK information for all DL HARQ processes and all configured DL cells. The NDI can be configured as part of the information provided by the Type-3 HARQ-ACK codebook. The serving gNB can request the UE to provide the Type-3 HARQ-ACK codebook via DCI formats such as DCI format 1_1, as described in TS 38.212v16.3.0, “NR; Multiplexing and Channel Coding”, and TS 38.213v16.3.0, “NR; Physical Layer Procedures for Control”. When the DCI format is used to request the UE to provide the Type-3 HARQ-ACK codebook instead of scheduling PDSCH reception or PUSCH transmission, all bits of the Frequency Domain Resource Allocation (FDRA) field in the DCI format are set to 0 when the resource allocation type is Type-0, or set to 1 when the resource allocation type is Type-1, or set to 0 or 1 when the DCI format can indicate resource allocation type-0 or resource allocation type-1. Considering all DL HARQ processes and all configured DL cells, the Type-3 HARQ-ACK codebook will include HARQ-ACK information for HARQ processes where HARQ-ACK information reporting is disabled. It is beneficial to avoid including unnecessary HARQ-ACK information. Therefore, when HARQ-ACK information reporting for a HARQ process is configured to be disabled, an enhanced Type-3 HARQ-ACK codebook determination is required.

[0086] This disclosure relates to communication systems. For systems such as NTN, propagation delays are much greater than in traditional terrestrial networks due to the long distance between the satellite and the UE. In NR systems, the number of HARQ processes can be as high as 16. Due to the long HARQ round-trip time in NTN, HARQ stall will occur if enhanced support for regular HARQ operation is not provided. This enhancement is based on disabling HARQ-ACK feedback for each HARQ process using UE-specific RRC signaling.

[0087] This paper discloses techniques, apparatuses, and methods for configuring and enhancing HARQ-ACK message disabling. Specifically, it discloses detailed configuration methods for disabling HARQ-ACK messages, as well as enhancements for HARQ-ACK codebooks and DCI design, applicable to scenarios where HARQ-ACK messages are disabled. The disclosed techniques, apparatuses, and methods can be applied not only to NTN systems but also to any other wireless communication system.

[0088] The embodiments of this disclosure are generally applicable to any communication system that uses HARQ-ACK information reporting to receive TBs associated with a HARQ process when HARQ-ACK information reporting can be enabled or disabled. The examples given for NTN systems should be considered in an inclusive manner, without excluding other wireless communication systems.

[0089] Figure 6 A flowchart of a method 600 for disabling HARQ-ACK information reporting and corresponding DCI format indication according to an embodiment of the present disclosure is shown. For example, method 600 can be provided by a base station (such as...) Figure 1 Implemented in gNB 102). Figure 6 The embodiments of method 600 shown are for illustrative purposes only. Figure 6 The one or more components shown may be implemented in a dedicated circuit configured to perform the function, or the one or more components may be implemented by one or more processors that execute instructions to perform the function.

[0090] Method 600 includes operations for configuring and indicating DL transmissions, wherein HARQ-ACK feedback can be enabled or disabled. In operation 602, the gNB generates and provides the UE with configuration information for enabling or disabling HARQ-ACK information for one or more HARQ processes. Furthermore, this information can be cell-specific and provided, for example, via a system information block, or UE-specific and provided, for example, via UE-specific RRC signaling or via an indication in the DCI format of a scheduled PDSCH reception, which includes a TB associated with the HARQ process.

[0091] The configuration method is discussed in the "Configuration for Disabling HARQ-ACK Feedback" section below. In operation 604, the gNB generates a DCI format and multiplexes it in the PDCCH transmission, wherein the DCI format schedules PDSCH reception, and wherein one or more fields in the DCI format can be configured to be 0 bits in size or larger than 0 bits, depending on whether HARQ-ACK information for the HARQ process is disabled or enabled, as further discussed later in the "Enhancements to DCI Design" section. The DCI format schedules PDSCH reception and includes information indicating whether HARQ-ACK information reporting for the decoding result of the TB associated with the HARQ process indicated by the DCI format is enabled or disabled. In operation 606, the gNB transmits the PDSCH scheduled by the DCI format. In operation 608, the gNB receives a PUSCH or PUCCH providing the HARQ-ACK codebook. The HARQ-ACK information provided by the HARQ-ACK codebook depends on whether the HARQ-ACK information is enabled or disabled for the HARQ process associated with the corresponding TB, as described later in the section “Enhancements to the HARQ-ACK Codebook”.

[0092] Figure 7 Another flowchart of a method 700 for configuring HARQ-ACK information for a corresponding HARQ process, according to an embodiment of the present disclosure, is shown. For example, method 700 may be configured by, for example... Figure 1 The UE implementation of UE 116 in the document. Figure 7 The embodiments of method 700 shown are for illustrative purposes only. Figure 7 The one or more components shown may be implemented in a dedicated circuit configured to perform the function, or the one or more components may be implemented by one or more processors that execute instructions to perform the function.

[0093] Method 700 includes operations for configuring and indicating whether HARQ-ACK information for a corresponding HARQ process is enabled or disabled. In operation 702, the UE receives configuration information including an indication to enable or disable HARQ-ACK information for one or more HARQ processes. Furthermore, this indication can be cell-specific or UE-specific, as described later in the section “Configuration for HARQ-ACK Feedback Disabling.” In operation 704, the UE receives a DCI format for scheduling PDSCH reception, wherein one or more fields in the DCI format have a size of 0 bits when HARQ-ACK information in response to the decoding result of the TB of the corresponding HARQ process indicated by the DCI format is disabled; otherwise, one or more fields have a size greater than 0 bits, as described later in the section “Enhancements to DCI Design.” In operation 706, the UE receives PDSCH based on the configuration and scheduling information via the DCI format. In operation 708, the UE transmits a PUCCH or PUSCH with a HARQ-ACK codebook. As described later in the section “Enhancing the HARQ-ACK Codebook”, the content of the HARQ-ACK codebook depends on the HARQ process for the corresponding TB and whether HARQ-ACK information is enabled or disabled.

[0094] In one embodiment, UE-specific RRC signaling, such as IEPDSCH-ServingCellConfig or IE PDSCH-Config in IE BWP-DownlinkDedicated, may include parameters indicating whether HARQ-ACK information can be disabled. Configuration information can be provided by UE-specific RRC signaling and can be common across all configured DL / UL BWPs, or it can be BWP-specific, for example, when different BWPs use different subcarrier spacing (SCS) configurations.

[0095] Furthermore, this configuration can be cell-specific, for example, when a PUCCH with HARQ-ACK information can be transmitted in more than one cell, and one cell uses TDD (disabling it may be applicable to avoid HARQ stall) while another cell uses FDD (disabling it may not be applicable). The configuration information can be indicated via a bitmap (such as a bitmap of length N) with a one-to-one mapping to the configured HARQ processes, where, for example, a bit value of 0 indicates that HARQ-ACK information is enabled, and a bit value of 1 indicates that HARQ-ACK information is disabled (and vice versa), and N is the number of configured HARQ processes, such as N=16 or N=32.

[0096] Alternatively, multiple HARQ processes with disabled (or enabled) HARQ-ACK information can be sequential and can be configured via start and end indices and / or the number of HARQ processes with disabled HARQ-ACK information. For example, HARQ processes with IDs from N1 to N2 are configured with disabled HARQ-ACK information, where this indication can be via N1 as the starting HARQ process ID and N2 as the ending HARQ process ID, or N1 as the starting HARQ process ID and (N2-N1+1) as the number of HARQ processes with disabled HARQ-ACK information. Table 1 shows the PDSCH configuration.

[0097] Table 1. PDSCH Configuration

[0098]

[0099] Table 2 shows the PDSCH configuration for disabling HARQ.

[0100] Table 2. Modifications to IE PDSCH-ServingCellConfig for disabling HARQ-ACK information

[0101]

[0102] In one embodiment, the above configuration method can be applied to PDSCH reception scheduled via DCI format. For SPS PDSCH reception, in the first method, disabling HARQ-ACK information is not supported. In the second method, disabling HARQ-ACK information can be configured, for example, in the corresponding SPS PDSCH configuration's IE SPS-Config. In the third method, disabling HARQ-ACK information can be indicated in the DCI format that activates SPS PDSCH reception. For SPS PDSCH, the following methods for disabling HARQ-ACK can be considered.

[0103] In one example (Method 1), the HARQ-ACK message disables the application of all SPS PDSCHHARQ processes.

[0104] In one example (Method 2), HARQ-ACK information for one or more HARQ processes used for SPS PDSCH reception can be disabled, while HARQ-ACK information for the remaining HARQ processes can be enabled. For example, when the corresponding HARQ process ID is configured with disabled HARQ-ACK information, the same HARQ disable configuration for the scheduled PDSCH also applies to the SPSPDSCH. In a variation of Method 2, as part of the SPS PDSCH configuration, such as in IE SPS-Config, the HARQ processes with disabled HARQ-ACK information for the SPSPDSCH can be indicated via a bitmap or via the start HARQ process ID and end HARQ process ID / number of disabled HARQ processes.

[0105] In one example (Method 3), HARQ information for the SPS PDSCH can be disabled for each SPS configuration or a subset of the HARQ processes in each SPS configuration. The subset of HARQ processes to be disabled can be predefined, or it can be M HARQ processes with larger IDs from all HARQ processes, where parameters M and N can be predefined or configured by a higher layer via UE-specific RRC signaling, for example, as part of the SPS configuration.

[0106] Figure 8 A flowchart of a method 800 for configuring and transmitting a Type-1 HARQ-ACK codebook according to an embodiment of this disclosure is shown. For example, method 800 may be provided by, for example... Figure 1 The UE implementation of UE 116 in the document. Figure 8 The embodiments of method 800 shown are for illustrative purposes only. Figure 8 The one or more components shown may be implemented in a dedicated circuit configured to perform the function, or the one or more components may be implemented by one or more processors that execute instructions to perform the function.

[0107] In one embodiment, the maximum codebook size can be configured for a type-1 HARQ-ACK codebook.

[0108] like Figure 8As shown, in operation 802, the UE receives configuration information for enabling or disabling HARQ-ACK information for one or more HARQ processes, as well as configuration information for a Type-1 HARQ-ACK codebook. The configuration of the Type-1 HARQ-ACK codebook may include the codebook size and / or the time slot set configuration, in which the UE can generate HARQ-ACK information in the HARQ-ACK codebook for a potential corresponding PDSCH reception within the time slot. The configuration information may be indicated by cell-specific RRC signaling (such as by MIB, SIB1, or other SIBs) or by UE-specific RRC signaling, such as a portion of PUCCH-config and / or PUSCH-config.

[0109] In operation 804, the UE receives the DCI format of the scheduled PDSCH reception, wherein when HARQ-ACK information in response to the decoding result of the TBS of the corresponding HARQ process indicated by the DCI format is disabled, one or more fields in the DCI format associated with the HARQ-ACK report have a size of 0 bits; otherwise, one or more fields have a size greater than 0 bits, as described later in the section "Enhancements to DCI Design". In operation 806, the UE receives the PDSCH based on configuration and scheduling information via the DCI format. In operation 808, the UE transmits a PUCCH or PUSCH with a HARQ-ACK codebook. The content of the HARQ-ACK codebook depends on whether HARQ-ACK information is enabled or disabled for the HARQ process of the corresponding TB. Specifically, the UE only includes HARQ-ACK information for possible PDSCH reception in the corresponding time slot (according to the configured TDRA table), the corresponding time slot being configured to be included in the codebook.

[0110] In one example (Method 1-1), M represents the maximum size of the Type-1 HARQ-ACK codebook obtained based on the configuration described in TS 38.213v16.3.0, "NR; Physical Layer Procedures for Control". Size K can be configured when one or more HARQ processes are configured with disabled HARQ-ACK information. The configuration of parameter K can be indicated by cell-specific signaling (e.g., MIB, SIB1, or other SIBs) or UE-specific RRC signaling, for example, as part of PUCCH-config and / or PUSCH-config. When the size of the Type-1 HARQ-ACK codebook determined based on the procedures in TS 38.213v16.3.0, "NR; Physical Layer Procedures for Control", exceeds K, the UE suspends further generation of HARQ-ACK information bits to be included in the Type-1 HARQ-ACK codebook. Furthermore, the time slot in which the UE generates HARQ-ACK information bits to be included in the Type-1 HARQ-ACK codebook can be predefined or configured by UE-specific or UE-common RRC signaling.

[0111] In one example (method 1-2), a bitmap of a type-1 HARQ-ACK codebook can be provided to the UE from a higher layer. This bitmap indicates the time slot in which the UE can receive HARQ-ACK information generated in the HARQ-ACK codebook for the corresponding PDSCH. The bitmap configuration can be indicated by cell-specific RRC signaling (such as by MIB, SIB1, or other SIBs) or by UE-specific RRC signaling, such as a portion of PUCCH-config and / or PUSCH-config.

[0112] For example, the length of the bitmap can be equal to the maximum number of time slots the UE can generate for the Type-1 HARQ-ACK codebook, where the maximum number of time slots can be determined based on the set of time slot timing values ​​used for HARQ-ACK information reporting and the configured TDDUL / DL configuration. For example, a bit value "0" in the bitmap can indicate that HARQ-ACK information for possible PDSCH reception in the corresponding time slot (according to the configured TDRA table) is included in the HARQ-ACK information, while a bit value "1" indicates that such corresponding HARQ-ACK information is not included (and vice versa).

[0113] Figure 9A An exemplary type-1 HARQ-ACK codebook 900 according to an embodiment of this disclosure is shown. Figure 9A The example of Type-1 HARQ-ACK codebook 900 shown is for illustrative purposes only. Figure 9A In this context, the time-domain size of the type-1 HARQ-ACK codebook is configured to, for example, 3.

[0114] Figure 9B Another type-1 HARQ-ACK codebook 950 according to an embodiment of this disclosure is shown. Figure 9B The example of Type-1 HARQ-ACK codebook 950 shown is for illustrative purposes only. Figure 9B In the bitmap, the information is used to indicate which slot(s) will be included in the HARQ-ACK codebook.

[0115] Figure 9A and 9B The type-1 HARQ-ACK codebook enhancement is shown, where A / N corresponds to HARQ processes with HARQ-ACK information enabled, D corresponds to HARQ processes with HARQ-ACK information disabled, and N corresponds to a schedule without PDSCH. The shaded blocks are not included in the HARQ-ACK codebook.

[0116] For a Type-3 HARQ-ACK codebook (e.g., Method 1), for a HARQ process with disabled HARQ-ACK information, the UE can report HARQ-ACK information with a predetermined value (such as a NACK value), and the codebook size can remain independent of whether the HARQ process is enabled or disabled, and include HARQ-ACK information for all HARQ processes. Alternatively, in the second method, the HARQ-ACK information in the Type-3 HARQ-ACK codebook may include only the HARQ-ACK information of HARQ processes with enabled HARQ-ACK information, at least when the configuration of the HARQ process with enabled HARQ-ACK information is predetermined or via higher-layer signaling, i.e., at least when the enabling / disabling of HARQ-ACK information for the HARQ process is not based on the DCI format of the PDSCH reception for the HARQ process.

[0117] In one example (Method 3-1), the disabling of HARQ-ACK information for each HARQ process is configured by a higher layer. Based on the configuration of the higher layer (such as in a system information block or via UE-specific RRC signaling), the size of the Type-3 HARQ-ACK codebook is determined to be the same as the number of HARQ processes with enabled HARQ-ACK information.

[0118] In one example (method 3-2), the UE can be instructed to disable HARQ-ACK information for a HARQ process via a DCI format that schedules the corresponding PDSCH reception with a TB for the HARQ process. The HARQ-ACK information disabling indication via the DCI format can be applied only to HARQ processes for which HARQ-ACK information disabling has not been configured via RRC signaling. In one example, the DCI format that triggers the UE report type-3 HARQ-ACK codebook may include an indication of a HARQ process with HARQ-ACK information to be included in the HARQ-ACK codebook. For example, DCI format 1_1 can trigger the UE report type-3 HARQ-ACK codebook without scheduling PDSCH reception; then several fields in the DCI format, such as those for modulation and coding schemes, VRB-PRB mapping, new data indicator, redundancy version, and HARQ process number, provide no valid information.

[0119] Some or all of these fields may be used partially or entirely to indicate HARQ-ACK processes, which have HARQ-ACK information that will be included in the Type-3 HARQ-ACK codebook. In one example, a bitmap may be used when the number of configured HARQ processes is no greater than the number of bits available for the DCI format in a bitmap.

[0120] In another example, if there are N HARQ processes and the bitmap size is M < N, then the front of the bitmap... Each bit can indicate the value for the previous... The report of HARQ-ACK information for each HARQ process, and the bitmap after Each bit can indicate the target after Reporting of HARQ-ACK information for each HARQ process. For example, for the previous bitmap... Each of these bits can be used to indicate whether to disable or enable for each HARQ-ACK information for each HARQ-ACK process.

[0121] In yet another example, HARQ-ACK information is reported in the Type-3 HARQ-ACK codebook for a set of HARQ processes with consecutive IDs, where the start ID and end ID, or the number of HARQ processes, can be indicated by some fields in the DCI format that do not provide valid information.

[0122] In one example (Method 3-3), the DAI field for the Type-2 HARQ-ACK codebook can be used to determine the Type-3 HARQ-ACK codebook, where the counter DAI field indicates the number of scheduled PDSCH receptions with enabled HARQ-ACK information up to the time the UE receives the DCI format that triggers the Type-3 HARQ-ACK codebook report. When the total DAI field is present in the DCI format, the total DAI field indicates the total number of PDSCH receptions with enabled HARQ-ACK information across all carriers up to the time the DCI format that triggers the Type-3 HARQ-ACK codebook report is received. The DAI field in the DCI format that triggers the Type-3 HARQ-ACK codebook report can have the same value as in the final DCI format, which schedules the UE to report PDSCH receptions with corresponding HARQ-ACK information in the Type-3 HARQ-ACK codebook, where the final DCI format is determined as described in TS 38.213v16.3.0, “NR; Physical Layer Procedures for Control”.

[0123] If the UE is scheduled to receive PDSCH for a HARQ process with disabled HARQ-ACK information, and the HARQ-ACK information will be included in the HARQ-ACK codebook multiplexed in the PUCCH transmission, the following method can be used at least for the Type-1 HARQ-ACK codebook, or for the Type-3 HARQ-ACK codebook when the HARQ-ACK information for the HARQ process is disabled by indicating via DCI format.

[0124] In one example (Method 4), the UE can report a predetermined HARQ-ACK information value, such as NACK, for a HARQ process with disabled HARQ-ACK information in the HARQ-ACK codebook. This method has a HARQ-ACK codebook size of O. ACK (3≤O ACK ≤11) may be beneficial, and further with the codebook size O ACK (3≤O ACK The condition ≤11) is used because Reed-Mueller codes are subsequently used to encode HARQ-ACK information, and the decoder can improve the detection performance of the HARQ-ACK codebook when some HARQ-ACK information bits have known values. When O ACK When <3 and the HARQ-ACK information bits are used for a disabled HARQ process, the UE may not send a PUCCH with HARQ-ACK information.

[0125] In one example (Method 5), the UE can report HARQ-ACK information based on the reception results of the corresponding TB. This can help the gNB perform link adaptation, for example, by determining the ratio of NACK to ACK values ​​typically used for open-loop link adaptation. This method has a HARQ-ACK codebook size of O. ACK (O ACK >11) could be beneficial, and further increases the codebook size O ACK (O ACK The condition is >11), because the polar code is subsequently used to encode the HARQ-ACK information bits, and using predetermined values ​​for some HARQ-ACK information bits does not benefit the decoding reliability of the HARQ-ACK codebook. Method 5 can be applied regardless of the size of the HARQ-ACK codebook. Method 5 can also be applied when the HARQ-ACK information is jointly encoded with SR or CSI, at least when the total payload is greater than 11 bits.

[0126] When the value of the HARQ-ACK message for a HARQ process reporting a disabled HARQ-ACK message is set to a predetermined value (such as NACK), and for PUCCH transmissions using PUCCH format 2, PUCCH format 3, or PUCCH format 4, and for UCI bit numbers less than or equal to 11, such as in 38.213v16.3.0, "NR; Physical Layer Procedures for Control," the parameter Δ used to determine the PUCCH transmission power adjustment component on the active UL BWPb of carrier f of primary cell c is defined. TF，b，f，c (i) can be derived from Δ TF，b，f，c (i) = 10log 10 (K1·(n HARQ-ACK (i)+O SR (i)+O CSI (i)) / N RE (i)) calculate, where n HARQ-ACK (i) is the number of HARQ-ACK information bits determined by the UE as described in 38.213v16.3.0, “NR; Physical Layer Procedures for Control”, for example, excluding HARQ-ACK information bits corresponding to HARQ processes with disabled HARQ-ACK information from the HARQ-ACK codebook. In other words, the number of HARQ-ACK information bits used to determine the PUCCH transmit power only considers HARQ-ACK information corresponding to HARQ-ACK processes with enabled HARQ-ACK information, which the UE includes in the codebook.

[0127] For example, when O ACK +O SR +OCSI When ≤11, the number of HARQ-ACK information bits in the type-1 HARQ-ACK codebook can be obtained as follows:

[0128] Among them: (1) This refers to the number of transport blocks received by the UE during PDSCH reception time m in serving cell c (if harq-ACK-SpatialBundlingPUCCH and PDSCH-CodeBlockGroupTransmission are not provided), or the number of transport blocks received by the UE during PDSCH reception time M in serving cell c (if PDSCH-CodeBlockGroupTransmission is provided and PDSCH reception is scheduled via DCI format 1_0), or the number of PDSCHs received (if harq-ACK-SpatialBundlingPUCCH or SPS PDSCH is provided and released during PDSCH reception time m in serving cell c, and HARQ-ACK information is enabled for the HARQ process corresponding to these transport blocks, and the UE reports the corresponding HARQ-ACK information on the PUCCH); and (2) This refers to the number of CBGs received during PDSCH reception time m in serving cell c (if PDSCH-CodeBlockGroupTransmission is provided, PDSCH reception is scheduled via DCI format 1_1, HARQ-ACK information is enabled for the HARQ process corresponding to these CBGs, and the UE reports the corresponding HARQ-ACK information in the PUCCH). In the alternative formula, or It is the difference between the total number of TBs or CBGs that the UE provides HARQ-ACK information in the PUCCH and the number of TBs or CBGs corresponding to HARQ processes with disabled HARQ-ACK reports. For HARQ processes with disabled HARQ-ACK reports, the UE sets the corresponding HARQ-ACK bit to a predetermined value, such as the value corresponding to NACK.

[0129] When HARQ information for a HARQ process is disabled, the DCI format for PDSCH reception with a TB corresponding to the HARQ process has several fields associated with HARQ-ACK information reporting. These fields become invalid or have functions that can be omitted and can be omitted from the DCI format, such as the counter DAI (for type-2 codebook) field, the total DAI field when configured in the DCI format for HARQ-ACK information reporting, the TPC field for adjusting the power of PUCCH transmission with HARQ-ACK information, the PUCCH resource indicator field for PUCCH transmission, and / or the PDSCH-to-HARQ_feedback timing indicator field for PUCCH transmission timing.

[0130] In one embodiment, when the DCI format schedules PDSCH reception with a TB corresponding to a HARQ process having enabled HARQ-ACK information, one or more fields in the DCI format having a configurable number of bits, such as the Bandwidth Part (BWP) indicator field, the SRS request field, and the ZP CSI-RS trigger field, can have a size of 0 bits. However, when the DCI format schedules PDSCH reception with a TB corresponding to a HARQ process having disabled HARQ-ACK information, the BWP indicator field, the SRS request field, and / or the ZP CSI-RS trigger field can be configured to have a non-zero size.

[0131] Conversely, when the DCI format schedules PDSCH reception with a TB corresponding to a HARQ process that has disabled HARQ-ACK information, the DAI field (for the type-2 codebook) (when configured), the TPC field for determining PUCCH transmit power, the PUCCH resource indicator field, and / or the PDSCH-to-HARQ_feedback timing indicator field can have a size of 0 bits, and when the DCI format schedules PDSCH reception with a TB corresponding to a HARQ process that has enabled HARQ-ACK information, these fields can have a size greater than 0 bits. The motivation for this design is to maintain the same size of the DCI format regardless of whether the HARQ-ACK information is enabled or disabled for the corresponding HARQ process, while avoiding unnecessary increases in the DCI format size due to the inclusion of redundant bits.

[0132] In one embodiment, a new DCI format may be introduced to schedule PDSCH reception with a TB corresponding to a HARQ process having disabled HARQ-ACK information. The new DCI format may configure a portion or one or more of the DAI (for Type-2 codebook) field, TPC field, PUCCH resource indicator field, and / or PDSCH-to-HARQ_feedback timing indicator field to have a size of 0 bits, while the remaining bits in these fields (if any) may be set to default values ​​(e.g., all "0"s). When needed, the size of the new DCI format may also be matched to the size of another DCI format (such as DCI format 0_0 / 1_0, 0_1, or 0_2) to maintain a total size of 3 for DCI formats with CRC scrambled using C-RNTI.

[0133] In one embodiment, enabling or disabling HARQ-ACK information for the decoding result of a TB corresponding to a HARQ process can be indicated by the DCI format of the PDSCH received by the scheduler providing the TB. For example, the values ​​of one or more fields of the DCI format can be set to predefined values. For example, one or more values ​​(e.g., all "0"s or all "1"s) can be defined or configured for one or more of the DAI (for Type-2 codebook) field, the TPC field for determining PUCCH transmit power, the PUCCH resource indicator field, and / or the PDSCH-to-HARQ_feedback timing indicator field to indicate the disabling of HARQ-ACK information for the HARQ process.

[0134] The flowchart above illustrates an example method that can be implemented according to the principles of this disclosure, and various modifications can be made to the method shown in the flowchart herein. For example, although shown as a series of steps, the individual steps in each diagram can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, steps can be omitted or replaced by other steps.

[0135] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications will be apparent to those skilled in the art. This disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. Nothing described herein should be construed as implying that any particular element, step, or function is essential and must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A method for providing hybrid automatic repeat request acknowledgment (HARQ-ACK) information, the method comprising: Receive configuration information including instructions to enable or disable the HARQ process; Receive at least one transport block TB associated with the HARQ process; When the instruction indicates that HARQ-ACK information of the HARQ process is disabled, at least one TB of HARQ-ACK information associated with the HARQ process is identified as a NACK value in the first type of HARQ-ACK codebook. Identify the transmit power of the Physical Uplink Control Channel (PUCCH) without considering at least one TB associated with a HARQ process that has disabled HARQ-ACK information; and PUCCH is transmitted based on transmission power.

2. The method according to claim 1, wherein, The transmit power is identified based on the number of transport blocks (TBs) received during the physical downlink shared channel (PDSCH) reception time m in serving cell c, and the number of TBs does not include the number of at least one TB associated with a HARQ process having disabled HARQ-ACK information.

3. The method according to claim 1, wherein, The transmit power is identified based on the number of code block groups (CBGs) received during the physical downlink shared channel (PDSCH) reception time m in serving cell c, and The number of CBGs is associated with a transport block TB, and the number of CBGs does not include the number of CBGs associated with at least one TB, wherein the at least one TB is associated with a HARQ process having disabled HARQ-ACK information.

4. A user equipment (UE), comprising: The transceiver is configured as follows: Receive configuration information including instructions to enable or disable the HARQ acknowledgment (HARQ-ACK) information for the hybrid automatic repeat request (HARQ) process, and Receive at least one transport block TB associated with the HARQ process. The Physical Uplink Control Channel (PUCCH) is transmitted based on the transmit power, and A processor, operably connected to the transceiver, is configured to: When the instruction indicates that HARQ-ACK information for the HARQ process is disabled, at least one TB of HARQ-ACK information associated with the HARQ process is identified as a NACK value in a first type of HARQ-ACK codebook, and Identify the transmit power of the Physical Uplink Control Channel (PUCCH) without considering at least one TB associated with a HARQ process that has disabled HARQ-ACK information.

5. The UE according to claim 4, wherein, The transmit power is identified based on the number of transport blocks (TBs) received during the physical downlink shared channel (PDSCH) reception time m in serving cell c, and the number of TBs does not include the number of at least one TB associated with a HARQ process having disabled HARQ-ACK information.

6. The UE according to claim 4, wherein, The transmit power is identified based on the number of code block groups (CBGs) received during the physical downlink shared channel (PDSCH) reception time m in serving cell c, and The number of CBGs is associated with a transport block TB, and the number of CBGs does not include the number of CBGs associated with at least one TB, wherein the at least one TB is associated with a HARQ process having disabled HARQ-ACK information.

7. A method for receiving HARQ-ACK information, the method comprising: Send configuration information including instructions to enable or disable the HARQ process; Send at least one transport block TB associated with the HARQ process; as well as The Physical Uplink Control Channel (PUCCH) is received based on the transmit power. Wherein, in the case where the indication indicates that HARQ-ACK information of the HARQ process is disabled, the HARQ-ACK information of at least one TB associated with the HARQ process has a NACK value in the first type of HARQ-ACK codebook, and The transmission power of PUCCH is identified without considering at least one TB associated with a HARQ process that has disabled HARQ-ACK information.

8. The method according to claim 7, wherein, The transmit power is based on the number of transport blocks (TBs) transmitted during the physical downlink shared channel (PDSCH) transmission time m in serving cell c, and the number of TBs does not include the number of at least one TB associated with a HARQ process having disabled HARQ-ACK information.

9. The method according to claim 7, wherein, The transmit power is based on the number of code block groups (CBGs) transmitted during the physical downlink shared channel (PDSCH) transmission time m in serving cell c, and The number of CBGs is associated with a transport block TB, and the number of CBGs does not include the number of CBGs associated with at least one TB, wherein the at least one TB is associated with a HARQ process having disabled HARQ-ACK information.

10. A base station, comprising: The transceiver is configured as follows: Configuration information that sends HARQ acknowledgment (HARQ-ACK) messages, including instructions to enable or disable the hybrid automatic repeat request (HARQ) process. Send at least one transport block TB associated with the HARQ process, and The Physical Uplink Control Channel (PUCCH) is received based on the transmit power. Wherein, in the case where the indication indicates that HARQ-ACK information of the HARQ process is disabled, the HARQ-ACK information of at least one TB associated with the HARQ process has a NACK value in the first type of HARQ-ACK codebook, and The transmission power of PUCCH is identified without considering at least one TB associated with a HARQ process that has disabled HARQ-ACK information.

11. The base station according to claim 10, wherein, The transmit power is based on the number of transport blocks (TBs) transmitted during the physical downlink shared channel (PDSCH) transmission time m in serving cell c, and the number of TBs does not include the number of at least one TB associated with a HARQ process having disabled HARQ-ACK information.

12. The base station according to claim 10, wherein, The transmit power is based on the number of code block groups (CBGs) transmitted during the physical downlink shared channel (PDSCH) transmission time m in serving cell c, and The number of CBGs is associated with a transport block TB, and the number of CBGs does not include the number of CBGs associated with at least one TB, wherein the at least one TB is associated with a HARQ process having disabled HARQ-ACK information.

Images