PROCEDURE FOR PARTIAL RETRACTION

DE602017086042T2Active Publication Date: 2024-11-06TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
DE602017086042
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Priority Date
2017-02-06
Filing Date
2017-12-20
Publication Date
2024-11-06
Estimated Expiration
2037-12-20

AI Technical Summary

Technical Problem

Existing Hybrid Automatic Repeat Request (HARQ) mechanisms in wireless communication systems are inefficient as they require retransmitting entire transport blocks due to partial puncturing by Ultra-Reliable Low Latency Communication (URLLC) transmissions, leading to wasteful retransmissions and interference with longer Mobile Broadband (MBB) transmissions.

Method used

Implementing partial retransmission methods where receivers receive indicators for mapping coded bits to specific locations within the retransmission, allowing for selective retransmission of only incorrectly decoded code blocks, and allocating resources flexibly to minimize interference with URLLC transmissions.

Benefits of technology

This approach reduces unnecessary retransmissions, minimizes interference, and allows for more efficient use of resources by enabling flexible distribution of retransmission data and URLLC data within the same time interval, improving the reliability and latency of both MBB and URLLC services.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader
Need to check novelty before this filing date? Find Prior Art

Description

Related Applications

[0001] This application claims the benefit of provisional patent application serial number 62 / 455,279, filed February 6, 2017.Technical Field

[0002] The present disclosure relates to Hybrid Automatic Repeat Request (HARQ), Mobile Broadband (MBB), and Ultra-Reliable Low Latency Communication (URLLC) scheduling.Background

[0003] A Transport Block (TB) is data from an upper layer, e.g., from the Media Access Controller (MAC), that is given to the physical layer for transmission in a Transmission Time Interval (TTI). A TB may range in size from 16 bits to 36696 bits for a 10 Megahertz (MHz) Long Term Evolution (LTE) system. A TB may be split into Code Blocks (CBs), which have a maximum size of 6144 bits, meaning that the largest TB will have 7 code blocks. A TB Cyclic Redundancy Check (CRC) value is attached to the transport block. If a TB is divided into CBs, a CB CRC is attached to each CB.

[0004] In many wireless communications systems Hybrid Automatic Repeat Request (HARQ) retransmission is a method to mitigate unpredictable interference and channel variations. For downlink, when a wireless device attempts to decode a data message, the wireless device sends to the transmitter an indicator that indicates whether the decoding was successful or not. When the transmitter receives an indicator indicating unsuccessful decoding, the transmitter typically performs a retransmission of the data message, which the receiver typically will combine with the original received transmission. The combining is known as soft combining. Two well-known techniques for soft combining are "Chase combining," in which every retransmission contains the same information, and "incremental redundancy," in which every retransmission contains different information from the previous transmission, e.g., the retransmission contains only those portions of the original transmission that were not received correctly. The combining will greatly increase the probability of successful decoding.

[0005] In LTE the indicator indicating the result of a decoding attempt is known as a HARQ Acknowledgement (HARQ-ACK). For LTE up to two transport blocks (two data messages) may be transmitted in each Transmission Time Interval (TTI), which means that the HARQ-ACK may consist of 2 bits, where each bit indicates successful or unsuccessful receipt of the respective transport block.

[0006] LTE is a standard in the Third Generation Partnership Project (3GPP) family of wireless systems and is highly optimized for Mobile Broadband (MBB) traffic. The TTI in LTE is a subframe of 1 ms duration and the HARQ-ACK is, for Frequency Division Duplex (FDD), transmitted in subframe n + 4 for a data transmission in subframe n. Ultra-Reliable Low Latency Communication (URLLC) is data service with extremely strict error and latency requirements. Error probabilities as low as 10 -5< or lower and 1 ms end-to-end latency or lower are expected requirements.

[0007] Fifth Generation (5G) is currently being studied by 3GPP and is targeting a wide range of data services including MBB and URLLC. To enable optimized service, the length of TTI is expected to be different for different services, where URLLC may have a shorter TTI length compared to MBB.

[0008] It may then happen that, while a transmitter is in the middle of a MBB transmission, that transmitter may receive a URLLC data packet that is also to be transmitted. In this scenario, it may therefore be desirable for the transmitter to blank, i.e. interrupt, the MBB transmission in certain time-frequency resources and instead perform a URLLC transmission on those resources so that the URLLC transmission meets its latency and reliability requirements. This has the drawback that the wireless device receiving the partial or punctured MBB will likely fail the decoding, a situation which is handled by the HARQ feedback mechanism of retransmitting transport blocks that were not successfully received and decoded.

