WO2019052627A1 - Communication radio d'unités de données de paquets critiques - Google Patents

Communication radio d'unités de données de paquets critiques Download PDF

Info

Publication number
WO2019052627A1
WO2019052627A1 PCT/EP2017/072842 EP2017072842W WO2019052627A1 WO 2019052627 A1 WO2019052627 A1 WO 2019052627A1 EP 2017072842 W EP2017072842 W EP 2017072842W WO 2019052627 A1 WO2019052627 A1 WO 2019052627A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdus
redundant
radio communication
transmitter
redundant pdus
Prior art date
Application number
PCT/EP2017/072842
Other languages
English (en)
Inventor
Junaid Ansari
Ismet Aktas
Mohammad Hossein JAFARI
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/EP2017/072842 priority Critical patent/WO2019052627A1/fr
Priority to EP17771705.5A priority patent/EP3682575B1/fr
Priority to US16/646,301 priority patent/US11343714B2/en
Publication of WO2019052627A1 publication Critical patent/WO2019052627A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0033—Systems modifying transmission characteristics according to link quality, e.g. power backoff arrangements specific to the transmitter
    • H04L1/0035—Systems modifying transmission characteristics according to link quality, e.g. power backoff arrangements specific to the transmitter evaluation of received explicit signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0022—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy in which mode-switching is influenced by the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/189—Transmission or retransmission of more than one copy of a message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/006—Quality of the received signal, e.g. BER, SNR, water filling

