Codebook configuration for HARQ reports

Abstract

Disclosed are devices, methods, and systems for configuring codebooks for HARQ reports. One method (700) includes receiving (702) a plurality of codebook configurations, each of the plurality of codebook configurations including information indicating a subset of a total Hybrid Automatic Repeat Request (HARQ) process for a Hybrid Automatic Repeat Request (HARQ) report. The method (700) includes autonomously selecting (704) a codebook configuration from the plurality of codebook configurations. The method (700) includes transmitting (706) information indicating the selected codebook configuration in configured authorized uplink control information, physical uplink shared channel transmission, or a combination thereof. The method (700) includes generating (708) the HARQ report for the subset of the total HARQ process based on the selected codebook configuration.

Description

[0001] Cross-reference of related applications

[0002] This application claims priority to U.S. Patent Application Serial No. 63 / 019,858, filed May 4, 2020, by Karthikeyan Ganesan, entitled “Apparatus, methods, and systems for automatically reporting UCI information in a CG UL resource,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The subject matter disclosed in this article generally relates to wireless communication, and more specifically, to codebook configurations used for HARQ reporting. Background Technology

[0004] In some wireless communication networks, HARQ reports can be used. In such networks, HARQ reports may be sent later than expected. Summary of the Invention

[0005] Disclosed are codebook configurations for HARQ reporting. The apparatus and system also perform the functions of the method. One embodiment of the method includes receiving a plurality of codebook configurations, each of which includes information indicating a subset of the overall hybrid automatic repeat request (HARQ) process for a HARQ report. In some embodiments, the method includes autonomously selecting a codebook configuration from the plurality of codebook configurations. In some embodiments, the method includes transmitting information indicating the selected codebook configuration in configured authorized uplink control information, physical uplink shared channel transmission, or a combination thereof. In various embodiments, the method includes generating the HARQ report for the subset of the overall HARQ process based on the selected codebook configuration.

[0006] An apparatus for configuring codebooks for HARQ reports includes a receiver that receives a plurality of codebook configurations, each of which includes information indicating a subset of the overall Hybrid Automatic Repeat Request (HARQ) process for HARQ reports. In various embodiments, the apparatus includes a processor that autonomously selects one of the plurality of codebook configurations. In some embodiments, the apparatus includes a transmitter that transmits information indicating the selected codebook configuration in the form of Configured Authorized Uplink Control Information, Physical Uplink Shared Channel (PHAS) transmission, or a combination thereof. In some embodiments, the processor generates the HARQ report for the subset of the overall HARQ process based on the selected codebook configuration. Attached Figure Description

[0007] A more specific description of the embodiments briefly described above will be presented by referring to the specific embodiments illustrated in the accompanying drawings. It is to be understood that these drawings depict only some embodiments and therefore should not be considered as limiting the scope; the embodiments will be described and explained with additional specificity and detail using the accompanying drawings, in which:

[0008] Figure 1 This is a schematic block diagram of one embodiment of a wireless communication system for configuring a codebook for HARQ reports;

[0009] Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used for codebook configuration for HARQ reports;

[0010] Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used for codebook configuration for HARQ reports;

[0011] Figure 4 This is a schematic block diagram illustrating one embodiment of code points in CG-UCI configured by RRC;

[0012] Figure 5 This is a schematic block diagram illustrating another embodiment of code points in CG-UCI configured by RRC;

[0013] Figure 6 This is a schematic block diagram illustrating another embodiment of code points in CG-UCI configured by RRC; and

[0014] Figure 7 This is a flowchart illustrating one embodiment of a method for configuring a codebook for HARQ reports. Detailed Implementation

[0015] As those skilled in the art will understand, aspects of the embodiments may be embodied as systems, devices, methods, or program products. Therefore, embodiments may take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, all of which are generally referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments may take the form of program products embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code (hereinafter referred to as “code”). The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In some embodiments, the storage device employs only signals for accessing the code.

[0016] Certain functional units described in this specification may be designated as modules to more specifically emphasize their implementation independence. For example, a module may be implemented as hardware circuitry that includes custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, or the like.

[0017] Modules can also be implemented in code and / or software for execution by various types of processors. For example, an identified code module may contain one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions. However, the executable files of the identified modules do not need to be physically located together, but may contain different instructions stored in different locations, which, when logically linked together, contain the module and implement the stated purpose of the module.