[0009] US2016 / 226643 A1 discloses partial retransmission of code block clusters and transmission of a different redundancy version of a code block cluster after receiving a NACK. The transmitter may group the code block clusters in segments of a transport block according to redundancy versions and send a control message to indicate the composition of the transport block.

[0010] WO2008 / 132599 A2 discloses methods for efficient retransmission.SummaryProblems with Existing Solutions

[0011] The problem with resolving the punctured Mobile Broadband (MBB) transmission with a retransmission is that even though the puncturing of the initial transmission (e.g., by an Ultra-Reliable Low Latency Communication (URLLC) transmission) affects only part of the data transmitted, the entire transport block must be retransmitted. That is, a relatively small puncturing transmission can cause the retransmission of a much larger MBB transmission, even though most of the MBB transmission was not punctured and received correctly. Furthermore, because the existing Hybrid Automatic Repeat Request (HARQ) feedback mechanism triggers retransmission of an entire transport block in the event of failure, and because a URLLC data packet may interrupt a longer MBB transmission at any time, this gives rise to the possibility that a relatively long MBB transmission is interrupted by a relatively short URLLC transmission, which causes the MBB transmission to fail. While the User Equipment (UE) is retransmitting the long MBB transmission, that transmission is again interrupted by a short URLLC transmission, which causes the entire MBB transmission to be retransmitted a second time, which may yet again be interrupted by yet another URLLC transmission, and so on. In other words, shorter URLLC transmissions can dramatically hinder successful transmission of longer MBB transmission. Such retransmission, and especially multiple retransmissions, is wasteful and additionally creates interference for other simultaneous data transmissions.

[0012] To address these problems, methods and systems for partial retransmission are provided herein, in which the wireless device receives an indicator indicating the mapping of coded bits (e.g., code blocks) to a location or locations in the retransmission, e.g., the mapping gives the receiver information about which subset or subsets of the coded bits will be retransmitted, and in which location of the retransmission each subset is located. The receiver can then receive the retransmission only in the indicated locations, and can attempt decoding the data packet together with soft information, if any, from the first transmission.

[0013] According to aspects of the present disclosure, a method for receiving, at a receiver, a partial retransmission from a sender, a receiver for receiving partial retransmission from a sender, a method of performing a partial retransmission by a sender, and a sender for performing a partial retransmission according to the appended independent claims are provided.Advantages of the Proposed Solution

[0014] Multi-bit HARQ feedback allows the receiver to indicate to the transmitter that certain code blocks could be decoded correctly while others could not, prompting the transmitter to retransmit the code blocks that were not decoded correctly. In the present disclosure, the UE is allocated with resources (a TTI with a number of symbols) for receiving a retransmission. However, a partial retransmission does not require all allocated resources (all symbols of the TTI), so the unused resources (symbols of the TTI) allocated for the retransmission can, e.g., be used for an URLLC transmission with shorter TTI. Furthermore, the sending node can distribute retransmission data and URLLC data on the allocated resources (the symbols of the allocated TTI) in a flexible way depending on the need, by using a mapping indicator to tell the UE on what symbols of the TTI to receive the retransmission data. This solution gives more freedom in the retransmission of erroneously received code blocks in that the locations of the retransmitted code block can be configured to minimize the probability of having to puncture the retransmission.

[0015] Embodiments described hereinafter which do not fall within the scope of the claims are to be interpreted as examples useful for understanding the invention.Brief Description of the Drawings

[0016] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure. Figure 1 illustrates one example of a wireless system (e.g., a cellular communications system) in which embodiments of the present disclosure may be implemented. Figure 2 is a flow chart illustrating an exemplary process for partial retransmission according to an embodiment of the present disclosure. Figure 3 illustrates an exemplary partial retransmission according to an embodiment of the present disclosure, in which a code block is retransmitted in subsequent symbols following the Downlink Control Information (DCI). Figure 4 illustrates an exemplary partial retransmission according to an embodiment of the present disclosure, in which a code block being retransmitted is distributed in such a way as to provide space available for use to transmit latency critical data. Figure 5 is a schematic block diagram of an exemplary wireless device according to an embodiment of the present disclosure. Figure 6 is a schematic block diagram of an exemplary wireless device according to another embodiment of the present disclosure. Figure 7 is a schematic block diagram of an exemplary network node according to an embodiment of the present disclosure. Figure 8 is a schematic block diagram of an exemplary network node according to another embodiment of the present disclosure. Figure 9 is a schematic block diagram of an exemplary virtualized embodiment of a network node according to an embodiment of the present disclosure. Figure 10 is a flow chart illustrating an exemplary process for partial retransmission according to another embodiment of the subject matter described herein. Detailed Description