Definitions

  • the present disclosure generally relates to a technique for communicating packet data units (PDUs) in a radio com munication. More specifically, and without limitation, methods and devices are provided for transmitting and receiving PDUs with reliability and timeliness constraints.
  • PDUs packet data units
  • a key objective of a next generation or 5G radio networks is the support of low- latency and highly reliable machine-type communication (MTC), also referred to as critical MTC (C-MTC) or ultra-reliable low-latency communication (U RLLC).
  • MTC machine-type communication
  • C-MTC critical MTC
  • U RLLC ultra-reliable low-latency communication
  • the U RLLC or C-MTC needs to address the low latency and high reliability requirements of very different use-cases such as industrial applications, smart grids, remote control of machines and devices, etc.
  • Diversity at the physical layer of the U RLLC or C-MTC in terms of space, time and frequency as well as and their combinations provides the technical means to improve reliability.
  • LTE Long Term Evolution
  • 3GPP 3rd Generation Partnership Project
  • LTE-Advanced are examples of existing 4G radio networks.
  • An LTE transmitter appends a 24-bit field to the transport block (TB) on the physical layer for a cyclic redundancy check (CRC) at the receiver.
  • CRC cyclic redundancy check
  • the radio propagation environment in important applications such as industrial use-cases suffers from strong and varying m ultipath effects (e.g. due to metal su rfaces in the environment causing reflections as well moving parts i n the environment and workers on a shop floor, etc.) leading to more pronounced packet losses, and hence need for retransmissions, compared to office or home deployment scenarios.
  • the price for reliability i.e. a packet error ratio (PER) on the order of 10-7
  • PER packet error ratio
  • existing communication systems cannot fulfill the requirements of U RLLC or C-MTC use-cases, which demand both an even higher degree of reliability and less latency.
  • latency and reliability come hand in hand.
  • mechanisms are needed to guarantee a certain (e.g., high) level of reliability while simultaneously fulfilling certain (e.g., low) latency bounds.
  • a method of transmitting protocol data units (PDUs) in a radio communication from a transmitter to a receiver comprises or triggers a step of receiving one or more control messages indicative of Quality of Service (QoS) requirements for the radio communication.
  • QoS requirements include a control command for a reliability of the radio communication and a control command for a latency of the radio communication.
  • the method further comprises or triggers a step of transmitting a batch of redundant PDUs from the transmitter to the receiver (wherein transmitting a batch of redundant PDUs may also be worded as transmitting a plurality of redundant PDUs).
  • a number of the redundant PDUs per batch depends on the control command for the reliability and a temporal spread of the redundant PDUs per batch depends on the control command for the latency (wherein a number of the redundant PDUs per batch may also be simply worded as a number of transmitted redundant PDUs).
  • the radio communication may be controlled based on one or more of the control messages, e.g., according to the control commands.
  • the controlling of at least one of the reliability and the latency may be a closed-loop or feedback control.
  • the reliability may be the controlled quantity of the feedback control.
  • the number of redundant PDUs may be the control quantity. More specifically, the number of the redundant PDUs may be the control quantity for controlling the reliability of the radio communication, e.g., subjected to the latency bounds indicated by the QoS requirements.
  • Some or each of the control messages, e.g., some or each of the control commands may function as the feedback of the feedback control.
  • the radio resources on which the redundant PDUs are transmitted may further depend upon the available radio resources at a given time.
  • a subset (also referred to as a pattern) of the radio resources used for the transmission may be dynamically determined in time, across frequency carriers, spatial streams and/or a combination thereof in fulfilment of both the number of the redundant PDUs and the temporal spread.
  • control command for the latency may be referred to as latency control command.
  • the control command for the reliability may be referred to as reliability control command.
  • control command may encompass any signal that is received at the transmitter and acts on the transmitting step, e.g., on the number of redundant PDUs and/or the temporal spread of the redundant PDUs.
  • the radio resources in the transmitting step available for or used by the redundant PDUs of the batch are collectively referred to as a pattern of the radio resources.
  • the number of the redundant PDUs (i.e., how many PDUs are mutually redundant, e.g., in the sense of a numerical value) may also be referred to as a degree of redundancy or a size of the pattern.
  • the QoS requirements may determine or control the number of the redundant PDUs to be transmitted in the radio communication from the transmitter to the receiver, e.g., in conjunction with the channel state.
  • the number of the redundant PDUs i.e., the number of redundant PDUs in one batch
  • the temporal spread of the redundant PDUs may also be referred to as a temporal extent of the redundant transmission or temporal extent of the batch or the pattern.
  • the temporal spread may be the duration of the batch including the different radio resources carrying the redundant PDUs.
  • the redundant PDUs in one batch may be transmitted simultaneously and/or
  • the temporal spread may be a (e.g., minimum) time interval encompassing all the radio resources on which the redundant PDUs (e.g., the PDUs of one batch) are transmitted.
  • the reliability may be measured (e.g., by the receiver), indicated and/or represented (e.g., in one or more of the control messages, particularly in the reliability control command) in terms of a bit-error rate or bit-error ratio (BER) or a packet-error rate or a packet-error rate or packet-error ratio (PER).
  • BER bit-error rate or bit-error ratio
  • PER packet-error rate or packet-error ratio
  • packet may refer to a PDU.
  • the latency may be measured (e.g., by the receiver), indicated and/or represented (e.g., in one or more of the control messages, particularly in the latency control command) in terms of a time unit, e.g., millisecond (ms), subframes and/or a transmission time interval (TTI).
  • ms millisecond
  • TTI transmission time interval
  • One or more of the control messages may be indicative of absolute and/or relative QoS requirements.
  • the QoS requirements may include a transmitter configuration such as one or more values or limits of (at least some of) the QoS requirements.
  • one or more of the control messages may be indicative of the QoS requirements in that the latency control command and/or the reliability control command is indicative of a value or a limit of the latency and/or a value or a limit of the reliability.
  • one or more of the control messages (e.g., an acknowledgement feedback or a dedicated message) may be indicative of the number of redundant PDUs per batch.
  • the indication of the QoS requirements may be indicative of maintaining and/or a change of (at least some of) the QoS requirements.
  • one or more of the control messages may be indicative of the QoS requirements in that the latency control command and/or reliability control command is indicative of maintaining or a change of the latency and/or the reliability.
  • the reliability control command may include at least one of an indicator for maintaining the number of redundant PDUs, an indicator for increasing the number of redundant PDUs, an indicator for decreasing the number of redundant PDUs, an indicator of a step size for increasing or decreasing the number of redundant PDUs and a value for the number of redundant PDUs.
  • the transmitter may transmit the redundant PDUs en bloc, i.e., in one batch. Further PDUs may be transmitted in further batches. The method may be repeated for each batch. The number of the redundant PDUs and/or the temporal spread of the redundant PDUs may be updated, e.g., from batch to batch.
  • the feedback control may take one or more of the control messages, e.g., the latest of the control messages, into account for the next batch. The control message functioning as the feedback may be received between consecutive batches.
  • the radio communication may be an ultra-reliable low-latency (URLLC)
  • URLLC ultra-reliable low-latency
  • C-MTC critical machine-type communication
  • M-MTC massive machine- type communication
  • the transmitter and/or the receiver may include or may be connected to at least one of a manufacturing device, an actuator, a sensor and a controller (e.g., a programmable logic controller, PLC).
  • the redundant PDUs may have equal content (e.g., a data payload or a Service Data Unit, SDU, carried by each of the PDUs).
  • the same content may be channel coded for the transmission using different redundancy versions.
  • headers e.g., one or more header fields
  • the redundant PDUs may be exact same copies.
  • the receiver may detect a redundant PDU (i.e., detect that a PDU is redundant, e.g., identical, to an earlier received PDU) by comparing a Radio Link Control (RLC) sequence numbers.
  • RLC sequence numbers may be compared at a Medium Access Control (MAC) layer of the receiver. Only one of the redundant PDUs may be forwarded to the RLC layer.
  • RLC Radio Link Control
  • the transmitter may be a source of traffic.
  • the receiver may be a destination of the traffic.
  • the redundant PDUs may carry redundant (e.g., identical) portions of the traffic.
  • the one or more control messages may be indicative of QoS requirements of the traffic in the radio communication.
  • One or more of the control messages may be indicative of a QoS Class Identifier (QCI) and/or a type of a bearer used by the radio communication.
  • the bearer may include a radio bearer and/or a dedicated bearer, e.g., for an Evolved Packet System (EPS) bearer.
  • EPS Evolved Packet System
  • the one or more control messages indicative of the QoS requirements for the radio communication may include one or more first control messages including or indicative of the reliability control command for the radio communication.
  • the one or more control messages indicative of the QoS requirements for the radio communication may include one or more second control messages including or indicative of the latency control command for the radio communication.
  • At least one of the number of the redundant PDUs per batch and the temporal spread of the redundant PDUs may further depend on a channel state (e.g., channel conditions) of a channel used for the radio communication from the transmitter to the receiver.
  • the transmitter may take into account the current channel conditions for determining the number and/or the temporal spread, wherein the determined number and/or the determined temporal spread are included in the control message.
  • the receiver takes into account the current channel conditions for determining the number and/or the temporal spread.
  • the number and/or the temporal spread may indirectly depend on the channel conditions as a result of the control messages (e.g., a number or proportion of NACKs) functioning as the feedback of the feedback control.
  • At least one of the number and the temporal spread may be initialized based on a predefined channel state.
  • the technique may reconfigure at least one of the number and the temporal spread at runtime, e.g., to a reliability requirement and/or a latency requirement.
  • the channel state used for determining at least one of the number and the temporal spread may be updated over time, e.g., by measuring reference signals transmitted from the receiver to the transmitter or based on Channel State Information (CSI), particularly a Channel Quality Indicator (CQI) or Signal-to-Noise Ratio (SNR), reported from the receiver to the transmitter.
  • CSI Channel State Information
  • CQI Channel Quality Indicator
  • SNR Signal-to-Noise Ratio
  • the number i.e., the introduced redundancy
  • the number may be updated over time or configured to meet the QoS requirements (e.g., the reliability requirement and/or the latency requirement).
  • the initialization and/or the updating of at least one of the number of PDUs per batch and the temporal spread of the batch may be determined using a look-up table, an analytical expression and/or implementation-specific values based on the channel state.
  • the predefined channel state may determine how much redundancy is needed to suffice the QoS requirements.
  • the QoS requirements may vary.
  • the reliability control command may include a reliability requirement for the reliability of the radio communication.
  • the number of the redundant PDUs per batch may depend on the reliability requirement.
  • the latency control command may include a latency requirement for the latency of the radio communication.
  • the temporal spread of the redundant PDUs per batch depends on the latency requirement.
  • the reliability requirement may include a reliability limit, e.g., a maximum BER or a maximum PER.
  • the latency requirement may include a latency limit, e.g., a maximum duration for the transmitting (and, optionally, processing) of the PDU from the transmitter to the receiver, e.g., for successfully transmitting at least one of the redundant PDUs from the transmitter to the receiver.
  • Side conditions of the feedback control for controlling the reliability may include the latency requirement according to the one or more control messages and/or a channel state of a channel used for the radio communication.
  • the QoS requirements may determine the temporal spread of the redundant PDUs in the radio communication from the transmitter to the receiver.
  • the temporal spread of the redundant PDUs may be strictly less than the latency requirement.
  • At least one of the control messages may be indicative of a device capability of the receiver or a device category of the receiver.
  • the device capability or the device category may imply one or each of the QoS requirements or any of the further constraints.
  • the device capability may imply an upper limit on the number of spatial streams and/or frequency carriers for the redundancy.
  • the at least one control message may be indicative of a service category.
  • the service category may imply the QoS requirements or may further specify the QoS requirements.
  • the device capability, the device category and/or the service category may include at least one of the URLLC, the C-MTC and the M-MTC.
  • the reliability requirement and/or the latency requirement may be more restrictive for C-MTC than for M-MTC.
  • At least one of the one or more control messages may be indicative of at least one of a network configuration and a network capability. At least one of the number of the redundant PDUs per batch and the temporal spread of the redundant PDUs per batch may further depend on at least one of the network configuration and the network capability.
  • the network configuration and/or the network capability may include a lower limit on the latency for the radio communication.
  • the network configuration or the network capability may include an amount of available and/or utilizable radio resources, which may imply an upper limit on the number of the redundant PDUs.
  • the network configuration or the network capability may also be referred to as network policy constraints.
  • At least one of the transmitter and the receiver may be part of a radio access network (RAN).
  • RAN radio access network
  • At least one of the one or more control messages may be received from the receiver.
  • the at least one control message from the receiver may function as the feedback of the feedback control.
  • the transmitter may be in radio communication with multiple receivers. Each of the receivers may provide at least one of the control messages. At least one of the number of the redundant PDUs per batch and the temporal spread of the redundant PDUs per batch may depend on the control messages received from the multiple receivers. At least one of the number of the redundant PDUs and the temporal spread of the redundant PDUs transmitted to one of the multiple receivers may depend on the number of the multiple receivers and/or the QoS requirements of all of the multiple receivers in radio communication with the transmitter.
  • At least one of the one or more control messages may include a configuration message received upon setting up the radio communication.
  • the control message may be received according to a communication protocol for setup, configuration or reconfiguration of the radio communication.
  • the control message may be part of a negotiation protocol of the radio communication.
  • the configuration message may be indicative of the latency requirement.
  • the latency requirement defined by the configuration message may be persistent for the radio communication.
  • Another control message may be indicative of the reliability requirement.
  • the reliability requirement may be changed by receiving further control messages during the radio communication.
  • the number of the redundant PDUs per batch may be maintained in the absence of an acknowledgment feedback from the receiver in the one or more control messages.
  • Each of the redundant PDUs in the batch may be transmitted independent of and/or prior to receiving an acknowledgment feedback from the receiver for any one of the redundant PDUs in the batch.
  • the PDU transmission and the acknowledgment feedback may relate to the same batch of redundant PDUs.
  • All PDUs that are mutually redundant i.e., the PDUs in one of the batches
  • the redundant PDUs may be transmitted without (e.g., explicitly) waiting for an acknowledgement feedback for the transmitted data (e.g., the data transmitted in each of the redundant PDUs).
  • the redundant PDUs may be transmitted solely based on the QoS requirements received prior to the transmission of all of the redundant PDUs and/or based on the channel state.
  • the channel state may also be referred to as a channel quality or channel conditions. If the redundant PDUs are transmitted using different frequency carriers, the channel quality may comprise the quality or conditions of the different channels used for the transmission. The channel quality or conditions of one of the frequency carriers may be different from the other one of the frequency carriers.
  • At least one of the one or more control messages may include an acknowledgment feedback received from the receiver in response to at least one earlier PDU transmitted from the transmitter to the receiver prior to the transmission of the redundant PDUs in the batch.
  • the acknowledgment feedback may include a positive acknowledgement, ACK, or a negative acknowledgment, NACK.
  • the acknowledgment feedback may function as the feedback of the feedback control.
  • the transmission of the at least one earlier PDU and the acknowledgment feedback may relate to different batches.
  • the reliability may be controlled based on the acknowledgment feedback.
  • the reliability requirement may be defined or changed according to the received acknowledgment feedback, e.g., during the ongoing radio communication.
  • the at least one earlier PDU may be referred to as the at least one first PDU.
  • a number of the at least one earlier PDU may also be referred to as a first number, i.e., the first number of the one or more first PDUs.
  • the redundant PDUs may be referred to as redundant second PDUs or, briefly, as the second PDUs (e.g., as opposed to the at least one earlier PDU received prior to receiving the at least one configuration message).
  • the number of the redundant second PDUs may also be referred to as a second number, i.e., as the second number of the redundant second PDUs.
  • a content of the at least one earlier PDU may be different from a content of the redundant PDUs in the batch.
  • Each of the least one first PDU i.e. the at least one earlier PDU
  • This mode of the radio communication i.e., the transmission of one or more batches, each comprising redundant PDUs, may be referred to as a second mode, e.g., as opposed to a first mode of the radio communication that is backward compatible with a conventional specification of the acknowledgment feedback.
  • a retransmission e.g., of an individual PDU
  • the acknowledgment feedback may be selectively triggered depending on the acknowledgment feedback.
  • the at least one first PDU may also include at least two redundant first PDUs.
  • the at least two redundant first PDUs may define a first batch.
  • the batch of the redundant second PDUs may be referred to as the second batch.
  • the transmitter may transmit multiple batches of redundant PDUs, e.g., consecutively.
  • the PDUs in each of the batches may be mutually redundant within the same batch.
  • Each PDU in one of the batches may be independent of, different from, and/or not redundant to any one of the PDUs in another one of the batches transmitted from the transmitter.
  • the QoS requirements may be controlled per batch by the acknowledgment feedback.
  • the acknowledgment feedback may control the number of redundant PDUs per batch.
  • the at least one earlier PDU may be transmitted in an earlier batch including an earlier number of redundant earlier PDUs.
  • the earlier number of redundant PDUs per batch may be changed to the number of redundant PDUs per batch based on the acknowledgment feedback. That is, the first number may be changed to the second number based on the acknowledgment feedback received in response to transmitting the first PDUs.
  • Each of the at least two redundant second PDUs may be different (e.g., in terms of content or payload data) from each of the at least two redundant first PDUs (i.e., the each of the earlier redundant PDUs).
  • the redundancy may be adjusted or configured to meet a reliability requirement for the radio communication and/or avoid wasting radio resource by transmitting with more redundancy than is necessary to achieve the required reliability.
  • the required reliability may be implied by the acknowledgment feedback and/or the change of the redundancy.
  • By redundantly transmitting the PDUs according to the changed redundancy retransmissions can be avoided. Both high reliability and low latency can be achievable.
  • the (e.g., earlier) "number" of redundant (e.g., earlier) PDUs in the context of a dependency of the (e.g., earlier) number or in the context of changing the (e.g., earlier) number may refer to the (e.g., earlier)
  • the (e.g., earlier) "number” of redundant (e.g., earlier) PDUs may refer to a corresponding plurality of PDUs, that is the corresponding batch of PDUs.
  • receiving the acknowledgment feedback does not trigger a retransmission of any one of the at least one earlier PDU.
  • receiving the acknowledgment feedback does not trigger a retransmission of any one of the first PDUs or the second PDUs.
  • receiving the acknowledgment feedback does not trigger a retransmission, even if the acknowledgment feedback is indicative of a negative acknowledgment.
  • none of the transmitted redundant PDUs in the batch is a retransmission of any one of the earlier PDUs or any PDU in the earlier batch.
  • Controlling or changing the number of redundant PDUs per batch depending on the acknowledgment feedback may include at least one of: maintaining the earlier number as the number of redundant PDUs per batch responsive to a single positive acknowledgment feedback for the earlier batch; decreasing the earlier number as the number of redundant PDUs per batch responsive to multiple positive
  • acknowledgment feedbacks for the earlier batch ; and increasing the earlier number as the number of redundant PDUs per batch responsive to one or multiple negative acknowledgment feedbacks for the earlier batch.
  • the number of redundant PDUs per batch may be maintained if the single positive acknowledgment feedback and one or more negative acknowledgment feedbacks are received for the earlier batch.
  • the number of redundant PDUs per batch may be increased in the absence of a positive acknowledgment feedback for the earlier batch if at least one negative acknowledgment feedback is received for the earlier batch.
  • a step size for increasing or decreasing the number of redundant PDUs per batch may depend on a number of the negative or positive acknowledgment feedbacks.
  • the redundant PDUs may be distributed differently (e.g., in time, space and/or frequency).
  • a trade-off between the distribution of the redundant PDUs per batch in time, on the one hand, and frequency and/or space, on the other hand may be controlled by at least one of the network load, the device capability and the latency requirement.
  • the distribution in time i.e., the temporal extent of the pattern, may be controlled or limited by the latency requirement.
  • the number of redundant PDUs per batch may be initialized prior to receiving the acknowledgment feedback and/or updated based on the received acknowledgment feedback.
  • the number of redundant PDUs per batch e.g., the first number, may be initialized by a predefined number, e.g., based on a predefined redundancy requirement and/or the predefined channel state.
  • a functional dependency (e.g., for the initialization and/or the updating) between the redundancy requirement and/or the predefined channel state (as an input) and the determined number (as an output) may be implemented by at least one of lookup tables, numerical computations using equations and machine learning.
  • the input may further comprise at least one of the latency requirement, the device capability and the availability of the radio resources.
  • the output may further comprise the pattern of the PDUs, i.e., the functional dependency may further determine the way the redundant PDUs are transmitted in time, frequency and/or space.
  • the predefined number and/or the first number may fulfill the reliability requirement for the predefined channel state.
  • the predefined channel state may be a predefined worst case of the channel state or a predefined lower bound of the channel state of the channel between the transmitter and the receiver.
  • the number of PDUs per batch or the redundancy requirement may be initialized based on the configuration message, a negotiation between the transmitter and the receiver and/or during setting up the radio communication between the transmitter and the receiver.
  • the predefined number of PDUs per batch may include a margin to ensure that a reliability requirement (e.g., a predefined or configured reliability requirement) is fulfilled.
  • a reliability requirement e.g., a predefined or configured reliability requirement
  • the first number may be determined so that the reliability requirement is certainly fulfilled or over-fulfilled. This initialization of the first number of redundant first PDUs may be referred to as an "aggressive" approach. For transmitting the first number of redundant first PDUs, the
  • corresponding radio resources of the redundant first PDUs may be distributed over frequency and time.
  • the number of PDUs per batch may be changed over time (e.g., reduced to be less resource consuming) according to the QoS requirements indicated by the one or more control messages.
  • the first number may be reduced to the second number based on the reliability requirement of the acknowledgment feedback.
  • the method may further comprise or trigger a step of switching between a first mode of the radio communication and a second mode of the radio communication.
  • a retransmission may be (e.g., selectively) enabled in the first mode. In the first mode, previously transmitted data is retransmitted depending on the acknowledgment feedback received in response to the previously transmitted data.
  • the retransmission may be (e.g., permanently) disabled in the second mode.
  • the redundant PDUs in each batch includes new data that is
  • the number of the redundant PDUs per batch depends on the reliability control command.
  • the temporal spread of the redundant PDUs per batch depends on the latency control command.
  • the retransmission in the first mode may relate to a transmission of one or more PDUs that are redundant to one or more previously transmitted PDUs for which the acknowledgment feedback has been received. That is, PDUs transmitted from the transmitter prior to and after the reception of the acknowledgment feedback may be redundant in the first mode.
  • the transmission in the second mode may relate to a transmission of one or more PDUs that carry new data independent of previously transmitted PDUs based on which the acknowledgment feedback has been received. That is, PDUs transmitted from the transmitter prior to and after the reception of the acknowledgment feedback may be not redundant, while different PDUs transmitted after the reception of the acknowledgment feedback may redundant in the second mode.
  • transmissions of PDUs for the radio communication may use no redundancy or a constant redundancy on the level of PDUs (e.g., the number of redundant PDUs is not changed).
  • the reception of the acknowledgment feedback does not trigger a retransmission of one or more of the at least one first PDUs, e.g., if the acknowledgment feedback is indicative of a negative acknowledgment.
  • the acknowledgment feedback (e.g., in the first mode and/or the second mode) may be implemented by or included in (e.g., a bit field of) an RLC status report (e.g., a status PDU or control PDU) and/or control information at the MAC layer.
  • a negative acknowledgment (NACK) in the acknowledgment feedback may be interpreted as an Automatic Repeat Request (ARQ) at the RLC layer or as a Hybrid ARQ (HARQ) at the MAC layer.
  • HARQ Hybrid ARQ
  • a NACK in the acknowledgment feedback may be interpreted as the control message indicative of the QoS, e.g., defining or changing the number of redundant PDUs.
  • the bit field corresponding to the HARQ feedback may represent the acknowledgment feedback.
  • the bit field may be interpreted as a request or trigger for the retransmission.
  • the bit field may be interpreted differently for changing the redundancy, e.g., the number of redundant PDUs.
  • the technique may be implemented using the MAC layer, e.g., using the HARQ ACK, for the acknowledgment feedback (e.g., in the second mode).
  • a conventional HARQ retransmissions may be disabled (e.g., in the second mode).
  • the RLC layer may provide a fallback mechanism that allows receiving (e.g., by triggering a
  • RLC ACKs may serve as the acknowledgment feedback controlling the reliability or the redundancy (i.e., the number of redundant PDUs) may also be exploited.
  • the redundant PDUs in the batch may be transmitted on radio resources that are different from each other in at least one of time, space and frequency.
  • the radio resource may be different in space by using different spatial streams, e.g., generated by precoding antenna signals for a plurality of antenna elements of an antenna array.
  • the different spatial streams may correspond to different directions of a main lobe of the transmission power used for the transmitting of the redundant PDUs.
  • the redundancy may be introduced at the RLC layer, the MAC layer or in between the RLC and MAC layers.
  • the redundant PDUs may be introduced in a protocol stack of the radio communication at or above the MAC layer of the protocol stack.
  • the MAC layer of the receiver may be enabled to determine which redundant PDUs belong to the same batch, e.g., based on the RLC sequence number.
  • the MAC layer of the transmitter may be configured to adequately distribute the redundant PDUs to the respective HARQ processes and/or HARQ entities for distribution in time, space and/or frequency according to the QoS requirements, i.e., in the pattern that fulfils the QoS requirements.
  • the redundant PDUs may be copied PDUs.
  • the expression "copied PDUs" may relate to PDUs that are mutually equivalent PDUs, e.g., identical PDUs.
  • the copied PDUs may include an original PDU used for generating the redundant PDUs by copying the original PDU.
  • the method may further comprise or trigger a step of generating the redundant PDUs per batch by copying a data unit (e.g., a PDU or an SDU) defining the content of the batch.
  • the redundant PDUs may be generated by copying (e.g., duplicating or multiplicating) the data unit including or representing the content of the batch.
  • the PDUs may be copied at the RLC layer, the MAC, layer or in between the RLC and MAC layers.
  • the redundancy may be introduced by copying a PDU (e.g., at the output of a layer, e.g., the RLC layer of the protocol stack) or by copying a Service Data Unit, SDU (e.g., at the input of a layer of the protocol stack, e.g., the MAC layer).
  • the copied PDUs may be equivalent in that they include the same content or payload data.
  • the receiver may identify the copied PDUs as belonging to the same batch based on identical RLC sequence numbers or identical Packet Data Convergence Protocol (PDCP) sequence numbers in the copied PDUs.
  • PDCP Packet Data Convergence Protocol
  • At least two of the redundant PDUs per batch may be distributed in time by assigning the at least two redundant PDUs to consecutive HARQ processes. Alternatively or in addition, at least two of the redundant PDUs per batch are distributed in time by assigning the at least two redundant PDUs to the same HARQ entity. Alternatively or in addition, at least two of the redundant PDUs are distributed in time by
  • At least two of the redundant PDUs may be distributed in at least one of space and frequency by assigning the at least two redundant PDUs to different HARQ entities. At least two of the redundant PDUs may be distributed in space by transmitting the at least two redundant PDUs on different spatial streams. At least two of the redundant PDUs may be distributed in frequency by transmitting the at least two redundant PDUs on different carrier frequencies.
  • a method of receiving protocol data units (PDUs) in a radio communication from a transmitter at a receiver comprises or triggers a step of transmitting, to the transmitter, one or more control messages indicative of Quality of Service (QoS) requirements for the radio communication .
  • QoS requirements including a control command for a reliability of the radio communication and a control command for a latency of the radio communication.
  • the method further comprises or triggers a step of receiving a batch of redundant PDUs from the transmitter. A number of the redundant PDUs per batch depends on the control command for the reliability. A temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • the receiving of the batch including the number of redundant PDUs may imply that the receiver is able to receive a radio signal at radio resources
  • each of the redundant PDUs it is not necessary that the receiver successfully receives (e.g., successfully demodulates and/or decodes) each of the redundant PDUs in the batch.
  • a cyclic redundancy check CRC
  • CRC cyclic redundancy check
  • the successful reception of one of the redundant PDUs in the batch may be sufficient (e.g., due to the redundancy of the redundant PDUs in the batch).
  • the method may further comprise or trigger a step of removing redundant PDUs from the batch based on identical sequence numbers included in the redundant PDUs.
  • the receiver may forward a first successfully received PDU out of the redundant PDUs of the batch, e.g., to a higher layer of the protocol stack at the receiver. Further redundant PDUs of the same batch, e.g., those PDUs of the batch received and/or processed after the first successfully received PDU, may be discarded.
  • the acknowledgment feedback may be transmitted to the receiver for each of the redundant PDUs in the batch, e.g. independent of whether the corresponding PDU is forwarded or discarded at the receiver.
  • the acknowledgment feedbacks may be indicative for each of the redundant PDUs whether or not the corresponding PDU has been successfully received (e.g., based on a positive or negative CRC).
  • the method may further comprise or trigger any step or may further comprise any feature disclosed in the context of the one method aspect for the transmitter, or a corresponding step or a corresponding feature for the receiver.
  • the technique can be implemented to control packet redundancy for regulating reliability and latency, e.g., of a C-MTCs, in industrial automation and/or URLLCs.
  • the technique can be implemented by enhancing an ARQ mechanism or HARQ mechanism to avoid or reduce retransmissions.
  • the technique can configure and/or control the radio communication.
  • the technique can improve reliability, e.g., at a fixed latency.
  • the technique is implementable at layers of a protocol stack higher than the physical layer such as the MAC layer and/or the RLC layer. Retransmissions at the MAC layer and/or the RLC layer can be avoided or reduced in a controlled and configurable manner.
  • the redundant PDUs may be the result of copying the content common to all of the redundant PDUs at any point upstream of the occurrence of the redundant PDUs.
  • the redundant packets may be generated at the MAC layer or between MAC and RLC layers.
  • the redundant packets may be transmitted through consecutive HARQ processes, without retransmissions triggered by an acknowledgment feedback.
  • the redundant packets may be transmitted though different HARQ entities, without acknowledgment feedback-triggered retransmissions.
  • the redundancies may be filtered at the MAC layer. The filter may eliminate multiple successful arrivals of the redundant packets.
  • the receiver may control the number of redundant copies by transmitting the one or more control messages according to the transmitting step of the receiving method as the feedback of the control mechanism.
  • the technique can avoid transmitting redundant packets in individually triggered retransmissions. Such retransmissions have a direct negative impact on the latency of the radio communication and this additional latency introduced through
  • the technique can be implemented as a control mechanism.
  • the control mechanism may control redundancy across time, frequency and spatial streams.
  • the control messages may be indicative of at least one of varying QoS requirements (also: QoS targets), varying link characteristics and varying device capabilities. Based on the control messages, different configurations for the transmission of the redundant packet can be used with runtime adaptation. For example, the QoS requirements can be fulfilled with an optimal use of radio resources.
  • At least one of the transmitter and the receiver may be configured for peer-to-peer communication (e.g., on a sidelink) and/or for accessing the RAN (e.g. an uplink, UL, and/or a downlink, DL).
  • At least one of the transmitter and the receiver may be a user equipment (UE, e.g., a 3GPP UE), a mobile or portable station (STA, e.g. a Wi-Fi STA), a device for machine-type communication (MTC) or a combination thereof.
  • UE user equipment
  • STA mobile or portable station
  • MTC machine-type communication
  • Examples for the UE and the mobile station include a mobile phone and a tablet computer.
  • Examples for the portable station include a laptop computer and a television set.
  • Examples for the MTC device include robots, sensors and/or actuators, e.g., in manufacturing, automotive communication and home automation.
  • the MTC device may be implemented in household appliances and consumer electronics. Examples for the combination include a self-driving vehicle, a door intercommunication system and an automated teller machine.
  • At least one of the transmitter and the receiver may be a base station of the RAN.
  • the base station may include a 3G base station or Node B, 4G base station or eNodeB, a 5G base station or gNodeB, an access point (e.g., a Wi-Fi access point) and a network controller (e.g., according to Bluetooth, ZigBee or Z-Wave).
  • the RAN may be implemented according to the Global System for Mobile
  • GSM Global System for Mobile communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • NR New Radio
  • a computer program product comprises program code portions for performing any one of the steps of the method aspects disclosed herein when the computer program product is executed by one or more computing devices.
  • the computer program product may be stored on a computer-readable recording medium.
  • the computer program product may also be provided for download via a data network, e.g., via the radio
  • the method may be encoded in a Field-Programmable Gate Array (FPGA) and/or an Application-Specific I ntegrated Circuit (ASIC), or the functionality may be provided for download by means of a hardware description language.
  • FPGA Field-Programmable Gate Array
  • ASIC Application-Specific I ntegrated Circuit
  • the transmitter is configured to perform or trigger the one method aspect.
  • the transmitter may comprise a receiving unit configured to receive one or more control messages indicative of QoS requirements for the radio communication, the QoS requirements including a control command for a reliability of the radio communication and a control command for a latency of the radio communication.
  • the transmitter may further comprise a transmitting unit configured to transmit a batch of redundant PDUs to the receiver, wherein a number of the redundant PDUs per batch depends on the control command for the reliability and a temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • a receiver for receiving PDUs in a radio communication from a transmitter is provided.
  • the receiver is configured to perform or trigger the other method aspect.
  • the receiver may comprise a transmitting unit configured to transmit, to the transmitter, one or more control messages indicative of QoS requirements for the radio communication, the QoS requirements including a control command for a reliability of the radio
  • the receiver may further comprise a receiving unit configured to receive a batch of redundant PDUs from the transmitter, wherein a number of the redundant PDUs per batch depends on the control command for the reliability and a temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • a transmitter for transmitting PDUs in a radio communication to a receiver comprises at least one processor and a memory.
  • Said memory comprises instructions executable by said at least one processor whereby the transmitter is operative to receive one or more control messages indicative of QoS requirements for the radio communication, the QoS requirements including a control command for a reliability of the radio communication and a control command for a latency of the radio communication.
  • Execution of the instructions further causes the transmitter to be operative to transmit a batch of redundant PDUs to the receiver, wherein a number of the redundant PDUs per batch depends on the control command for the reliability and a temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • a receiver for receiving PDUs in a radio communication from a transmitter.
  • the receiver comprises at least one processor and a memory.
  • Said memory comprises instructions executable by said at least one processor whereby the receiver is operative to transmit, to the transmitter, one or more control messages indicative of QoS requirements for the radio communication, the QoS requirements including a control command for a reliability of the radio
  • Execution of the instructions further causes the receiver to be operative to receive a batch of redundant PDUs from the transmitter, wherein a number of the redundant PDUs per batch depends on the control command for the reliability and a temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • a transmitter for transmitting PDUs in a radio communication to a receiver may comprise one or more modules for performing the one method aspect.
  • the transmitter comprises a reception module for receiving one or more control messages indicative of QoS requirements for the radio communication, the QoS requirements including a control command for a reliability of the radio communication and a control command for a latency of the radio communication.
  • the transmitter further comprises a transmission module for transmitting a batch of redundant PDUs to the receiver, wherein a number of the redundant PDUs per batch depends on the control command for the reliability and a temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • a receiver for receiving PDUs in a radio communication from a transmitter may comprise one or more modules for performing the other method aspect.
  • the receiver comprises a transmission module for transmitting, to the transmitter, one or more control messages indicative of QoS requirements for the radio communication, the QoS requirements including a control command for a reliability of the radio communication and a control command for a latency of the radio communication.
  • the receiver further comprises a reception module for receiving a batch of redundant PDUs from the transmitter, wherein a number of the redundant PDUs per batch depends on the control command for the reliability and a temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • the transmitter (or any node or station for embodying the transmitter) and the receiver (or any node or station for embodying the receiver) may further comprise any feature disclosed in the context of the method aspects. Particularly, any one of the units and modules, or a dedicated unit or module, may be configured to perform or trigger one or more of the steps of any one of the method aspects.
  • Fig. 1 shows a schematic block diagram of a transmitter for transmitting protocol data units in a radio communication from the transmitter to a receiver;
  • Fig. 2 shows a schematic block diagram of a receiver for receiving protocol data units in a radio communication from a transmitter at the receiver;
  • Fig. 3 shows a flowchart for a method of transmitting protocol data units, which is implementable by the transmitter of Fig. 1;
  • Fig. 4 shows a flowchart for a method of receiving protocol data units, which is implementable by the receiver of Fig. 2;
  • Fig. 5 shows a schematic block diagram for an example of a protocol stack for the radio communication, which is implementable at each of the transmitter and the receiver;
  • Fig. 6 schematically illustrates first embodiments of protocol stacks at the transmitter and the receiver in the radio communication
  • Fig. 7 schematically illustrates a first example of a pattern of radio resources in time and frequency, on which a batch of redundant protocol data units is transmitted and received by the first embodiments of the protocol stacks;
  • Fig. 8 schematically illustrates second embodiments of protocol stacks at the transmitter and the receiver in the radio communication
  • Fig. 9 schematically illustrates a second example of a pattern of radio resources in time and frequency, on which a batch of redundant protocol data units is transmitted and received by the second embodiments of the protocol stacks;
  • Fig. 12 schematically illustrates a third example of a pattern of radio resources in time and frequency for a batch of redundant protocol data units
  • Fig. 13 schematically illustrates a fourth example of a pattern of radio resources in time and frequency for a batch of redundant protocol data units
  • Fig. 14 shows a flowchart for a first method embodiment of the method of Fig. 3;
  • Fig. 15 shows a flowchart for second method embodiments of the methods of Figs. 3 and 4;
  • Fig. 16 shows a flowchart for a third method embodiment of the method of Fig. 3;
  • Fig. 17 shows a flowchart for a third method embodiment of the method of Fig. 4;
  • Fig. 18 shows a schematic block diagram of an embodiment of the transmitter;
  • Fig. 19 shows a schematic block diagram of an embodiment of the receiver.
  • Fig. 1 schematically illustrates a block diagram of a transmitter for transmitting protocol data units (PDUs) in a radio communication from the transmitter to a receiver.
  • the transmitter i.e., any device for transmitting PDUs, is generically referred to by reference sign 100.
  • the transmitter 100 comprises a reception module 102 that receives one or more control messages indicative of Quality of Service (QoS) requirements for the radio communication.
  • QoS requirements include a control command for a reliability of the radio communication and a control command for a latency of the radio communication.
  • the transmitter 100 further comprises a transmission module 106 that transmits a batch of redundant PDUs from the transmitter 100 to the receiver. A number of the redundant PDUs per batch depends on the control command for the reliability. Furthermore, a temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • the transmitter 100 further comprises a redundancy introduction module 104 for generating the redundant PDUs.
  • the modules 102, 106 and, where appropriate, 104 may be implemented on a medium access control (MAC) layer or a radio link control (RLC) layer of a protocol stack for the radio communication.
  • the redundant PDUs may be redundant MAC PDUs (e.g., also if the redundancy is introduced at the RLC layer by copying RLC PDUs).
  • the redundant PDUs may be generated by copying an RLC PDUs at the lower end of the radio link control (RLC) layer (optionally further including an indicator of the batch to which the redundant PDU belongs and/or an indicator of the radio resource position within a radio resource pattern of the batch).
  • the redundant PDUs may be generated by copying service data units (SDUs) at the upper end of the MAC layer.
  • SDUs service data units
  • modules of the transmitter 100 may be implemented by units configured to provide the corresponding functionality.
  • Fig. 2 schematically illustrates a block diagram of a receiver for receiving PDUs in a radio communication from a transmitter to the receiver.
  • Reference sign 200 generically refers to the receiver, i.e., any device for receiving PDUs.
  • the receiver 200 comprises a transmission module 202 that transmits, to the transmitter, one or more control messages indicative of QoS requirements for the radio communication.
  • the QoS requirements include a control command for a reliability of the radio communication and a control command for a latency of the radio communication.
  • the receiver 200 further comprises a reception module 204 that receives a batch of redundant PDUs from the transmitter. A number of the redundant PDUs per batch depends on the control command for the reliability and a temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • the receiver 200 further comprises a redundancy removal module 206 for removing the redundancy in the received batch of redundant PDUs.
  • the modules 202, 204 and, where appropriate, 206 may be implemented on the MAC layer or an RLC layer of a protocol stack for the radio communication.
  • the redundant PDUs may be redundant MAC PDUs (e.g., also if the redundancy removal module 206 is implemented on the RLC layer).
  • the redundant PDUs may be removed by forwarding solely one successfully received RLC PDUs (e.g., the first successfully received RLC PDU) at the lower end of the RLC layer (e.g., wherein the redundant PDUs are associated to a certain batch based on an indicator included RLC PDU).
  • the redundant PDUs may be removed by forwarding solely one successfully received MAC PDUs or MAC SDU (e.g., the first successfully received MAC PDU or MAC SDU) at the lower end or the upper end, respectively, of the MAC layer. All other PDUs or SDUs may be discarded.
  • modules of the receiver 200 may be implemented by units configured to provide the corresponding functionality.
  • the receiver in radio communication with the transmitter 100 may be an instance of the receiver 200.
  • the transmitter in radio communication with the receiver 200 may be an instance of the transmitter 100.
  • the transmitter 100 and/or the receiver 200 may a radio device.
  • the radio device may be connected to and/or part of a radio access network (RAN).
  • the radio device may be embodied by a base station of the RAN, nodes connected to the RAN for controlling the base station or a combination thereof.
  • the base station may encompass a network controller (e.g., a Wi-Fi access point) or a radio access node (e.g. a 3G Node B, a 4G eNodeB or a 5G gNodeB) of the RAN.
  • the base station may be configured to provide radio access.
  • a radio device may include a mobile (or portable) station or a radio device connectable to the RAN.
  • the radio device may be a user equipment (UE) and/or a device for machine-type communication (MTC).
  • the transmitter 100 and the receiver 200 may be configured to wirelessly connect to each other, e.g., in an ad-hoc radio network or via 3GPP sidelinks.
  • Fig. 3 shows a flowchart for a method 300 of transmitting PDUs in a radio
  • the method comprises or triggers a step 302 of receiving one or more control messages indicative of QoS requirements for the radio communication.
  • the QoS requirements include a control command for a reliability of the radio communication and a control command for a latency of the radio communication.
  • the method further comprises or triggers a step 306 of transmitting a batch of redundant PDUs from the transmitter to the receiver. A number of the redundant PDUs per batch depends on the control command for the reliability. A temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • the method 300 further comprises or triggers a step 304 of generating the redundant PDUs by copying a data unit (e.g., an RLC PDU or a MAC SDU).
  • the data unit may define the content of the batch of redundant PDUs.
  • the step 304 may be a substep of the step 302 or 306.
  • the method 300 may be performed by the transmitter 100.
  • the modules 102, 104 and 106 may perform the steps 302, 304 and 306, respectively.
  • Fig. 4 shows a flowchart for a method 400 of receiving PDUs in a radio
  • the method comprises or triggers a step 402 of transmitting, to the transmitter, one or more control messages indicative of QoS requirements for the radio communication.
  • the QoS requirements include a control command for a reliability of the radio communication and a control command for a latency of the radio communication.
  • the method further comprises or triggers a step 404 of receiving a batch of redundant PDUs from the transmitter. A number of the redundant PDUs per batch depends on the control command for the reliability. A temporal spread of the redundant PDUs per batch depends on the control command for the latency.
  • the method 400 further comprises or triggers a step 406 of removing redundant PDUs based on identical sequence numbers (e.g., an RLC sequence number). Only one of the redundant PDUs, e.g., the first successfully received PDU, of the batch is forwarded towards higher layers as a representative of the entire content of the batch.
  • the step 406 may be a substep of the step 404.
  • the method 400 may be performed by the receiver 200.
  • the modules 202, 204 and 206 may perform the steps 402, 404 and 406, respectively.
  • Embodiments of the technique may selectively generate and transmit the batch of redundant PDUs.
  • the redundant batch transmission may be triggered by one of the control messages (e.g., in the steps 302 and 402), e.g., indicative of a C- MTC or URLLC.
  • the transmitter 100 and the receiver 200 may maintain compatibility with at least one of IEEE 802.11 (WLAN), IEEE 802.15.1
  • Wired Wired fidelity
  • Wired Wi-Fi
  • Wi-Fi Wireless Fidelity
  • Wired Wi-Fi
  • Wi-Fi Wireless Fidelity
  • Wi-Fi Wireless Fidelity
  • Wi-Fi Wireless Fidelity
  • the technique can increase the reliability of the radio communication, e.g., as compared to LTE and/or for C-MTC or URLLC use-cases.
  • the transmission reliability can be achieved while also fulfilling the latency requirements for the radio
  • the PDUs and/or the SDUs may also be referred to as data units, data packets or briefly as "packets".
  • Reliability may be defined as the probability that a certain data packet from the transmitter 100 is successfully delivered to the receiver 200 within a pre-defined delay, i.e., latency.
  • Packet error rate (PER) is used as a measure of reliability at the application level, which is often also referred as block error probability (BLEP) at the lower layers of the protocol stack.
  • BLEP block error probability
  • the technique may be implemented by transmitting, in the step 106, multiple redundant packets (e.g., copies of packets) in a pattern across.
  • the pattern may comprise radio resources on (a) consecutive subframes; (b) different carriers
  • the technique is preferably implemented without relying on explicit (e.g., NACK-triggered) retransmissions.
  • explicit e.g., NACK-triggered
  • the latency of the radio communication can be controlled and latency requirements can be fulfilled.
  • the size of the pattern i.e., the number of redundant packets transmitted across time, frequency and/or spatial streams, may be controlled by the one or more control messages, e.g., in a redundancy control mechanism, based on the step 302.
  • the redundancy control mechanism may be implemented by exploiting an
  • acknowledgment feedback (e.g., indicative of a positive acknowledgment, ACK, or a negative acknowledgement, NACK) on packets of a previous batch of packets as the feedback of a closed-loop control received in the step 302 to adapt the redundancy in the transmission of the next batch according to the step 306.
  • the temporal extent of the pattern i.e., the temporal spread or distribution of the transmitted redundant packets across time, may be controlled by the one or more control messages, e.g., in a latency control mechanism, based on the step 302.
  • the redundancy control mechanism and the latency control mechanism may be implemented as one control mechanism.
  • One or each of the number and the temporal spread of the redundant PDUs in the batch may depend on at least one common control command in the control messages, e.g., a network policy or a network load (e.g., of the RAN comprising the transmitter 100), a device capability (e.g., of the receiver 200), the reliability control command and the latency control command for the radio communication.
  • the redundancy control mechanism and/or the latency control mechanism may be implemented as a feedback (or closed-loop) control mechanism.
  • the technique may further allow an adaptation and/or a configuration to specific targets for the reliability as well as the latency at runtime. For example, at least one of the reliability and the latency may be changed based on one or more of the control messages after the radio communication has been established. At most one of the reliability (e.g., limit) and the latency (e.g., a limit) may be predefined on or before establishing the radio communication.
  • terminologies such as base station (particularly, eNodeB or eNB) and UE for the transmitter 100 and the receiver 200 are non-limiting and do not imply a certain hierarchical relation between the transmitter 100 and the receiver 200.
  • the transmitter 100 may be considered as a radio device "1" and the receiver 200 may be considered as a radio device "2". These two devices 100 and 200 communicate with each other over some radio channel.
  • Fig. 5 schematically illustrates a block diagram for an exemplary protocol stack 500 of the radio communication.
  • the protocol stack 500 of 3GPP LTE is outlined in Fig. 5 and briefly described below in the light of the latency and the reliability of the radio communication.
  • Corresponding features for a transmission direction and reception direction may be implemented at the transmitted 100 and the receiver 200, respectively, at least for backward compatibility.
  • the physical (PHY) layer 502 provides adaptive coding, modulation and power control as well as multi-antenna processing.
  • a 24-bit cyclic redundancy check (CRC) is inserted (in the transmission direction), leading to a residual error of 10-7.
  • the medium access control (MAC) layer 504 does multiplexing and scheduling of data from different radio bearers.
  • Hybrid ARQ (HARQ) with incremental redundancy is implemented.
  • a typical residual error probability of 10-4 to 10-3 remains within the HARQ protocol, which is mainly due to unreliable but efficient HARQ
  • the MAC layer at the transmitter 100 erroneously considers the MAC PDU to be successfully received and, thus, refrains from a HARQ retransmission, while a reordering timer at the radio-link control (RLC) layer 506 of the receiver 200 expires and triggers an RLC retransmission according to an ARQ functionality.
  • the RLC retransmission is even more time-consuming than the HARQ retransmission.
  • the batch of redundant PDUs (e.g., copies of MAC PDUs) transmitted in advance at the MAC layer 504 of the transmitter 100 according to the step 306 marginalizes the possibility that the RLC layer 506 has to be involved. That is, only in the extremely rare case of all the redundant PDUs at the MAC layer 504 of the receiver 200 being received with failure, the RLC layer 506 triggers an RLC retransmission.
  • the control command for the reliability may control the number of redundant PDUs so as to maintain a certain fraction of successfully received PDUs among all the redundant PDUs.
  • the radio link control (RLC) layer 506 provides segmentation and concatenation of data and, if configured in an acknowledged mode, provides ARQ functionality, i.e., the RLC retransmissions selectively based on a sliding window scheme.
  • the RLC layer 506 provides in-sequence delivery to higher layers. Since both data and RLC ARQ feedback, i.e., the RLC status report, is transmitted using the 24-bit CRC from the PHY layer 502, a residual error probability of 10-7 remains on this layer.
  • the protocol data convergence protocol (PDCP) on layer 508 provides header compression to reduce overhead, as well as ciphering of data to be transmitted.
  • the PDCP layer 508 at the eNB functions as an anchor point for handovers and provides lossless inter-eNB handover by forwarding outstanding data from source to target eNB. It is affected with the same residual error as on the RLC layer 506, i.e., no additional CRC or ARQ is done on this protocol layer in typical LTE configurations.
  • the radio resource control (RRC) protocol on layer 510 handles control signaling messages between eNB and UEs, and uses the same LTE protocol stack as user plane, i.e., Internet protocol (IP) data. This means RRC control signaling as well as IP data is sent via the PDCP layer 508, the RLC layer 506, the MAC layer 504 and the PHY layer 502.
  • RRC radio resource control
  • the RRC layer 510 is connected to the core network in the non- access stratum (NAS).
  • NAS non- access stratum
  • user traffic is exchanged between the PDCP layer 508 and an I P layer 512.
  • CA Carrier Aggregation
  • HARQ entities running in parallel (e.g., multiple entities of the PHY layer 502 and parts of the MAC layer 504) per radio communication between a pair of transmitter 100 and receiver 200.
  • Fig. 6 schematically illustrates first embodiments of protocol stacks 500, which are implementable at the transmitter 100 and the receiver 200, respectively, for the radio communication.
  • control message reception module 102 and the control message transmission module 202 may be implemented at any of the layers 502 to 508.
  • the modules 104 and 106 as well as the modules 204 and 206 are implemented at the MAC layer 504.
  • the transmitter 100 comprises the redundancy introduction module 104 (which is also referred to as "add redundancy functionality") at the upper end of the MAC layer 504, i.e., in the MAC layer 504 at the upstream end for processing data to be transmitted.
  • the redundancy is added in terms of outgoing packets, e.g., PDUs at the MAC layer 504.
  • the redundancy introduction module 104 generates multiple copies of the incoming packets (e.g., RLC PDUs or MAC SDUs) within the MAC layer 504 or between the MAC layer 504 and the RLC layer 506.
  • the redundancy in terms of redundant MAC PDUs may be the result of copying MAC SDUs (as packets incoming to the MAC layer 504).
  • the removal of redundancies is also residing at the MAC layer 504.
  • the transmission module 106 distributes the redundant PDUs (or briefly: "packets") across consecutive HARQ processes.
  • Fig. 7 schematically illustrates a pattern 700 of radio resources 702 occupied by the redundant PDUs (or "packets") 704 of the batch transmitted in the step 306.
  • the pattern 700 is arranged in a grid including time 706 (e.g., in terms of subframes or TTIs) and radio frequency 708 (e.g., in terms of sub-carries).
  • the PDUs 704 are transmitted on radio resources 702 on consecutive subframes, e.g., on the same carrier and/or set of sub-carriers.
  • the first correct PDU 704 (i.e., the first of the redundant PDUs 704 with positive CRC) is forwarded to the RLC layer 506 (e.g., as an MAC SDU).
  • the RLC layer 506 e.g., as an MAC SDU.
  • no retransmissions will be triggered, e.g., regardless of whether such PDUs are correctly received or incorrectly received (including PDUs that are not at all received).
  • control messages may be indicative (e.g., by using the ACK and NACK signals as PDU-individual feedback without the NACK signal triggering a retransmission) of the correctly and incorrectly received PDUs in the pattern 700.
  • the transmitter 100 and/or the receiver 200 may gather statistics on the individual radio resources (e.g., resource elements or physical resource blocks).
  • the pattern 700 may be control (i.e., changed for transmissions 306 of redundant PDUs in future) based on the statistics.
  • a redundancy control mechanism may be triggered in an instance of the step 402, optionally using the acknowledgment feedback of the MAC layer 504 (i.e., the ACK and NACK signals) and/or depending on a ratio of successfully received PDUs for the entire batch.
  • the number of ACK and NACK signals, or their ratio may represent the control commands.
  • the number of redundant PDUs (e.g., the number of copies) is configured at runtime by means of the control messages fed back in the steps 302 and 402.
  • a pre-defined redundancy can be introduced by the module 104 based on a service type using, for instance, a look-up table or prior configuration.
  • an adaption scheme can be applied which controls the redundancy of packets (i.e., the number of redundant PDUs) at runtime.
  • the redundant PDUs are assigned to consecutive HARQ processes.
  • the scheduler at the MAC layer 504 assigns the redundant PDUs 704 to the 8 HARQ processes (of one HARQ entity) available in an LTE implementation.
  • the redundant PDUs 704 are assigned to consecutive HARQ processes, e.g., an original PDU 704 symbolically represented by X is assigned to a HARQ process i, a duplicate X* of the original PDU 704 is assigned to a HARQ process i+1, and so forth.
  • the redundant PDUs 704 defining the batch are distributed across consecutive subframes 706.
  • the second PDU can already be checked in the second subframe or TTI (e.g., without waiting for triggering and receiving a retransmission).
  • the chance that the content (i.e., any one of the redundant PDUs 704) is successfully delivered is increased, particularly in case of short term distortions (e.g., due to fading and multipath propagation) of the channel used for the radio communication. If one of the transmissions is not successful, this will be very likely detected by one of the CRC checksums per HARQ processes.
  • the successfully received PDU (e.g., the first PDU with correct CRC) is passed on to the RLC layer 506 (e.g., in a conventional manner).
  • the RLC layer 506 e.g., in a conventional manner.
  • Other introduced redundancies, i.e., other PDUs 704 of the same batch, are discarded.
  • two variants are implementable.
  • one variant e.g., without controlling the QoS requirements during the radio communication
  • no other variant e.g., without controlling the QoS requirements during the radio communication
  • acknowledgment feedback (i.e., neither ACK nor NACK) is transmitted. That is, no control messages corresponding to retransmission requests are transmitted by the receiver 200.
  • an acknowledgment feedback is transmitted from the receiver 200 for at least some of the other HARQ process, e.g., for each HARQ process associated with the batch.
  • the number of redundant PDUs used by the transmitter 100 is controlled, as an example for the redundancy control mechanism.
  • any embodiment may implement two variants for the respective HARQ process.
  • the erroneous redundancies i.e., the PDUs 704 received with the negative CRC
  • neither ACK nor NACK is send, i.e., no retransmissions are requested.
  • Fig. 8 schematically illustrates block diagrams for the protocol stacks 500 at the transmitter 100 and the receiver 200, respectively, according to the second embodiment.
  • Redundant PDUs 704 are distributed across different HARQ entities in the
  • transmission module 106 at the transmitter 100 which leads to a pattern 700 of radio resources 702 carrying the redundant PDUs 704 on at least two different carriers, as schematically illustrated in the Fig. 9 on a grid spanned by time 706 and frequency 708.
  • the different HARQ entities may be associated with different spatial streams.
  • the redundant PDUs 704 are transmitted in the step 306 on different carriers (e.g., sub-bands, optionally using CA).
  • the first of the redundant PDU 704 that is correctly received at the receiver 200 is forwarded to the RLC layer 506. For all other packets, no retransmissions will be triggered. Rather, in any embodiment, a redundancy control mechanism may be triggered by means of the control messages in further instances of the step 402.
  • the second embodiments assign a subset or all of the redundant PDUs 704 (e.g., copies) to different (i.e., multiple) HARQ entities in the transmission module 106.
  • the disjoint subsets of the redundant PDUs 704 are transmitted on different carriers. This has the advantage that the redundant PDUs 704 are protected by entirely different channel conditions of the different carriers. If one carrier suffers from interference, the others might still have good channel conditions.
  • two sub-bands is used. Similar to the first embodiments, i.e., the usage of consecutive HARQ processes, if any one of the PDUs 704 is send successfully via any of the HARQ entities from the transmitter 100 to the receiver 200, the first PDU 704 with the correct CRC is passed on to the RLC layer 506. Other redundant PDUs 704 (e.g., copies) are discarded.
  • no acknowledgment feedback i.e. neither ACK nor NACK
  • the receiver 200 i.e., no retransmissions are issued.
  • the first packet with the correct CRC is simply passed on to the RLC layer, and for the other HARQ entities and the HARQ processes therein, control messages (e.g., reusing the existing acknowledgment feedback) are transmitted in further instances of the steps 402, which serve as the feedback of the redundancy control mechanism obeyed by the transmitter 100 in the subsequent instance of the transmission step 306.
  • any embodiment may implement one of the following two variants.
  • erroneous duplications are discarded, and neither ACK nor NACK is send back to the transmitter 100, i.e., no retransmissions are requested.
  • redundancy control mechanism which is implementable by any of the embodiments, is described.
  • Adding redundancies in the step 304 can lead to a significant overprovisioning of the radio resources 702.
  • a feedback is transmitted as an instance of the control messages. The feedback is based on the number of CRC fails, e.g., determined by the HARQ entities and the HARQ processes therein.
  • the number of CRC fails per batch is as an indicator that steers the number of radio resources 702 and the corresponding number of redundant PDUs 704 transmitted on such radio resources 702 (e.g., in the respective HARQ entities and HARQ processes therein) according to the step 306. Moreover, if the latency requirements are satisfied and enough radio resources 702 are available, the remaining radio resources are feedback-controlled to steer the reliability of the radio communication, i.e., the number of redundancies.
  • the feedback for the feedback control mechanism may be implemented using, and reinterpreting, an existing acknowledgment feedback, e.g., in the HARQ signaling.
  • an existing acknowledgment feedback e.g., in the HARQ signaling.
  • Such a feedback in the control messages can be readily implemented, e.g., in existing LTE networks, and is applicable in other systems.
  • command interpretations of an ACK bit in the acknowledgment feedback are applied with the following meaning (which deviates from a conventional interpretation of HARQ feedbacks).
  • No ACK i.e., a missing ACK
  • An ACK bit being equal to "0" indicates to the transmitter 100 that the number of redundant copies can be decreased and/or should be decrease.
  • An ACK bit being equal to "1" indicates that the number of redundant copies can be increased and/or should be increased.
  • the acknowledgment feedback (as an instance of the control message) comprises (e.g., at least) two ACK bits with the following command interpretation.
  • the acknowledgment feedback comprising "00" is indicative of the number of redundant copies being appropriate, i.e. no change of the number of redundant PDUs 704 per batch is commanded.
  • the acknowledgment feedback comprising "01" is indicative to the transmitter 100 that the number of redundant copies or should can be decreased.
  • the acknowledgment feedback comprising "10" is indicative to the transmitter 100 that the number of redundant copies can or should be increased.
  • No command may be associated with the bit string "11" in the acknowledgment feedback, and/or this value may be interpreted as a transmission error in the acknowledgment feedback.
  • multiple acknowledgment feedbacks (as an instances of the control messages) relating to the same batch of previously transmitted redundant PDUs 704 (e.g., all acknowledgment feedbacks relating to the same batch) are collectively interpreted by the transmitter 100 as a feedback command for controlling reliability and/or latency.
  • the acknowledgment feedbacks may comprise one or multiple ACKs and/or one or multiple NACKs with respect to the same batch of redundant PDUs 704.
  • the acknowledgment feedbacks, received in one or more instances of the step 302 trigger the following feedback control commands at the transmitter 100.
  • a single ACK is indicative of the number of redundant PDUs 704 per batch being appropriate, i.e., the transmitter 100 maintains the number of redundant PDUs 704 per batch unchanged.
  • Multiple ACKs are indicative to the transmitter 100 that the number of redundant PDUs 704 can or should be increased. For example, two or three ACKs may be indicative of increasing the number of redundancies by two or three redundant PDUs 704, respectively.
  • Multiple NACKs are indicative that the number of redundant PDUs 704 per batch can or should be decreased, e.g., two or three NACKs to decrease the number of redundancies by two or three, respectively.
  • the one or more control messages may comprise one or more dedicated data messages, e.g., with the following meaning.
  • One or more of the control messages may comprise a bit string (e.g., more than 2 bits) or a certain data message.
  • the bit string or the data message may directly be indicative of a varying step size for incrementing and/or decrementing the number of redundant PDUs 704 per batch.
  • the transmitter 100 and the receiver 200 may be configuration (e.g., preconfigured at deployment and/or by an initial control message). Alternatively or in addition, the configuration may be determined in a negotiation between the transmitter 100 and the receiver 200, e.g., upon establishing the radio communication.
  • any one of the feedback implementations is combinable with any one of the embodiments.
  • the embodiments, particularly the first and second embodiments are not mutually exclusive. Components from one exemplary embodiment may be present in another exemplary embodiment. A person skilled in the art can readily implement such components described in the context of one exemplary embodiment in the other exemplary embodiments.
  • Figs. 10 to 13 show non-limiting examples of introducing redundancy in patterns 700 to achieve reliability with different latency requirements (also referred to as latency targets).
  • the pattern 700 may be determined and/or changed by the transmitter 100 in response to the control messages, e.g., at runtime.
  • the factors influencing such a decision include the QoS requirements (also referred to as QoS targets) themselves (i.e., latency and reliability targets) as well as, optionally, the available radio resources, their individual quality and/or the overall traffic characteristics.
  • Fig. 10 schematically illustrates a pattern 700 fulfilling tighter latency requirements compared to Fig. 11 and Fig. 12.
  • the scheme in Fig. 11 is exercised compared to Fig. 10 if the latency requirement is not as tight or if radio resources are not available on another carrier.
  • a decision for the pattern 700 according to Fig. 11 may be triggered based on the quality of the carrier itself.
  • Fig. 13 schematically illustrates a pattern 700 that achieves the highest degree of reliability, e.g., compared to the other three patterns in Figs. 10 to 12.
  • the pattern 700 of Fig. 13 may be the result of combining the first and second embodiments.
  • radio communication may comprise an uplink transmission (e.g., from an UE as the transmitter 100 to an eNodeB as the receiver 200) and/or a downlink transmission (e.g., from an eNodeB as the transmitter 100 to UE as the receiver 200).
  • the technique is applicable for the radio communication comprising a D2D communication.
  • the patterns 700 of Figs. 10 to 13 extend in time 706 and frequency 708, the patterns 700 may, alternatively or in addition to the diversity in frequency 708, extend in different spatial streams. That is, the pattern 700 of the radio resources 702 for the redundant PDUs 704 are distributed across time, frequency and/or spatial streams in order to satisfy the reliability as well as latency
  • the pattern 700 is also referred to as redundancy options.
  • the patterns may be further tailored (e.g., redundancy options may be selected, configured, granted and/or assigned) based on the device capabilities and/or deployment conditions.
  • a radio device e.g., taking either the role of the transmitter 100 or the receiver 200, e.g., an MTC device
  • radio device is selected and/or configured with the device capabilities as addition constraints.
  • the redundancy control mechanism may collect the feedback (as one or more control messages) from each HARQ entity. Based on the feedback of each HARQ entity, the control mechanism may adjust the number of redundant PDUs 704 per batch and/or per HARQ entity, and distribute the PDUs 704 accordingly, e.g., using any of the example patterns 700. For example, more redundancies (i.e., more of the redundant PDUs 704 in the batch) may be transmitted over one of the HARQ entities that requested more redundancies.
  • the technique may be implemented exclusively on the MAC layer 504 of the transmitter 100 and the receiver 200.
  • the technique may be transparent to other layers, e.g., the PHY layer 502 and/or the RLC layer 506.
  • the RLC layer 506 may be unaffected by the technique.
  • the RLC layer 506 may be configured such that ARQ is enabled or disabled (i.e., acknowledged mode, AM, or unacknowledged mode, UM, of the RLC layer 506).
  • ARQ is enabled or disabled (i.e., acknowledged mode, AM, or unacknowledged mode, UM, of the RLC layer 506).
  • ARQ at the RLC layer 506 can significantly increase the reliability at the cost of increasing delays (and, thus, latency).
  • an RLC retransmission can lead to multiple MAC HARQ
  • the RLC retransmission can also be reduced by the technique (e.g., even without changes to the RLC layer 506).
  • Fig. 14 shows a flowchart for a first method embodiment of the method 300 of Fig. 3, which is combinable with any implementation or embodiment disclosed herein.
  • the method 300 may be performed in batches, wherein an arrival 301 of a packet, e.g., an SDU for the MAC layer 504 from the RLC layer 506, triggers the method 300, particularly the transmission 306 of a corresponding batch, i.e., a batch of redundant PDUs 704 each including the content of the packet.
  • a packet e.g., an SDU for the MAC layer 504 from the RLC layer 506
  • a corresponding batch i.e., a batch of redundant PDUs 704 each including the content of the packet.
  • the QoS requirements are determined based on the control messages, which may include initial control messages upon deployment of the pair of transmitter 100 and the receiver 200 or upon setting up the radio communication and/or feedback control messages (e.g., the acknowledgment feedback) received in response to a batch previously transmitted on the same radio communication.
  • the control messages may include initial control messages upon deployment of the pair of transmitter 100 and the receiver 200 or upon setting up the radio communication and/or feedback control messages (e.g., the acknowledgment feedback) received in response to a batch previously transmitted on the same radio communication.
  • the pattern 700 may be determined.
  • the step 303 may be implemented as a substep of the step 304 or 306.
  • Fig. 15 shows a flowchart for second method embodiments of the methods 300 and 400 of Figs. 3 and 4, respectively. Implementations of the steps of the methods 300 and 400 are indicated by corresponding reference signs.
  • a step 305 of the method 300 the redundant PDUs 704 are passed to the multiple HARQ entities, e.g., according to the second embodiment of the transmitter 100, in order to transmit in the step 306 those PDUs according to the pattern 700.
  • the step 305 may be combined with the step 303 of the first method embodiment of Fig. 14 and/or may be a substep of the step 304 or 306.
  • the redundant PDUs 704 may be transmitted over multiple HARQ entities and HARQ processes without the
  • the one or more control messages may be configuration messages received upon deployment in the step 302.
  • the selective forwarding 405 performed by the receiver 200 may be a substep of a CRC verification in the step 404 or may be implemented in the removal step 406.
  • the removal of redundant PDUs 704 may be based on the RLC sequence number, which is identical in the redundant PDUs 704 as they include identical copies of the RLC PDU.
  • the redundancy removal module 206 performing the step 406 may include a list or window of forwarded RLC sequence numbers ensuring that each RLC sequence numbers is forwarded to the RLC layer 506 only one.
  • Fig. 16 shows a flowchart for a third method embodiment of the method 300 of Fig. 3.
  • Fig. 17 shows a flowchart for a third method embodiment of the method 400 of Fig. 4.
  • the third method embodiments may be implemented as an alternative to the respective second method embodiments in that the implementation does not require configuring the transmitter 100 and the receiver 200 upon deployment.
  • the QoS requirements are defined based on the feedback from the receiver 200 to the transmitter 100 in the step 302 and 402 for the redundancy control mechanism.
  • the third method embodiments may be implemented as an extension of the respective second method embodiments so that the QoS requirements preconfigured at deployment are changed during the radio communication by the redundancy control mechanism based on the feedback.
  • Fig. 18 shows a schematic block diagram for an embodiment of a transmitting station 1800 embodying the transmitter 100.
  • the transmitter 100 comprises one or more processors 1804 for performing the method 300 and memory 1806 coupled to the one or more processors 1804.
  • the memory 1806 may be encoded with instructions that implement at least one of the modules 102, 104 and 106.
  • the one or more processors 1804 may be a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, microcode and/or encoded logic operable to provide, either alone or in conjunction with other components of the transmitter 100, such as the memory 1806, transmitter functionality.
  • the one or more processors 1804 may execute
  • Such functionality may include providing various features and steps discussed herein, including any of the benefits disclosed herein.
  • the expression "being operative to perform an action” may denote the transmitter 100 being configured to perform the action.
  • the transmitter 100 may be embodied by a transmitting station 1800 (e.g., a base station or a mobile station).
  • the transmitting station 1800 comprises a radio interface 1802 coupled to the transmitter 100 for radio communication with one or more receivers.
  • Fig. 19 shows a schematic block diagram for an embodiment of a transmitting station 1900 embodying the receiver 200.
  • the receiver 200 comprises one or more processors 1904 for performing the method 400 and memory 1906 coupled to the one or more processors 1904.
  • the memory 1906 may be encoded with instructions that implement at least one of the modules 202, 204 and 206.
  • the one or more processors 1904 may be a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, microcode and/or encoded logic operable to provide, either alone or in conjunction with other components of the receiver 200, such as the memory 1906, receiver functionality.
  • the one or more processors 1904 may execute
  • Such functionality may include providing various features and steps discussed herein, including any of the benefits disclosed herein.
  • the expression "being operative to perform an action” may denote the receiver 200 being configured to perform the action.
  • the receiver 200 may be embodied by a receiving station 1900 (e.g., a base station or a mobile station).
  • the transmitting station 1900 comprises a radio interface 1902 coupled to the receiver 200 for radio communication with one or more transmitters.
  • embodiments of the technique enable higher reliability of a communication system (e.g., LTE, NR, UMTS, etc.) by introducing redundant packet transmissions in a controlled manner. Same or further embodiments can obtain reduced transmission latency while ensuring the reliability target. The reliability may be governed through redundant transmissions.
  • a communication system e.g., LTE, NR, UMTS, etc.
  • An adaptive mechanism e.g., a feedback control mechanism
  • the adaptive mechanisms allow the communication system to handle variable traffic patterns, and different QoS requirements at runtime, i.e., different latency and reliability requirements.
  • utilization of radio capacity can be improved by means of the redundancy control scheme.
  • the technique can be deployed by applying upgrades in terms of functionality and/or configuration to existing systems (e.g., 3GPP LTE systems).
  • the upgrades allow supporting URLL or C-MTC application targets, particularly rapidly changing targets.
  • the technique can be implemented based on simulations using a software-defined radio (SDR) framework (e.g., existing simulators designed to support development, deployment and/or maintenance of real-time software radio applications) or any experimental or commercial prototype, e.g., for implementing the functional dependency of the pattern on the QoS requirements and the channel state.
  • SDR software-defined radio

Abstract

L'invention concerne une technique qui permet de communiquer des unités de données du protocole (PDU) dans une communication radio d'un émetteur (100) à un récepteur (200). Selon un aspect de procédé de la technique, un ou plusieurs messages de commande indiquant les exigences de qualité de service (QoS) pour la communication radio sont reçus. Les exigences de QoS comprennent une instruction de commande pour une fiabilité de la communication radio et une instruction de commande pour une latence de la communication radio. Un lot de PDU redondantes est transmis de l'émetteur (100) au récepteur (200). Un nombre de PDU redondantes par lot dépend de l'instruction de commande pour la fiabilité et un étalement temporel des PDU redondantes par lot dépend de l'instruction de commande pour la latence.
PCT/EP2017/072842 2017-09-12 2017-09-12 Communication radio d'unités de données de paquets critiques WO2019052627A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/EP2017/072842 WO2019052627A1 (fr) 2017-09-12 2017-09-12 Communication radio d'unités de données de paquets critiques
EP17771705.5A EP3682575B1 (fr) 2017-09-12 2017-09-12 Communication radio d'unités de données de paquets critiques
US16/646,301 US11343714B2 (en) 2017-09-12 2017-09-12 Radio communication of critical packet data units

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2017/072842 WO2019052627A1 (fr) 2017-09-12 2017-09-12 Communication radio d'unités de données de paquets critiques

Publications (1)

Publication Number Publication Date
WO2019052627A1 true WO2019052627A1 (fr) 2019-03-21

Family

ID=59930333

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/072842 WO2019052627A1 (fr) 2017-09-12 2017-09-12 Communication radio d'unités de données de paquets critiques

Country Status (3)

Country Link
US (1) US11343714B2 (fr)
EP (1) EP3682575B1 (fr)
WO (1) WO2019052627A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210211239A1 (en) * 2018-09-18 2021-07-08 Huawei Tecnologies Co., Ltd. Data Transmission Method and Apparatus

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11595796B2 (en) * 2019-11-08 2023-02-28 Qualcomm Incorporated Methods and apparatus for CV2X communication
CN114902568A (zh) * 2019-12-19 2022-08-12 诺基亚技术有限公司 协议数据单元（pdu）错误概率反馈

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120159278A1 (en) * 2010-06-22 2012-06-21 Yu-Chih Jen Method of Handling a Damage Information-Assisted Hybrid ARQ Scheme and Related Communication Device

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4405875B2 (ja) * 2004-08-25 2010-01-27 富士通株式会社 エラー訂正用データの生成方法及び生成装置並びに生成プログラム及び同プログラムを格納したコンピュータ読み取り可能な記録媒体
ES2949260T3 (es) 2007-06-18 2023-09-27 Optis Wireless Technology Llc Procedimiento y disposición en una red de telecomunicaciones móviles para Solicitud de Repetición Automática Híbrida HARQ con agrupación de intervalos de tiempo de transmisión TTI y con redundancia incremental
KR100979510B1 (ko) * 2008-06-03 2010-09-02 주식회사 세아네트웍스 Ｈａｒｑ를 지원하는 무선 통신 시스템 및 데이터 전송방법
KR101669966B1 (ko) 2009-05-11 2016-10-27 엘지전자 주식회사 다중 반송파를 지원하는 무선 통신 시스템에서 중복 데이터를 송신 및 수신하는 방법 및 장치
EP2791744A4 (fr) * 2011-12-16 2015-06-10 Schneider Electric Usa Inc Architecture électrique de co-localisation
CN103312441B (zh) * 2012-03-15 2017-11-17 华为技术有限公司 数据包传输方法及系统、发送端设备与接收端设备
WO2017003047A1 (fr) 2015-07-02 2017-01-05 엘지전자(주) Procédé de transmission et de réception de données de liaison montante dans un système de communications sans fil, et dispositif associé
US10484129B2 (en) * 2016-01-21 2019-11-19 Qualcomm Incorporated Protocol layer packet coding for transmitter/receiver buffer optimization
WO2017172983A1 (fr) * 2016-03-30 2017-10-05 Idac Holdings, Inc. Système et procédé pour une modulation spatiale avancée dans des systèmes 5g
US10630410B2 (en) * 2016-05-13 2020-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Network architecture, methods, and devices for a wireless communications network
US10367677B2 (en) * 2016-05-13 2019-07-30 Telefonaktiebolaget Lm Ericsson (Publ) Network architecture, methods, and devices for a wireless communications network
US10778779B2 (en) * 2016-06-17 2020-09-15 Huawei Technologies Co., Ltd. Method and system for session management for ultra reliable and low latency communications in high mobility scenarios
US10334598B2 (en) * 2017-04-25 2019-06-25 Motorola Mobility Llc Determining a priority order based on uplink transmission parameters

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120159278A1 (en) * 2010-06-22 2012-06-21 Yu-Chih Jen Method of Handling a Damage Information-Assisted Hybrid ARQ Scheme and Related Communication Device

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
B. HOLFELD ET AL.: "Wireless Communication for Factory Automation: An Opportunity for LTE and 5G Systems", IEEE COMMUNICATION MAGAZINE, June 2016 (2016-06-01)
HUAWEI ET AL: "Redundancy Schemes below PDCP Layer", vol. RAN WG2, no. Athens, Greece; 20170213 - 20170217, 12 February 2017 (2017-02-12), XP051211890, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170212] *
S. A. ASHRAF ET AL.: "Ultra-Reliable and Low-Latency Communication for Wireless Factory Automation: From LTE to 5G", PROC. OF IEEE CONFERENCE ON EMERGING TECHNOLOGIES AND FACTORY AUTOMATION, September 2016 (2016-09-01)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210211239A1 (en) * 2018-09-18 2021-07-08 Huawei Tecnologies Co., Ltd. Data Transmission Method and Apparatus