[0018] In fact, a code module can be a single instruction or multiple instructions, and can even be distributed across several different code segments, different programs, and spanning several memory devices. Similarly, operational data can be identified and described within a module, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or distributed across different locations, contained on different computer-readable storage devices. When a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0019] Any combination of one or more computer-readable media may be used. The computer-readable media may be a computer-readable storage medium. The computer-readable storage medium may be a storage device for storing code. For example, the storage device may be (but is not limited to) an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, device, or apparatus, or any suitable combination thereof.

[0020] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, computer-readable storage media can be any tangible medium containing or storing programs for use by or in connection with an instruction execution system, device, or apparatus.

[0021] The code used to implement the operations of the embodiments may be any number of lines and may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, or similar, and conventional procedural programming languages ​​such as the "C" programming language or similar, and / or machine languages ​​such as assembly language. The code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or may be connected to an external computer (e.g., via the Internet provided by an Internet service provider).

[0022] In this specification, references to "an embodiment," "embodiment," or similar language indicate that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, refer to the same embodiment, but rather to "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "comprising but not limited to." Unless expressly stated otherwise, the list of items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a" and "described" also mean "one or more."

[0023] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. In the following description, numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0024] The following description of aspects of the embodiments is based on schematic flowcharts and / or block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or block diagrams, and combinations of blocks in the schematic flowcharts and / or block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that instructions executable via the processor of the computer or other programmable data processing apparatus create a manner that implements the functions / actions specified in the blocks of the schematic flowcharts and / or block diagrams.

[0025] The code may also be stored in a storage device that can instruct a computer, other programmable data processing equipment or other means to function in a particular manner, such that the instructions stored in the storage device produce an article of writing containing instructions that implement the functions / actions specified in the schematic flowcharts and / or schematic block diagrams.

[0026] The code may also be loaded onto a computer, other programmable data processing apparatus or other device, such that a series of operational steps are executed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0027] The schematic flowcharts and / or block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or block diagrams may represent a portion of a module, segment, or code, which contains one or more executable instructions for implementing a specified logical function.

[0028] It should also be noted that in some alternative implementations, the functions marked in the boxes may appear in a different order than those marked in the diagram. For example, depending on the functionality involved, two boxes shown consecutively may actually be executed substantially simultaneously, or the boxes may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectively equivalent to one or more blocks or portions thereof in the illustrated diagram are conceivable.

[0029] While various arrow types and line styles may be used in flowcharts and / or block diagrams, it should be understood that this does not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a wait or monitoring period of unspecified duration between enumeration steps in a depicted embodiment. It will also be noted that each block of the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0030] The description of the elements in each figure can be referenced to the elements in the preceding figures. Similar numbers refer to similar elements in all figures, including alternative embodiments of similar elements.

[0031] Figure 1 An embodiment of a wireless communication system 100 for configuring a codebook for HARQ reports is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 A specific number of remote units 102 and network units 104 are depicted, but those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0032] In one embodiment, remote unit 102 may include a computing device, such as a desktop computer, laptop computer, personal digital assistant (“PDA”), tablet computer, smartphone, smart TV (e.g., a TV connected to the Internet), set-top box, game console, security system (including security cameras), in-vehicle computer, network device (e.g., router, switch, modem), aircraft, drone, or the like. In some embodiments, remote unit 102 includes a wearable device, such as a smartwatch, fitness tracker, optical head-mounted display, or the like. Furthermore, remote unit 102 may be referred to as a subscriber unit, mobile phone, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or by other terms used in the art. Remote unit 102 may communicate directly with one or more of network units 104 via UL communication signals. In some embodiments, remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0033] Network unit 104 may be distributed across a geographical area. In some embodiments, network unit 104 may also be referred to as and / or may include access point, access terminal, base station, base station, core network (“CN”), radio network entity, node B, evolved node B (“eNB”), 5G node B (“gNB”), home node B, relay node, device, core network, air server, radio access node, access point (“AP”), new radio (“NR”), network entity, access and mobility management function (“AMF”), unified data management (“UDM”), unified database (“UDR”), UDM / UDR, policy control function (“PCF”), radio access network (“RAN”), network slice selection function (“NSSF”), operation, supervision and management (“OAM”), session management function (“SMF”), user plane function (“UPF”), application function, authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), or any other term used in the field. Network unit 104 is typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks, such as the Internet and the public switched telephone network, and other networks. These and other elements of the radio access and core networks are not described but are well known to those skilled in the art.