[0017] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0018] Radio Node: As used herein, a "radio node" is either a radio access node or a wireless device.

[0019] Radio Access Node: As used herein, a "radio access node" or "radio network node" is any node in a radio access network of a cellular communications network that operates to wirelessly transmit and / or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node.

[0020] Core Network Node: As used herein, a "core network node" is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), or the like.

[0021] Wireless Device: As used herein, a "wireless device" is any type of device that has access to (i.e., is served by) a cellular communications network by wirelessly transmitting and / or receiving signals to a radio access node(s). Some examples of a wireless device include, but are not limited to, a User Equipment device (UE) in a 3GPP network and a Machine Type Communication (MTC) device.

[0022] Network Node: As used herein, a "network node" is any node that is either part of the radio access network or the core network of a cellular communications network / system.

[0023] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0024] Note that, in the description herein, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0025] Figure 1 illustrates one example of a wireless system 10 (e.g., a cellular communications system) in which embodiments of the present disclosure may be implemented. In the embodiment illustrated in Figure 1, the wireless system 10 includes a radio access node 12, and a wireless device 14.

[0026] Figure 2 is a flow chart illustrating an exemplary process for partial retransmission according to an embodiment of the subject matter described herein. In the embodiment illustrated in Figure 2, the process begins after a receiver (e.g., the wireless device 14), has received a first transmission from a sender (e.g., the radio access node 12). The receiver has determined that some portion or portions of the first transmission were not received correctly, and reported this fact back to the sender of the first transmission, e.g., via a Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgement (NACK). Multiple-bit HARQ feedback allows the receiver to indicate which portions or code blocks were correctly received (e.g., via a positive Acknowledgement (ACK) for those portions or code blocks) and which portions or code blocks were not correctly received (e.g., via a NACK for those portions or code blocks). In the examples detailed below, the sender is assumed to be the radio access node 12, but the present disclosure is not limited to just this. In alternative embodiments, for example, the sender may be another wireless device.

[0027] At step 100, the receiver receives a control information message indicating a second transmission to be received in a Transmission Time Interval (TTI) comprising a plurality of symbols, wherein the second transmission includes retransmitted data in a subset of the plurality of symbols of the TTI, the retransmitted data comprising a retransmission of a portion of the first transmission. In one embodiment, the control information message comprises a Downlink Control Information (DCI) message.

[0028] At step 102, the receiver receives the second transmission. The control information message may be sent separately from the second transmission or it may be part of the second transmission.

[0029] At step 104, the receiver determines, based on a mapping indicator indicating the subset of the plurality of symbols of the TTI, the location or locations of the retransmitted data within the second transmission. In one embodiment, the mapping indicator indicates the locations within the second transmission that will be occupied by the retransmitted data. In one embodiment, the mapping indicator indicates which portions of the first transmission occupy those locations within the second transmission. In one embodiment, the mapping indicator contains both information that identifies the portion(s) to be retransmitted and the location(s) in which the portion(s) will appear within the retransmission. This information - e.g., what portions of the first transmission appear in the second transmission and / or where they appear in the second retransmission - may be referred to as the "transmission format" of the second transmission. In one embodiment, the mapping indicator is a component of the DCI message. In one embodiment, the mapping indicator is provided via a mechanism other than the DCI message.

[0030] It is noted that, where the control information indicating that a second transmission is to be received comprises a DCI message, the DCI message may conceptually be considered to be part of the second transmission, e.g., the DCI message may be considered part of the "retransmission." Alternatively, the DCI message may be considered an entity separate from the retransmission, in which case the DCI message may be referred to as the "retransmission assignment."

[0031] At step 106, the receiver decodes the second transmission at the determined location(s) within the second transmission. In one embodiment, either the control signaling information or the mapping indicator may contain information that instructs the receiver whether the retransmitted data will replace the originally transmitted data or whether it will be soft combined with the corresponding portion of the first transmission. An example of such information is the Redundancy Version (RV) used in LTE.

[0032] It is noted that, in alternative embodiments, steps 102 and 104 may be fully or partially omitted. For example, in embodiments where the retransmitted portions are always located closest to the beginning of the retransmission, the receiver already knows the location of the retransmitted portions within the second transmission, in which case a mapping indicator is not needed, or, if a mapping indicator is used to identify the portion(s) being retransmitted, the mapping indicator need not also identify the locations of the retransmitted portions within the second transmission.

