EP3577815A1 - Retransmission pour signaux perforés - Google Patents

Retransmission pour signaux perforés

Info

Publication number
EP3577815A1
EP3577815A1 EP17829322.1A EP17829322A EP3577815A1 EP 3577815 A1 EP3577815 A1 EP 3577815A1 EP 17829322 A EP17829322 A EP 17829322A EP 3577815 A1 EP3577815 A1 EP 3577815A1
Authority
EP
European Patent Office
Prior art keywords
punctured
signal
radio node
another
node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP17829322.1A
Other languages
German (de)
English (en)
Inventor
Caner KILINC
Sara SANDBERG
Mattias Anderson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP3577815A1 publication Critical patent/EP3577815A1/fr
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end
    • H04L1/1858Transmission or retransmission of more than one copy of acknowledgement message
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end
    • H04L1/1835Buffer management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end
    • H04L1/1864ARQ related signaling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/189Transmission or retransmission of more than one copy of a message
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/1896ARQ related signaling

Definitions

  • the disclosed subject matter relates generally to telecommunications. Certain embodiments relate more particularly to telecommunications devices and methods for sending and decoding punctured signals.
  • the length of the TTI is expected to vary.
  • URLLC may have a shorter TTI length than eMBB.
  • URLLC data transmission is supposed to happen, while the eMBB transmission may be occurring, as soon as a URLLC data packet arrives to the transmitter. It may therefore be desirable to puncture (interrupt) the eMBB transmission in certain time-frequency resources and perform a URLLC transmission on those resources. This comes with the drawback that the receiver of the (partial) eMBB will with high probability not be able to decode successfully.
  • HARQ Hybrid Automatic Repeat Request
  • the LTE HARQ mechanism consists of multiple stop-and-wait protocols that can be applied in parallel to allow continuous transmission of data.
  • HARQ entities there is one HARQ entity per terminal and per component carrier.
  • HARQ processes belong to the same HARQ entity, but have independent HARQ acknowledgements.
  • the TTI subframe
  • the HARQ-ACK for FDD, is transmitted in subframe n+4 for a data transmission in subframe n.
  • the HARQ retransmission timing is fixed, and the HARQ retransmission process typically takes 8ms for each retransmission.
  • a receiver For downlink, when a receiver has attempted to decode a data message it transmits an indicator to the transmitter indicating whether the decoding was successful or not.
  • the transmitter receives an indicator indicating un-successful decoding the transmitter typically performs a re-transmission of the data message which the receiver most likely will combine with the original received transmission.
  • the retransmission may use a different set of coded bits than the previous transmission as in incremental redundancy (IR) HARQ, which includes Chase combining (CC) as a special case.
  • IR incremental redundancy
  • CC Chase combining
  • This combining is known as soft combining where Chase and incremental redundancy are two well-known variants. The combining will greatly increase the probability of successful decoding as described by 3GPP TS.36.321.
  • each retransmission may be different to the previous transmission, but all retransmissions represent the same information bits.
  • the receiver combines the soft information of the first transmission with the soft information of the retransmission. If exactly the same coded bits are used for the first transmission and the retransmission, i.e. Chase combining, the combined soft information corresponds to a codeword with the same length as the first transmission. If any bits that were not part of the first transmission are included in the retransmission, the combined soft information corresponds to a longer codeword with lower code rate.
  • the erroneously received packet is stored in a buffer memory, a soft buffer, and it is later combined with one or several retransmissions.
  • the decoder is operating on the combined soft buffer, thereby producing a more reliable output than if only a single transmission would have been used.
  • a transmitter transmits a signal that is punctured by another signal.
  • the transmitter can directly estimate the probability that the receiver will not be able to decode the transmitted signal. If the probability is above a predetermined or adaptive threshold, the transmitter retransmits at least the punctured portion of the punctured signal. The retransmission can be done before a retransmission request/NACK response is received from the receiver. Moreover, the transmitter may retransmit only a corrupted part of the punctured signal rather than retransmitting an entire subframe of data.
  • the punctured signal is a signal carrying eMBB data and the another signal is a signal carrying URLLC data.
  • the retransmission of punctured bits over an uplink may be handled differently than a retransmission over a downlink. For example, when
  • the retransmission of the corrupted part of the eMBB data can be performed in accordance with two alternative embodiments.
  • a radio access node e.g., eNodeB or gNodeB
  • determines that the received eMBB data is punctured it schedules UL resources for the wireless device to allow retransmission only of the corrupted eMBB data, rather than scheduling resources for retransmission of the whole eMBB transmission.
  • the wireless device may retransmit only the part of the eMBB data that it punctured in the initial transmission.
  • the wireless device may retransmit the corrupted punctured data using pre-scheduled UL resources (i.e., a grant free UL retransmission) as soon as such resources become available. This may be performed substantially immediately after the first eMBB transmission, if the wireless device determines that the probability that the radio access node will not be able to decode successfully due to puncturing is high, e.g., above a threshold.
  • retransmission of the corrupted punctured eMBB data may be performed directly after a punctured transmission as well, e.g., if the radio access node estimates that the wireless device will not be able to decode the data successfully. Moreover, if the radio access node has already retransmitted the eMBB data, it may ignore the first NACK received from the UE.
  • the radio access node when retransmitting over a downlink, may be required to transmit the entire eMBB transmission when, for example, the eMBB and URLLC transmissions were scheduled to different wireless devices and the wireless device receiving the eMBB data has no way of mapping a partial
  • a partial retransmission may suffice where, for example, a downlink preemption indication is transmitted using a group common DCI in PDCCH.
  • Group-common (GC) DCI is similar to ordinary DCI.
  • UEs can be configured with a CORESET to monitor group-common signaling.
  • the group-common DCI carries information on dynamic slot format, preemption indication or SRS switching and power control.
  • the group common DCI enables any wireless device monitoring the group common DCI to keep track of puncturing by URLLC transmissions intended for other wireless devices. Given this preemption indication, the radio access node may retransmit only a corrupted portion of the eMBB transmission.
  • both an radio access node and a wireless device may have access to information about the exact bits of the eMBB data that has been punctured. This information may be used by the radio access node to partially clear the soft information in the soft buffer.
  • the transmitter omits the probability of decoding failure estimation and instead assumes that decoding failure will occur.
  • At least the corrupted part of the signal is always retransmitted anytime puncturing is done.
  • a radio node receives the signal that is punctured by another signal from the transmitting radio node.
  • the receiver detects that the received signal is punctured and ignores soft information corresponding to the punctured bits in a decoding process.
  • control signaling e.g., a preemption indication signaled within a group common DCI
  • sent by the transmitting radio node may indicate to the receiving radio node information about which portion of the punctured signal is punctured. Ignoring the soft information may include setting LLR values corresponding to the ignored soft information to zero.
  • the receiving radio node also determines that the transmitting radio node will likely retransmit at least a punctured portion of the punctured signal and, based on the determining, refrains from transmitting a NACK to the transmitting radio node as part of a HARQ process.
  • Still other embodiments comprise systems that include one or more of the radio nodes summarized above, including one or more radio access nodes and one or more wireless devices. Yet other embodiments comprise computer program products and computer-readable media storing computer program products, where the computer program products comprise program instructions for execution by a processor of a radio node, such that the radio node is thereby operative to carry out one or more of the methods summarized above or variants thereof, as detailed further, below.
  • an amount of resources needed for HARQ retransmission may be significantly reduced by retransmitting only the corrupted part of the eMBB data when receiving a NACK (or in anticipation of a NACK) rather than retransmitting an entire eMBB subframe of data.
  • This benefit may be particularly applicable to an uplink.
  • retransmission delay may be reduced significantly due to the transmitter retransmitting corrupted punctured data without waiting for the NACK.
  • decoding is more likely to succeed when the radio access node can determine the exact bits that have been punctured and thereby partially clear the corresponding soft information in the soft buffer.
  • FIG. 1 illustrates communication system according to an embodiment of the disclosed subject matter.
  • FIG. 2A illustrates a wireless communication device according to an embodiment of the disclosed subject matter.
  • FIG. 2B illustrates a wireless communication device according to another embodiment of the disclosed subject matter.
  • FIG. 3 A illustrates a radio access node according to an embodiment of the disclosed subject matter.
  • FIG. 3B illustrates a radio access node according to another embodiment of the disclosed subject matter.
  • FIG. 4 illustrates a radio access node according to yet another embodiment of the disclosed subject matter.
  • FIG. 5 illustrates an eMBB data signal punctured by a URLLC signal in an uplink.
  • FIG. 6 illustrates a signal timing diagram between a wireless device and a network node in which the network node schedules UL resources only for retransmission of corrupted punctured eMBB bits.
  • FIG. 7 illustrates a signal timing diagram between a wireless device and a network node in which an UL HARQ retransmission is made without NACK where semi-statically scheduled UL resources are utilized to retransmit data in a punctured eMBB signal.
  • FIG. 8 illustrates an eMBB data signal punctured by a URLLC signal in a downlink.
  • FIG. 9 illustrates a signal timing diagram between a wireless device and a network node in which a DL HARQ retransmission is made without NACK.
  • FIG. 10 illustrates an eMBB data signal punctured by a URLLC signal in a downlink where the URLLC signal is addressed to a different wireless device than the eMBB data signal.
  • FIG. 11 is a flow chart that illustrates the operation of a wireless device or radio access node that transmits punctured signals according to certain embodiments of the present disclosure.
  • FIG. 12 is a flow chart that illustrates the operation of a wireless device or radio access node that receives punctured signals according to certain embodiments of the present disclosure.
  • FIG. 13 is a flow chart that illustrates the operation of a wireless device or radio access node that transmits punctured signals according to certain embodiments of the present disclosure.
  • any suitable radio access node such as a base station or gNodeB (g B) may be used instead of an eNB.
  • any signal having a lower latency requirement than another signal may be used instead of URLLC signals and eMBB signals as the puncturing and punctured signals, respectively.
  • a wireless device also referred to herein as a UE for brevity
  • transmits eMBB data in uplink the data may be punctured by URLLC data transmitted in the resources scheduled for eMBB, as illustrated in Figure 5.
  • transmission may also store information about which bits of the eMBB transmission that were punctured. This could for example be a range of bits defined through the first bit and the last bit of the punctured range.
  • the UE estimates the probability that the eMBB data cannot be successfully decoded by a radio access node (also referred to herein as an eNodeB or eNB for brevity), due to the puncturing.
  • the estimation may be performed substantially immediately after the first transmission.
  • An example procedure for estimating the probability is described further below. If the probability of decoding failure due to puncturing is above a specified threshold, the UE retransmits the punctured part of the eMBB data as soon as possible.
  • the UE may perform the retransmission of the corrupted punctured part of eMBB data in one of two alternative ways:
  • the UE receives a grant with UL resources from eNB (or a NACK on PHICH), or
  • the UE utilizes pre-scheduled uplink resources.
  • the eNB When the eNB receives the punctured eMBB data, which is illustrated in Figure 5, it determines that the received data is punctured as soon as it detects and decodes the URLLC UL control signals. The eNB sets the log-likelihood ratio (LLR) values of the punctured eMBB bits to zero before starting the decoding process. This is possible for uplink
  • the eNB transmits a NACK on PHICH and schedules uplink resources to allow the UE to retransmit the corrupted part of the eMBB data as illustrated in Figure 6.
  • the UE receives the scheduling grant, information indicating that the UE is only expected to retransmit the punctured bits may be included in the grant.
  • Another alternative is to avoid any additional signaling and instead predefine that the UE is expected to transmit only punctured bits if it has punctured the first eMBB transmission and the scheduling grant only contains enough resources to retransmit the punctured bits.
  • the eNB does not have to transmit a NACK on PHICH. As an alternative it can transmit an ACK, or even not transmit a PHICH at all. If the scheduled resources allow, instead of only transmitting punctured bits, the UE could transmit the punctured bits, as well as previously untransmitted bits.
  • HARQ retransmission types there are two HARQ retransmission types in LTE UL, adaptive and non- adaptive.
  • non-adaptive HARQ only NACK feedback is transmitted to the UE and if NACK received, the retransmission occurs in a predefined fixed time with the same scheduling information as for the previous transmission.
  • the size of the first transmission will be larger compared to the retransmission where only the corrupted part of eMBB data is included.
  • MCS and RB's may change as per resources allocated by the eNB on PDCCH DCIO transmission. In this case, the adaptive HARQ solution in NR would be preferable.
  • the eNB waits to receive the UE's retransmission of the corrupted part of eMBB data instead of sending a NACK and transmitting a scheduling grant for the retransmission.
  • An example signal timing diagram is shown in Figure 7.
  • the UE's ID is known to the eNB and the eNB knows whether there are any semi-statically scheduled UL resources available for the UE to perform grant free UL transmissions.
  • the eNB could transmit the ACK for the retransmission earlier.
  • the embodiment depicted in Figure 7 may be preferred, however, is that the ACK comes in the same subframe as an ACK for the HARQ process for the original transmission.
  • the UE uses the pre-scheduled resources to retransmit the corrupted part of the eMBB data, as soon as there are pre- scheduled resources available right after the first eMBB transmission. In this way, the latency of the eMBB transmission is reduced significantly.
  • the UE can transmit previously untransmitted bits, as well as the corrupted part of the punctured transmission.
  • the URLLC transmission includes a control information part comprising DMRS (De- Modulation Reference Signals) for demodulation of the control information as well as control information, and a data part comprising DMRS for demodulation of data as well as data.
  • DMRS De- Modulation Reference Signals
  • Figure 8 illustrates a scenario where the eMBB data transmission is punctured by URLLC data in downlink.
  • the retransmission of punctured eMBB data may, in certain embodiments, be performed differently depending on if it is the same UE that is the receiver of both eMBB and URLLC or if it is two different UEs that are receivers. According to some embodiments, however, the retransmission of eMBB data is performed the same way but information about which bits were punctured may not be as readily available when two different UEs receive the eMBB and URLLC transmissions.
  • the same UE receives both eMBB and URLLC
  • the same UE When the same UE receives both eMBB and URLLC, it may be configured to attempt to detect the DMRS for the URLLC PDCCH within the eMBB transmission. This
  • the configuration may be by means of an RRC (Radio Resource Control) information message configuring the device to detect that puncturing is occurring if a specific reference signal is detected (in this case URLLC PDCCH DMRS).
  • URLLC PDCCH DMRS Radio Resource Control
  • the UE may determine exactly which bits in the eMBB data transmission that were punctured.
  • the UE may set the LLR values of the punctured bits to zero before decoding. If the probability of decoding failure, calculated as described further below, is above a threshold, the UE may wait for the e B's retransmission of the punctured eMBB bits instead of sending a NACK. As an alternative, the UE may send a NACK as usual.
  • the eNB may estimate the probability of decoding failure directly after puncturing of eMBB data. If the estimated probability is above a threshold, the eNB may retransmit the punctured eMBB bits. Alternatively, the eNB may forgo the probability estimate and assume that the UE will be unable to decode the eMBB transmission and retransmit the punctured eMBB bits. This may be the case when, for example, more than a threshold number of bits are punctured such that a decoding failure is practically unavoidable. In either case, the eNB may retransmit the punctured eMBB bits without waiting until a NACK is received from the UE.
  • the eMBB bits are transmitted, since the UE has information from decoding of the URLLC PDCCH about which bits the retransmission corresponds to.
  • the e B may transmit previously untransmited bits as well as the bits punctured from the URLLC transmission.
  • the UE may combine the information in the soft buffer (where LLR values of punctured bits are already zero) with the soft information of the retransmission.
  • the soft information now corresponds to a codeword without punctured bits and decoding is likely to be completed successfully, as shown in Figure 9.
  • the retransmission delay may be significantly reduced.
  • the ACK for the retransmission can be sent earlier in an alternative embodiment.
  • One UE receives eMBB and another UE receives URLLC
  • UE-1 interprets the punctured bits as ordinary eMBB data, since it has no information about the puncturing. The UE cannot either set the LLR values of the punctured bits to zero, since it doesn't know that puncturing has occurred. It is therefore unlikely that decoding of the eMBB data will be successful.
  • the transmitting eNB can estimate the probability of decoding failure as explained further below. If the probability is above a threshold, the eNB may retransmit the whole eMBB data block as soon as possible. This retransmission can contain signaling that tells UE-1 that it should discard the last received transmission, clear the soft buffer, and use the retransmission instead.
  • the retransmission may be accompanied by appropriate signaling that describes exactly which bits in the soft buffer that the retransmitted bits correspond to.
  • the eNB After the retransmission, the eNB will receive a NACK from UE-1 that should be discarded.
  • a preemption indication may be signaled with a group common DCI, which enables any wireless device monitoring the group common DCI to be informed of puncturing by URLLC transmissions intended for other wireless devices.
  • the preemption indication may also indicate which bits are punctured.
  • UE-1 can monitor for and receive the preemption indication and thereby detect which bits correspond to the punctured bits and thereby suffice with a retransmission of only a portion of the eMBB data block that contains the punctured bits.
  • the monitoring of the group common DCI introduces some delay, however, in receiving and acting on the puncturing information relative to the case in which the same UE receives both the eMBB and the URLLC data.
  • the transmitter may estimate the probability that the receiver cannot decode the punctured eMBB data.
  • the probability of decoding failure may depend on or be function of one or more different decoding factors including, e.g., a code block size of the eMBB data before encoding, and/or the code rate and the fraction of codeword bits that are punctured. It may also depend on the signal-to-noise ratio of the transmission and/or the modulation scheme used.
  • the probability of decoding failure may be determined by a look up table indexed according to the one or more decoding factors.
  • the probability may depend on a formula that depends on one or more decoding factors.
  • a combination of a table and formula may be implemented.
  • the fraction of punctured data that may still allow successful decoding is very small, in the order of only a few punctured bits per codeword to a few percent of punctured bits. If the receiver knows exactly which bits are corrupted and sets the log- likelihood ratio (LLR) values of these bits to zero, the probability of successful decoding increases. Setting the LLR values to zero is equivalent to the case where no soft information is available for these bits.
  • the described embodiments may be implemented in any appropriate type of communication system supporting any suitable communication standards and using any suitable components. As one example, certain embodiments may be implemented in a communication system such as that illustrated in FIG. 1. Although certain embodiments are described with respect to LTE systems and related terminology, the disclosed concepts are not limited to LTE or a 3 GPP system. Additionally, although reference may be made to the term "cell”, the described concepts may also apply in other contexts, such as beams used in Fifth Generation (5G) systems, for instance.
  • 5G Fifth Generation
  • a communication system 100 comprises a plurality of wireless communication devices 105 (e.g., UEs, machine type communication [MTC] / machine-to- machine [M2M] UEs) and a plurality of radio access nodes 110 (e.g., eNodeBs, gNodeBs, or other base stations).
  • the wireless devices 105 and radio access nodes 110 may be collectively referred to herein as radio nodes.
  • Communication system 100 is organized into cells 115, which are connected to a core network 120 via corresponding radio access nodes 110.
  • Radio access nodes 110 are capable of communicating with wireless communication devices 105 along with any additional elements suitable to support communication between wireless communication devices or between a wireless communication device and another
  • wireless communication devices 105 may represent communication devices that include any suitable combination of hardware and/or software, these wireless
  • communication devices may, in certain embodiments, represent devices such as those illustrated in greater detail by FIGS. 2 A and 2B.
  • the illustrated radio access node may represent network nodes that include any suitable combination of hardware and/or software, these nodes may, in particular embodiments, represent devices such as those illustrated in greater detail by FIGS. 3 A, 3B and 4.
  • a wireless communication device 200A comprises a processor 205 (e.g., Central Processing Units [CPUs], Application Specific Integrated Circuits [ASICs], Field Programmable Gate Arrays [FPGAs], and/or the like), a memory 210, a transceiver 215, and an antenna 220.
  • processors 205 e.g., Central Processing Units [CPUs], Application Specific Integrated Circuits [ASICs], Field Programmable Gate Arrays [FPGAs], and/or the like
  • CPUs Central Processing Units
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • communication devices may be provided by the device processor executing instructions stored on a computer-readable medium, such as memory 210.
  • Alternative embodiments may include additional components beyond those shown in FIG. 2A that may be responsible for providing certain aspects of the device's functionality, including any of the functionality described herein.
  • a wireless communication device 200B comprises at least one module 225 configured to perform one or more corresponding functions. Examples of such functions include various method steps or combinations of method steps as described herein with reference to wireless communication device(s).
  • a module may comprise any suitable combination of software and/or hardware configured to perform the corresponding function. For instance, in some embodiments a module comprises software configured to perform a corresponding function when executed on an associated platform, such as that illustrated in FIG. 2A.
  • a radio access node 300A comprises a control system 320 that comprises a node processor 305 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 310, and a network interface 315.
  • radio access node 300A comprises at least one radio unit 325 comprising at least one transmitter 335 and at least one receiver coupled to at least one antenna 330.
  • radio unit 325 is external to control system 320 and connected to control system 320 via, e.g., a wired connection (e.g., an optical cable).
  • radio unit 325 and potentially the antenna 330 are integrated together with control system 320.
  • Node processor 305 operates to provide at least one function 345 of radio access node 300A as described herein.
  • the function(s) are implemented in software that is stored, e.g., in the memory 310 and executed by node processor 305.
  • node processor 305 executing instructions stored on a computer-readable medium, such as memory 310 shown in FIG. 3 A.
  • radio access node 300 may comprise additional components to provide additional functionality, such as the functionality described herein and/or related supporting functionality.
  • a radio access node 300B comprises at least one module 350 configured to perform one or more corresponding functions. Examples of such functions include various method steps or combinations of method steps as described herein with reference to radio access node(s).
  • a module may comprise any suitable combination of software and/or hardware configured to perform the corresponding function. For instance, in some embodiments a module comprises software configured to perform a corresponding function when executed on an associated platform, such as that illustrated in FIG. 3A.
  • FIG. 4 is a block diagram that illustrates a virtualized radio access node 400 according to an embodiment of the disclosed subject matter.
  • the concepts described in relation to FIG. 4 may be similarly applied to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures.
  • the term "virtualized radio access node” refers to an implementation of a radio access node in which at least a portion of the functionality of the radio access node is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).
  • radio access node 400 comprises control system 320 as described in relation to FIG. 3 A.
  • Control system 320 is connected to one or more processing nodes 420 coupled to or included as part of a network(s) 425 via network interface 315.
  • Each processing node 420 comprises one or more processors 405 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 410, and a network interface 415.
  • processors 405 e.g., CPUs, ASICs, FPGAs, and/or the like
  • radio access node 300A some or all of the functions 345 of radio access node 300A described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment s) hosted by processing node(s) 420.
  • additional signaling or communication between processing node(s) 420 and control system 320 is used in order to carry out at least some of the desired functions 345.
  • control system 320 may be omitted, in which case the radio unit(s) 325 communicate directly with the processing node(s) 420 via an appropriate network interface(s).
  • a computer program comprises instructions which, when executed by at least one processor, causes at least one processor to carry out the functionality of a radio access node (e.g., radio access node 110 or 300A) or another node (e.g., processing node 420) implementing one or more of the functions of the radio access node in a virtual environment according to any of the embodiments described herein.
  • a radio access node e.g., radio access node 110 or 300A
  • another node e.g., processing node 420
  • Embodiments further include a carrier containing any of these computer programs. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • FIG 11 is a flowchart illustrating a method of operating radio node, which may be a network node (e.g., radio access node 110) or a wireless device (e.g., wireless communication device 105), to transmit punctured signals in a wireless communications system.
  • the method 1100 comprises a step SI 105 in which a signal that is punctured by another signal is transmitted to a receiving end (e.g., a wireless device or a network node, as the case may be).
  • the method 1100 further comprises a step SI 1 10 in which a probability of decoding failure by the receiving end is estimated.
  • the method 1100 further comprises step SI 115, in which if the estimated probability is above a threshold, at least a punctured portion of the punctured signal is retransmitted.
  • the at least a portion of the punctured signal is retransmitted before a NACK is received for the punctured signal from the receiving end.
  • the punctured signal may be an eMBB signal and the another signal may be a URLLC signal.
  • the method may include additional steps not shown, may omit certain steps, and/or the order of the steps may differ from that shown.
  • the probability estimation step, SI 110 may be carried out before the initial transmission step, SI 105.
  • a step of puncturing the punctured signal by another signal is not shown but may be considered as a preliminary step of the method.
  • FIG. 12 is another flowchart illustrating a method of operating a network node (e.g., radio access node 110) or a wireless device (e.g., wireless communication device 105) to receive punctured signals in a wireless communications system.
  • the method 1200 comprises a step S1205 in which a signal that is punctured by another signal is received from a transmitting end (e.g., a wireless device or a network node, as the case may be).
  • the method 1200 further comprises a step S1210 in which it is detected that the received signal is punctured.
  • the method 1200 further comprises step S1215, in which soft information generated by a decoding process that corresponds to at least a punctured portion of the punctured signal is ignored.
  • the method may include additional steps not shown, may omit certain steps, and/or the order of the steps may differ from that shown.
  • the method further comprises the network node or wireless device determining that the transmitting end will likely retransmit at least a punctured portion of the punctured signal (SI 220) and, based on the determining, refrain from transmitting a NACK to the transmitting end (S1225).
  • the method may include detecting and decoding control signaling of the another signal, the control signaling indicating to the wireless device information about which portion of the punctured signal is punctured (S1230). The information may then be used to determine which soft information is to be ignored in the decoding process. Ignoring the soft information may include setting LLR values corresponding to the ignored soft information to zero.
  • Figure 13 depicts a method 1300 in which the step of estimating a probability of decoding failure, i.e., step SI 110, is omitted.
  • method 1300 includes
  • a step S1305 in which a signal that is punctured by another signal is transmitted to a receiving end.
  • the method 1300 further comprises a step S1310, in which only a portion of the punctured signal is retransmitted, the portion including at least a punctured portion of the punctured signal.
  • the at least a portion of the punctured signal is retransmitted before a NACK is received for the punctured signal from the receiving end.
  • the punctured signal may be an eMBB signal and the another signal may be a URLLC signal.
  • the portion of the punctured signal comprises one or more segments of a transport block.
  • portion of the one or more segments of the transport block may include a code block group.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Abstract