[0034] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in the 3rd Generation Partnership Project (“3GPP”), wherein network unit 104 uses an OFDM modulation scheme for transmission on the downlink (“DL”), and remote unit 102 uses a single-carrier frequency division multiple access (“SC-FDMA”) or orthogonal frequency division multiplexing (“OFDM”) scheme for transmission on the uplink (“UL”). However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, and CDMA2000. Other protocols include ZigBee and Sigfoxx. This disclosure is not intended to limit it to any particular wireless communication system architecture or protocol implementation.

[0035] Network unit 104 can serve several remote units 102 within a service area (e.g., a cell or cell sector) via a wireless communication link. Network unit 104 transmits DL communication signals to serve the remote units 102 in the time domain, frequency domain, and / or spatial domain.

[0036] In various embodiments, remote unit 102 may receive a plurality of codebook configurations, each of which includes information indicating a subset of the overall HARQ reporting process. In some embodiments, remote unit 102 may autonomously select one of the plurality of codebook configurations. In some embodiments, remote unit 102 may transmit information indicating the selected codebook configuration in configured authorized uplink control information, physical uplink shared channel transmission, or a combination thereof. In various embodiments, remote unit 102 may generate a HARQ report for a subset of the overall HARQ reporting process based on the selected codebook configuration. Therefore, remote unit 102 may be used for codebook configuration for HARQ reporting.

[0037] Figure 2 This paper depicts one embodiment of a device 200 that can be used for codebook configuration for HARQ reporting. Device 200 includes one embodiment of a remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In some embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, memory 204, transmitter 210, and receiver 212, and may not include an input device 206 and / or display 208.

[0038] In one embodiment, processor 202 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 202 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 202 executes instructions stored in memory 204 to perform the methods and routines described herein. Processor 202 is communicatively coupled to memory 204, input device 206, display 208, transmitter 210, and receiver 212.

[0039] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on remote unit 102.

[0040] In one embodiment, input device 206 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, or the like. In some embodiments, for example, input device 206 may be integrated with display 208 as a touchscreen or similar touch-sensitive display. In some embodiments, input device 206 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0041] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include (but is not limited to) a liquid crystal display (“LCD”), a light-emitting diode (“LED”) display, an organic light-emitting diode (“OLED”) display, a projector, or a similar display device capable of outputting images, text, or the like to a user. As another non-limiting example, display 208 may include a wearable display, such as a smartwatch, smart glasses, a heads-up display, or the like. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, or the like.

[0042] In some embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate audible alarms or notifications (e.g., beeps or buzzers). In some embodiments, display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be located near input device 206.

[0043] In some embodiments, receiver 212 receives a plurality of codebook configurations, each of which includes information indicating a subset of the overall hybrid automatic repeat request (HAR) process for a hybrid automatic repeat request (HAR) report. In various embodiments, processor 202 autonomously selects a codebook configuration from the plurality of codebook configurations. In some embodiments, transmitter 210 transmits information indicating the selected codebook configuration in configured authorized uplink control information, physical uplink shared channel transmission, or a combination thereof. In some embodiments, processor 202 generates a hybrid automatic repeat request (HAR) report for a subset of the overall hybrid automatic repeat request (HAR) process based on the selected codebook configuration.

[0044] Although only one transmitter 210 and one receiver 212 are described, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitters 210 and receivers 212 may be of any suitable type. In one embodiment, the transmitters 210 and receivers 212 may be part of a transceiver.

[0045] Figure 3 An embodiment of a device 300 is depicted that can be used for codebook configuration for HARQ reporting. Device 300 includes one embodiment of a network unit 104. Furthermore, network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As will be understood, processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of remote unit 102, respectively.

[0046] In various embodiments, the Physical Uplink Control Channel (“PUCCH”) uses a Category 4 (“Cat4”) Listen-Before-Speak (“LBT”) access mechanism, and LBT failures during PUCCH transmission can delay the transmission of Hybrid Automatic Repeat Request Acknowledgment (“HARQ-ACK”) reports and / or Channel State Information (“CSI”) reports to the gNB. In some embodiments, aperiodic and / or autonomous reports of uplink control information (“UCI”) (such as HARQ-ACK reports and / or CSI reports) are multiplexed with uplink (“UL”) shared channel (“SCH”) transport blocks (“TB”) in configured authorized (“CG”) UL resources.