[0033] It is also noted that the subject matter described herein contemplates an embodiment in which the receiver is not informed which portions of the first transmission are being retransmitted - i.e., the sender presumes that, since the receiver notified the sender which portions of the first transmission were not successfully received, the receiver already knows what will be retransmitted by the sender. Such an embodiment, however, presumes that the HARQ NACK message (or whatever mechanism was used by the receiver to notify the sender of unsuccessfully received portions of the first transmission) was received by the sender without corruption. Since such corruption of the HARQ NACK message is theoretically possible, a more robust embodiment of the subject matter described herein identifies to the receiver which portions are being retransmitted; this allows the receiver to confirm that the HARQ NACK message information was correctly received by the sender.

[0034] In one embodiment, the receiver may try one or more hypotheses based on the HARQ NACK message, where one hypothesis may be that the HARQ NACK message may be corrupt. For example, the receiver may have sent two HARQ NACKs indicating incorrect reception of two parts. At reception of the retransmission, the receiver may try three hypotheses: (a) assume that both HARQ NACKs were NOT corrupted; (b) assume that the first HARQ NACK was corrupted but the second HARQ NACK was not corrupted; and (c) assume that the second HARQ NACK was corrupted but the first HARQ NACK was not corrupted.

[0035] Figures 3 and 4 graphically illustrate example retransmissions according to various embodiments of the subject matter described herein. In the embodiments illustrated in Figures 3 and 4, the Transmission Time Interval (TTI) of a transmission is divided into 7 symbols, where the first symbol contains a DCI and subsequent symbols are divided into pairs, each carrying one Code Block (CB), thus the Transport Block (TB) is divided into 3 code blocks.Embodiment: DCI Indication of Retransmitted CB

[0036] Figure 3 illustrates an exemplary partial retransmission according to an embodiment of the subject matter described herein, in which a CB is retransmitted in subsequent symbols following the DCI. In this embodiment, the receiver is already configured (by higher layers, or by specification) to always assume that CBs in retransmissions are located in subsequent symbols directly following the DCI, and in strict incrementing order. The DCI of the retransmission then contains an indication of which CB is present in the retransmission, and which RV is used.

[0037] In the embodiment illustrated in Figure 3, the receiver receives a first transmission 16 comprising a DCI followed by three code blocks, CB1, CB2, and CB3, represented in Figure 3 as pattern-filled boxes. The receiver indicates to the server, e.g., with a multi-bit HARQ feedback, that code blocks 1 and 3 were correctly decoded, but code block 2 was not correctly decoded.

[0038] The receiver next receives a retransmission 18. In one embodiment, the DCI for the retransmission 18 may contain the bitmap 010, indicating that only code block 2 is present, and also RV=1, indicating that the second RV of all retransmitted code blocks is used (first is RV=0). Thus, the receiver can use incremental redundancy to be able to decode CB2.

[0039] If, during the retransmission TTI, a Ultra-Reliable Low Latency Communication (URLLC) packet (or other latency-critical packet) is provided to the transmitter for transmission, there are opportunities to transmit the URLLC packet in the retransmission TTI without the need of puncturing another transmission, since the retransmission TTI contains unused resources, which are represented in Figure 3 as white (unfilled) boxes. To make the retransmission consist of sequential symbols is also particularly useful in a case of high Doppler-spread, especially if the control region additionally consists of a Demodulation Reference Signal (DMRS) in symbol 2.

[0040] Should the first transmission of CB2 have been punctured by a URLLC transmission, leading to the faulty decoding of said code block, the transmitter should preferably choose RV=0 in the retransmission. As the transmitter has performed the puncturing, it knows when to make this decision.Embodiment: In-Order Spread Out Allocation

[0041] Figure 4 illustrates an exemplary partial retransmission according to an embodiment of the subject matter described herein, in which a code block being retransmitted is distributed in such a way as to provide space available for use to transmit latency critical data. Figure 4 compares a retransmission 20, in which the code block(s) being retransmitted are located sequentially at the front of the retransmission 20, to a retransmission 22, in which the code block(s) being retransmitted are distributed throughout the retransmission 22.

[0042] In one embodiment, the DCI indicates only which code blocks are present in the retransmission, together with an RV value (which may or may not be individual per code block). In this embodiment, however, the receiver is pre-configured with a mapping that maps the set of code blocks being retransmitted to the locations within the retransmission where the retransmitted code block will appear. An example of such a map is shown in Table 1: Table 1: Example mapping from retransmission set to symbol locationRetransm it? (0=no, 1=yes)Code BlockCB1CB2CB3Symbol 2Symbol 3Symbol 4Symbol 5Symbol 6Symbol 70013a3b0102a2b0112a2b3a3b1001a1b1011a1b3a3b1101a1b2a2b1111a1b2a2b3a3b