Also Published As

Publication number Publication date
US20200296622A1 (en) 2020-09-17
EP3682575A1 (fr) 2020-07-22
US11343714B2 (en) 2022-05-24
EP3682575B1 (fr) 2023-04-05

Similar Documents

Publication Publication Date Title
CN108541360B (zh) 通信系统
US10530431B2 (en) Method and apparatus in a wireless communication system
KR101343899B1 (ko) 정보를 처리하기 위한 방법, 시스템 및 기기
EP3566353B1 (fr) Procédés et appareils dans un système de communication sans fil
EP3497849B1 (fr) Synchronisation harq de liaison descendante à tdd avec 1 ms tti et temps de traitement réduit
CN113785516A (zh) 侧链数据分组确认
US11343714B2 (en) Radio communication of critical packet data units
CN110178330B (zh) 用于在无线电通信中传递数据的技术
CN116097592A (zh) 第二层协议层的无速率译码
US11277232B2 (en) Method and devices employing retransmission schemes
KR20190097963A (ko) 무선 통신 시스템에서 데이터 송수신 방법 및 장치
EP4101097B1 (fr) Appareil, procédé, et programme informatique
EP3542484B1 (fr) Technique de transfert de données dans une communication radio
WO2022223104A1 (fr) Transmission double d&#39;unités de données de protocole
EP4315693A1 (fr) Valeurs de paramètres de transmission dynamique pour retransmissions
WO2022223103A1 (fr) Duplication de liaison descendante d&#39;unités de données de protocole
JP2022068858A (ja) Ｈａｒｑ再送信を処理するデバイス
CN116762294A (zh) 无线通信中的反馈技术

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17771705

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017771705

Country of ref document: EP

Effective date: 20200414