[0047] In some embodiments, the User Equipment (“UE”) may encounter an LBT failure in one or more beams configured for PUCCH transmission. An LBT failure may prevent (e.g., hinder, disable) the UE from transmitting a HARQ-ACK report and / or a CSI report until the next PUCCH opportunity. In such embodiments, if CG resources exist before the next PUCCH opportunity and no UL data is to be transmitted or multiplexed with a transport block, the UE may transmit the HARQ-ACK report and / or CSI report in the CG resources instead of in the UL-SCH.

[0048] In various embodiments, the UE may proactively use CG resources to report HARQ-ACK feedback or CSI reports based on the maximum permissible duration of delayed HARQ-ACK feedback and / or CSI reports, where the maximum permissible duration is defined as a time slot configurable by Radio Resource Control (“RRC”) signaling. In some embodiments, the maximum permissible duration of delayed HARQ-ACK feedback may be derived based on the latency requirements of the service or based on the lifetime of Industrial Internet of Things (“IIoT”) and / or Ultra Reliable Low Latency Communication (“URLLC”). For example, if the LBT fails at the expected time of the PUCCH, no further UL transmission will be scheduled until a Configurable Authorized Uplink (“CG-UL”) resource is available. In this example, HARQ-ACK feedback may be multiplexed in the CG-UL depending on the maximum permissible duration of delayed HARQ-ACK feedback. In another example, if the HARQ-ACK feedback transmission indicates that K1 is not a numerical value (“NNK1”), then this represents the minimum time until the next CG-UL resource. If the UE cannot find a CG UL resource or the next CG UL resource outside of the maximum allowed duration or NNK1, then the Hybrid Automatic Repeat Request (“HARQ”) feedback report can be discarded.

[0049] In some embodiments, one or more bits may be introduced into the Configurable Authorized Uplink Control Information (“CG-UCI”) to inform the gNB to distinguish CG resources that multiplex HARQ-ACK reports and / or CSI reports with uplink shared channel (“UL-SCH”) transport blocks. In one embodiment, HARQ-ACK reports and / or CSI reports are multiplexed with UL transport block transmissions. In another embodiment, if UL data is not present, HARQ-ACK reports and / or CSI reports are transmitted without UL transport blocks. In various embodiments, if any UL-SCH data is to be transmitted on CG resources, but its priority is lower than that of HARQ-ACK or CSI reports, the transmission of UL-SCH data may be delayed. This may mean that only HARQ-ACK reports and / or CSI reports are transmitted on CG resources, but not UL-SCH data. The interpretation of code points in the CG-UCI (e.g., information indicating what is contained in the CG resource, such as one or more bits) may be configured by RRC signaling.