[0043] In the embodiment illustrated by Table 1, retransmitted code blocks are divided into a first part (a) and a second part (b), which in this example corresponds to the first and second half of the code block. Empty cells in the table indicate symbol locations within the retransmission that are not used for retransmitted code blocks (and thus may be used for other purposes, such as for latency-critical transmissions).

[0044] This example mapping would maximize the number of separate groups of empty symbols for each retransmission set, which provides the best possibility of being able to transmit latency critical packets without puncturing, since transmission opportunities occur frequently within the TTI. In the embodiment illustrated in Figure 4, for example, a first transmission (not shown) was received by the receiver, which indicated to the sender that the first code block (CB1), was not decoded successfully.

[0045] In one embodiment, the sender will retransmit failed code blocks in the same location as they originally appeared, e.g., CB1 occupies the first two symbols after the DCI of the retransmission 20. If a latency-critical packet (e.g., an URLLC packet) arrives at the transmitter just as the transmitter is sending the DCI of the retransmission 20, the soonest that the URLLC packet can also be transmitted (without puncturing another transmission) isn't until symbol 4. It is noted that the same problem occurs for the retransmission 18 in Figure 3 - namely, that the first opportunity to send an URLLC packet does not appear until symbol 4.

[0046] In contrast, the retransmission 22 uses a distributed retransmission format according to the Table 1. According to table 1, if only CB1 is to be retransmitted, the retransmitted code block is split into two parts, with the first part (CB1a) being transmitted during symbol 3 and the second part (CB1b) being transmitted in symbol 6. This is shown graphically as the retransmission 22 in Figure 4. As a result of using this distributed retransmission format, the first opportunity to inject a latency-critical packet without puncturing another transmission occurs at symbol 2 (rather than at symbol 4 in the sequential retransmission format of the retransmission 18 and in the "same location as original" retransmission format of retransmission 20).

[0047] It will be understood that if a latency-critical transmission arrives at the transmitter while no code blocks are being retransmitted, then the TTI being transmitted at that time probably has no free resources, in which case the latency-sensitive transmission will need to wait until the next TTI (or else the transmitter will need to puncture one of the transmissions currently in progress).

[0048] The receiver may be configured with several mappings such as the one above. The DCI may then indicate which mapping is to be used, or the receiver might be configured with a "current" mapping by higher layers, that might change based on indication from the transmitter.Embodiment: Retransmission Specific Mapping

[0049] In one embodiment, the transmitter may explicitly indicate the mapping that is to be used for the retransmission in the DCI. In one embodiment, this indication may be a set of bits indicating for each symbol following the DCI if that symbol is used by the retransmission.Embodiment: Frequency Location

[0050] In one embodiment, the partitioned code blocks might not always only be separated by time (i.e., contained in separate symbols), but might overlap in time, being separated also by frequency. In these embodiments, the mapping would also include information about frequency locations of code blocks or code block parts. Such a mapping may be for instance mapping to Resource Elements (REs) rather than symbols.Embodiment: Multiple User Massive Input Massive Output (MU-MIMO)

[0051] In a system where the transmitter is capable of performing MU-MIMO transmissions, the transmitter may transmit two TBs intended for different receivers simultaneously on the same frequency resources, but separated spatially. In a case where CBs are separated in time, the HARQ feedback indicates which CBs were decoded correctly and at least half of the CBs transmitted to the users were decoded correctly, the transmitter is able to map the retransmission of CBs to the users to be separated in time.

[0052] For example: Assuming each TB consists of 4 CBs, the first transmission to receivers 1 and 2 would be (omitting DCI for clarity): RX1: [CB1, CB2, CB3, CB4], RX2: [CB1, CB2, CB3, CB4]

[0053] If the HARQ feedbacks indicates the following decoding results, RX1: [0, 1, 0, 1], RX2: [0, 0, 1, 1], the transmitter may choose mappings such that the corresponding retransmissions are: RX1: [CB1 CB3, NULL, NULL], RX2: [NULL, NULL, CB1, CB2], where NULL means no transmission. In this particular example, the transmitter does not need to use MU-MIMO for retransmission of the code blocks, because there is no interference on the code blocks between the receivers. In another example there may be interference between retransmitted code blocks, in which case the transmitter would use MU-MIMO for the retransmission.

[0054] Figure 5 is a schematic block diagram of the wireless device 14 (e.g., a UE) according to some embodiments of the present disclosure. As illustrated, the wireless device 14 includes circuitry 24 comprising one or more processors 26 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), Digital Signal Processors (DSPs), and / or the like) and memory 28. The wireless device 14 also includes one or more transceivers 30 each including one or more transmitters 32 and one or more receivers 34 coupled to one or more antennas 36. In some embodiments, the functionality of the wireless device 14 described above may be implemented in hardware (e.g., via hardware within the circuitry 24 and / or within the processor(s) 26) or be implemented in a combination of hardware and software (e.g., fully or partially implemented in software that is, e.g., stored in the memory 28 and executed by the processor(s) 26).

[0055] In some embodiments, a computer program including instructions which, when executed by the at least one processor 26, causes the at least one processor 26 to carry out at least some of the functionality of the wireless device 14 according to any of the embodiments described herein is provided. In some embodiments, a carrier containing the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0056] Figure 6 is a schematic block diagram of the wireless device 14 (e.g., a UE) according to some other embodiments of the present disclosure. The wireless device 14 includes one or more modules 38, each of which is implemented in software. The module(s) 38 provide the functionality of the wireless device 14 described herein. For example, the modules(s) 38 may include a receiving module operable to perform step 100 of Figure 2, a mapping module to perform steps 102 and 104 of Figure 2, and a decoding module to perform step 106 of Figure 2.

[0057] Figure 7 is a schematic block diagram of a network node 40 according to some embodiments of the present disclosure. As illustrated, the network node 40 includes a control system 42 that includes circuitry comprising one or more processors 44 (e.g., CPUs, ASICs, DSPs, FPGAs, and / or the like) and memory 46. The control system 42 also includes a network interface 48. In embodiments in which the network node 40 is a radio access node, the network node 40 also includes one or more radio units 50 that each include one or more transmitters 52 and one or more receivers 54 coupled to one or more antennas 56. In some embodiments, the functionality of the network node 40 (e.g., the functionality of the radio access node 12) described above may be fully or partially implemented in software that is, e.g., stored in the memory 46 and executed by the processor(s) 44.

[0058] Figure 8 is a schematic block diagram of the network node 40 (e.g., the radio access node 12) according to some other embodiments of the present disclosure. The network node 40 includes one or more modules 58, each of which is implemented in software. The module(s) 58 provide the functionality of the network node 40 described herein. The module(s) 58 may comprise, for example, one or more modules operable to provide the functionality of the network node 40 described herein.

[0059] Figure 9 is a schematic block diagram that illustrates a virtualized embodiment of the network node 40 (e.g., the radio access node 12) according to some embodiments of the present disclosure. As used herein, a "virtualized" network node is the network node 40 in which a portion of the functionality of the network node 40 is implemented as a virtual component (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, the network node 40 optionally includes the control system 42, as described with respect to Figure 7. In addition, if the network node 40 is the radio access node 12, the network node 40 also includes the one or more radio units 50, as described with respect to Figure 7. The control system 42 (if present) is connected to one or more processing nodes 60 coupled to or included as part of a network(s) 62 via the network interface 48. Alternatively, if the control system 42 is not present, the one or more radio units 50 (if present) are connected to the one or more processing nodes 60 via a network interface(s). Alternatively, all of the functionality of the network node 40 described herein may be implemented in the processing nodes 60 (i.e., the network node 40 does not include the control system 42 or the radio unit(s) 50). Each processing node 60 includes one or more processors 64 (e.g., CPUs, ASICs, DSPs, FPGAs, and / or the like), memory 66, and a network interface 68.

[0060] In this example, functions 70 of the network node 40 described herein are implemented at the one or more processing nodes 60 or distributed across the control system 42 (if present) and the one or more processing nodes 60 in any desired manner. In some particular embodiments, some or all of the functions 70 of the network node 40 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 60. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 60 and the control system 42 (if present) or alternatively the radio unit(s) 50 (if present) is used in order to carry out at least some of the desired functions. Notably, in some embodiments, the control system 42 may not be included, in which case the radio unit(s) 50 (if present) communicates directly with the processing node(s) 60 via appropriate network interface(s).

[0061] In some particular embodiments, higher layer functionality (e.g., layer 3 and up and possibly some of layer 2 of the protocol stack) of the network node 40 may be implemented at the processing node(s) 60 as virtual components (i.e., implemented "in the cloud") whereas lower layer functionality (e.g., layer 1 and possibly some of layer 2 of the protocol stack) may be implemented in the radio unit(s) 50 and possibly the control system 42.

[0062] In some embodiments, a computer program including instructions which, when executed by the at least one processor 44, 64, causes the at least one processor 44, 64 to carry out the functionality of the network node 40 or a processing node 60 according to any of the embodiments described herein is provided. In some embodiments, a carrier containing the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as the memory 46, 66).

