Receiver Feedback in Wireless Systems
By dynamically adjusting receiver feedback according to the HARQ processing status and WTRU configuration in the wireless communication system, the optimized mapping of code block groups and transmission blocks is achieved, solving the problem of unoptimized resource allocation and improving transmission efficiency and reliability.
Patent Information
- Application Number
- CN202210705954.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-08-09
- Filing Date
- 2018-01-03
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2038-01-03
AI Technical Summary
In wireless communication systems, it is difficult for the prior art to effectively determine the format, content, type and timing of the receiver feedback based on the hybrid automatic repeat request (HARQ) processing status and the wireless transmit/receive unit (WTRU) configuration, resulting in unoptimized resource allocation. Impact transmission efficiency.
By dynamically adjusting the format, content and type of receiver feedback according to the configuration and channel conditions of the WTRU during the HARQ process, using soft combination processing and feedback suppression parameters, the mapping of code block groups (CBG) and transmission blocks (TB) is achieved. , and provide uniform and non-uniform resource allocation based on the pre-occupation transmission probability.
It improves the flexibility and accuracy of HARQ feedback, optimizes resource allocation, reduces the number of retransmissions, and improves the transmission efficiency and reliability of wireless communication systems.
Smart Images

Figure CN115189816B_ABST
Abstract
Description
[0001] This application is a divisional application of Chinese Patent Application No. 201880005828.2, entitled “Receiver Feedback in Wireless Systems”, filed on January 3, 2018, which is incorporated herein by reference in its entirety.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS
[0003] This application claims priority to and the benefit of U.S. Provisional Application Serial No. 62 / 442,093 filed on January 4, 2017, U.S. Provisional Application Serial No. 62 / 453,085 filed on February 1, 2017, U.S. Provisional Application Serial No. 62 / 500,989 filed on May 3, 2017, U.S. Patent Application Serial No. 62 / 519,675 filed on June 14, 2017, and U.S. Patent Application Serial No. 62 / 542,927 filed on August 9, 2017, all of which are incorporated herein by reference in their entirety. Background Art
[0004] Mobile communications using wireless communications continue to develop. The fifth generation may be referred to as 5G. Previous (legacy) generations of mobile communications may be, for example, fourth generation (4G) Long Term Evolution (LTE). Summary of the invention
[0005] Systems, methods and means for receiver feedback in a wireless system are disclosed. The receiver feedback format, content, type and / or timing may be determined based on, for example, a hybrid automatic repeat request (HARQ) processing state. The HARQ processing state may correspond to, for example, a transmission sequence of a HARQ process, a maximum time for the HARQ process to continue, a measured or estimated link quality, demodulation performance and / or the number of successfully decoded code blocks. The receiver feedback format, content, type and / or timing may be determined based on, for example, a configuration of a wireless transmit / receive unit (WTRU). The configuration may indicate one or more of the following: a type of soft combining process to be applied in a HARQ process, a HARQ operation point for the HARQ process, one or more reference transmissions for controlling the type of HARQ feedback for the HARQ process, and a feedback suppression parameter for one or more transmissions in a sequence associated with a HARQ process or a transport block (TB). Transmissions (e.g., valid transmissions) of a subset of one or more code block groups (CBGs) may be used. Adaptive resource allocation may be used to send a subset of one or more CBGs. Mini-time slots may be used to retransmit a subset of one or more CBGs. The WTRU may monitor a downlink control channel (e.g., a new downlink) (e.g., when a transmission is expected). A retransmission CBG index may be indicated. A timing relationship between downlink assignments, transmissions (retransmissions), and adaptive feedback for adaptive slot sizes may be used. Uniform and non-uniform CB to CBG mappings may be provided (e.g., provided by the WTRU) based on, for example, one or more parameters, interference and channel conditions, and / or the probability of actually pre-occupied transmissions. A CB to CBG mapping indication may be provided to, for example, support selection of a CB to CBG mapping from multiple CB to CBG mappings. Intra-WTRU and inter-WTRU interference / pre-occupancy indications may be provided. A feedback bit counter downlink assignment index (DAI) may enable the WTRU to determine how many feedback bits are required for feedback reporting of a lost DL assignment. Adaptive bundling of feedback report bits may be used to achieve a fixed feedback report size per DL assignment. Unequal reliability may be used for the multiplexed feedback reports.
[0006] The WTRU and the wireless communication system may have one or more configured (e.g., programmed with executable instructions) computer processors. For example, the WTRU may have a processor configured to communicate with a wireless communication network (e.g., by using UR-LLC communication). The WTRU processor may be configured to receive a first downlink control information (DCI) indicating whether a transport block (TB)-based hybrid automatic repeat request (HARQ) feedback should be provided for a downlink transmission, or whether a code block group (CBG)-based HARQ feedback should be provided for the downlink transmission. The WTRU processor may be configured to receive a downlink transmission associated with the first DCI, the downlink transmission including a transport block having one or more code blocks. The WTRU processor may be configured to attempt to decode the one or more code blocks of the transport block. The WTRU processor may be configured to determine that the first DCI indicates that CBG-based HARQ feedback should be provided. If the processor determines that the first DCI indication should provide CBG-based HARQ feedback, the WTRU processor may be configured to determine a mapping of the one or more code blocks to one or more CBGs; based on whether the corresponding code block of at least one of the one or more CBGs is successfully decoded, determine HARQ feedback for at least one of the one or more CBGs, and send the HARQ feedback for the one or more CBGs to the wireless communication network. The WTRU processor may be configured to determine that the first DCI indication should provide TB-based HARQ feedback. If the WTRU processor determines that the first DCI indication should provide TB-based HARQ feedback, the WTRU processor may be configured to determine HARQ feedback for the transport block and send the HARQ feedback for the transport block to the wireless communication network.
[0007] The mapping may be a mapping of the one or more code blocks to the code block group in at least one of frequency or time. The mapping may be based on one or more of: the number of subcarriers or OFDM symbols assigned to the code block group or the transmission, a maximum code block length, the number of code block groups in the transmission, the number of code blocks in the transmission, and the number of time symbols and / or resource blocks occupied by a potential pre-empted transmission.
[0008] The determined HARQ feedback for the one or more CBGs may be an ACK if each of the corresponding code blocks is successfully decoded, and the determined HARQ feedback for the one or more CBGs may be a NACK if one or more of the one or more code blocks are not successfully decoded. The WTRU processor may be configured to receive a retransmission in response to the sent NACK from the wireless communication network. The wireless communication network may have a processor configured to receive the sent ACK or NACK and determine to send a retransmission if a NACK is received.
[0009] The WTRU processor may be configured to receive a second DCI for a retransmission. The second DCI may indicate which CBGs are being retransmitted. The second DCI may indicate which CBGs included in the retransmission may be combined with previously received CBGs when performing soft decoding. The second DCI may include a bitmap that may be used to indicate which CBGs included in the retransmission may be combined with previously received CBGs when performing soft decoding. The wireless communication network may have a processor configured to determine to send the second DCI and the content of the second DCI.
[0010] The WTRU processor may be configured to monitor the first downlink control information and monitor the second downlink control information based on a camp-on instruction from a wireless communication network.The wireless communication network may have a processor configured to determine to send a camp-on instruction to the WTRU.
[0011] The WTRU may include a HARQ buffer. The WTRU processor may be configured to manage the HARQ buffer and discard data in the HARQ buffer if the one or more code blocks are not successfully decoded.
[0012] The WTRU processor may be configured to determine a camp-on indication to send in uplink control information to a wireless communication network if the one or more code blocks are not successfully decoded.
[0013] The wireless communication network may have a processor configured to determine to send first downlink control information (DCI) and send the first downlink control information, the first downlink control information indicating whether transport block (TB)-based hybrid automatic repeat request (HARQ) feedback should be provided for downlink transmission or whether code block group (CBG)-based HARQ feedback should be provided for downlink transmission. The wireless communication network may have a processor configured to receive the sent HARQ feedback, the feedback including TB-based HARQ feedback. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Figure 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed examples may be implemented.
[0015] Figure 1B is a diagram showing the example of Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within a communication system is shown in FIG.
[0016] Figure 1C is a diagram showing the example of Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) for use within the communication system shown in FIG.
[0017] Figure 1D is a diagram showing the example of Figure 1A System diagram of another exemplary RAN and another exemplary CN used within the communication system shown in .
[0018] Figure 2 is an example of a punctured transmission with a different HARQ feedback type for each transmission.
[0019] Figure 3 is an example of a CBG spanning multiple CBs in the time domain.
[0020] Figure 4 is an example of a CBG spanning multiple CBs in the time domain.
[0021] Figure 5 is an example of a non-uniform CB to CBG mapping, which allows minimizing retransmitted CBs in case of pre-emption.
[0022] Figure 5A are examples of frequency-first and time-first CB-CBG mapping. DETAILED DESCRIPTION
[0023] A detailed description of illustrative embodiments will now be described with reference to the accompanying drawings. Although this description provides detailed examples of possible implementations, it should be noted that these details are intended to be exemplary and in no way limit the scope of the present application.
[0024] Figure 1A1 is a diagram showing an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, the communication system 100 may use one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filter bank multi-carrier (FBMC), etc.
[0025] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112, although it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network components. Each WTRU 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, any of the WTRUs 102a, 102b, 102c, 102d may be referred to as a “station” and / or “STA”, which may be configured to transmit and / or receive wireless signals, and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices working in an industrial and / or automated process chain environment), consumer electronic devices, and devices working on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.
[0026] The communication system 100 may also include a base station 114a and / or a base station 114b. Each base station 114a, 114b may be any type of device configured to facilitate access to one or more communication networks (e.g., CN 106 / 115, Internet 110, and / or other networks 112) by wirelessly interfacing with at least one of the WTRUs 102a, 102b, 102c, 102d. For example, the base stations 114a, 114b may be base transceiver stations (BTS), Node Bs, eNode Bs, Home Node Bs, Home eNode Bs, gNBs, NR Node Bs, site controllers, access points (APs), and wireless routers, among others. Although each base station 114a, 114b is depicted as a single component, it should be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network components.
[0027] The base station 114a may be part of the RAN 104 / 113, and the RAN may also include other base stations and / or network components (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, and the like. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies called cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage for a specific geographic area that is relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, that is, each transceiver corresponds to a sector of the cell. In an embodiment, the base station 114a may use multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, by using beamforming, signals may be transmitted and / or received in a desired spatial direction.
[0028] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).
[0029] More specifically, as described above, the communication system 100 may be a multiple access system and may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, among others. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and / or High Speed UL Packet Access (HSUPA).
[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-APro).
[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using new radio (NR).
[0032] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access (e.g., using dual connectivity (DC) principles). Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).
[0033] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), and GSM EDGE (GERAN), among others.
[0034] Figure 1A The base station 114b in the example may be a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may use any appropriate RAT to facilitate wireless connectivity in a local area, such as a business location, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless local area network (WLAN) by implementing a radio technology such as IEEE 802.11. In an embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless personal area network (WPAN) by implementing a radio technology such as IEEE 802.15. In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell by using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, and the like). Figure 1A As shown, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114b does not need to access the Internet 110 via the CN 106 / 115.
[0035] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or may perform advanced security functions such as user authentication. Although in Figure 1AAlthough not shown, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 104 / 113. For example, in addition to being connected to the RAN 104 / 113 employing NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
[0036] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer network devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet Protocol Suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, wherein the one or more RANs may use the same RAT or a different RAT as the RAN 104 / 113.
[0037] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
[0038] Figure 1B is a system diagram showing an example WTRU 102. Figure 1B As shown, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It should be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0039] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, however it should be appreciated that the processor 118 and the transceiver 120 may also be integrated into one electronic component or chip.
[0040] The transmit / receive component 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive component 122 may be an antenna configured to transmit and / or receive RF signals. As an example, in an embodiment, the transmit / receive component 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In an embodiment, the transmit / receive component 122 may be configured to transmit and / or receive RF and light signals. It should be appreciated that the transmit / receive component 122 may be configured to transmit and / or receive any combination of wireless signals.
[0041] Although in Figure 1B 102 as a single component, but the WTRU 102 may include any number of transmit / receive components 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive components 122 (e.g., multiple antennas) for transmitting and receiving radio signals over the air interface 116.
[0042] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive component 122 and to demodulate signals received by the transmit / receive component 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers that allow the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.
[0043] The processor 118 of the WTRU 102 may be coupled to the speaker / microphone 124, the keyboard 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data from these components. The processor 118 may also output user data to the speaker / microphone 124, the keyboard 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store information in any suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in memories that are not physically located in the WTRU 102, such as, for example, a server or a home computer (not shown).
[0044] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power for use by other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (Ni-Cd), nickel-zinc (Ni-Zn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
[0045] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) via the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be appreciated that the WTRU 102 may acquire location information via any suitable positioning method while remaining consistent with an embodiment.
[0046] The processor 118 may also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Modules, frequency modulation (FM) radio units, digital music players, media players, video game console modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices, and activity trackers, etc. The peripherals 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.
[0047] The WTRU 102 may include a full-duplex radio in which the reception or transmission of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous for the radio. The full-duplex radio may include an interference management unit 139 that reduces and / or substantially eliminates self-interference by means of hardware (e.g., chokes) or by signal processing by a processor (e.g., a separate processor (not shown) or by the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio that transmits and receives some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)).
[0048] Figure 1C 1 is a system diagram showing the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c using an E-UTRA radio technology over the air interface 116. The RAN 104 may also be in communication with the CN 106.
[0049] The RAN 104 may include eNode-Bs 160a, 160b, 160c, however it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. Each of the eNode-Bs 160a, 160b, 160c may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.
[0050] Each eNodeB 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.
[0051] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Although each of the foregoing components is described as being part of the CN 106, it should be appreciated that any of these components may be owned and / or operated by an entity other than the CN operator.
[0052] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, performing bearer activation / deactivation processing, and selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.
[0053] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may also perform other functions, such as anchoring the user plane during inter-eNB handovers, triggering paging processing when DL data is available for the WTRUs 102a, 102b, 102c, and managing and storing the contexts of the WTRUs 102a, 102b, 102c, and the like.
[0054] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0055] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or be in communication with an IP gateway, such as an IP Multimedia Subsystem (IMS) server, and the IP gateway may serve as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.
[0056] Although in Figures 1A-1D Although the WTRU is described as a wireless terminal, it should be appreciated that in certain typical embodiments, such a terminal may use a (eg, temporary or permanent) wired communication interface with a communication network.
[0057] In a typical embodiment, the other network 112 may be a WLAN.
[0058] A WLAN using an infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may access or be connected to a distributed system (DS) or other types of wired / wireless networks that send traffic into and / or out of the BSS. Traffic originating from outside the BSS and destined for the STA may arrive through the AP and be delivered to the STA. Traffic originating from the STA and destined for a destination outside the BSS may be sent to the AP for delivery to the corresponding destination. Traffic between STAs within the BSS may be sent through the AP, for example, the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. The point-to-point traffic may be sent using a direct link establishment (DLS) between the source and destination STAs (e.g., directly therebetween). In certain typical embodiments, the DLS may use 802.11e DLS or 802.11z channelized DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. Here, the IBSS communication mode may sometimes be referred to as an "ad hoc" communication mode.
[0059] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may transmit a beacon on a fixed channel (e.g., a primary channel). The primary channel may have a fixed width (e.g., a bandwidth of 20 MHz) or a width that is dynamically set with the aid of signaling. The primary channel may be a working channel of the BSS and may be used by STAs to establish a connection with the AP. In certain typical embodiments, carrier sense multiple access (CSMA / CA) with collision avoidance (e.g., in an 802.11 system) may be implemented. For CSMA / CA, STAs (e.g., each STA) including the AP may sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, the particular STA may back off. In a specified BSS, one STA (e.g., only one station) may transmit at any given time.
[0060] A high throughput (HT) STA may communicate using a 40 MHz wide channel (eg, by combining a 20 MHz wide primary channel with a 20 MHz wide adjacent or non-adjacent channel to form a 40 MHz wide channel).
[0061] Very high throughput (VHT) STA can support channels with widths of 20MHz, 40MHz, 80MHz and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels or by combining two discontinuous 80MHz channels (this combination can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data can be transmitted and passed through a segment parser, which can separate the data into two streams. Inverse fast Fourier transform (IFFT) processing and time domain processing can be performed separately on each stream. The stream can be mapped on two 80MHz channels, and the data can be transmitted by the STA performing the transmission. At the receiver of the STA performing the reception, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).
[0062] 802.11af and 802.11ah support working modes below 1 GHz. Compared with 802.11n and 802.11ac, the channel working bandwidth and carrier used in 802.11af and 802.11ah are reduced. 802.11af supports 5MHz, 10MHz and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz and 16MHz bandwidths using non-TVWS spectrum. According to certain typical embodiments, 802.11ah can support instrument type control / machine type communication (such as MTC devices in macro coverage areas). MTC can have certain capabilities, such as limited capabilities including support (for example, only support) certain and / or limited bandwidths. The MTC device may include a battery, and the battery life of the battery is higher than a threshold (for example, for maintaining a very long battery life).
[0063] For WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah), the WLAN system includes a channel that can be designated as a primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by a certain STA, where the STA originates from all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz and / or other channel bandwidth operating modes, for STAs (e.g., MTC-type devices) that support (e.g., only support) 1MHz mode, the width of the primary channel can be 1MHz. Carrier sensing and / or network allocation vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy (e.g., because a STA (which only supports the 1MHz operating mode) transmits to the AP), then the entire available frequency band can be considered busy even if most of the frequency band remains idle and available for use.
[0064] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.
[0065] Figure 1D1 is a system diagram showing the RAN 113 and the CN 115 according to an embodiment. As described above, the RAN 113 may communicate with the WTRUs 102a, 102b, 102c using NR radio technology over the air interface 116. The RAN 113 may also communicate with the CN 115.
[0066] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each gNB 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may use beamforming processing to transmit and / or receive signals to and / or from the gNBs 180a, 180b, 180c. Thus, for example, the gNB 180a may use multiple antennas to transmit wireless signals to the WTRU 102a and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit a plurality of component carriers (not shown) to the WTRU 102a. A subset of these component carriers may be on an unlicensed spectrum while the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and gNB 180b (and / or gNB 180c).
[0067] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with a scalable digital configuration. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different for different transmissions, different cells, and / or different portions of the radio transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., containing different numbers of OFDM symbols and / or continuously varying absolute time lengths).
[0068] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect to the gNB 180a, 180b, 180c while communicating / connecting to another RAN (e.g., the eNode-B 160a, 160b, 160c). For example, the WTRU 102a, 102b, 102c may communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c in a substantially simultaneous manner by implementing the DC principle. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput to serve the WTRU 102a, 102b, 102c.
[0069] Each gNB 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, support network slicing, implement dual connectivity, implement interworking between NR and E-UTRA, route user plane data to user plane functions (UPFs) 184a, 184b, and route control plane information to access and mobility management functions (AMFs) 182a, 182b, and the like. Figure 1D As shown, gNBs 180a, 180b, and 180c can communicate with each other via the X2 interface.
[0070] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and may include a data network (DN) 185a, 185b. Although each of the aforementioned components is described as part of the CN 115, it should be understood that any of these components may be owned and / or operated by entities other than the CN operator.
[0071] The AMF 182a, 182b may be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, and mobility management, etc. The AMF 182a, 1823b may use network slicing processing to customize the CN support provided to the WTRU 102a, 102b, 102c based on the type of service used by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, and / or services for machine type communication (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) using other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.
[0072] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and may configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.
[0073] The UPF 184a, 184b can be connected to one or more gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which can provide the WTRU 102a, 102b, 102c with access to packet-switched networks (e.g., the Internet 110) to facilitate communication between the WTRU 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b can perform other functions such as routing and forwarding packets, implementing user plane policies, supporting multi-host PDU sessions, processing user plane QoS, buffering downlink packets, and providing mobility anchor processing, etc.
[0074] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the local data network (DN) 185a, 185b via an N3 interface connected to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b and through the UPF 184a, 184b.
[0075] In view of Figures 1A-1D and about Figures 1A-1D , one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU 102a-d, base station 114a-b, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein. These simulation devices may be one or more devices configured to simulate one or more or all of the functions herein. For example, these simulation devices may be used to test other devices and / or simulate network and / or WTRU functions.
[0076] The simulation device can be designed to implement one or more tests about other devices in a laboratory environment and / or an operator network environment. For example, the one or more simulation devices can perform one or more or all functions while being implemented and / or deployed as part of a wired and / or wireless communication network in whole or in part to test other devices inside the communication network. The one or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device can be directly coupled to other devices to perform the test, and / or can use over-the-air wireless communication to perform the test.
[0077] The one or more simulation devices can perform one or more functions, including all functions, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test lab and / or a test scenario of a wired and / or wireless communication network that is not deployed (e.g., tested) to implement tests on one or more components. The one or more simulation devices can be test devices. The simulation device can transmit and / or receive data using direct RF coupling and / or wireless communication with the aid of RF circuits (as an example, the circuits can include one or more antennas).
[0078] A network may refer to one or more gNBs that may be associated with one or more transmission / reception points (TRPs) or other nodes (one or more) in a radio access network.
[0079] Mobile communications are constantly evolving. The fifth generation of evolution is known as 5G.
[0080] HARQ-related feedback may support codeblock-based puncturing of HARQ operations and / or transmissions. One or more of the following may be combined: measurement-based probability feedback per transmission, feedback per codeblock, and / or feedback per TB. Support may be provided for switching reporting (e.g., reporting type and / or method) for HARQ processes and / or for TBs (e.g., to optimize the tradeoff between granularity and overhead assuming a given HARQ operating point).
[0081] Sub-TB feedback configuration may be used (e.g., different sub-TB regions may be configured with different HARQ feedback types). Feedback requests may be used (e.g., for sub-TB resources), for example, regardless of whether such sub-TB resources are included in the current retransmission. For example, the feedback request may confirm a previous probabilistic HARQ feedback. The WTRU may select sub-TB resources for feedback. Sub-TB resources may be retransmitted (e.g., mapping of subsets of sub-TB resources, methods for reusing unused resources, and methods for controlling soft combining).
[0082] A 5G system may, for example, correspond at least partially to a new radio (NR) access technology.
[0083] The 5G air interface may support ultra-low latency (LLC) transmission, ultra-reliable transmission (URC) and / or machine type communication (MTC) operations, which may include narrowband operations. These communications may be referred to as UR-LLC communications.
[0084] In an example supporting LLC, the air interface latency may be, for example, 1 ms round trip time (RTT). The transmission time interval (TTI) may be, for example, between 100 us and 250 us.
[0085] Support for ultra-low access latency (eg, time from initial system access to completion of transmission of the first user plane data unit) may be provided.
[0086] Communications (e.g., IC and / or vehicle-to-everything communications (V2X)) may have end-to-end (e2e) latency, e.g., less than 10 ms.
[0087] In an example supporting URC, transmission reliability may be, for example, approximately 99.999% transmission success rate and service availability.
[0088] Support for mobility can be provided. The mobility speed can be in the range of, for example, 0 to 500 km / h.
[0089] Can be less than 10e -6 The packet loss rate (PLR) provided by the system is used for communications (e.g., IC and V2X).
[0090] In an example of supporting MTC operations, the air interface can support narrowband operation (e.g., using less than 200KHz), extended battery life (e.g., up to 15 years of autonomy), and / or minimal communication overhead for small and infrequent data transmissions (e.g., low data rates in the range of 1-100kbps with access latencies of seconds to hours).
[0091] Orthogonal frequency division multiplexing (OFDM) can be used as a signal format for data transmission, for example for LTE and / or IEEE802.11. OFDM can be used to divide the spectrum into multiple parallel orthogonal sub-bands. (E.g., each) subcarrier can be shaped using a rectangular window in the time domain, which can result in a sinusoidal-shaped subcarrier in the frequency domain. OFDM access (OFDMA) can be implemented as management with (e.g., perfect) frequency synchronization and (e.g., strict) uplink timing alignment over the duration of a cyclic prefix, for example to maintain orthogonality between signals and minimize inter-carrier interference. For example, in a system where a WTRU can be connected to multiple access points simultaneously, strict synchronization can be a challenge. Additional power reduction can be applied to uplink transmissions, for example, to comply with spectrum emission requirements in adjacent bands, which may occur when there is aggregation of segmented spectrum for WTRU transmissions.
[0092] For example, when operating with a large continuous spectrum without the need for aggregation, OFDM (e.g., cyclic prefix (CP)-OFDM) implementations may apply more stringent RF requirements. CP-based OFDM transmission schemes may result in a downlink physical layer similar to previous generations of 5G in terms of, for example, modifications to pilot signal density and location.
[0093] For 5G systems, 5G NR access may use waveforms other than OFDM.
[0094] A reference signal (RS) may refer to any reference signal, preamble, or system signature that may be received and / or transmitted by a WTRU, e.g., for one or more purposes described herein. Different RSs may be defined for downlink (DL) and uplink (UL) transmissions. For example (e.g., in DL), a reference may correspond to a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a synchronization signal, or a beam reference signal (BRS), etc. For example (e.g., in UL), a reference signal may correspond to a sounding reference signal (SRS), a demodulation reference signal (DMRS), a preamble, or a beam reference signal (BRS), etc.
[0095] 5G systems can support data transmissions with different requirements (e.g., in terms of latency, throughput, and reliability), which may result in different processing principles and transmission properties. In an example, data (e.g., associated with ultra-low latency and / or ultra-reliable use cases) can be transmitted using (e.g., very) short transmission time intervals (TTIs), such as by using micro-slots (e.g., using x symbols and / or a first digital configuration) within slot-based framing (e.g., each TTI has a modest payload). Data (e.g., associated with mobile broadband or massive MTC use cases) can be transmitted using longer TTIs (e.g., to reduce control channel overhead), such as by using slot-based transmissions (e.g., using y>x symbols and / or using a second digital configuration).
[0096] Data (e.g., data associated with ultra-low latency or ultra-reliable use cases) may be sent with very tight delays from the time it is generated from the application layer. Delaying data transmission until the end of an ongoing transmission using a larger TTI may be unacceptable. For example, given that delay-sensitive traffic may be sporadic, reserving dedicated resources may be inefficient. Next-generation (e.g., 5G) wireless systems may support transmission of delay-sensitive data in resources used for ongoing transmissions while maintaining robust performance for both transmissions.
[0097] Code block based hybrid automatic repeat request (HARQ) processing may be supported. Block based coding may be used (e.g., further) to encode data contained in a transmission (e.g., which is sent as a transport block (TB)). A TB may contain one or more code blocks (CBs) associated with one or more MAC PDUs. Block based coding may be used, for example, to isolate and / or limit transmission errors and / or puncturing events to a specific portion of a transmission, for example, to improve decoding efficiency and minimize retransmissions. Block based coding may include mapping code blocks to code block groups. The mapping may be performed in frequency, time, and / or a combination of frequency and time. The mapping may be indicated in control information. For example, a wireless communication network may have a processor that is configured to determine the mapping and may send the mapping to a WTRU in downlink control information. The WTRU may have a processor that is configured to monitor a DCI and receive the DCI, receive a downlink transmission with a code block, and attempt to decode the code block using the mapping received in the DCI.
[0098] The HARQ feedback may be generated by a HARQ process, for example, based on a reception result of a transmission of (e.g., one) TB. For example, the WTRU may have a processor configured for HARQ feedback and may determine the HARQ feedback based on attempting to decode a code block of a code block group using a mapping received on a DCI. The WTRU processor may be configured to send a NACK to the wireless communication network if the decoding is unsuccessful and to send an ACK if the encoding is successful. The wireless communication network may have a processor configured to resend the mapping of the code block to the code block group if the processor determines that a NACK is received from the WTRU. In an example (e.g., when block-based encoding is used), the HARQ feedback may be generated at a higher granularity (e.g., per CB), at the expense of a higher overhead (e.g., an increased number of feedback bits) to transmit such feedback.
[0099] The generation and transmission of HARQ-related feedback may be improved. For example, the improvements may be useful when block-based coding is used and / or when puncturing events may occur in the system.
[0100] The feedback process is applicable to many use cases, technologies, and scenarios.
[0101] In an example, a first transmission may be initiated. The first transmission may be performed using at least a portion of physical layer resources. The one or more resources may correspond to at least a portion of physical layer resources associated with a second transmission.
[0102] The first transmission may be, for example, a "punctured" transmission, an "interference" transmission, a "delay-sensitive" transmission, or a "mini-slot" transmission. The second transmission may be, for example, an "ongoing" transmission, a "best-effort" transmission, or a "slot-based" transmission.
[0103] The first and second transmissions may be sent by the same entity or different entities. The first and second transmissions may be received by (or intended for) the same entity or different entities. The first and second transmissions may be downlink or uplink transmissions, which may be part of an infrastructure (e.g., cellular system) based transmission. The first and second transmissions may be direct WTRU-to-WTRU transmissions (e.g., sidelink type transmissions).
[0104] The (eg, each) entity may be part of, for example, a WTRU or a network infrastructure node.
[0105] The feedback process may be associated with a specific aspect, process and / or component of the radio access.
[0106] The WTRU may apply (e.g., having a processor configured with executable instructions) a feedback process based on one or more of the following: for example, (i) a digital configuration, a spectrum operation mode (SOM), and / or its configuration associated with the transmission (e.g., a set of resources, carriers, subcarrier spacing, symbol duration, priority associated with specific data, TTI duration, framing (e.g., time slot based, mini-time slot based), etc.); (ii) physical layer resources associated with the transmission; (iii) control channels and / or one or more related characteristics associated with the transmission and / or physical layer resources ( (e.g., RNTI, position in terms of search space, or CCE, etc.); (iv) receiving downlink control information, such as an explicit request for a specific method to be applied (e.g., no HARQ feedback), a first reporting method, or a second reporting method; (v) reference and / or demodulation signals related to the transmission; (vi) a configuration received by an upper layer (e.g., a configured feedback and / or transmission mode); (vii) a configuration associated with one or more HARQ processes (e.g., including a group of processes), which may include an applicable soft combining process (e.g., incremental redundancy or catch-up combining).
[0107] A (e.g., NR) system may support soft combining for HARQ processes, which may include multiple processes, such as incremental redundancy or chase combining. In an example (e.g., for a given HARQ process using incremental redundancy (IR)), for a given TB, HARQ retransmissions may be performed using a different number of bits (TBS) relative to a previous transmission of the same TB. For example, given the soft combining mode of operation with IR, a different number of bits may be used. This may be the case for turbo coding (e.g., as may be used for LTE) or (variable-sized) LDPC (e.g., as may be used for NR). WTRU buffering and processing may be higher for coding (UL) and soft combining (DL). HARQ retransmissions with IR may have different values and / or combinations for one or more of TTI duration, PRB allocation, MCS, etc., which may result in the same or different TBS. In an example (e.g., for a given HARQ process using chase combining), (e.g., any) HARQ transmissions associated with the HARQ process and the same TB may use the same number of bits (TBS). The scheduler may determine whether IR or chase combining may be used and may determine the TTI for a given HARQ process for a given TB (or whether the transmission is a slotted transmission or a mini-slotted transmission). The WTRU may receive signaling to this effect and may make an appropriate determination for (e.g., each) transmission. The WTRU may handle the HARQ processing timeline in terms of granted UL transmissions and the HARQ feedback timeline (e.g., accordingly).
[0108] An example process is provided for generating receiver feedback information.
[0109] Different types of feedback may be generated at different times.
[0110] In one example, a WTRU may be configured (e.g., for downlink transmission) to generate and / or send uplink control information according to the configuration of the WTRU. The configuration may include programming a processor with HARQ-related parameters, such as the type of soft combining processing to be applied, the HARQ operation point for a given HARQ process, one or more reference transmissions (e.g., the type of HARQ-related feedback for controlling one or more transmissions of the HARQ process), and / or feedback suppression parameters, such as one or more specific transmissions in a sequence associated with a given HARQ process or transport block (TB).
[0111] In (eg, alternative) examples, HARQ-related parameters may be expressed in terms of time (eg, in terms of TTI(s)) with respect to scheduling opportunities for HARQ processes, etc. For example, HARQ-related feedback may refer to feedback corresponding to a particular transmission associated with a HARQ process.
[0112] The target operating point may correspond to, for example, a target number x of transmissions(s) for a given HARQ process. target The WTRU may be configured (e.g., a processor programmed with the configuration) to report specific HARQ-related feedback, e.g., starting with a transmission corresponding to a configured value. This type of feedback may correspond to, for example, DM-based feedback, CSI-based feedback, CB-based feedback, or TB-based feedback.
[0113] The feedback type control parameter may be provided (eg, by the wireless communication network to the WTRU). The one or more reference transmissions for a given HARQ process may correspond to transmissions x in the sequence i_type The WTRU may be configured (eg, a processor programmed with the configuration) to enable and / or change the type of HARQ related feedback for downlink transmissions of the associated HARQ process. i_type The WTRU may be configured (e.g., a processor programmed with the configuration) to control switching of the type of feedback sent by the WTRU from one type to another. These feedback types may correspond to, for example, DM-based feedback, CSI-based feedback, CB-based feedback, or TB-based feedback.
[0114] The feedback suppression parameter may correspond to one or more values x threshold(e.g., from a set such as [1,2,3,infinity]). The value (e.g., 1, 2, or 3) may indicate (e.g., for downlink transmissions) that the WTRU may refrain from generating HARQ-related feedback and / or reports for an initial transmission (e.g., refraining until the first transmission), a first retransmission, or a second retransmission, respectively. The infinite value may indicate that the WTRU may send HARQ-related feedback (e.g., only) upon receiving (e.g., explicitly) control signaling requesting such feedback. The suppression parameter may be associated with a type of feedback (e.g., all) that may be applicable and / or configured for the relevant HARQ process or a specific type that may be applicable thereto. The type of feedback may correspond to, for example, DM-based feedback, CSI-based feedback, CB-based feedback, or TB-based feedback. The WTRU has a processor that is programmed to receive a feedback suppression parameter from a wireless communication network, read the feedback suppression parameter, and determine an action based on the received feedback suppression parameter. The wireless communication network may have one or more processors that are programmed to determine the feedback suppression parameter and send the parameter to the WTRU.
[0115] The configuration may have different granularities. The configuration may be different for an uplink HARQ process and a downlink HARQ process. A HARQ process may be specific to a given TrCH. A HARQ process may support transmissions according to different transmission durations (e.g., different numerical configurations), which may generally be referred to as TTIs. The configuration may be in addition to other (e.g., legacy) parameters (e.g., a maximum number of HARQ transmissions).
[0116] The WTRU may be configured (e.g., for downlink transmission) (e.g., a processor programmed with the configuration) to generate and / or send uplink control information based on a HARQ process state. The state may correspond to an aspect, such as a sequence in transmission for a HARQ process. The state may (e.g., also) correspond to a timing aspect, such as a maximum time that a HARQ process continues, etc. The state may correspond to, for example, a measured or estimated link quality, demodulation performance, or the number of successfully decoded code blocks.
[0117] A WTRU (e.g., a processor programmed with the configuration) may be configured using the feedback methods described herein for a subset of resources within a TB (e.g., and / or all resources). For example, the WTRU may be configured with a set of suppression parameters. For example, one or more (e.g., each) individual suppression parameters may be defined for different types of feedback for each sub-TB resource (e.g., each code block, or each group of code blocks) and / or for different sub-TB resources (e.g., for the same downlink transmission (retransmission)). For example, a first group of sub-TB resources may be configured with DM-based feedback, while another group of sub-TB resources may be configured with CB-based feedback. The WTRU may be configured (e.g., explicitly) (e.g., a processor programmed with the configuration) to report feedback for a specific subset of sub-TB resources. The WTRU report may correspond to feedback (e.g., DM-based feedback, CSI-based feedback, and / or CB-based feedback as further described below).
[0118] For example, if feedback is expected, the WTRU may expect (e.g., for uplink transmissions) to receive HARQ-related feedback using similar logic. For example, the WTRU may determine (e.g., a processor may determine) the format, content, and / or type of the feedback based on logic similar to the logic used to generate feedback for downlink transmissions.
[0119] The WTRU processor may receive configuration in downlink control signaling, which may allow dynamic control of feedback-related HARQ processing.
[0120] The feedback may be based on demodulation (DM) performance. For example, the WTRU processor may generate HARQ related feedback based on metrics related to demodulation performance.
[0121] The WTRU may be configured (eg, a processor programmed with the configuration) to generate HARQ-related feedback for physical transmission resources.
[0122] A set of physical resources associated with a transmission may be subdivided, for example, by resource regions. A resource region may correspond to a subset of resources in time, frequency, and / or space allocated to the transmission. In an example, a resource region may correspond to a subset of one or more PRBs on a particular symbol (or one or more portions thereof). For example, a resource region may correspond to a symbol (or a portion thereof). A region may (e.g., further) be associated with one or more demodulation reference signals (DM-RS).
[0123] Different parts of a transmission (eg, one or more code blocks or transport blocks) may be mapped to multiple resource regions. (Eg, each) part may correspond to a specific region.
[0124] The WTRU may determine, with the processor, that a downlink transmission is scheduled using a particular resource allocation. The WTRU may perform, with the processor, one or more actions upon receiving a transmission.
[0125] For example (e.g., upon reception), the WTRU processor may determine areas (one or more) for which a transmission may have been above a certain reception quality, which may be reported as positive feedback or measurements. The WTRU processor may determine which areas may otherwise be reported as negative feedback or measurements. This may be based on, for example, SINR measurements, decoding of individual CBs, or other metrics. The WTRU processor may make a determination based on, for example, relative DM-RS, signal strength, an estimate of how close the WTRU is to successfully decoding a portion of the transmission, based on individual (e.g., failed or successfully decoded) code blocks, etc.
[0126] For example (e.g., upon reception), the WTRU processor may determine that it failed to decode one or more (e.g., all) code blocks that may be mapped on the resource region, which may be reported as negative feedback. The WTRU processor may determine that it successfully decoded one or more (e.g., all) code blocks mapped on the resource region, which may be reported as positive feedback.
[0127] For example (e.g., upon reception), the WTRU processor may determine the region(s) for which transmissions are above a certain reception quality. The regions may correspond to symbols. Symbols may be reported as good quality or poor quality, which may be calculated as a function of SINR. For example, poor quality may be reported as negative feedback or as a measurement. For example, good quality may be reported as positive feedback or as a measurement.
[0128] The WTRU processor may report corresponding feedback for one or more areas (e.g., to the wireless communication network). The WTRU processor may report measurement values for one or more areas (e.g., areas of insufficient quality or all areas). The WTRU processor may report (e.g., to the wireless communication network) ACK / NACK bits per area or similarly. The reporting may be arranged by, for example, one or more processes as described herein.
[0129] In one example, the WTRU processor may (e.g., further) determine that more than x areas have insufficient quality. The WTRU processor may report feedback (e.g., to the wireless communication network), i.e., a single report for all areas. The WTRU may use a different reporting procedure (e.g., a TB-based procedure or a channel state indicator value). The WTRU processor may (e.g., alternatively) report more granularity (e.g., to the wireless communication network). The network scheduler may (e.g., based on the increased granularity) determine a resource allocation with a higher probability of successful decoding.
[0130] For example, given that demodulation-based measurements can be generated earlier than code block-based feedback or TB-based feedback, reporting may be useful for ultra-low latency services. SINR measurements may (e.g., further) provide probability information back to a transmitter (e.g., a scheduler). The transmitter may, for example, perform more efficient retransmissions when operating at an expected operating point (e.g., early in a transmission period of a transport block).
[0131] Feedback reporting based on demodulation performance may provide an indication to the scheduler of the confidence of the WTRU for decoding a TB or a portion of a TB (e.g., a sub-TB resource). The confidence (or likelihood or probability) of a decoding (e.g., correct decoding) may be fed back as a quantized value. For example, the WTRU processor may use x bits to report feedback based on demodulation performance. Each code point may correspond to a predefined confidence level.
[0132] Despite having a high confidence of correct decoding, the WTRU may not be able to decode the TB and / or sub-TB resources associated with the reported feedback. For example, after having received an indication of a high probability of decoding, the scheduler may not include the TB and / or sub-TB resources in future retransmissions. The WTRU processor may determine to maintain the feedback state (e.g., which may now be an absolute NACK) and / or any stored received soft data. Although no other transmissions (retransmissions) have been received since the previous feedback report, the network may instruct the WTRU to feedback the HARQ value for the TB and / or sub-TB resources. For example, the WTRU processor may receive a first transmission and may provide decoding confidence feedback for two sub-regions of the TB. The WTRU processor may determine that the first region has a high probability of correct decoding and the second region has a low probability of correct decoding. The indication that one region has a high probability of correct decoding and the second region has a low probability of correct decoding may trigger the scheduler to retransmit the data of the second region in the first retransmission, and the data of the second region may not be included in the first retransmission. The WTRU processor may then determine that the WTRU cannot correctly decode the first region. The wireless communication network may instruct the WTRU to feed back a HARQ report (eg, an absolute ACK / NACK type report) for the first region after a first retransmission, even though the first region itself may not have been included in the first retransmission.
[0133] Feedback based on demodulation performance may be determined based on measurements obtained from a demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS), other RSs, and / or measurements obtained from actual data transmissions. The WTRU processor may be configured with an association between reference measurement (or data measurement) resources and / or HARQ feedback.
[0134] The feedback may be based on code block (CB) decoding.For example, the WTRU processor may be configured to generate HARQ related feedback for (eg, each) code block (or group of code blocks thereof).
[0135] The WTRU processor may determine that feedback may not be generated for one or more code blocks (or resource regions), for example, the determination may be based on signaling and / or determination that the corresponding resources may experience interference (e.g., puncturing). For example, this may be useful when the transmitter (e.g., scheduler) may (e.g.) be aware of the pre-emption (e.g., due to the first transmission of some resources allocated to the second resource). In (e.g., another) example, the transmitter aware of the event may determine that feedback for the pre-empted CB may be ignored (e.g., applicable to puncturing) or enriched (e.g., applicable to superposition). The WTRU processor may make this determination, for example, based on whether a CRC for (e.g., each) code block is included. This may (e.g., implicitly) indicate the change to the receiver by, for example, discarding or masking the CRC per CB when the transmitter inserts the CRC at the beginning of (e.g., each) CB.
[0136] The WTRU processor may (for example, in this case) perform one or more of the following: (i) ignore feedback for the punctured CBs and provide single-bit feedback for all remaining CBs; (ii) provide enriched feedback per CB (or CB group) for the indicated CBs and provide single-bit feedback for all remaining CBs (superposition).
[0137] The enriched feedback may provide an ACK / NACK indication that may be generated for a single CB or for a CB group (CBG). The grouping of CBs may be configured or indicated by control signaling. For example, when TB multiplexing or multiplexing of CBs from different TBs may be supported, the grouping may be based, for example, on CBs mapped to different TBs in the same transmission. The switch between the enriched feedback and the single-bit feedback may be configured for each HARQ transmission (retransmission) number of a particular HARQ process. The enriched / multi-bit feedback may be based on, for example, an explicit index (e.g., a CBG index and the CBG index plus an offset therebetween, or an index for each CBG) and / or implicitly (e.g., based on feedback on an index of a PRB, a slot, a mini-slot, or a symbol) to determine the CB that is NACKed. There may be a bitmap of 1A / N bits per CBG. For example, the bundling size may be indicated by a prefix (e.g., a 2-bit prefix mapped to four possible bundling sizes).
[0138] The feedback may be based on transport block (TB) decoding.The WTRU processor may be configured to generate HARQ related feedback for (eg, each) TB.
[0139] The WTRU processor may be configured to generate HARQ-related feedback, for example, by combining two or more of the foregoing examples (and / or other examples) based on, for example, the HARQ process state and / or the DCI request(s). For example, the WTRU processor may generate different types of feedback: (i) for different HARQ entities (e.g., by configuration); (ii) for different HARQ processes (e.g., by dynamic control signaling, by applicable framing (e.g., slots or mini-slots)); (iii) for different uplink control channels (e.g., whether the feedback is on a common shared uplink control channel or on a dedicated transmission (with or without other data)); (iv) for different transmissions in a transmission (retransmission) sequence for a given HARQ process; and / or (v) as a function of an applicable soft combining process for a HARQ process.
[0140] The process may provide for transmission of receiver feedback. The WTRU processor may be configured to report HARQ related feedback in one of a plurality of payload arrangements. The feedback reporting process may be applied in conjunction with any of the feedback types described herein, for example, for feedback related to link quality (DM-based feedback) and / or for feedback related to resource regions or code blocks (CB-based feedback).
[0141] Additional information bits can be introduced, for example, using channel selection. y Selecting one of the possible uplink resources for feedback transmission may provide y additional bits of feedback information. In one example, this may be used to indicate the applicable report type.
[0142] Mode-based signaling (e.g., compression procedures) may be supported and may be based on, for example, CB, RE, and / or PRB mappings. The WTRU processor may be configured with one or more groups of elements. The elements may be resources (e.g., forming one or more resource regions) and / or code blocks (e.g., forming one or more subsets, such as one subset per TB when TB multiplexing may be supported for a given transmission). Resource regions and code block groups may or may not be mapped to each other.
[0143] The WTRU processor may (e.g., further) be configured with one or more modes. A mode may correspond to a group including one or more groups of elements. An element may be represented by one or more modes. (e.g., each) mode may be associated with a code point or an identifier.
[0144] For example, the WTRU processor may be configured with patterns. In an example, pattern 00 may represent elements 1, 3, 5, and 7 of a transmission (e.g., an element may be an indexed CB of a transmission or an indexed resource region of a resource allocation for the transmission). Pattern 10 may represent elements 0, 2, 4, and 6 of a transmission. Pattern 01 may represent elements 0-3 of a transmission. Pattern 11 may represent elements 4-7 of a transmission.
[0145] For example, when a variable number of bits can be reported, Huffman-based coding can (e.g., also) be used. A 1-bit root indicator can indicate reporting of all elements for a report type (e.g., an entire TB for a single TB per transmission). For example, when multiple formats can be defined for a given uplink control channel and / or channel selection can be configured for transmission of uplink feedback, a variable number of feedback bits can be supported.
[0146] The size, content and number of modes may (eg, further) be a function of dynamic scheduling information (eg, DCI). For example, the number of possible reporting modes may be a function of resource allocation size, or number of code blocks, etc. The determination may be based on a predetermined function.
[0147] The WTRU processor may generate HARQ related feedback. The (e.g., each) pattern may indicate what is being reported, or may (e.g., further implicitly) indicate a positive or negative acknowledgement of the relevant element of the report. In an example, the WTRU processor may determine the pattern to report in the feedback, for example, by selecting a pattern that minimizes the number of unnecessary retransmissions (e.g., a pattern that may include all negatively acknowledged elements and the fewest possible positively acknowledged elements).
[0148] This may be effective, for example, when a network configuration report for a WTRU with multiple modes may be based on a resource allocation strategy for puncturing events that may be coherent with those modes. For example, a coherent mode may include at least one mode corresponding to resources that may (e.g., only) be (e.g., will) be used for puncturing, and the scheduler may use those resources to schedule puncturing events (e.g., when necessary).
[0149] High-rate channel state information may (eg, also) be provided.
[0150] In (eg, another) example, the WTRU may receive downlink control signaling that may request feedback, for example, based on an indicated mode (eg, for an element of a relevant mode).
[0151] In (e.g., another) example, the WTRU may receive downlink control signaling that may request a retransmission that includes (e.g., includes only) elements of an indicated pattern, such as (e.g., only) code blocks of the relevant pattern for applicable TBs. For example, the WTRU processor may determine to include these elements (e.g., when multiplexing of CBs associated with different TBs is supported) when the transport block size indicated in the control signaling allows. The same HARQ process may be used. The CBs may (e.g., alternatively) belong to different HARQ processes, which may be indicated in the received control signaling.
[0152] In (e.g., another) example, the CB for retransmission can be derived (e.g., implicitly) based on, for example, a receiver indicating one or more of: (i) frequency domain parameters (e.g., an index of a PRB, a set of PRBs for each one or more enriched FB processes) and / or (ii) time domain parameters (e.g., an index of a slot, a mini-slot, a symbol). For example, a mini-slot indication can be used to notify the transmitter to retransmit all CBs mapped to the scheduled resources used on the mini-slot.
[0153] The receiver may determine the index based on, for example, demodulation performance, RS measurements, and / or (eg, explicit) decoding of the CRC per CB.
[0154] The WTRU processor may be configured to feedback HARQ reports for a pattern (e.g., entire TB, sub-TB, CB group, single CB, etc.), and the reports and / or patterns may be independent of their presence in the associated transmission (retransmissions). The WTRU processor may be configured to feedback HARQ reports for CBs (e.g., all CBs) of the original TB after the xth retransmission (e.g., when only a subset of CBs are included in the xth retransmission).
[0155] The signaling may be based on a reception state (eg, a suppression process). At least N blocks may be decoded, eg, to enable combining.
[0156] For example, the WTRU processor may be configured or instructed to report "at least N code blocks were decoded". This may be useful, for example, for a puncturing event to determine whether a code block that is known not to have been punctured can (e.g., should or must) be retransmitted. The scheduler may already know that the punctured code block should be retransmitted. N may be a function of the total number of code blocks C (e.g., C-1).
[0157] For example, combinations regarding processes may be provided based on HARQ process status and / or DCI requests.
[0158] The WTRU processor may indicate the resources associated with the feedback report.
[0159] The WTRU processor may be signaled to provide feedback for a set of sub-TB resources (e.g., a pattern, a CB group, etc.). The WTRU processor may determine a set of sub-TB resources to provide feedback resources (e.g., those sub-TB resources for which the WTRU needs to provide feedback resources). For example, the WTRU processor may have provided confidence-based feedback on some sub-TB resources in the past, and such feedback may still be valid or may still be invalid. The WTRU processor may determine whether to update the feedback report (e.g., depending on the feedback validity). The WTRU processor may include a resource identifier in the feedback report to indicate the purpose of the feedback report (e.g., each feedback report) to the scheduler. For example, the WTRU may send a confidence-based report for a CB (e.g., each CB) after transmission. The report may indicate the likelihood of correct decoding (e.g., a strong likelihood). The WTRU may be signaled to report feedback for some or all CBs for which it previously provided confidence-based reports. In the event that the WTRU processor successfully decodes a CB that the WTRU previously indicated that it could successfully decode, the WTRU may determine not to provide updated feedback. If the WTRU processor cannot decode a CB that the WTRU previously indicated it could successfully decode, the WTRU processor may provide a CB identifier and a NACK value. The WTRU may be signaled to provide feedback for all correctly decoded sub-TB resources (e.g., regardless of whether the WTRU has indicated an ACK). An identifier for a missing sub-TB resource may be used as an indication of a NACK for that sub-TB resource. The WTRU may be signaled to provide feedback for sub-TB resources whose HARQ ACK / NACK status has changed since its previous feedback report.
[0160] The WTRU processor may be configured, for example, to report according to a first reporting procedure for certain transmissions and according to one or more other reporting procedures for other transmissions (which may be for the same HARQ process and / or the same TB). This may be indicated, for example, in downlink control information and / or dynamically based on the WTRU's configuration.
[0161] For example, the WTRU processor may be configured to report DM-based HARQ-related feedback for one or more initial transmissions of a HARQ process. This may be useful, for example, to provide additional channel state information. The WTRU processor may (e.g., further) be configured to report CB-based feedback, for example, when it determines that no more than a threshold x of CBs have been successfully decoded. The WTRU processor may be configured to report (e.g., a single) HARQ ACK / NACK bit, for example, starting from another threshold (e.g., a configured operating point and above).
[0162] For example, when HARQ ACK may be applicable, the WTRU processor may (eg, alternatively) determine that a (eg, single) bit may be sent for TB-based reporting.
[0163] Figure 2 is an example of a transmission 200 that is punctured 201 due to a URLLC transmission and a different HARQ feedback type is expected at each retransmission. Figure 2 Different CBs 202, 204, 206, 208, 210, 212 are shown in FIG. During the first transmission 200, the second CB 204 and the third 206 CB are punctured to enable transmission of URLLC (e.g., transmission of URLLC to another WTRU). The WTRU processor may be configured to report feedback per region. The feedback may be confidence-based (e.g., DM-based) and / or absolute ACK / NACK-based feedback. For example, the WTRU processor may feedback a NACK for the first region and an ACK for the second region. In the first retransmission 214, the WTRU processor receives the CB for which it feedbacks a NACK (e.g., only the CB). The WTRU processor may be configured to perform feedback based on each CB. The second CB 204 and the third 206 CB may not have a combining gain (e.g., because they are punctured in the first transmission), so decoding may fail. In the third retransmission 218, the second and third CBs are transmitted (e.g., only the second and third CBs are transmitted). The WTRU processor may be configured to provide HARQ feedback per TB (e.g., because feedback per CB may use more resources and the gain associated with granular feedback may be limited by the number of CBs left to be retransmitted (e.g., few)). The WTRU may have a second retransmission 216. After the third retransmission 218, the WTRU processor may provide feedback ACK for the TB (e.g., the entire TB) and this may complete the process. In this example, the first feedback may utilize confidence-based feedback. The decoding confidence for the second region may be considered high, but the decoding may have failed, and the TB-based feedback for the second retransmission (216) may be configured for the entire TB, or for those sub-TB regions that still have active retransmissions (e.g., rather than regions without active retransmissions). The WTRU processor may be configured to provide feedback reports for previous confidence-based reports for different sub-TB regions (e.g., sub-TB regions where only active retransmissions exist).
[0164] The WTRU processor may be configured to report feedback for a set of DL transmissions. The set of DL transmissions may include transport blocks sent on any combination of: multiple component carriers (CCs), multiple bandwidth parts (BWPs), multiple time slots, multiple spatial layers, and / or multiple codewords. A WTRU (e.g., configured with multiple CCs) may have a large and varying amount of feedback to report at any time. Using a dynamic feedback codebook may reduce the overhead of semi-static configuration. If the transmission uses CBG segmentation and CBG feedback is utilized, the amount of feedback may be very large.
[0165] When determining feedback, the WTRU processor may determine whether the order in which the Ack / Nack (A / N) values are assigned in the feedback payload matches the order expected by the network. The DCI scheduling data may provide the WTRU with information about the order of feedback bits within the feedback report. The DCI may include a feedback bit counter DAI (e.g., which may replace or be in addition to a counter downlink assignment index (DAI)) that enables the WTRU to determine the order of a DL assignment among the total number of DL assignments that the WTRU may receive). The DAI may indicate to the WTRU one or more of: (i) the number of bits required to provide feedback for the DL assignment; (ii) the bit position at which the HARQ A / N bit for the DL assignment should be located in the feedback report; and / or (iii) the total number of feedback bits included in the feedback report.
[0166] The number of bits required to provide feedback for a DL assignment may be indicated. For example, the feedback may be for CBG-based feedback, and the WTRU processor may be configured with one or more feedback bits per CBG. The number of bits may be fixed across retransmissions of a TB (e.g., regardless of how many CBGs are in a particular retransmission); may depend on the number of CBGs present in the retransmission; and / or may indicate the number of feedback bits used per CBG feedback report.
[0167] The bit position of the HARQ A / N bits for the DL assignment in the feedback report may be indicated, for example, the network entity may signal this bit position information to the WTRU. For example, a first DL assignment may indicate to the WTRU that the position of the feedback report may start at bit '0'. A second DL assignment may indicate to the WTRU that the position of its feedback report may start at bit '5'. Such an indication may enable the WTRU to know how many bits are required for the NACK in the event that the first DL assignment DCI is lost.
[0168] The total number of feedback bits to be included in the feedback report (eg, the size of the feedback payload) may be indicated. The WTRU processor may determine the size of the feedback for the missing assignments and may adjust its payload to match the expected order at the network.
[0169] An example of a feedback bit counter is where the WTRU receives a first assignment with feedback bit counter = 0 and the feedback report within the grant may be 4 bits of information. The WTRU may expect that if it receives a second DL assignment, it should have feedback bit counter = 4. If the WTRU instead receives a DL assignment with a feedback bit counter greater than 4 (e.g., x), the WTRU processor may determine that it has missed the assignment and that the WTRU needs x-4 bits of feedback as NACK to maintain the appropriate feedback report size.
[0170] The feedback bit DAI may be indicated (eg, explicitly).The feedback bit DAI may be an index into a table of values that may be semi-statically provided to the WTRU.
[0171] The feedback bit DAI may be used as a supplement or as a replacement for the counter DAI in the DL assignment DCI.
[0172] The WTRU processor may determine from the counter DAI that it has lost one or more assignments. The WTRU processor may send a set of bits to the wireless communication network indicating a NACK of the maximum feedback size (or a configurable default size) required for one or more assignments that may have been lost. This may result in a mismatch with the expected feedback size at the network. The WTRU processor may indicate to the network that it has lost one or more DL assignments and padding must be used. The WTRU may indicate padding by using a bit flag. For example, the WTRU may send a single bit to indicate whether the assigned feedback size is obtained from the DCI (explicitly or implicitly) or whether the feedback size is a default value (due to no DL assignment being received).
[0173] The WTRU may have lost the last DL assignment (or the last set of assignments). There may be no starting position for the next set of feedback bits. The WTRU processor may not know the number of bits to NACK. The WTRU processor may use a maximum feedback size (or a configurable size). The WTRU processor may indicate to the network (e.g., by using a flag) that padding is used. The WTRU processor may use multiple bits to indicate the amount of padding.
[0174] The WTRU processor may use the DAI counter when scheduling data using a mix of timeslots and mini-timeslots. The WTRU processor may be scheduled for data transmission on regular timeslots, mini-timeslots (e.g., which have different sizes), and aggregated timeslots. The transmission duration may be semi-statically configured for each component carrier (or BWP for each component carrier). The transmission duration may be changed dynamically (e.g., for transmission within one component carrier or within one BWP of a component carrier).
[0175] The counter DAI or feedback bit DAI may be incremented in any order of BWP, CC, time and / or codeword. For example, the counter DAI or feedback bit DAI may be incremented in the order of BWP first, CC second, and time third. BWP and CC may be sorted using an index. The DAI may be incremented with the assignment in the BWP of the first CC, the assignment in the BWP of the second CC, and so on, and moved to the next time slot and repeated in the BWP / CC.
[0176] For different BWPs and / or CCs using different slot lengths or digital configurations, the incrementing may follow the same rules. For certain time instances, some BWPs and / or CCs may have scheduling opportunities. The DAI increment may be performed with the BWP of the CC and with the time scheduling opportunity (e.g., slot, mini-slot, symbol) of the subframe. The DAI increment may be performed with the BWP of the second CC and with the time scheduling opportunity (e.g., slot, mini-slot, symbol) of the subframe, and so on.
[0177] Bundled HARQ feedback can be used to reduce or fix the size of feedback for one or more DL assignments. Bundling can refer to combining (e.g., adding) feedback bits together to reduce the total amount of feedback bits. Examples of bundling may include one or more of the following: (i) CBG feedback bits can be bundled (e.g., one or more feedback bits for multiple groups of CBGs within one or more TBs can be combined together); (ii) feedback bits for multiple BWPs for a CC can be bundled together; (iii) feedback bits for multiple CCs can be bundled together (e.g., DL assignments scheduled in the same timeslot of different CCs can have bundled feedback); (iv) feedback bits for multiple timeslots or mini-slots can be bundled together (e.g., feedback bits for assignments in timeslots / mini-slots within a subframe can be bundled together); (v) feedback bits for multiple spatial layers can be bundled in together (e.g., spatial bundling) (e.g., the spatial layer can use CBG-based feedback, such as a fixed number of CBGs per layer, and spatial bundling can be achieved by: feedback of the first CBG of the first layer is bundled with feedback of the first CBG of the second layer, and so on, feedback of the second CBG of the first layer is bundled with feedback of the second CBG of the second layer, and so on, which can continue for CBGs of TBs in the same timeslot / microslot); (vi) feedback bits for multiple DL assignments on the same beam can be bundled together; and / or (vii) feedback bits for DL assignments for the same service (e.g., eMBB, URLLC, mMTC) can be bundled together.
[0178] Bundling rules may be configured (e.g., to ensure that the feedback bit string for a DL assignment may remain at a default and / or configurable value). Maintaining a fixed value for feedback for DL assignments may ensure that even if some DL assignments are lost, there is no ambiguity between what the WTRU intended to send and what the network believes it received as a feedback report. The fixed feedback value for each DL assignment may be less than the maximum value, in which case bundling may be used. The WTRU processor may be configured with a bundling method as described herein to achieve an appropriate feedback value. The feedback bits required for some DL assignments may be less than the fixed value. The WTRU may use repetition of feedback, or may use padding to achieve a fixed feedback bit string value.
[0179] The fixed feedback string value assigned per DL may depend on one or more of the following: (i) the PUCCH resources used to send feedback (e.g., the PUCCH format, e.g., feedback using short PUCCH may use a first value, while feedback using long PUCCH may use a second value); (ii) parameters of the data being transmitted (e.g., URLLC data may have a first feedback bit string value, while eMBB may have a second value and / or the digital configuration configured for the CC or BWP may determine the feedback bit string value); (iii) the number of CCs or BWPs configured and / or activated and / or the number of BWPs per CC; and / or (iv) the number of time slots, mini-time slots, or subframes for which feedback is reported in a single report.
[0180] Feedback may have unequal reliability. The WTRU processor may report feedback for two types of services to the wireless communication network in one feedback reporting instance. For example, the WTRU may be configured with URLLC data on a first CC and eMBB data on a second CC. The WTRU processor may use a single UL channel for feedback reporting. The required reliability of the components of the feedback report may vary. The WTRU processor may send the feedback report in a manner that can achieve the most stringent reliability requirements for multiple services. For example, power settings, multiplexing and / or PUCCH resource parameters (e.g., diversity capability) may be selected to ensure that the entire feedback report achieves the most sensitive feedback requirements.
[0181] Unequal error protection for feedback reports can be used. For example, the feedback bits of a feedback report can be divided into groups with similar reliability requirements. The feedback bits can be mapped to a specific set of resources for the feedback report - where a set of resources can achieve different reliabilities (e.g., depending on the reliability requirements of the feedback group). For example, the PUCCH can occupy multiple OFDM symbols, and some symbols can be sent with greater power than other symbols. Feedback bits that require higher reliability can be mapped to resources in symbols with greater transmission power. Feedback that requires higher reliability can be repeated on multiple resources within the PUCCH resources (e.g., in multiple hops of the PUCCH resources). Feedback that requires lower reliability may not be repeated on multiple resources within the PUCCH resources.
[0182] Feedback resource selection may be used. There may be conflicts in feedback reports for different DL assignments with different requirements. Feedback for URLLC may use a first set of PUCCH parameters, while feedback for eMBB may use a second set of PUCCH parameters. Multiple feedback reports may be multiplexed into a single feedback report. The WTRU may be configured with rules to determine the appropriate PUCCH resources for providing the multiplexed feedback reports. For example, the WTRU may use PUCCH resources associated with any DL assignment multiplexed in the feedback report, and / or the WTRU may use different PUCCH resources to send the multiplexed feedback reports.
[0183] All or a subset of the feedback reports may be multiplexed into a single feedback report. For example, a subset of feedback reports may be multiplexed where the resources for reliably sending URLLC service feedback reports may be so large that insufficient resources are available to implement multiplexing of eMBB service feedback reports. The WTRU processor may be configured with priority rules to determine what feedback may be included in a feedback report.
[0184] The WTRU processor may use the PUCCH resources indicated in a DL assignment (e.g., the last received DL assignment). For example, if the WTRU is time-multiplexing feedback reports for multiple DL assignments, the WTRU may use the PUCCH resources indicated in the DL assignment.
[0185] The WTRU processor may determine the number of information bits (eg, to set the reported transmit power).
[0186] The WTRU processor may determine the number of HARQ-ACK information bits (e.g., for setting the transmit power of a PUCCH transmission carrying the report and / or determining the number of modulation symbols carrying HARQ-ACK information (which may be multiplexed with data in a PUSCH transmission). The number of bits may be used as an input to a formula for power control of the PUCCH or for multiplexing in the PUSCH.
[0187] A transmission (PUCCH or PUSCH) may be configured to contain CBG-level and / or TB-level HARQ-ACK information for at least one PDSCH transmission. The at least one PDSCH transmission may be mapped on at least one resource defined at least in part by a carrier, a serving cell, a bandwidth portion, a time slot, and / or a micro-time slot. For example, the WTRU may be configured to report HARQ-ACK associated with two PDSCHs in two carriers (or serving cells) or in two time slots. The PDSCH may be configured to contain data from at least one TB.
[0188] Whether the WTRU reports CBG-level and / or TB-level HARQ (e.g., TBs for a given PDSCH transmission) may be indicated in the downlink control information (DCI). The WTRU processor or the network may encode this information by a bit sequence of the same value (e.g., 0 or 1), where the length of the sequence may correspond to the number of CBGs of a transport block or the maximum number of CBGs, which may be configured by higher layers. The WTRU processor and the network may determine to use a consistent codebook size. For example, when the WTRU detects that a DL assignment is lost (e.g., by using a counter DAI or other technique), the WTRU processor may include the same number of bits regardless of whether CBG-level or TB-level feedback is expected. To count the number of HARQ-ACK information bits, the WTRU processor may: (i) count single (1) HARQ-ACK information bits for TBs of received PDSCHs for which TB-level HARQ-ACK should be provided based on an indication from the DCI or a higher layer configuration; (ii) count single (1) HARQ-ACK information bits for TBs of PDSCHs that are detected as lost (e.g., by using a counter DAI or other technique) for which TB-level HARQ-ACK should be provided based on a higher layer configuration (e.g., regardless of an indication from the DCI); (iii) determine the number of TBs of the PDSCH based on the configuration (e.g., based on whether spatial multiplexing is configured for the PDSCH); and (iv) count the NCBGs for the TBs of the received PDSCH. (v) counting NCBG HARQ-ACK information bits for TBs of PDSCH detected as lost (e.g., by using a counter DAI or other technique) for which a CBG level should be provided based on a higher layer configuration; and / or (vi) counting NCBG HARQ-ACK information bits for TBs of PDSCH detected as lost (e.g., by using a counter DAI or other technique) for which a CBG level should be provided based on a higher layer configuration, where the WTRU is configured to determine whether to use a CBG level or a TB level based on an indication in the DCI. Even if the same codebook size is used, the WTRU can use sufficient but not excessive transmission power (or resource elements) for the transmission of HARQ-ACK for multiple PDSCHs including TB level or CBG level.
[0189] The WTRU processor may be configured to report sub-TB HARQ feedback. Such reporting may allow the scheduler to not repeat transmission of correctly decoded sub-TB resources (eg, CBs). This may limit system interference and / or improve spectral efficiency.
[0190] The retransmission may include a subset of the sub-TB resources (e.g., a subset of the original CBs). The remaining CBs may be mapped to the assigned resources in a similar manner as the first transmission. Figure 2 In the retransmissions in , the CB may be mapped to the same set of resource elements. The remaining resources may remain unused (eg, blank).
[0191] The remaining CBs may be concatenated and sent in adjacent resources of the assigned resource block. For example, in the case of retransmitting CB2 and CB4 of a TB, they may be mapped into adjacent resources (e.g., mapped into the first OFDM symbol of the assigned resources). The mapping of each CB or the remaining CBs of the concatenation may be explicitly indicated in the assignment for retransmission.
[0192] The WTRU processor may determine a modulation and coding scheme (MCS) for a retransmission (e.g., a new MCS compared to a previous transmission and / or a previous retransmission). For example, the WTRU processor may obtain the MCS for a transmission so that a greater number of resources are used for each retransmitted CBG. The WTRU processor may obtain the MCS from a downlink assignment for a CBG retransmission. The WTRU may be configured with a mapping function for the MCS based on one or more of: the number of retransmitted CBGs, the original (or previous) number of sent CBGs, and / or the original MCS.
[0193] The transmit power used for the retransmission of the CBG may be different from the previous transmission. For example, a change in transmit power may be beneficial for system interference and applicable to situations where the MCS has changed. The WTRU processor may determine that there is a change in transmit power for the retransmission, for example based on an indication explicitly included in the downlink assignment and / or implicitly based on the downlink assignment. For example, the WTRU processor may receive an indication from the gNB regarding a change in the relationship between the power of the demodulation reference signal and the data.
[0194] The CBGs of a TB may be indexed. In retransmissions, the retransmitted CBGs may be ordered by increasing or decreasing index and may be placed adjacent to each other. This may enable non-punctured data retransmissions. If the resource allocation for the retransmission is the same as a previous transmission or retransmission (which may have a greater number of CBGs), there may be a mismatch between the required number of resource elements and the resource elements available in the resource allocation. The resource allocation may be adjusted based on the number of CBGs being retransmitted. For example, the WTRU may be configured with a different (possibly smaller) set of PRBs for retransmissions, which may be, for example, a subset of the originally transmitted CBGs of the CBG being retransmitted.
[0195] Code blocks (CBs) or CBGs may be defined per symbol or set thereof. For example, CBG mapping may be performed first in the frequency domain and then in the time domain (e.g., frequency-first mapping). For example, a resource allocation may span 7 symbols (e.g., in time), and each of the 7 CBs or CBGs may span each subcarrier for a unique symbol (e.g., the first CB / CBG is sent in the first symbol, the second CB / CBG is sent in the second symbol, and so on). Transmissions may be configured so that no code block / CBG may span multiple symbols, and each symbol may include one or more code blocks / CBGs (e.g., each symbol may have an integer number of code blocks / CBGs). This may attempt to ensure that interference events occurring on an integer number of symbols have no negative impact on code blocks sent in adjacent symbols. The size of the code block may depend on the frequency span of the resource allocation. In a retransmission using a reduced resource allocation, a code block or CBG of the first transmission may be allowed to span multiple symbols. The WTRU may be configured to expect the transmitted CBGs (and / or CBs) to be re-segmented into (e.g., new) sets of CBGs (and / or CBs). For example, in a first transmission, the first code block may occupy the entire transmission bandwidth in the first symbol. In a retransmission over a reduced number of PRBs, the code block may now span two symbols. The code block may be segmented into two smaller code blocks, each spanning the frequency allocation of a single symbol. The code block segmentation may be taken into account when the WTRU feeds back the HARQ A / N for the retransmission. For example, the HARQ A / N may be common feedback for the two new code blocks, and / or a separate HARQ A / N feedback may be sent for each new code block.
[0196] The number of CBGs and / or the number of CBs per CBG and the resource mapping of CB / CBGs may depend on the allocation (e.g., the size of the frequency allocation, the timeslot size, etc.) and possibly some rules. These rules may be fixed or configurable by the network (and / or a combination of fixed and configurable). The number of CBGs may be obtained based on a one-to-one mapping with the number of symbols in the allocation. For example, a WTRU scheduled with data on a timeslot size of x symbols may be assumed to have y CBGs, where y=fct(x). For example, y=x, and each symbol is used for a single CBG. The number of CBGs may depend on the total number of subcarriers z. For example, if the number of subcarriers z is greater than a threshold, the CBG may consist of some or all of the resource elements of the symbol. If z is less than a threshold, the CBG may span multiple symbols. For example, when the interference is bursty in the time domain rather than in the frequency domain, it may be beneficial for the CBG to span as few symbols as possible. For example, the number of symbols spanned by a CBG (defined as s) can be obtained as s = floor (minimum_CBG_length / z), where minimum_CBG_length (minimum_CBG_length) can be fixed or configurable. In some cases, the frequency allocation z may be greater than a second threshold (e.g., t2), and in this case, multiple CBGs may be mapped to a single symbol. The total number of subcarriers z may be evenly divided across multiple CBGs. In an example, the CBG mapping on a symbol may be done in such a way that as many CBGs as possible use the maximum CBG length (e.g., t2). The number of CBGs per symbol y_s may be determined by y_s = ceiling (z / t2).
[0197] For example, in the case where the CBG consists of a single CB, the CB mapping can be similar to the CBG mapping. The CB to CBG mapping can be obtained based on the number of subcarriers and / or OFDM symbols assigned to each CBG. For example, the number of CBs in a CBG can be obtained based on the number of resource elements assigned to the CBG (e.g., if the assignment is continuous in time and frequency, the total number of subcarriers multiplied by the number of OFDM symbols). The resource elements assigned to the CBG can be evenly divided over a fixed number of CBs, or can be calculated in a manner that allows the maximum number of CBs to have a maximum length. For example, the number n of CBs in a CBG can be determined based on the maximum CB length (max_CB_length) and the total number w of resource elements in the CBG, such that n=ceiling(w / max_CB_length).
[0198] In one example, a TB may be divided into CBs in such a way that most CBs may have a maximum CB length. The group of CBs may then be grouped into CBGs. The grouping may be performed in such a way as to reduce the number of symbols spanned by the CBGs. For example, CB to RE mapping and CB to CBG mapping may be done first in frequency and then in time (e.g., first across the subcarriers of the first symbol, then across the subcarriers of the second symbol, and so on). CBs mapped to multiple symbols may be grouped into the CBG if the CBG does not yet include another CB mapped to multiple symbols.
[0199] In one example, a CBG may span several symbols in the time domain while occupying a more limited bandwidth in the frequency domain. This scenario may arise, for example, in the following situations: (i) when interference may (e.g., expected) span a bandwidth that may be smaller than the bandwidth that can be allocated for the transmission and / or (ii) when multiple preemptive transmissions (e.g., which have limited bandwidth and one or more limited durations) may occur or are occurring. The scheduler may (e.g., in the latter case) make the choice of allocating multiple preemptive transmissions in resources that could be occupied by a (e.g., a single) CBG, which may minimize the number of (e.g., required) CBGs to be retransmitted. The exemplary mapping in Figure 3 and 4 is shown in .
[0200] Figure 3 is an example of a CBG spanning multiple CBs in the time domain. Figure 3 ), the number of CBs spanned by a CBG in the frequency domain may be F=1.
[0201] Figure 4 is an example of a CBG spanning multiple CBs in the time domain. Figure 3 ), the number of CBs spanned by a CBG in the frequency domain may be F=2.
[0202] The WTRU processor may derive the CB to CBG mapping based on, for example, one or more of the following parameters: (i) the number of CBs (F) that the CBG may span in the frequency domain; (ii) the number of CBs that the CBG may span in the time domain; (iii) the number of CBGs used for transmission; (iv) the number of CBs in transmission; (v) the number of time symbols and / or resource blocks that may be occupied by transmission; (vi) the number of time symbols and / or resource blocks that may be occupied by a CB; (vii) the number of time symbols and / or resource blocks that may be occupied by potential pre-empted transmissions or interference, such as a mini-slot duration; and / or (viii) a set of one or more groups of time symbols and / or resource blocks that may correspond to time and / or frequency allocations for potential pre-empted transmissions or interference (e.g., a set of symbol indices that may correspond to a potential start of a pre-empted transmission).
[0203] The optimal process for mapping CBs to CBGs may vary depending on, for example, interference and channel conditions, the probability of preemptive transmissions occurring, etc. The mapping may be determined using, for example, one or more of the aforementioned parameters and / or other parameters. For example, the parameters may be configured by a higher layer. The parameters may be specific to a transmission profile that may be associated with the transmission. One or more parameters may (e.g., may also) be indicated in a field of a DCI that may be associated with the transmission, for example, to allow for more dynamic adaptation of the mapping to channel and traffic conditions.
[0204] A non-uniform CB to CBG mapping may be provided. In an example, the CB to CBG mapping may be configured such that the number of CBs per CBG of one or more CBGs may be significantly less than that of other CBGs. Such a CBG may be referred to as, for example, an "underloaded" CBG. In one example (e.g., when scheduling a preempted transmission may be required), the scheduler may prioritize preempting resources that may be occupied by code blocks of an underloaded CBG, and may prioritize avoiding preempting resources that may be occupied by code blocks of other CBGs. In the event that preemption occurs, the method may minimize the number of CBs that may need to be retransmitted. Underloaded CBGs and / or CBs that may be mapped to underloaded CBGs may occupy resources that may be spread out in the time domain, for example, to maximize the chance that the scheduler can find resources that may be occupied by underloaded CBGs (e.g., regardless of the time of the preempted transmission). Figure 5 An example is shown in FIG.
[0205] Figure 5A is an example of time and frequency mapping of code blocks to code block groups. Figure 5AExamples of time-first and frequency-first mapping of code blocks to code block groups are shown. The mapping of code blocks to code block groups can be determined based on expected interference or puncturing of the transmission. For example, if interference or puncturing is expected to span a limited area in the frequency domain, the transmitted code blocks can be mapped to code block groups in a frequency-first manner. An example of frequency-first mapping is shown in FIG. Figure 5A , and is labeled "frequency first". In the frequency first example, interference is expected to exist for the frequencies associated with the shaded code blocks (502), so the code blocks are mapped to code block groups based on frequency. In another example, if interference or puncturing is expected to span a limited area in the time domain, the transmitted code blocks can be mapped to code block groups in a time first manner. An example of time first mapping is shown in FIG. Figure 5A , and is labeled "time-first". In the time-first example, it is expected that the shadow code blocks (504) will have interference, so the code blocks are mapped to code block groups based on time. The type of code block to code block group mapping can be indicated in the downlink control indication (DCI). The type of code block to code block group mapping can be changed to adapt to changing interference conditions and expected interference types.
[0206] Figure 5 is an example of a non-uniform CB to CBG mapping that allows minimizing retransmitted CBs in the event of pre-emption. In the example, (e.g., each) rectangle may represent a CB. CBGs #4, #5, and #6 may be underloaded. In the example, it may be necessary to schedule high priority traffic on a mini-slot with 2 symbols. For example, depending on the timing of the high priority transmission, the scheduler may choose to schedule the transmission on the resources of CBG #4, #5, or #6. In one example, only 2 CBs may need to be retransmitted (e.g., subsequently) for a TB.
[0207] For example, the WTRU processor may be configured with one or more of the following parameters (e.g., to determine an appropriate mapping): (i) a target number of CBs for an underloaded CBG; (ii) a target number of CBs for a normal (not underloaded) CBG; and / or (iii) an indication of the CBs to be mapped to the underloaded CBG. For example, the indication may include a set of resources that may be allocated to the CB (e.g., in the frequency domain and / or time domain). For example, the indication may include an explicit list of CBs. For example, the indication may include at least one parameter that may be used in a formula from which a CB to CBG mapping for a normal CBG and an underloaded CBG may be derived.
[0208] A CB to CBG mapping indication may be provided. The WTRU processor may be configured with multiple CB to CBG mappings (e.g., uniform and non-uniform). For example, upon receiving an indication from the network, the WTRU processor may determine which mapping may (e.g., should) be used.
[0209] An explicit indication can be provided to the WTRU by a wireless communication network. In an example, the WTRU processor can receive an explicit indication that can point to (e.g., a) configured mapping. For example, DCI signaling can be used to send the indication. For example, the indication can be sent at the start of a time slot / micro-slot. The DCI can be common (e.g., group common PDCCH or within a group common search space) or WTRU-specific.
[0210] An implicit indication can be provided. In an example, the gNB can implicitly indicate, for example, the CB to CBG mapping. The gNB can provide, for example, a preemption indication, an indication of potential preemption resources, and / or a time pattern indication.
[0211] In an example of a preemption indication, the WTRU can receive information about the frequency / time resources being preempted. The WTRU can group the CBs according to the indication. In an example of a WTRU that may be configured with 2 CBGs, for example, when the WTRU may not receive a preemption indication, the WTRU can evenly map the CBs to the CBGs. The WTRU can receive a preemption indication. The WTRU can map the CBs within the frequency / time resources that may be preempted (e.g., according to the preemption indication) to the first CBG and the remaining CBs to the second CBG.
[0212] In an example of an indication of potential preemption resources, the WTRU processor can be configured (e.g., by the indication) with the resources (e.g., potential) that will be used for preemption. The WTRU can map the CBs within the indicated resources to separate CBG(s). In an example, the WTRU processor can be configured with K potential resources for preemption and N CBGs, where K can be less than N (e.g., K < N). For example, the first K CBGs can be formed by the CBs that can respectively correspond to the K potential resources. The remaining (e.g., N - K) CBGs can be formed, for example, evenly from the other CBs.
[0213] In an example of a time pattern indication, the WTRU processor can apply a (e.g., a) configured mapping according to the time pattern. In an example of "bad" channels that can be time-correlated, the CBs with bad channel conditions can be grouped into (e.g., a) CBG, while the remaining CBs can be grouped (e.g., evenly) into other CBGs.
[0214] Mini-slots for sub-TB retransmissions may be used. The size of the slot may be adjusted based on the number of CBGs being retransmitted. The WTRU processor may receive a DCI for retransmission from the wireless communication network that indicates the slot size for retransmission. The WTRU processor may implicitly determine the slot size (or transmission time interval) when it receives a DCI indicating a CBG for retransmission (UL or DL) (e.g., if the WTRU is configured such that each CB or CBG is mapped to a single, possibly continuous symbol). The WTRU may expect the PDSCH and RS mapping to follow the rules configured for the mini-slots (e.g., rather than the rules for the slot size used for the previous transmission (retransmission)). For example, the way in which the PDSCH and / or RS are mapped to resource elements may depend on whether the WTRU uses mini-slots and / or the length of the mini-slots.
[0215] The WTRU processor may be configured with DL control channel opportunities to monitor scheduling assignments (e.g., DCIs). For example, the WTRU may be configured with periodically occurring DL control channel opportunities, which may be associated with a fixed timeslot size (e.g., a regular timeslot size). In order to efficiently use mini-slots for retransmissions, it may be beneficial to schedule sub-TB retransmissions of multiple WTRUs in adjacent mini-slots. The WTRU processor may be indicated by the wireless communication network in the DCI for retransmissions in terms of symbols (or mini-slots) between the DCI and the data. For example, a WTRU processor may be scheduled in its regular DL control channel opportunity (e.g., at the beginning of a regular timeslot) for a transmission that may have a shorter duration. Another WTRU processor may also be scheduled in its regular DL control channel opportunity, however the WTRU may be indicated a symbol offset for the beginning of its DL assignment for sub-TB retransmissions.
[0216] The WTRU processor may be configured with a first set of DL control channel opportunities for scheduling first transmissions and / or full TB retransmissions, and a second set of DL control channel opportunities for scheduling sub-TB retransmissions. The second set of DL control channel opportunities may enable mini-slot scheduling with a greater number of possible starting symbols.
[0217] To save power, the WTRU processor may monitor (e.g., only) the first set of DL control channel opportunities until instructed to monitor the second set of DL control channel opportunities or autonomously determine to monitor the second set of DL control channel opportunities. For example, the WTRU processor may be notified by the wireless communication network in a DCI in the first DL control channel opportunity to start monitoring the second set of DL control channel opportunities. In an example, the WTRU may start monitoring the second set of DL control channel opportunities upon receiving a pre-emption indication from the gNB. The pre-emption indication may be received by the WTRU in the first set of DL control channel opportunities (possibly in the next DL control channel opportunity that occurs immediately after the pre-emption occurs). The first DL channel opportunity of the second set that the WTRU processor may monitor may be the first DL channel opportunity after receiving the pre-emption indication, or may occur at a (e.g., configurable) time offset after receiving the pre-emption indication. In the example of the WTRU autonomous determination, the WTRU may start monitoring the second set of DL control channel opportunities once the feedback has a sub-TB HARQ with a mix of ACK and NACK. For example, if the WTRU feeds back ACKs for a subset of CBGs (e.g., some CBGs are NACKed), the WTRU processor may start monitoring a second set of DL control channel opportunities (e.g., to enable mini-slot scheduling of CBG retransmissions). The WTRU may monitor the second set of DL control channel opportunities until instructed to stop by the gNB. The WTRU may monitor the second set of DL control channel opportunities until the retransmission of one or more HARQ processes that triggered the monitoring is completed.
[0218] The second set of DL control channel opportunities may be distinguished from the first set of DL control channel opportunities by one or more of: (i) different opportunities in time (e.g., different symbol positions within a timeline, or different positions within a subframe); (ii) different positions in frequency; (iii) different control resource sets (CORESETs); (iv) different search space subsets within a CORESET; and / or (v) different beams. For example, the WTRU may receive a first transmission on a first beam and any retransmissions on a second beam (e.g., a beam with a narrower beamwidth).
[0219] After being instructed or autonomously determining to switch to the second set of DL control channel opportunities, the WTRU may expect any downlink assignments (for first transmission or retransmission) sent within the set of DL control channel opportunities. For example, the second set of DL control channel opportunities may be a superset of the first set of DL control channel opportunities. The WTRU processor may be configured to keep the total number of blind decoding attempts per time period fixed. Once the DL control channel opportunities are increased in time, the WTRU may reduce them in frequency, CORESET and / or search space.
[0220] After concatenating and mapping the CBs to a smaller set of symbols, the scheduler can leave the remaining resources unused (e.g., blank). The scheduler can adjust the slot size to the number of CBs to be retransmitted. The scheduler can limit the amount of unused resources, and this can improve spectral efficiency.
[0221] The scheduler may include a new TB (or a set of sub-TB resources of the new TB) in the remaining unused resources. The new sub-TB resources may belong to the new TB or to the same TB of an ongoing HARQ process. As an example of a new sub-TB resource belonging to a new TB, a DL transmission may include a CB of a first TB that is retransmitted together with a CB of a second TB (e.g., which is sent for the first time, or is retransmitted but has a different retransmission number TB (e.g., RV number)). As an example of a new sub-TB resource belonging to the same TB of an ongoing HARQ process, the first transmission may include a subset of CBs of a TB (e.g., all CBs), and the retransmission may include a combination of the retransmitted CBs from the first transmission and a set of CBs that are also transmitted for the first time and belong to the same TB. A TB may be mapped to multiple time slots, and the retransmission number of each CB per time slot may be independent.
[0222] The WTRU processor may be configured (e.g., where a timeslot is used to send different portions of different TBs) to provide HARQ feedback for any of: portions of each TB (e.g., sub-TB feedback similar to CB group level feedback), each TB (e.g., per-TB feedback for each TB), and / or bundled TBs (e.g., multiplexed feedback for some or all TBs included in the timeslot). The HARQ feedback method for a single TB per timeslot may be reused for multiple TBs per timeslot. For example, the WTRU may provide WTRU-selected feedback by sending feedback only for TBs with ACKs within the timeslot.
[0223] An indication of the index of the CBG being retransmitted may be used. There may be a mismatch between the CBG for which the WTRU feeds back a NACK and the CBG being retransmitted. The mismatch may be due to incorrect decoding of the HARQ feedback by the gNB or a mismatch in available resources available for the retransmission (which may prevent the WTRU from receiving all retransmitted CBGs in a single retransmission). In this way, the CBG being retransmitted may be indicated in the downlink assignment (e.g., DCI) for the retransmission.
[0224] A bitmap covering the original CBGs included in the TB may be included in the retransmission scheduling assignment. Each bit in the bitmap may indicate whether a particular CBG is included in the retransmission. This may be prohibitive for large transmission bandwidths that require a large number of CBGs. The bitmap may need to be more adaptive when re-segmenting CBGs for retransmission. For example, the total number of CBGs sent (retransmitted) may be indicated to the WTRU and the CBG bitmap may be enabled to be correctly interpreted by the WTRU.
[0225] An implicit numbering of the CBG index in the first transmission (e.g., based on a frequency first and time second transmission order) and an explicit indication of the CBG index for retransmissions may be used. Compression methods such as those discussed for CBG-based feedback (e.g., pattern-based) may be reused for indicating retransmitted CBGs.
[0226] The WTRU may receive an indication to retransmit a CBG. Such indication may include a CBG index and may include an offset value. The offset value may indicate to the WTRU processor the starting point (e.g., resource element or CB) within the CBG at which the retransmission is being performed. The WTRU may not expect the retransmission of any RE of the CBG to be located before the point indicated by the offset value.
[0227] Timing between transmissions, retransmissions, and HARQ feedback may be used. The timing relationship between a transmission and HARQ feedback for the transmission may be indicated in a scheduling assignment. The timing may be in units of the slot size used to schedule the transmission. However, in the case where the size of the slot used for the retransmission is different from the slot used for the previous transmission (retransmission) of the same HARQ process, there may be inconsistencies in the interpretation of the timing offset. The timing offset between a transmission (retransmission) indicated to the WTRU and its HARQ feedback may always be in units of the slot size used for the original transmission of the HARQ process or in units of the slot size of the corresponding transmission (retransmission) associated with the HARQ feedback. The timing offset between the feedback for a transmission (retransmission) and the first DL control channel opportunity (where the WTRU may receive scheduling from the wireless communication network for another retransmission of the HARQ process) may also be in units of the slot size used for the original transmission or the most recent transmission (retransmission).
[0228] Soft combining of the soft data transmitted (retransmitted) may be beneficial and / or may improve decoding performance. The WTRU may be indicated by the wireless communication network whether the retransmitted CB (or sub-TB resource) may be combined with one or more previous transmissions (retransmissions) of the CB (or sub-TB resource). The subset of the retransmitted CB may be suitable for combining with the same CB sent in the first subset of the previous transmission (retransmission) (e.g., all previous transmissions (retransmissions)). Another subset may be combined with the second subset of the previous transmission (retransmission). For example, the WTRU may receive an original transmission and a first retransmission about a set of CBs from the wireless communication network. Upon receiving the second retransmission of the same set of CBs, the wireless communication network may indicate that the WTRU may combine the subset of the CB with the CB received in the original transmission (e.g., only with it) (e.g., not with those received in the first retransmission). This may be beneficial if puncturing of the CB subset occurs in the first retransmission. Combining with punctured resources may reduce BER performance and may result in unnecessary large retransmissions (or completely failed transmissions).
[0229] The ability to combine data of a TB (or sub-TB resource) on different transmissions (retransmissions) may be indicated dynamically. For example, the assignment of a DL transmission (retransmission) may include an indication of a list of previous transmissions that may be combined with a TB or sub-TB resource. The indication may be implicit. An example of an implicit indication may be whether to request feedback on previous transmissions from the WTRU. For example, requesting feedback on a TB or sub-TB resource may indicate to the WTRU that it may use it for combining. In another example, if no indication of a puncturing event is provided to the WTRU, the WTRU processor may determine that the data may be combined with other transmissions (retransmissions).
[0230] The WTRU processor may determine (e.g., autonomously determine) a set of transmissions (retransmissions) for which the WTRU may perform soft combining (e.g., per sub-TB (e.g., CB) resource). For example, the WTRU processor may use a subset of the transmissions (retransmissions) based on expected demodulation performance. The WTRU processor may determine that the demodulation performance of one or more retransmissions is below a certain threshold and may discard soft data for one or more transmissions (retransmissions) associated with the resources on which the WTRU performs measurements.
[0231] UL retransmission of CBG can be performed by the WTRU processor.
[0232] The WTRU processor may (e.g., be required to) retransmit a subset of the CBGs sent in a previous transmission to the wireless communication network. The methods described herein for DL retransmissions of CBGs may also be applicable to UL retransmissions of CBGs. Thus, the methods described herein with respect to the DL may also be applicable to the UL, and these examples are not meant to be limited to a certain transmission direction.
[0233] When the WTRU blanks resources for a CBG that is not retransmitted, the WTRU processor may reallocate power to another ongoing transmission. For example, due to carrier aggregation or dual connectivity, the WTRU may have multiple UL transmissions. The UL power control may depend on the number of active transmissions. The WTRU processor may consider all active transmissions in a symbol to determine the appropriate power sharing between different UL transmissions. Due to zero-power transmissions of some CBGs on a carrier, different parts of the transmissions on other carriers are allocated different transmission powers. For example, if a zero-power transmission of a CBG on a first carrier is being performed, the WTRU processor may allocate the power normally used for the first carrier to transmissions on a second carrier.
[0234] An uplink interference camp indication may be provided. The indication may include intra-WTRU interference / camp
[0235] In an example, high priority / low latency data may arrive at a WTRU buffer. For example, the WTRU processor may interrupt an ongoing uplink transmission for lower priority data even after the network may have received part of the low priority data, for example, in a time slot. This type of event may be referred to as intra-WTRU "uplink preemption" where multiple transmissions originate from the same WTRU.
[0236] For example, the WTRU processor may notify the network of the uplink preemption so that the network may be aware that a portion of the data sent in the (e.g., current) timeslot may be used for a different transmission of higher priority data. The network (e.g., which is informed of the uplink preemption by the WTRU) may discard the lower priority data that may be sent on the interfered resources. This may be referred to as a preemption indication. The receiver may use the preemption indication, for example, to manage its HARQ soft buffers. In an example, the receiver may choose to flush or discard data that may be received on the indicated portion for low priority transmission. For example, the receiver may (e.g., may also) use the indication when a (e.g., subsequent) transmission may be received for the interfered data portion.
[0237] The WTRU may, for example, explicitly or implicitly indicate an uplink pre-emption event to the wireless communication network. The explicit indication may be in the form of a resource indication. For example, the indication may point to resources in the time domain, the frequency domain, or the time-frequency domain. The indication may (e.g., additionally or alternatively, e.g., in the context of code block based HARQ) point to one or more code blocks (CBs) or code block groups (CBGs) from a low priority transmission that may have been pre-empted (e.g., previously pre-empted).
[0238] The camp-on indication may be sent, for example, using a new UCI field within the PUSCH channel. For example, the UCI may be sent before the camp-on occurs or after the camp-on occurs. In (e.g., additional or alternative) examples, a (e.g., special) control channel (e.g., specific to high priority transmissions) may carry the indication, for example, before or after the camp-on event. In an example, a front-loaded PUCCH may accompany the high priority transmission, which may include the indication.
[0239] For example, by masking an additional CRC or by adding (e.g., special) bits, pre-emption can (e.g., may also) be an encoded part of the CB or CBG, e.g., to convey to the receiver that the CB or CBG may be (e.g., being) pre-empted.
[0240] The WTRU may (eg, may also) indicate a preemption event using, for example, an in-band indication, which may be linked to the type of uplink resources (eg, semi-persistent, grant-free, or scheduled) that may be used to send high priority data.
[0241] The indication may include inter-WTRU interference / pre-emption.
[0242] In an example, the WTRU may not have sufficient resources to send higher priority data. The WTRU may occupy and preempt resources used by other WTRUs that may be sending ongoing lower priority data. For example, interference may be indicated to other WTRUs that are occupying the medium so that they may temporarily suspend their ongoing transmission of lower priority data. This may be referred to as, for example, "inter-WTRU uplink preemption indication".
[0243] For example, inter-WTRU uplink camping indication may be implemented by allowing multiple WTRUs to use resource blocks for both low priority data and high priority data. For example, in high cell load scenarios (where resources may be occupied by lower priority data), camping indication may be useful.
[0244] An inter-WTRU uplink pre-emption indication may be attached to, for example, (e.g., each) resource. In an example, an RS may be sent on a portion of a PRB to occupy it, for example, when (e.g., only when) it is used to send higher priority data. A WTRU that may be using a shared resource may, for example, check whether the resource may be used by a higher priority WTRU (e.g., by sensing or decoding an RS that may be unique to each resource) before occupying the medium. For example, by sending an RS from a serving cell (e.g., which is masked by its cell ID) or by transmitting information on a downlink control channel, the network node may (e.g., additionally or alternatively) mark the use of a resource to other (e.g., hidden) WTRUs that may not detect the use of the resource.
[0245] The inter-WTRU uplink pre-occupancy indication may be indicated in different processes, for example, the pre-occupancy may be indicated without blocking a portion of the shared resource (e.g., separately). In an example, the inter-WTRU uplink pre-occupancy indication may be sent on or with the uplink control information (e.g., on the UCI portion of the PUSCH or on the PUCCH). The network may (e.g., then) indicate other WTRUs that may (e.g., seek to) occupy the medium to avoid or suspend their transmission(s). This may be communicated, for example, on a downlink control channel. For example, when the medium may no longer be occupied (e.g., occupied for one or more high priority transmissions), when a configured suspension timer expires, and / or when signaled by the network, the WTRU with the interrupted transmission may resume its transmission of lower priority data.
[0246] Each computing system described herein may have one or more computer processors (with a memory configured with executable instructions) or hardware to implement the functions described herein, including determining the parameters described herein and sending and receiving messages between entities (e.g., WTRU and network) to accomplish the described functions. The above process may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium to be executed by a computer and / or processor.
[0247] Systems, methods, and means for receiver feedback in a wireless system have been disclosed. The receiver feedback format, content, type, and / or timing may be determined based on, for example, a hybrid automatic repeat request (HARQ) processing state corresponding to, for example, a transmission sequence of a HARQ process, a maximum time for which the HARQ process continues, a measured or estimated link quality, demodulation performance, and / or a number of code blocks successfully decoded. The receiver feedback format, content, type, and / or timing may be determined based on, for example, a configuration of a wireless transmit / receive unit (WTRU), which indicates at least one of: a type of soft combining process to be applied in the HARQ process, a HARQ operation point for the HARQ process, one or more reference transmissions for controlling the type of HARQ feedback for the HARQ process, and feedback suppression parameters for one or more transmissions in a sequence associated with the HARQ process or a transport block (TB). Uniform and non-uniform CB to CBG mappings may be provided (e.g., by a WTRU) based on, for example, one or more parameters, interference and channel conditions, and / or a probability of actually occupying a transmission. A CB to CBG mapping indication may be provided, for example, to support selection of a CB to CBG mapping from multiple CB to CBG mappings. Intra-WTRU and inter-WTRU interference / preemption indications may be provided.
[0248] The processes and approaches described herein may be applied in any combination, may be applied to other wireless technologies, and for other services.
[0249] WTRU may refer to an identity of a physical device, or to an identity of a user, such as a subscription-related identity, such as an MSISDN, SIP URI, etc. WTRU may refer to an application-based identity, such as a user name that may be used for each application.
[0250] The functions described herein may be implemented, for example, on a UR-LLC communication channel between a WTRU and a wireless communication system. The WTRU and the wireless communication system may have one or more computer processors configured (e.g., programmed with executable instructions) to perform the functions described herein. For example, the WTRU may have a processor configured to communicate with a wireless communication network (e.g., by using UR-LLC communication). The WTRU processor may be configured to receive a first downlink control information (DCI) indicating whether a hybrid automatic repeat request (HARQ) feedback based on a transport block (TB) should be provided for a downlink transmission, or whether a HARQ feedback based on a code block group (CBG) should be provided for a downlink transmission. The WTRU processor may be configured to receive a downlink transmission associated with a first DCI, the downlink transmission comprising a transport block having one or more code blocks. The WTRU processor may be configured to attempt to decode one or more code blocks of a transport block. The WTRU processor may be configured to determine that the first DCI indicates that HARQ feedback based on a CBG should be provided. If the processor determines that the first DCI indication should provide CBG-based HARQ feedback, the WTRU processor may be configured to determine a mapping of one or more code blocks to one or more CBGs; based on whether the corresponding code block of at least one of the one or more CBGs is successfully decoded, determine HARQ feedback for the at least one CBG, and send the HARQ feedback for the one or more CBGs to the wireless communication network. The WTRU processor may be configured to determine that the first DCI indication should provide TB-based HARQ feedback. If the WTRU processor determines that the first DCI indication should provide TB-based HARQ feedback, the WTRU processor may be configured to determine HARQ feedback for a transport block, and send the HARQ feedback for the transport block to the wireless communication network.
[0251] The mapping may be a mapping of the one or more code blocks to the code block group in at least one of frequency or time. The mapping may be based on one or more of: the number of subcarriers or OFDM symbols assigned to the code block group or the transmission, a maximum code block length, the number of code block groups in the transmission, the number of code blocks in the transmission, and the number of time symbols and / or resource blocks occupied by a potential pre-empted transmission.
[0252] The determined HARQ feedback for the one or more CBGs may be an ACK if each of the corresponding code blocks is successfully decoded, and the determined HARQ feedback for the one or more CBGs may be a NACK if one or more of the one or more code blocks are not successfully decoded. The WTRU processor may be configured to receive a retransmission from the wireless communication network in response to the sent NACK. The wireless communication network may have a processor configured to receive the sent ACK or NACK and determine to send a retransmission if a NACK is received.
[0253] The WTRU processor may be configured to receive a second DCI for a retransmission. The second DCI may indicate which CBGs are being retransmitted. The second DCI may indicate which CBGs included in the retransmission may be combined with previously received CBGs when performing soft decoding. The second DCI may include a bitmap that may be used to indicate which CBGs included in the retransmission may be combined with previously received CBGs when performing soft decoding. The wireless communication network may have a processor configured to determine to send the second DCI and the content of the second DCI.
[0254] The WTRU processor may be configured to monitor the first downlink control information and monitor the second downlink control information based on a camp-on instruction from a wireless communication network.The wireless communication network may have a processor configured to determine to send a camp-on instruction to the WTRU.
[0255] The WTRU may include a HARQ buffer. The WTRU processor may be configured to manage the HARQ buffer and discard data in the HARQ buffer if one or more code blocks are not successfully decoded.
[0256] The WTRU processor may be configured to determine a camp-on indication to send in uplink control information to the wireless communication network if one or more code blocks are not successfully decoded.
[0257] The wireless communication network may have a processor configured to determine to send first downlink control information (DCI) indicating whether a transport block (TB)-based hybrid automatic repeat request (HARQ) feedback should be provided for downlink transmission or whether a code block group (CBG)-based HARQ feedback should be provided for downlink transmission, and send the first downlink control information. The wireless communication network may have a processor configured to receive the sent HARQ feedback, the feedback including TB-based HARQ feedback.
[0258] Each computing system described herein may have one or more computer processors (with a memory configured with executable instructions) or hardware to implement the functions described herein, including determining the parameters described herein and sending and receiving messages between entities (e.g., WTRU and network) to accomplish the described functions. The above process may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium to be executed by a computer and / or processor.
[0259] The above-described processing may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include electronic signals (transmitted via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, buffer memory, semiconductor memory devices, magnetic media (e.g., internal hard disks and removable disks), magneto-optical media, and / or optical media (e.g., CD-ROM disks and / or digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, terminal, base station, RNC, and / or any host computer.
Claims
1. A wireless transmit / receive unit (WTRU), the WTRU comprising: A processor and a transceiver configured to: receiving configuration information including information indicating that a code block group (CBG) based type of hybrid automatic repeat request (HARQ) feedback should be provided by the WTRU, receiving first downlink control information (DCI) associated with a first downlink transmission, receiving the first downlink transmission comprising at least one transport block (TB), wherein the at least one TB comprises a plurality of CBGs, and wherein each of the CBGs comprises one or more code blocks (CBs), and In a case where the first DCI indicates that TB-type based HARQ feedback is to be provided for the first downlink transmission, first TB-based HARQ feedback associated with the first downlink transmission is sent, wherein the first TB-based HARQ feedback includes a number of bits corresponding to the number of CBGs of the first downlink transmission.
2. The WTRU of claim 1, wherein the number of bits of the first TB-based HARQ feedback associated with the first downlink transmission each have a first value.
3. The WTRU of claim 2, wherein the first value indicates whether the at least one TB of the first downlink transmission is successfully decoded.
4. The WTRU of claim 1 , wherein the processor and the transceiver are configured to: receiving a second DCI associated with a second downlink transmission; receiving the second downlink transmission comprising at least one TB, wherein the at least one TB comprises a second plurality of CBGs, and wherein each CBG in the second plurality of CBGs comprises one or more second CBs; and In a case where the second DCI indicates that the CBG-based type of HARQ feedback will be provided for the second downlink transmission, second CBG-based HARQ feedback associated with the second downlink transmission is transmitted, wherein the second CBG-based HARQ feedback includes a second number of bits corresponding to a second number of CBGs of the second downlink transmission.
5. The WTRU of claim 4, wherein a bit of the second CBG-based HARQ feedback associated with the second downlink transmission has a value indicating whether a corresponding CBG in the CBG of the second downlink transmission is successfully decoded.
6. The WTRU of claim 1 , wherein the processor is further configured to: determining, in at least one of a frequency domain or a time domain, a mapping of the CB to the plurality of CBGs of the first downlink transmission, and Wherein the first downlink transmission is received using the mapping.
7. A WTRU according to claim 6, wherein the mapping is based on one or more of: the number of subcarriers or orthogonal frequency division multiplexing (OFDM) symbols assigned to the multiple CBGs, the maximum code block length, the number of CBGs for the first downlink transmission, the number of CBs in the first downlink transmission, and / or one or more of: the number of time symbols or the number of resource blocks occupied by potential pre-occupied transmissions.
8. The WTRU of claim 1, wherein the first downlink transmission is associated with a HARQ process.
9. The WTRU of claim 1, wherein the first DCI comprises a bitmap, and wherein the bitmap indicates a CBG with which the first downlink transmission can be combined with a previously received CBG.
10. The WTRU of claim 1 , wherein the processor and the transceiver are configured to: Configuration information is received, the configuration information comprising information indicating a maximum number of CBGs per TB, and wherein the first TB-based HARQ feedback comprises a number of bits equal to the maximum number of CBGs per TB.
11. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising, receiving configuration information including information indicating that a code block group (CBG) based type of hybrid automatic repeat request (HARQ) feedback should be provided by the WTRU; receiving first downlink control information (DCI) associated with a first downlink transmission; receiving the first downlink transmission comprising at least one transport block (TB), wherein the at least one TB comprises a plurality of CBGs, and wherein each of the CBGs comprises one or more code blocks (CBs); as well as In a case where the first DCI indicates that TB-type based HARQ feedback is to be provided for the first downlink transmission, first TB-based HARQ feedback associated with the first downlink transmission is sent, wherein the first TB-based HARQ feedback includes a number of bits corresponding to the number of CBGs of the first downlink transmission.
12. The method according to claim 11, in, The number of bits of the first TB-based HARQ feedback associated with the first downlink transmission each have a first value.
13. The method according to claim 12, in, The first value indicates whether the at least one TB of the first downlink transmission is successfully decoded.
14. The method according to claim 11, further comprising: include: receiving a second DCI associated with a second downlink transmission; receiving the second downlink transmission comprising at least one TB, wherein the at least one TB comprises a second plurality of CBGs, and wherein each CBG in the second plurality of CBGs comprises one or more second CBs; as well as In a case where the second DCI indicates that the CBG-based type of HARQ feedback will be provided for the second downlink transmission, a second CBG-based HARQ feedback associated with the second downlink transmission is transmitted, wherein the second CBG-based HARQ feedback includes a number of bits corresponding to the number of CBGs of the second downlink transmission.
15. The method of claim 14, wherein the bit of the second CBG-based HARQ feedback associated with the second downlink transmission has a value indicating whether a corresponding CBG in the CBG of the second downlink transmission is successfully decoded.
16. The method according to claim 11, further comprising: include: determining, in at least one of a frequency domain or a time domain, a mapping of the CB to the plurality of CBGs of the first downlink transmission, and Wherein the first downlink transmission is received using the mapping.
17. The method according to claim 16, in, The mapping is based on one or more of: the number of subcarriers or orthogonal frequency division multiplexing (OFDM) symbols assigned to the multiple CBGs, the maximum code block length, the number of CBGs for the first downlink transmission, the number of CBs in the first downlink transmission, and / or one or more of: the number of time symbols or the number of resource blocks occupied by potential reserved transmissions.
18. The method according to claim 11, in, The first downlink transmission is associated with a HARQ process.
19. The method of claim 11, wherein the first DCI comprises a bitmap, and wherein the bitmap indicates a CBG with which the first downlink transmission can be combined with a previously received CBG.
20. The method according to claim 11, further comprising: include: Configuration information is received, the configuration information comprising information indicating a maximum number of CBGs per TB, and wherein the first TB-based HARQ feedback comprises a number of bits equal to the maximum number of CBGs per TB.
Citation Information
Patent Citations
Method for requesting retransmission, method for retransmission and devices thereof
CN102318254A
Methods and apparatuses for resource mapping for multiple transport blocks over wireless backhaul link
CN102742338A
Method and apparatus for channel resource mapping in carrier aggregation
CN102754381A
Method and apparatus for efficiently transmitting control information to support uplink multiple antenna transmission
CN102823184A
Acknowledgement bundling in a mimo communication system
CN102893551A