L'invention porte sur un nœud radio (105, 110) configuré pour être utilisé dans un système de communication sans fil. À cet égard, le nœud radio (105, 110) est configuré pour transmettre à un autre nœud radio un signal qui est perforé par un autre signal. Le nœud radio (105, 110) est également configuré pour estimer une probabilité d'échec de décodage qui caractérise une probabilité que l'autre radio ne parviendra pas à décoder le signal perforé. Le nœud radio (105, 110) est en outre configuré pour retransmettre au moins une partie perforée du signal perforé si la probabilité estimée est supérieure à un seuil.
EP17829322.1A 2017-02-06 2017-12-21 Retransmission pour signaux perforés Pending EP3577815A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762455296P 2017-02-06 2017-02-06
PCT/IB2017/058240 WO2018142201A1 (fr) 2017-02-06 2017-12-21 Retransmission pour signaux perforés

Publications (1)

Publication Number Publication Date
EP3577815A1 true EP3577815A1 (fr) 2019-12-11

Family

ID=60972287

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17829322.1A Pending EP3577815A1 (fr) 2017-02-06 2017-12-21 Retransmission pour signaux perforés

Country Status (4)

Country Link
US (1) US11677513B2 (fr)
EP (1) EP3577815A1 (fr)
CN (1) CN110463109B (fr)
WO (1) WO2018142201A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3504823A4 (fr) * 2016-09-22 2020-07-29 MediaTek Inc. Conception améliorée de systèmes de communication connaissant une erreur de rafale

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3579435B1 (fr) * 2017-02-07 2021-08-04 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé et dispositif de transmission de données
KR102320439B1 (ko) * 2017-03-08 2021-11-03 삼성전자 주식회사 무선 셀룰라 통신 시스템에서 제어 및 데이터 정보 자원 매핑 방법 및 장치
US10609699B2 (en) * 2017-03-16 2020-03-31 Kt Corporation Method for monitoring, transmitting, and receiving downlink pre-emption indication information in new radio networks and apparatus thereof
US11337182B2 (en) * 2017-03-24 2022-05-17 Motorola Mobility Llc Indication for a portion of a time interval
CN108696936B (zh) * 2017-04-12 2022-11-11 华为技术有限公司 数据发送方法、接收方法和相关设备
CN111654357B (zh) 2017-04-21 2023-06-30 Oppo广东移动通信有限公司 数据传输方法、网络侧设备及终端
EP3619851A4 (fr) * 2017-05-05 2021-01-13 Nokia Technologies Oy Perforation d'une large bande mobile améliorée
US11271701B2 (en) * 2018-01-12 2022-03-08 Qualcomm Incorporated Physical downlink control channel (PDCCH) monitoring with overlapping resources
US20210345371A1 (en) * 2018-09-30 2021-11-04 Telefonaktiebolaget Lm Ericsson (Publ) Method and Apparatus for Self-Scheduled Uplink Transmission
CN111130707B (zh) * 2018-11-01 2021-07-06 大唐移动通信设备有限公司 混合自动重传的传输方法、装置、网络设备及终端
US11438826B2 (en) * 2018-12-19 2022-09-06 Qualcomm Incoporated Using a pre-emption indication associated with a quasi co-location relationship
WO2021002784A1 (fr) * 2019-07-01 2021-01-07 Telefonaktiebolaget Lm Ericsson (Publ) Planification de liaison montante
EP4008151A4 (fr) * 2019-08-01 2023-03-01 Qualcomm Incorporated Indication de préemption en liaison montante pour iab à base de duplex intégral
WO2021102724A1 (fr) * 2019-11-27 2021-06-03 Qualcomm Incorporated Multiples informations de commande de liaison descendante pour ordonnancement de groupe

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8085875B2 (en) * 2004-07-16 2011-12-27 Qualcomm Incorporated Incremental pilot insertion for channnel and interference estimation
KR101457688B1 (ko) 2007-10-04 2014-11-12 엘지전자 주식회사 제어채널의 수신오류를 검출하는 데이터 전송방법
CN101615974B (zh) * 2008-06-27 2012-11-14 富士通株式会社 用于通信系统的调制编码集合的设计方法和装置
US8855227B2 (en) 2011-08-19 2014-10-07 Telefonaktiebolaget L M Ericsson (Publ) Methods of receiving multiple input multiple output signals and related communication devices
WO2013134948A1 (fr) 2012-03-16 2013-09-19 Telefonaktiebolaget L M Ericsson (Publ) Procédés pour une réception fiable de données de rétroaction harq dans des déploiements hétérogènes
US9094164B2 (en) * 2012-04-17 2015-07-28 Qualcomm Incorporated Methods and apparatus to improve channel estimation in communication systems
US11252717B2 (en) * 2016-09-02 2022-02-15 Huawei Technologies Co., Ltd. Co-existence of latency tolerant and low latency communications
EP3520277B1 (fr) * 2016-09-30 2022-03-09 Sony Group Corporation Appareil et procédés de télécommunications sans fil
US10581662B2 (en) * 2016-09-30 2020-03-03 Sony Corporation Interleaving aspects in signal space diversity overlapped with non-orthogonal colliding transmissions
EP4290791A3 (fr) * 2016-12-21 2024-03-13 Nokia Technologies Oy Retransmission automatique de données endommagées dans des réseaux sans fil

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3504823A4 (fr) * 2016-09-22 2020-07-29 MediaTek Inc. Conception améliorée de systèmes de communication connaissant une erreur de rafale