[0063] In one embodiment, a receiver that has indicated unsuccessful reception of a portion or portions of a transmission receives a retransmission of the unsuccessfully received portion or portions of the first transmission. The receiver can then receive the retransmission only in the indicated locations, and can attempt to decode the data packet together with soft information (if any) from the first transmission.

[0064] In one embodiment, the receiver indicates unsuccessful reception of a portion or portions of a transmission via the HARQ feedback mechanism. In one embodiment, the HARQ feedback includes multiple bits per transport block. In one embodiment, these bits are used to signal a HARQ ACK or NACK per transport block or per code block (e.g., if a transport block contains multiple code blocks).

[0065] In one embodiment, the retransmission does not include information that identifies the portions being retransmitted. In another embodiment, the retransmission includes information that identifies the portions being retransmitted. In these embodiments, the receiver may use the information that identifies the portions being transmitted to verify that the retransmission includes the correct portions that the receiver indicated as being unsuccessfully received during the original transmission.

[0066] In one embodiment, the retransmission does not include an indicator that identifies the locations within the retransmission that contain the portions that are being retransmitted. In one embodiment, the receiver may presume that a retransmitted portion occupies the same location in the retransmission as the unsuccessfully received portion occupied in the original transmission. In another embodiment, the receiver may presume that the retransmitted portion or portions occupy the first-arriving locations within the retransmission.

[0067] In one embodiment the retransmission includes an indicator that identifies the locations, within the retransmission, that contain the portions being retransmitted. In one embodiment, the retransmission includes information from which the wireless device can determine the content and / or location of the portions being retransmitted. In one embodiment, the indicator is contained within DCI provided to the wireless device.

[0068] In one embodiment, the retransmission includes mapping information which the receiver uses to determine the content and / or location of the portions being retransmitted. In one embodiment, the transmitter may explicitly indicate the mapping that is to be used for the retransmission in the DCI. In one embodiment, this indication may be a set of bits indicating for each symbol following the DCI if that symbol is used by the retransmission. In one embodiment, the mapping information comprises an index into a lookup table that provides information indicating the content and location, within the retransmission, of the portions being retransmitted. In one embodiment, the mapping information identifies one lookup table out of a set of lookup tables that provide information indicating the content and location, within the retransmission, of the portions being retransmitted. In one embodiment, the lookup table or lookup tables are conveyed to the receiver via network signaling.

[0069] In one embodiment, the partitioned code blocks may be separated by frequency rather than by time, e.g., the code blocks occupy the same time but different frequencies. In one embodiment the partitioned code blocks may be separated by time and by frequency. In these embodiments, the mapping would include information about frequency locations of code blocks or code block parts. Such a mapping may be for instance mapping to REs rather than symbols.

[0070] In one embodiment, the retransmitted portions may be distributed within the retransmission or placed together at the end of the retransmission, e.g., so that URLLC or other high-priority transmissions may occupy the first portions of the retransmission and thus meet strict latency requirements. In one embodiment, the retransmitted portions may be placed together at the beginning of the retransmission, e.g., close to the Demodulation Reference Signals (DMRS), which reduces the likelihood that the retransmission may fail, especially in conditions of high Doppler spread.

[0071] Figure 10 is a flow chart illustrating an exemplary process for partial retransmission according to another embodiment of the subject matter described herein. In one embodiment, the process illustrated in Figure 10 may be performed by a network node (e.g., the radio access node 12), referred to herein as the sender, in communication with a receiver (e.g., the wireless device 14).

[0072] At step 1000, the sender sends, to a receiver, a first transmission.

[0073] At step 1002, the sender receives, from the receiver, an indication identifying at least one portion of the first transmission that should be retransmitted. In one embodiment, the receiver responds to the first transmission with a multi-bit HARQ, indicating, for example, that some of the code blocks contained within the first transmission could not be decoded correctly.

[0074] At step 1004, the sender sends, to the receiver, a control information message indicating that a second transmission will be transmitted in a TTI comprising a plurality of symbols, the second transmission comprising retransmitted data in a subset of the plurality of symbols of the TTI, the retransmitted data comprising a retransmission of a portion of the first transmission. In one embodiment, the control information message may be a DCI message.

[0075] At step 1006, the sender sends, to the receiver, a mapping indicator for indicating a location of the retransmitted data within the second transmission. As indicated by the dotted outline, step 1006 is optional, e.g., the mapping indicator may have been previously provided to the receiver, or the receiver may have previously been provisioned with the mapping indicator, for example. Moreover, where the mapping indicator is sent to the receiver, the mapping indicator may be sent prior to step 1004, may be sent as part of the control information message in step 1004, may be sent after step 1004 but before step 1008, as illustrated in Figure 10, or may be sent as part of the second transmission in step 1008.

[0076] At step 1008, the sender sends, to the receiver, the second transmission. The receiver will then use the mapping indicator to determine the location(s) of the retransmitted data within the second transmission.

Claims

1. A method for receiving, at a receiver, a partial retransmission from a sender, the method comprising: receiving (100) a control information message indicating a transmission to be received in a Transmission Time Interval, TTI, comprising a plurality of symbols, the transmission comprising retransmitted data in a subset of the plurality of symbols of the TTI, the retransmitted data comprising a subset of code blocks of a previously transmitted transport block; receiving (102) the transmission comprising the retransmitted data; determining (104) symbol locations within the TTI of the transmission occupied by the subset of code blocks, based on a mapping of the subset of code blocks to symbol locations, in which mapping each code block of the subset is distributed over at least two non-contiguous symbols of the plurality of symbols of the TTI; and decoding (106) the retransmitted data at the determined symbol locations.

2. The method of claim 1, wherein the control information message identifies the subset of code blocks of the previously transmitted transport block.

3. The method of any of claims 1 to 2, wherein the control information message comprises a mapping indicator indicating the mapping to use for determining symbol locations within the TTI, among a plurality of configured mappings.

4. The method of any of claims 1 to 3, wherein each code block of the subset is split into two parts, the two parts being distributed at least one symbol apart in the plurality of symbols of the TTI.

5. A receiver for receiving partial retransmission from a sender, the receiver adapted to: receive a control information message indicating a transmission to be received in a Transmission Time Interval, TTI, comprising a plurality of symbols, the transmission comprising retransmitted data in a subset of the plurality of symbols of the TTI, the retransmitted data comprising a subset of code blocks of a previously transmitted transport block; receive the transmission comprising the retransmitted data; determine symbol locations within the TTI of the transmission occupied by the subset of code blocks, based on a mapping of the subset of code blocks to symbol locations, in which mapping each code block of the subset is distributed over at least two non-contiguous symbols of the plurality of symbols of the TTI; and decode the retransmitted data at the determined symbol locations.

6. The receiver of claim 5, wherein the control information message identifies the subset of code blocks of the previously transmitted transport block.

7. The receiver of any of claims 5 to 6, wherein the control information message comprises a mapping indicator indicating the mapping to use for determining symbol locations within the TTI, among a plurality of configured mappings.

8. The receiver of any of claims 5 to 7, wherein each code block of the subset is split into two parts, the two parts being distributed at least one symbol apart in the plurality of symbols of the TTI.

9. A method of performing a partial retransmission by a sender, the method comprising: sending, to a receiver, a first transmission of a transport block; receiving, from the receiver, an indication identifying a subset of code blocks of the transport block that should be retransmitted; sending, to the receiver, a control information message indicating that a second transmission will be transmitted in a Transmission Time Interval, TTI, comprising a plurality of symbols, the second transmission comprising retransmitted data in a subset of the plurality of symbols of the TTI, the retransmitted data comprising the subset of the code blocks of the transport block; and sending, to the receiver, the second transmission comprising the subset of code blocks at symbol locations within the TTI determined based on a mapping in which each code block of the subset is distributed over at least two non-contiguous symbols of the plurality of symbols of the TTI.

10. The method of claim 9, wherein the control information message identifies the subset of code blocks of the transport block.

11. The method of any of claims 9 to 10, wherein the control information message comprises a mapping indicator indicating the mapping to use for determining symbol locations within the TTI, among a plurality of configured mappings.

12. The method of any of claims 9 to 11, wherein each code block of the subset is split into two parts, the two parts being distributed at least one symbol apart in the plurality of symbols of the TTI.

13. A sender for performing a partial retransmission, the sender adapted to: send, to a receiver, a first transmission of a transport block; receive, from the receiver, an indication identifying a subset of code blocks of the transport block that should be retransmitted; send, to the receiver, a control information message indicating that a second transmission will be transmitted in a Transmission Time Interval, TTI, comprising a plurality of symbols, the second transmission comprising retransmitted data in a subset of the plurality of symbols of the TTI, the retransmitted data comprising the subset of the code blocks of the transport block,; and send, to the receiver, the second transmission comprising the subset of code blocks at symbol locations within the TTI determined based on a mapping in which each code block of the subset is distributed over at least two non-contiguous symbols of the plurality of symbols of the TTI.

14. The sender of claim 13, wherein the control information message identifies the subset of code blocks of the transport block.

15. The sender of any of claims 13 to 14, wherein the control information message comprises a mapping indicator indicating the mapping to use for determining symbol locations within the TTI, among a plurality of configured mappings.