[0050] Figure 4 This is a schematic block diagram 400 illustrating an embodiment of codepoints in CG-UCI configured by RRC, said codepoints having indications of content transmitted on CG resources (e.g., Figure 4 Column 2) bit fields (e.g., Figure 4 (Columns 1, 00, 01, 10, 11). If this code point (e.g., bit field) is not transmitted, then the gNB only expects UL-SCH TB data on the CG resource.

[0051] Figure 5 This is a schematic block diagram 500 illustrating another embodiment of codepoints in CG-UCI configured by RRC, said codepoints having indications of content transmitted on CG resources (e.g., Figure 5 Column 2) bit fields (e.g., Figure 5 Column 1, 00, 01).

[0052] Figure 6 This is a schematic block diagram 600 illustrating another embodiment of codepoints in CG-UCI configured by RRC, said codepoints having indications of content transmitted on CG resources (e.g., Figure 6 Column 2) bit fields (e.g., Figure 6 Column 1, 00, 01).

[0053] In some embodiments, if multiplexed with UL-SCH data, the amount of resources (e.g., resource elements (“REs”) used in the CG-UL resource for HARQ-ACK feedback (e.g., HARQ-ACK reports) and / or CSI reports can be determined based on the β offset value. In such embodiments, RRC signaling can configure the β offset value for multiplexing HARQ-ACK feedback and / or CSI reports with UL-SCH data in the CG resource. In some embodiments, RRC signaling configures a set of β offset values ​​for multiplexing HARQ-ACK feedback and / or CSI reports with UL-SCH data in the CG resource, and the actual value used by the UE can be signaled in the CG-UCI. In various embodiments, a code point or invalid code point of the β offset can indicate the absence of UL-SCH data in the CG resource. In some embodiments, different formats and / or sizes of the CG-UCI can be configured for the CG-UL resource via RRC signaling, wherein the content of the CG-UCI can be configured by RRC signaling.

[0054] In various embodiments, the UE may transmit HARQ-ACK reports for all HARQ procedures, while simultaneously transmitting HARQ-ACK reports in CG resources. In such embodiments, HARQ-ACK reports corresponding to all HARQ procedures are generated based on ascending order of HARQ procedure identifiers (“IDs”). In some embodiments, the gNB may assume that the UE reports HARQ-ACK feedback for all HARQ procedure IDs.

[0055] In some embodiments, the UE can autonomously select a subset of HARQ procedures for reporting HARQ-ACK reports, and the selected HARQ procedure IDs from the subset of HARQ procedures can be included in the HARQ-ACK report. In various embodiments, the UE can use bits in the CG-UCI to indicate that it only autonomously reports HARQ-ACK reports from a subset of HARQ procedures, or RRC signaling can configure whether all HARQ procedures or a subset of the total HARQ process will be used for UCI reporting on CG resources. In one embodiment, each codebook configuration contains rules containing subsets of HARQ procedures from one or more serving cells.

[0056] In some embodiments, the UE may include the HARQ procedure ID in the CG resource, followed by the corresponding HARQ-ACK report.

[0057] In some embodiments, the UE may be configured to use a semi-static or dynamic codebook for generating HARQ-ACK feedback to be transmitted in CG resources via RRC signaling, or this configuration may be dynamically indicated by the UE in CG-UCI.

[0058] In various embodiments, if the gNB expects to detect PUCCH transmissions but is unable to do so (e.g., due to LBT failure), it may assume the default case of transmitting only the UCI on the first available CG resource, rather than using code points in the CG-UCI to indicate whether UCI type and / or UL-SCH TB data is transmitted. In such embodiments, the gNB may expect to receive the corresponding UCI on the next available CG resource configured to the UE, without any explicit indication in the CG-UCI.

[0059] As may be understood, various embodiments may be described with respect to unlicensed or shared spectrum; however, any embodiments described herein may be applied to licensed carriers for IIoT communications and / or URLLC.

[0060] In some embodiments, for IIoT communication and / or URLLC, if the PUCCH resource is unavailable for transmitting HARQ-ACK and / or CSI reports within the latency constraints of the service type, then the CG resource can be used to transmit HARQACK or CSI reports to meet low latency requirements or lifetime. In some embodiments, if the UE fails to decode a previous DL TB or if consecutive decoding of DL TBs fails, then the UE may report HARQ-ACK and / or CSI in the next CG-UL resource. In another embodiment, HARQ ACK and / or CSI reports may be transmitted in the CG-UCI.

[0061] Figure 7 This is a flowchart illustrating one embodiment of a method 700 for configuring a codebook for HARQ reports. In some embodiments, method 700 is executed by a device such as remote unit 102. In some embodiments, method 700 may be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or the like.

[0062] In various embodiments, method 700 includes receiving 702 a plurality of codebook configurations, wherein each of the plurality of codebook configurations includes information indicating a subset of the overall hybrid automatic repeat request (HARQ) process for a hybrid automatic repeat request (HARQ) report. In some embodiments, method 700 includes autonomously selecting 704 a codebook configuration from the plurality of codebook configurations. In some embodiments, method 700 includes transmitting 706 information indicating the selected codebook configuration in configured authorized uplink control information, physical uplink shared channel transmission, or a combination thereof. In various embodiments, method 700 includes generating 708 a hybrid automatic repeat request (HARQ) report for a subset of the overall hybrid automatic repeat request (HARQ) process based on the selected codebook configuration, and transmitting it in CG-UL resources.

[0063] In various embodiments, receiving multiple codebook configurations includes receiving multiple codebook configurations via radio resource control signaling. In some embodiments, method 700 further includes determining a report of a hybrid automatic repeat request report in response to the physical uplink control channel not being transmitted in a first available configured-granted uplink resource. In various embodiments, transmitting the hybrid automatic repeat request report in the configured-granted uplink resource according to a maximum permissible duration is in relation to the time slot used for delaying the transmission of the hybrid automatic repeat request report.

[0064] In one instance, the Configurable Authorized Uplink Control Information includes an indicator indicating whether, in the case of multiplexing an Uplink Shared Channel Transport Block with a Hybrid Automatic Repeat Request Report or Channel State Information Report, or a combination thereof, only the Uplink Shared Channel Transport Block is included. In some embodiments, in response to a lack of transmission of the Physical Uplink Control Channel, the default content in the Configurable Authorized Uplink Control Information is a Hybrid Automatic Repeat Request Report from the first available Configurable Authorized Resource. In some embodiments, method 700 further includes determining whether to default transmission of all Hybrid Automatic Repeat Requests with all Hybrid Automatic Repeat Request Process Identifiers.

[0065] In various embodiments, method 700 further includes determining radio resource control signaling corresponding to a β offset value for multiplexing hybrid automatic repeat request reports, channel state information reports, or combinations thereof with uplink shared channel transport blocks. In one embodiment, autonomously selecting a codebook configuration from multiple codebook configurations includes autonomously selecting the codebook configuration from multiple codebook configurations in response to a physical uplink control channel not being transmitted due to a listen-before-tell failure in unlicensed listen-before-tell communication (e.g., triggered in the case where the PUCCH is not transmitted) or in response to a hybrid automatic repeat request report not being transmitted in the physical uplink control channel due to priority in industrial IoT communication, ultra-reliable low-latency communication, or combinations thereof (e.g., triggered in the case where a particular HARQ-ACK report is dropped in the PUCCH because the PUCCH is assigned to carry a high-priority HARQ-ACK report).

[0066] In some embodiments, method 700 further includes receiving configuration information for configured-granted uplink control information via radio resource control signaling. In some embodiments, method 700 further includes an ordered hybrid automatic repeat request procedure based on a hybrid automatic repeat request procedure identifier and the ascending order of the corresponding serving cell. In various embodiments, method 700 further includes transmitting a channel state information report in response to a physical uplink control channel not being transmitted in the first available configured-granted uplink resource.

[0067] In one instance, method 700 further includes determining that the autonomous reporting of channel state information reports in configured-authorized uplink resources depends on a maximum allowed duration. In some embodiments, the maximum allowed duration is in terms of the time slot used for delaying the transmission of channel state information reports. In some embodiments, in response to a physical uplink control channel transmission not being transmitted, the default content in the configured-authorized uplink control information is a channel state information report from the first available configured-authorized resource.

[0068] In one embodiment, a method includes: receiving a plurality of codebook configurations, wherein each of the plurality of codebook configurations includes information indicating a subset of a total hybrid automatic repeat request (HARQ) process for a hybrid automatic repeat request (HARQ) report; autonomously selecting a codebook configuration from the plurality of codebook configurations; transmitting information indicating the selected codebook configuration in configured authorized uplink control information, physical uplink shared channel transmission, or a combination thereof; and generating a hybrid automatic repeat request (HARQ) report for a subset of the total hybrid automatic repeat request process based on the selected codebook configuration.

[0069] In some embodiments, receiving multiple codebook configurations includes receiving multiple codebook configurations via radio resource control signaling.

[0070] In some embodiments, the method further includes determining a report of a hybrid automatic repeat request in response to the physical uplink control channel not being transmitted in the first available configured authorized uplink resource.

[0071] In various embodiments, transmitting the hybrid automatic repeat request report in the configured authorized uplink resources according to the maximum allowed duration refers to the time slot used to delay the transmission of the hybrid automatic repeat request report.

[0072] In one instance, the configured authorized uplink control information includes an indicator indicating whether, in the case of multiplexing uplink shared channel transport blocks with hybrid automatic repeat request reports or channel state information reports or combinations thereof, only uplink shared channel transport blocks are included.

[0073] In some embodiments, in response to the failure of a physical uplink control channel transmission, the default content in the configured authorized uplink control information is a hybrid automatic repeat request report from the first available configured authorized resource.

[0074] In some embodiments, the method further includes determining whether to transmit all hybrid autorepeat requests for all hybrid autorepeat request process identifiers by default.

[0075] In various embodiments, the method further includes determining radio resource control signaling corresponding to a β offset value for multiplexing a hybrid automatic repeat request report, channel state information report, or a combination thereof with an uplink shared channel transport block.

[0076] In one instance, the codebook configuration in the autonomous selection of multiple codebook configurations includes the codebook configuration in response to the failure of the physical uplink control channel due to the failure of the listen-after-speak communication in unauthorized listen-after-speak communication, or in response to the failure of the hybrid automatic repeat request report in the physical uplink control channel due to priority in industrial IoT communication, ultra-reliable low-latency communication, or a combination thereof.

[0077] In some embodiments, the method further includes receiving configuration information for configured authorized uplink control information via radio resource control signaling.

[0078] In some embodiments, the method further includes an ordered hybrid automatic repeat request process based on a hybrid automatic repeat request process identifier and the ascending order of the corresponding serving cell.

[0079] In various embodiments, the method further includes the transmission of a channel state information report in response to the physical uplink control channel not being transmitted in the first available configured authorized uplink resources.

[0080] In one instance, the method further includes determining that the autonomous reporting of channel state information in configured authorized uplink resources depends on the maximum allowed duration.

[0081] In some embodiments, the maximum permissible duration is in terms of the time slot used for delaying the transmission of channel state information reports.

[0082] In some embodiments, in response to the failure of physical uplink control channel transmission, the default content in the configured authorized uplink control information is a channel state information report from the first available configured authorized resource.

[0083] In one embodiment, an apparatus includes: a receiver receiving a plurality of codebook configurations, wherein each of the plurality of codebook configurations includes information indicating a subset of the overall hybrid automatic repeat request (HAR) process for a hybrid automatic repeat request (HAR) report; a processor autonomously selecting a codebook configuration from the plurality of codebook configurations; and a transmitter transmitting information indicating the selected codebook configuration in the form of configured authorized uplink control information, physical uplink shared channel transmission, or a combination thereof; wherein the processor generates a hybrid automatic repeat request (HAR) report for a subset of the overall hybrid automatic repeat request (HAR) process based on the selected codebook configuration.

[0084] In some embodiments, receiving multiple codebook configurations by the receiver includes receiving multiple codebook configurations via radio resource control signaling.

[0085] In some embodiments, the processor determines a hybrid automatic repeat request report in response to a report that the physical uplink control channel is not transmitted in the first available configured authorized uplink resource.

[0086] In various embodiments, transmitting the hybrid automatic repeat request report in the configured authorized uplink resources according to the maximum allowed duration refers to the time slot used to delay the transmission of the hybrid automatic repeat request report.

[0087] In one instance, the configured authorized uplink control information includes an indicator indicating whether, in the case of multiplexing uplink shared channel transport blocks with hybrid automatic repeat request reports or channel state information reports or combinations thereof, only uplink shared channel transport blocks are included.

[0088] In some embodiments, in response to the failure of a physical uplink control channel transmission, the default content in the configured authorized uplink control information is a hybrid automatic repeat request report from the first available configured authorized resource.

[0089] In some embodiments, the processor determines whether to transmit all mixed autorepeating requests for all mixed autorepeating request process identifiers by default.

[0090] In various embodiments, the processor determines radio resource control signaling corresponding to a β offset value for multiplexing a hybrid automatic repeat request report, channel state information report, or a combination thereof with an uplink shared channel transport block.

[0091] In one instance, the codebook configuration in the autonomous selection of multiple codebook configurations includes the codebook configuration in response to the failure of the physical uplink control channel due to the failure of the listen-after-speak communication in unauthorized listen-after-speak communication, or in response to the failure of the hybrid automatic repeat request report in the physical uplink control channel due to priority in industrial IoT communication, ultra-reliable low-latency communication, or a combination thereof.

[0092] In some embodiments, the receiver receives configuration information for configured authorized uplink control information via radio resource control signaling.

[0093] In some embodiments, the processor sorts the Hybrid Automatic Repeat Request Procedures according to the Hybrid Automatic Repeat Request Procedure Identifier and the ascending order of the corresponding serving cells.

[0094] In various embodiments, the processor determines the transmission of a channel state information report in response to the physical uplink control channel not being transmitted in the first available configured authorized uplink resources.

[0095] In one instance, the processor determines whether to autonomously report channel state information in configured authorized uplink resources, depending on the maximum allowed duration.

[0096] In some embodiments, the maximum permissible duration is in terms of the time slot used for delaying the transmission of channel state information reports.

[0097] In some embodiments, in response to the failure of physical uplink control channel transmission, the default content in the configured authorized uplink control information is a channel state information report from the first available configured authorized resource.

[0098] The embodiments may be implemented in other specific forms. The described embodiments are to be regarded in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All modifications within the equivalent meaning and scope of the claims should be covered within its scope.

Claims

1. A method performed by a user equipment (UE), the method comprising: Receive multiple codebook configurations, each of the multiple codebook configurations including information indicating a subset of multiple HARQ procedures for hybrid automatic repeat request HARQ reporting; Choose the codebook configuration from the multiple codebook configurations; Information indicating the selected codebook configuration is transmitted in the configured authorized CG uplink control information (UCI), physical uplink shared channel (PUSCH) transmission, or a combination thereof; as well as The HARQ report is generated for the subset of the plurality of HARQ procedures based on the selected codebook configuration.

2. The method of claim 1, wherein receiving the plurality of codebook configurations includes receiving the plurality of codebook configurations via Radio Resource Control (RRC) signaling.

3. The method of claim 1, further comprising determining the HARQ report in response to the Physical Uplink Control Channel (PUCCH) not being transmitted in the first available CG uplink resources.

4. The method of claim 3, wherein transmitting the HARQ report in the CG uplink resource according to the maximum permissible duration is in relation to the time slot used for delaying the transmission of the HARQ report.

5. The method of claim 1, wherein the CG UCI indicates whether, in the case of multiplexing the uplink shared channel transport block with the HARQ report or channel state information report or a combination thereof, only the uplink shared channel transport block is included.

6. The method according to claim 5, wherein, In response to the failure of Physical Uplink Control Channel (PUCCH) transmission, the default content in the CG UCI is the HARQ report in the first available CG resource.

7. The method of claim 6, further comprising determining whether to transmit all HARQs for all HARQ process identifiers.

8. The method of claim 1, further comprising determining radio resource control (RRC) signaling corresponding to a β offset value for multiplexing the HARQ report, channel state information (CSI) report, or a combination thereof with an uplink shared channel transport block.

9. The method of claim 1, wherein the autonomous selection of the codebook configuration among the plurality of codebook configurations includes autonomously selecting the codebook configuration among the plurality of codebook configurations in response to failure to transmit the Physical Uplink Control Channel (PUCCH) due to a failure of READ-READ communication in unauthorized READ-READ communication, or in response to failure to transmit a HARQ report in the PUCCH due to priority of Industrial IoT communication, Ultra-Reliable Low-Latency Communication, or a combination thereof.

10. The method of claim 1, further comprising receiving configuration information of the CG UCI via Radio Resource Control (RRC) signaling.

11. The method of claim 1, further comprising an ordered HARQ process based on the HARQ process identifier and the ascending order of the corresponding serving cell.

12. The method of claim 1, further comprising determining the transmission of a channel state information report in response to the physical uplink control channel PUCCH not being transmitted in the first available CG uplink resources.

13. The method of claim 12, further comprising determining that the autonomous reporting of the channel state information in the uplink resources of the CG depends on the maximum allowed duration.

14. The method of claim 13, wherein the maximum permissible duration is in relation to the time slot used for delaying the transmission of the channel state information report.

15. The method according to claim 12, wherein, In response to the failure of PUCCH transmission, the default content in the CG UCI is the channel state information report in the first available CG resource.

16. A user equipment (UE) comprising: A receiver that receives multiple codebook configurations, each of which includes information indicating a subset of multiple HARQ processes for hybrid automatic repeat request HARQ reporting; The processor autonomously selects one of the multiple codebook configurations; as well as The transmitter transmits information indicating the selected codebook configuration in the transmission of Configuration Authorized CG Uplink Control Information (UCI), Physical Uplink Shared Channel (PUSCH), or a combination thereof. The processor is configured to generate the HARQ report for a subset of the plurality of HARQ procedures based on the selected codebook.

17. The UE of claim 16, wherein receiving the plurality of codebook configurations by the receiver includes receiving the plurality of codebook configurations via Radio Resource Control (RRC) signaling.

18. The UE of claim 16, wherein the processor determines the HARQ report in response to the Physical Uplink Control Channel (PUCCH) not being transmitted in the first available CG uplink resource.

19. The UE of claim 18, wherein transmitting the HARQ report in the CG uplink resources according to the maximum permissible duration is in relation to the time slot used for delaying the transmission of the HARQ report.

20. The UE of claim 16, wherein the CG UCI includes an indicator indicating whether, in the case of multiplexing the uplink shared channel transport block with the HARQ report or channel state information report or a combination thereof, only the uplink shared channel transport block is included.

Images