Also Published As

Publication number Publication date
US20190379491A1 (en) 2019-12-12
US11677513B2 (en) 2023-06-13
CN110463109A (zh) 2019-11-15
WO2018142201A1 (fr) 2018-08-09
CN110463109B (zh) 2023-01-20

Similar Documents

Publication Publication Date Title
US11677513B2 (en) Retransmission for punctured signals
US11838130B2 (en) Method for partial retransmission
CN110447190B (zh) 用于harq-ack反馈的指示
US11057163B2 (en) Data transmission method and related device
US20110032925A1 (en) Method of transmitting group ack/nack in a communication system
RU2554527C2 (ru) Способы и устройства в телекоммуникационной системе
EP3731588B1 (fr) Réseau radio et procédés réalisés dans ceux-ci
KR20170128309A (ko) 다층 프로토콜 무선 시스템에서의 버스티 펑쳐링 및 간섭을 완화하는 코드 블록 레벨 에러 정정 및 매체 액세스 제어 (mac) 레벨 하이브리드 자동 반복 요청들
EP3440790B1 (fr) Noeud de réseau radio, dispositif sans fil et procédés réalisés dans le noeud et le dispositif
US10644840B2 (en) Methods of efficient HARQ operation for low latency and high performance services
JP6955576B2 (ja) 第2のサービスの送信における第1のサービスのためのデータのパンクチャバンドリング
CN110140317B (zh) 解码部分无线电传送
FI20195875A1 (en) Common link adaptation for a downlink control channel and data channel for wireless networks

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20190724

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20210318

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

APBK Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNE

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

APBR Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3E

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED