EP3707844A1 - Réémission robuste d'accusés de réception - Google Patents

Réémission robuste d'accusés de réception

Info

Publication number
EP3707844A1
EP3707844A1 EP18807810.9A EP18807810A EP3707844A1 EP 3707844 A1 EP3707844 A1 EP 3707844A1 EP 18807810 A EP18807810 A EP 18807810A EP 3707844 A1 EP3707844 A1 EP 3707844A1
Authority
EP
European Patent Office
Prior art keywords
acknowledgement
data
indication
value
retransmission request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP18807810.9A
Other languages
German (de)
English (en)
Other versions
EP3707844B1 (fr
Inventor
Srinivas YERRAMALLI
Xiaoxia Zhang
Jing Sun
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP3707844A1 publication Critical patent/EP3707844A1/fr
Application granted granted Critical
Publication of EP3707844B1 publication Critical patent/EP3707844B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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/1816—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of the same, encoded, message
    • 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/1607—Details of the supervisory signal
    • H04L1/1685—Details of the supervisory signal the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
    • 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1858—Transmission or retransmission of more than one copy of acknowledgement 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
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • 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/1614—Details of the supervisory signal using bitmaps
    • 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
    • H04L2001/125—Arrangements for preventing errors in the return channel

Definitions

  • the following relates generally to wireless communication, and more specifically to designs for robust acknowledgement retransmissions.
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power).
  • Examples of such multiple-access systems include fourth generation (4G) systems such as a Long Term Evolution (LTE) systems or LTE-Advanced (LTE-A) systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G fourth generation
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • 5G New Radio
  • a wireless multiple-access communications system may include a number of base stations or network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE).
  • UE user equipment
  • HARQ operations include a base station transmitting a downlink (DL) grant and data to a UE, and the UE sending an acknowledgement (e.g., either a positive acknowledgement (ACK) or a negative acknowledgement (NAK)) to the base station that indicates whether the UE was successful at decoding the data it received.
  • ACK positive acknowledgement
  • NAK negative acknowledgement
  • the base station may not receive an ACK/NAK from the UE even though the base station expects to receive one.
  • This scenario may correspond to various situations, such as: the DL grant was not received by the UE so the UE did not transmit an ACK/NAK, the UE transmitted an ACK/NAK but the signal quality (e.g., signal-to-interference-plus-noise-ratio (SINR)) was too low for the base station to receive the ACK/NAK, or, in shared spectrum (e.g., unlicensed) applications, the UE failed a listen-before-talk (LBT) attempt to transmit the ACK/NAK.
  • SINR signal-to-interference-plus-noise-ratio
  • the described techniques relate to improved methods, systems, devices, or apparatuses that support robust designs for acknowledgement (e.g., positive
  • ACK acknowledgement
  • NAK negative acknowledgement
  • a method of wireless communication may include receiving a transport block (TB) of data from a network, decoding the TB of data, transmitting to the network a first acknowledgement based on a result of the decoding, receiving a signal from the network that includes an acknowledgement retransmission request and a TB indication that indicates a TB of data to which the acknowledgement retransmission request relates, determining a second acknowledgement based on the acknowledgement retransmission request and the TB indication, and transmitting the second acknowledgement to the network.
  • TB transport block
  • the apparatus may include means for receiving a TB of data from a network, means for decoding the TB of data, means for transmitting to the network a first acknowledgement based on a result of the decoding, means for receiving a signal from the network that includes an
  • the apparatus may include a processor, memory coupled to the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to receive a TB of data from a network, decode the TB of data, transmit to the network a first acknowledgement based on a result of the decoding, receive a signal from the network that includes an acknowledgement retransmission request and a TB indication that indicates a TB of data to which the acknowledgement retransmission request relates, determine a second acknowledgement based on the acknowledgement retransmission request and the TB indication, and transmit the second acknowledgement to the network.
  • a non-transitory computer readable medium storing code for wireless communication is described.
  • the code may include instructions executable by a processor to receive a TB of data from a network, decode the TB of data, transmit to the network a first acknowledgement based on a result of the decoding, receive a signal from the network that includes an acknowledgement retransmission request and a TB indication that indicates a TB of data to which the acknowledgement retransmission request relates, determine a second acknowledgement based on the acknowledgement retransmission request and the TB indication, and transmit the second acknowledgement to the network.
  • a method of wireless communication may include transmitting to a user equipment (UE) a grant and a TB of data associated with the grant, transmitting a signal to the UE that includes an acknowledgement retransmission request and a TB indication related to the acknowledgement retransmission request, wherein the TB indication identifies the TB of data transmitted to the UE, and receiving an acknowledgement from the UE for the TB of data, the acknowledgement being associated with the acknowledgement retransmission request.
  • UE user equipment
  • the apparatus may include means for transmitting to a UE a grant and a TB of data associated with the grant, means for transmitting a signal to the UE that includes an acknowledgement retransmission request and a TB indication related to the acknowledgement
  • the TB indication identifies the TB of data transmitted to the UE, and means for receiving an acknowledgement from the UE for the TB of data, the acknowledgement being associated with the acknowledgement retransmission request.
  • the apparatus may include a processor, memory coupled to the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to transmit to a UE a grant and a TB of data associated with the grant, transmit a signal to the UE that includes an acknowledgement retransmission request and a TB indication related to the acknowledgement retransmission request, wherein the TB indication identifies the TB of data transmitted to the UE, and receive an acknowledgement from the UE for the TB of data, the acknowledgement being associated with the
  • a non-transitory computer readable medium storing code for wireless communication is described.
  • the code may include instructions executable by a processor to transmit to a UE a grant and a TB of data associated with the grant, transmit a signal to the UE that includes an acknowledgement retransmission request and a TB indication related to the acknowledgement retransmission request, wherein the TB indication identifies the TB of data transmitted to the UE, and receive an
  • acknowledgement from the UE for the TB of data the acknowledgement being associated with the acknowledgement retransmission request.
  • a method of wireless communication may include receiving a TB of data from a network, decoding the TB of data, transmitting to the network a first acknowledgement based on a result of the decoding, receiving an acknowledgement retransmission request from the network, and transmitting to the network a signal that includes the first acknowledgement and a TB indication, wherein the TB indication indicates that the first acknowledgement is associated with the TB of data.
  • the apparatus may include means for receiving a TB of data from a network, means for decoding the TB of data, means for transmitting to the network a first acknowledgement based on a result of the decoding, means for receiving an acknowledgement retransmission request from the network, and means for transmitting to the network a signal that includes the first acknowledgement and a TB indication, wherein the TB indication indicates that the first acknowledgement is associated with the TB of data.
  • the apparatus may include a processor, memory coupled to the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to receive a TB of data from a network, decode the TB of data, transmit to the network a first acknowledgement based on a result of the decoding, receive an acknowledgement retransmission request from the network, and transmit to the network a signal that includes the first acknowledgement and a TB indication, wherein the TB indication indicates that the first acknowledgement is associated with the TB of data.
  • a non-transitory computer readable medium storing code for wireless communication is described.
  • the code may include instructions executable by a processor to receive a TB of data from a network, decode the TB of data, transmit to the network a first acknowledgement based on a result of the decoding, receive an acknowledgement retransmission request from the network, and transmit to the network a signal that includes the first acknowledgement and a TB indication, wherein the TB indication indicates that the first acknowledgement is associated with the TB of data.
  • a method of wireless communication may include transmitting to a UE a TB of data, transmitting to the UE an acknowledgement retransmission request for the TB of data, receiving a signal from the UE that includes an acknowledgement and a TB indication that indicates a TB of data to which the acknowledgement retransmission request relates, and determining whether the acknowledgement is related to the TB of data or a different TB of data based on the TB indication.
  • the apparatus may include means for transmitting to a UE a TB of data, means for transmitting to the UE an acknowledgement retransmission request for the TB of data, means for receiving a signal from the UE that includes an acknowledgement and a TB indication that indicates a TB of data to which the acknowledgement retransmission request relates, and means for determining whether the acknowledgement is related to the TB of data or a different TB of data based on the TB indication.
  • the apparatus may include a processor, memory coupled to the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to transmit to a UE a TB of data, transmit to the UE an acknowledgement
  • retransmission request for the TB of data receive a signal from the UE that includes an acknowledgement and a TB indication that indicates a TB of data to which the acknowledgement retransmission request relates, and determine whether the
  • acknowledgement is related to the TB of data or a different TB of data based on the TB indication.
  • a non-transitory computer readable medium storing code for wireless communication is described.
  • the code may include instructions executable by a processor to transmit to a UE a TB of data, transmit to the UE an acknowledgement retransmission request for the TB of data, receive a signal from the UE that includes an acknowledgement and a TB indication that indicates a TB of data to which the acknowledgement retransmission request relates, and determine whether the
  • acknowledgement is related to the TB of data or a different TB of data based on the TB indication.
  • FIG. 1 illustrates an example of a system for wireless communication that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • FIGs. 2A and 2B illustrate call flow diagrams showing communications related to acknowledgement transmissions scenarios.
  • FIGs. 3 and 4 illustrate call flow diagrams showing communications that support robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • FIGs. 5 and 6 show block diagrams of a device that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • FIG. 7 illustrates a block diagram of a system including a UE that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • FIGs. 8 and 9 show block diagrams of a device that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • FIG. 10 illustrates a block diagram of a system including a base station that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • FIGs. 11-16 illustrate methods for robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • the described aspects of the disclosure relate to improved methods, systems, devices, or apparatuses that facilitate robust acknowledgement retransmissions.
  • the techniques described herein enable transport blocks (TBs) of data to be identified and associated with acknowledgement (positive acknowledgements (ACK), negative acknowledgements (NAK), generally referred to as "A/N" herein)
  • a base station may signal to a user equipment (UE) the TB of data to which an A/N retransmission request pertains.
  • UE user equipment
  • a UE may signal to a base station the TB of data to which the A/N retransmission pertains.
  • Various example techniques may enable base stations and/or UEs to more accurately identify when, and what, TBs of data are unsuccessfully communicated between base stations and UEs.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports robust acknowledgement retransmissions in accordance with various aspects of the present disclosure.
  • the wireless communications system 100 includes base stations 105, UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, or a New Radio (NR) network.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • NR New Radio
  • wireless communications system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low-cost and low-complexity devices.
  • ultra-reliable e.g., mission critical
  • Base stations 105 may wirelessly communicate with UEs 115 via one or more base station antennas.
  • Base stations 105 described herein may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation Node B or giga-nodeB (either of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or some other suitable terminology.
  • Wireless communications system 100 may include base stations 105 of different types (e.g., macro or small cell base stations).
  • the UEs 115 described herein may be able to communicate with various types of base stations 105 and network equipment including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like.
  • Each base station 105 may be associated with a particular geographic coverage area 110 in which communications with various UEs 115 is supported. Each base station 105 may provide communication coverage for a respective geographic coverage area 110 via communication links 125, and communication links 125 between a base station 105 and a UE 115 may utilize one or more carriers. Communication links 125 shown in wireless communications system 100 may include uplink transmissions from a UE 115 to a base station 105, or downlink transmissions, from a base station 105 to a UE 115. Downlink transmissions may also be called forward link transmissions while uplink transmissions may also be called reverse link transmissions.
  • the geographic coverage area 110 for a base station 105 may be divided into sectors making up only a portion of the geographic coverage area 110, and each sector may be associated with a cell.
  • each base station 105 may provide communication coverage for a macro cell, a small cell, a hot spot, or other types of cells, or various combinations thereof.
  • a base station 105 may be movable and therefore provide communication coverage for a moving geographic coverage area 110.
  • different geographic coverage areas 110 associated with different technologies may overlap, and overlapping geographic coverage areas 110 associated with different technologies may be supported by the same base station 105 or by different base stations 105.
  • the wireless communications system 100 may include, for example, a heterogeneous LTE/LTE-A or NR network in which different types of base stations 105 provide coverage for various geographic coverage areas 110.
  • cell refers to a logical communication entity used for
  • a base station 105 may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) operating via the same or a different carrier.
  • a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband Internet-of-Things (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of devices.
  • MTC machine-type communication
  • NB-IoT narrowband Internet-of-Things
  • eMBB enhanced mobile broadband
  • the term "cell” may refer to a portion of a geographic coverage area 110 (e.g., a sector) over which the logical entity operates.
  • UEs 115 may be dispersed throughout the wireless communications system 100, and each UE 115 may be stationary or mobile.
  • a UE 115 may also be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the "device” may also be referred to as a unit, a station, a terminal, or a client.
  • a UE 115 may also be a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may also refer to a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or an MTC device, or the like, which may be implemented in various articles such as appliances, vehicles, meters, or the like.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC massive machine type communications
  • Some UEs 115 may be low cost or low complexity devices, and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication).
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station 105 without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application program that can make use of the information or present the information to humans interacting with the program or application.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception simultaneously). In some examples half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for UEs 115 include entering a power saving "deep sleep" mode when not engaging in active communications, or operating over a limited bandwidth (e.g., according to narrowband communications). In some cases, UEs 115 may be designed to support critical functions (e.g., mission critical functions), and a wireless communications system 100 may be configured to provide ultra-reliable communications for these functions.
  • critical functions e.g., mission critical functions
  • a UE 115 may also be able to communicate directly with other UEs 115 (e.g., using a peer-to-peer (P2P) or device-to-device (D2D) protocol).
  • P2P peer-to-peer
  • D2D device-to-device
  • One or more of a group of UEs 115 utilizing D2D communications may be within the geographic coverage area 110 of a base station 105.
  • Other UEs 115 in such a group may be outside the geographic coverage area 110 of a base station 105, or be otherwise unable to receive transmissions from a base station 105.
  • groups of UEs 115 communicating via D2D communications may utilize a one-to-many (1:M) system in which each UE 115 transmits to every other UE 115 in the group.
  • a base station 105 facilitates the scheduling of resources for D2D communications.
  • D2D communications are carried out between UEs 115 without the involvement of a base station 105.
  • Base stations 105 may communicate with the core network 130 and with one another. For example, base stations 105 may interface with the core network 130 through backhaul links 132 (e.g., via an S I or other interface). Base stations 105 may communicate with one another over backhaul links 134 (e.g., via an X2 or other interface) either directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130).
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one Packet Data Network (PDN) gateway (P-GW).
  • EPC evolved packet core
  • MME mobility management entity
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • P-GW Packet Data Network gateway
  • the MME may manage non-access stratum (e.g., control plane) functions such as mobility,
  • User IP packets may be transferred through the S-GW, which itself may be connected to the P-GW.
  • the P-GW may provide IP address allocation as well as other functions.
  • the P-GW may be connected to the network operators IP services.
  • the operators IP services may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched (PS) Streaming Service.
  • IMS IP Multimedia Subsystem
  • PS Packet-Switched
  • At least some of the network devices may include subcomponents such as an access network entity, which may be an example of an access node controller (ANC).
  • Each access network entity may communicate with UEs 115 through a number of other access network transmission entities, which may be referred to as a radio head, a smart radio head, or a transmission/reception point (TRP).
  • TRP transmission/reception point
  • various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., a base station 105).
  • Wireless communications system 100 may operate using one or more frequency bands, typically in the range of 300 MHz to 300 GHz.
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band, since the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and
  • the waves may penetrate structures sufficiently for a macro cell to provide service to UEs 115 located indoors.
  • Transmission of UHF waves may be associated with smaller antennas and shorter range (e.g., less than 100 km) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • Wireless communications system 100 may also operate in a super high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter band.
  • SHF region includes bands such as the 5 GHz industrial, scientific, and medical (ISM) bands, which may be used opportunistically by devices that can tolerate interference from other users.
  • ISM bands 5 GHz industrial, scientific, and medical bands
  • Wireless communications system 100 may also operate in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band.
  • EHF extremely high frequency
  • wireless communications system 100 may support millimeter wave (mmW) communications between UEs 115 and base stations 105, and EHF antennas of the respective devices may be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate use of antenna arrays within a UE 115 (e.g., for multiple-input multiple-output (MEVIO) operations such as spatial multiplexing, or for directional beamforming).
  • MUVIO multiple-input multiple-output
  • the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. Techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
  • wireless communications system 100 may utilize both licensed and unlicensed radio frequency spectrum bands.
  • wireless communications system 100 may employ LTE License Assisted Access (LTE-LAA) or LTE-Unlicensed (LTE-U) radio access technology or NR technology in an unlicensed band such as the 5 GHz ISM band.
  • LTE-LAA LTE License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz ISM band.
  • wireless devices such as base stations 105 and UEs 115 may employ listen-bef ore-talk (LBT) procedures to ensure a frequency channel is clear before transmitting data.
  • LBT listen-bef ore-talk
  • operations in unlicensed bands may be based on a CA configuration in conjunction with CCs operating in a licensed band.
  • Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, peer- to-peer transmissions, or a combination of these.
  • Duplexing in unlicensed spectrum may be based on frequency division duplexing (FDD), time division duplexing (TDD), or a combination of both.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • the antennas of a base station 105 or UE 115 may be located within one or more antennas or antenna arrays, which may support MIMO operations such as spatial multiplexing, or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a base station 105 may be located in diverse geographic locations.
  • a base station 105 may have an antenna array with a number of rows and columns of antenna ports that the base station 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.
  • MIMO wireless systems use a transmission scheme between a transmitting device (e.g., a base station 105) and a receiving device (e.g., a UE 115), where both transmitting device and the receiving device are equipped with multiple antennas.
  • a transmitting device e.g., a base station 105
  • a receiving device e.g., a UE 115
  • MIMO communications may employ multipath signal propagation to increase the utilization of a radio frequency spectrum band by transmitting or receiving different signals via different spatial paths, which may be referred to as spatial multiplexing.
  • the different signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas.
  • the different signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the different signals may be referred to as a separate spatial stream, and the different antennas or different combinations of antennas at a given device (e.g., the orthogonal resource of the device associated with the spatial dimension) may be referred to as spatial layers.
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105 or a UE 115) to shape or steer an antenna beam (e.g., a transmit beam or receive beam) along a direction between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying certain phase offset, timing advance/delay, or amplitude adjustment to signals carried via each of the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).
  • a base station 105 may multiple use antennas or antenna arrays to conduct beamforming operations for directional communications with a UE 115. For instance, signals may be transmitted multiple times in different directions, which may include a signal being transmitted according to different beamforming weight sets associated with different directions of transmission.
  • a receiving device e.g., a UE 115, which may be an example of a mmW receiving device
  • a receiving device may try multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets applied to signals received at a plurality of antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at a plurality of antenna elements of an antenna array, any of which may be referred to as "listening" according to different receive beams or receive directions.
  • wireless communications system 100 may be a packet-based network that operate according to a layered protocol stack.
  • PDCP Packet Data Convergence Protocol
  • a Radio Link Control (RLC) layer may in some cases perform packet segmentation and reassembly to communicate over logical channels.
  • RLC Radio Link Control
  • a Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer may also use hybrid automatic repeat request (HARQ) to provide retransmission at the MAC layer to improve link efficiency.
  • HARQ hybrid automatic repeat request
  • the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a base station 105 or core network 130 supporting radio bearers for user plane data.
  • RRC Radio Resource Control
  • PHY Physical
  • UEs 115 and base stations 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • HARQ feedback is one technique of increasing the likelihood that data is received correctly over a communication link 125.
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)).
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., signal-to-noise conditions).
  • a wireless device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • the radio frames may be identified by a system frame number (SFN) ranging from 0 to 1023.
  • SFN system frame number
  • Each frame may include ten subframes numbered from 0 to 9, and each subframe may have a duration of 1 millisecond.
  • a subframe may be further divided into two slots each having a duration of 0.5 milliseconds, and each slot may contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). Excluding the cyclic prefix, each symbol period may contain 2048 sampling periods.
  • a subframe may be the smallest scheduling unit of the wireless communications system 100, and may be referred to as a transmission time interval (TTI).
  • TTI transmission time interval
  • a smallest scheduling unit of the wireless communications system 100 may be shorter than a subframe or may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) or in selected component carriers using sTTIs).
  • a slot may further be divided into multiple mini-slots containing one or more symbols and in some instances, a symbol of a mini-slot or a mini-slot may be the smallest unit of scheduling. Each symbol may vary in duration depending on the subcarrier spacing or frequency band of operation, for example.
  • Some wireless communications systems may implement slot aggregation in which multiple slots or mini-slots may be aggregated together for communication between a UE 115 and a base station 105.
  • a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier (e.g., a 15 kHz frequency range).
  • a resource block may contain 12 consecutive subcarriers in the frequency domain (e.g., collectively forming a "carrier") and, for a normal cyclic prefix in each orthogonal frequency- division multiplexing (OFDM) symbol, 7 consecutive OFDM symbol periods in the time domain (1 slot), or 84 total resource elements across the frequency and time domains.
  • the number of bits carried by each resource element may depend on the modulation scheme (the configuration of modulation symbols that may be applied during each symbol period).
  • the more resource elements that a UE 115 receives and the higher the modulation scheme e.g., the higher the number of bits that may be represented by a modulation symbol according to a given modulation scheme
  • the higher the data rate may be for the UE 115.
  • communications resource may refer to a combination of a radio frequency spectrum band resource, a time resource, and a spatial resource (e.g., spatial layers), and the use of multiple spatial layers may further increase the data rate for communications with a UE 115.
  • a spatial resource e.g., spatial layers
  • carrier refers to a set of radio frequency spectrum resources having a defined organizational structure for supporting uplink or downlink
  • communication link 125 may include a portion of a radio frequency spectrum band that may also be referred to as a frequency channel.
  • a carrier may be made up of multiple sub-carriers (e.g., waveform signals of multiple different frequencies).
  • a carrier may be organized to include multiple physical channels, where each physical channel may carry user data, control information, or other signaling.
  • the organizational structure of the carriers may be different for different radio access technologies (e.g., LTE, LTE-A, NR, etc.). For example, communications over a carrier may be organized according to TTIs or slots, each of which may include user data as well as control information or signaling to support decoding the user data.
  • a carrier may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling that coordinates operation for the carrier.
  • acquisition signaling e.g., synchronization signals or system information, etc.
  • control signaling that coordinates operation for the carrier.
  • a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.
  • Physical channels may be multiplexed on a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • control information transmitted in a physical control channel may be distributed between different control regions in a cascaded manner (e.g., between a common control region or common search space and one or more UE- specific control regions or UE-specific search spaces).
  • a carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a number of predetermined bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, or 20 MHz).
  • the system bandwidth may refer to a minimum bandwidth unit for scheduling communications between a base station 105 and a UE 115.
  • a base station 105 or a UE 115 may also support communications over carriers having a smaller bandwidth than the system bandwidth.
  • the system bandwidth may be referred to as "wideband” bandwidth and the smaller bandwidth may be referred to as a “narrowband” bandwidth.
  • wideband communications may be performed according to a 20 MHz carrier bandwidth and narrowband communications may be performed according to a 1.4 MHz carrier bandwidth.
  • Devices of the wireless communications system 100 may have a hardware configuration that supports communications over a particular carrier bandwidth, or may be configurable to support communications over one of a set of carrier bandwidths.
  • base stations 105 or UEs 115 may perform some communications according to a system bandwidth (e.g., wideband communications), and may perform some communications according to a smaller bandwidth (e.g., narrowband communications).
  • the wireless communications system 100 may include base stations 105 and/or UEs that can support simultaneous communications via carriers associated with more than one different bandwidth.
  • Wireless communications system 100 may support communication with a UE 115 on multiple cells or carriers, a feature which may be referred to as carrier aggregation (CA) or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink CCs and one or more uplink CCs according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both FDD and TDD component carriers.
  • wireless communications system 100 may utilize enhanced component carriers (eCCs).
  • eCC may be characterized by one or more features including wider carrier or frequency channel bandwidth, shorter symbol duration, shorter TTI duration, or modified control channel configuration.
  • an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have a suboptimal or non-ideal backhaul link).
  • An eCC may also be configured for use in unlicensed spectrum or shared spectrum (e.g., where more than one operator is allowed to use the spectrum).
  • An eCC characterized by wide carrier bandwidth may include one or more segments that may be utilized by UEs 115 that are not capable of monitoring the whole carrier bandwidth or are otherwise configured to use a limited carrier bandwidth (e.g., to conserve power).
  • an eCC may utilize a different symbol duration than other CCs, which may include use of a reduced symbol duration as compared with symbol durations of the other CCs.
  • a shorter symbol duration may be associated with increased spacing between adjacent subcarriers.
  • a device such as a UE 115 or base station 105, utilizing eCCs may transmit wideband signals (e.g., according to frequency channel or carrier bandwidths of 20, 40, 60, 80 MHz, etc.) at reduced symbol durations (e.g., 16.67 microseconds).
  • a TTI in eCC may consist of one or multiple symbol periods. In some cases, the TTI duration (that is, the number of symbol periods in a TTI) may be variable.
  • Wireless communications systems such as an NR system may use a combination of licensed, shared, and unlicensed spectrum bands, among others.
  • the flexibility of eCC symbol duration and subcarrier spacing may allow for the use of eCC across multiple spectrums.
  • NR shared spectrum may increase spectrum utilization and spectral efficiency, specifically through dynamic vertical (e.g., across frequency) and horizontal (e.g., across time) sharing of resources.
  • Wireless communication system 100 may implement various aspects described in more detail below to improve the robustness of acknowledgement retransmissions.
  • wireless communication system 100 enables TBs of data to be identified and associated with A/N retransmissions.
  • base station 105 may signal to UE 115 the TB of data to which an A/N retransmission request pertains.
  • UE 115 may signal to base station 105 the TB of data to which the A/N retransmission pertains.
  • FIG. 2A illustrates a call flow diagram 200-a between base station 105 and UE 115 according to one example scenario.
  • base station 105 transmits a first downlink (DL) grant (DL grant 1) and an associated TB of data (e.g., a TB of data contained in a physical DL shared channel (PDSCH)) to UE 115.
  • DL grant 1 a first downlink
  • PDSCH physical DL shared channel
  • UE 115 receives DL grant 1 and attempts to decode the TB of data associated with DL grant 1.
  • UE 115 transmits an A/N (e.g., ACK if the data was successfully decoded, NAK if the data was not successful decoded) to base station 105.
  • base station 105 receives the A/N and determines whether the TB of data associated with DL grant 1 needs to be retransmitted.
  • A/N e.g., ACK if the data was successfully decoded, NAK if the data was not
  • base station 105 transmits a second DL grant (DL grant 2) and an associated TB of data (e.g., data different from the TB of data associated with DL grant 1) to UE 115.
  • DL grant 2 DL grant 2
  • UE 115 receives DL grant 2 and attempts to decode the TB of data associated with DL grant 2.
  • UE 115 transmits a second A/N to base station 105. Unlike the first A/N associated with DL grant 1, base station 105 does not receive the second A/N at 240-a.
  • the signal quality (e.g., signal-to- interference-plus-noise ratio (SINR)) may be such that base station 105 is unable to receive the second A/N.
  • base station 105 sends an A/N retransmission request or trigger to UE 115 at 245-a.
  • UE 115 receives the A/N retransmission trigger at 250-a and retransmits to base station 105 the A/N for the TB of data associated DL grant 2 at 255-a.
  • base station 105 receives the retransmitted second A/N.
  • FIG. 2B illustrates a call flow diagram 200-b between base station 105 and UE 115 according to another example scenario in which UE 115 does not receive a DL grant transmitted by base station 105.
  • base station 105 transmits a first DL grant (DL grant 1) and an associated TB of data to UE 115.
  • DL grant 1 DL grant 1
  • UE 115 receives DL grant 1 and attempts to decode the TB of data associated with DL grant 1.
  • UE 115 transmits an A/N (e.g., ACK if the data was successfully decoded, NAK if the data was not successful decoded) to base station 105.
  • base station 105 receives the A/N and determines whether the TB of data associated with DL grant 1 needs to be retransmitted.
  • A/N e.g., ACK if the data was successfully decoded, NAK if the data was not successful decoded
  • base station 105 transmits a second DL grant (DL grant 2) and an associated TB of data (e.g., data different from the TB of data associated with DL grant 1) to UE 115.
  • DL grant 2 DL grant 2
  • UE 115 does not transmit a second A/N for the TB of data associated with the second DL grant.
  • Base station 105 expects to receive a second A/N at a specified resource (e.g., time and frequency), but does not receive the second A/N at 240-b because UE 115 did not receive DL grant 2.
  • Base station 105 is unaware that UE 115 did not receive DL grant 2 and its associated TB of data and that this was the reason the second A/N is missing.
  • Base station 105 sends an A/N retransmission request or trigger for DL grant 2 to UE 115 at 245-b.
  • UE 115 receives the A/N retransmission trigger at 250-b but is unware that the A/N retransmission trigger is for DL grant 2 and its associated TB of data.
  • the UE 115 interprets that the A/N retransmission trigger is for the last DL grant and associated TB of data it received (e.g., DL grant 1 and associated data) and retransmits to base station 105 the A/N for the TB of data associated DL grant 1 at 255-b.
  • base station 105 receives the retransmitted A/N associated with DL grant 1 and interprets the retransmitted A/N as associated with DL grant 2, which is incorrect. To reduce or prevent errors in interpreting to which TB an A/N
  • message exchanges between base station 105 and UE 115 may be made more robust or enhanced as described in more detail below with reference to FIGs. 3-15.
  • FIG. 3 illustrates a call flow diagram 300 between base station 105 and UE 115 according to an example scenario in which an A/N retransmission request from base station 105 to UE 115 is enhanced or made more robust to reduce errors in mapping TBs to A/N retransmissions and/or retransmission requests.
  • base station 105 transmits a first DL grant (DL grant 1) and an associated TB of data to UE 115.
  • UE 115 receives DL grant 1 and attempts to decode the TB of data associated with DL grant 1.
  • UE 115 transmits an A/N (e.g., ACK if the data was successfully decoded, NAK if the data was not successful decoded) to base station 105.
  • A/N e.g., ACK if the data was successfully decoded, NAK if the data was not successful decoded
  • base station 105 receives the A/N and determines whether the TB of data associated with DL grant 1 needs to be retransmitted.
  • base station 105 transmits a second DL grant (DL grant 2) and an associated TB of data (e.g., data different from the TB of data associated with DL grant 1) to UE 115.
  • DL grant 2 DL grant 2
  • UE 115 does not receive DL grant 2 and, therefore, UE 115 does not transmit a second A/N for the TB of data associated with the second DL grant.
  • Base station 105 expects to receive a second A/N at a specified resource (e.g., time and frequency), but does not receive the second A/N at 340 because UE 115 did not receive DL grant 2.
  • base station 105 is unaware that UE 115 did not receive DL grant 2 and its associated TB of data and that this was the reason the second A/N is missing.
  • base station 105 sends an A/N retransmission request or trigger for DL grant 2 to UE 115 at 345.
  • the A/N retransmission at 345 includes a TB indication that indicates that the A/N retransmission request relates to DL grant 2.
  • the TB indication may include any information that enables UE 115 to identify the TB of data associated with the A/N retransmission request.
  • the TB indication may include a slot number indication for the TB of data, which may allow UE 115 to identify the appropriate TB of data.
  • the slot number indication may include an absolute slot number, a modulo absolute slot number (to reduce the size of the field of the TB indication), a relative slot number from a current slot, or the like.
  • the TB indication may include a new data indicator (NDI) that switches values for each new TB of data.
  • the NDI may correspond to a single bit of information (which may provide for a relatively small payload) or multiple bits (e.g., in situations where there are multiple code words for each HARQ process).
  • the NDI may be useful in deployments in which the A/N retransmission trigger is for a single TB of data as opposed to one TB of data in a particular retransmission with multiple TBs of data.
  • the A/N retransmission request transmitted to UE 115 may be one of multiple A/N retransmission requests associated with multiple HARQ processes transmitted in a signal to UE 115, and each A/N retransmission request may include an associated TB indication.
  • UE 115 receives the A/N retransmission trigger, including the TB indication, at 350. Because the A/N retransmission trigger includes the TB indication, UE 115 is able to identify that the A/N retransmission trigger is for DL grant 2 and its associated TB of data. For example, when an NDI is used, UE 115 may compare the NDI of the TB indication with the NDI of the latest TB of data it received (e.g., the TB of data associated with DL grant 1). If the NDIs are the same, UE 115 may identify that the A/N retransmission trigger corresponds to the last TB of data it received and may retransmit the A/N for that TB of data.
  • UE 115 may identify that it missed DL grant 2 and its associated TB of data. Accordingly, at 355, UE 115 may transmit a NAK to base station 105 in response to receiving and processing the A/N retransmission trigger and TB indication. In an alternative example, UE 115 and base station 105 may be configured to transmit, receive, and process tri- state A/N in which the third A/N state may provide an explicit indication that a DL grant was missed. At 360, base station 105 receives the NAK (or tri- state A/N) for DL grant 2 and may then retransmit DL grant 2 and its TB of data in accordance with HARQ techniques. The technique depicted in FIG. 3 may result in a larger downlink control information (DCI) payload given that the TB indication is included with the A/N retransmission trigger and an A/N
  • DCI downlink control information
  • the larger DCI payload resulting from including the TB indication may enable less blind decoding for UE 115, which may conventionally be enabled by zero padding the DCI.
  • FIG. 4 illustrates a call flow diagram 400 between base station 105 and UE 115 according to an example scenario in which an A/N retransmission from UE 115 to base station 105 is enhanced or made more robust to reduce errors in mapping TBs to A/N retransmissions and/or retransmission requests.
  • base station 105 transmits a first DL grant (DL grant 1) and an associated TB of data to UE 115.
  • UE 115 receives DL grant 1 and attempts to decode the TB of data associated with DL grant 1.
  • UE 115 transmits an A/N (e.g., ACK if the data was successfully decoded, NAK if the data was not successful decoded) to base station 105.
  • A/N e.g., ACK if the data was successfully decoded, NAK if the data was not successful decoded
  • base station 105 receives the A/N and determines whether the TB of data associated with DL grant 1 needs to be retransmitted.
  • base station 105 transmits a second DL grant (DL grant 2) and an associated TB of data (e.g., data different from the TB of data associated with DL grant 1) to UE 115.
  • DL grant 2 DL grant 2
  • UE 115 does not receive DL grant 2 and, therefore, UE 115 does not transmit a second A/N for the TB of data associated with the second DL grant.
  • Base station 105 expects to receive a second A/N at a specified resource (e.g., time and frequency), but does not receive the second A/N at 440 because UE 115 did not receive DL grant 2.
  • base station 105 is unaware that UE 115 did not receive DL grant 2 and its associated TB of data and that this was the reason the second A/N is missing.
  • Base station 105 sends an A/N retransmission request or trigger for DL grant 2 to UE 115 at 445.
  • UE 115 receives the A/N retransmission trigger at 450.
  • UE 115 transmits an A/N retransmission to base station 105.
  • the A/N retransmission includes a TB indication.
  • the TB indication may include any information that enables base station 105 to identify the TB of data associated with the A/N retransmission. For example, this information may include a slot number and/or an NDI.
  • base station 105 receives the A/N retransmission including the TB indication, which, in this case, indicates the TB associated with DL grant 1. Because the A/N retransmission includes the TB indication, base station 105 is able to identify that the A/N retransmission is for DL grant 1 and its associated TB of data. Base station 105 may compare the TB indication with TB information of the TB corresponding to the A/N retransmission trigger (e.g., TB associated with DL grant 2). The comparison by base station 105 may be similar to the comparison by UE 115 described with reference to FIG. 3 (e.g., comparison of NDIs and/or slot numbers).
  • base station 105 may identify that UE 115 did not receive DL grant 2 and its associated TB of data and may retransmit DL grant 2 and its TB of data to UE 115.
  • the technique depicted in FIG. 4 may result an A/N retransmission with a larger payload, given that the TB indication is included with the A/N retransmission, and a DCI payload that has little, to no change, in its payload compared to conventional techniques.
  • the techniques described with reference to FIGs. 3 and 4 may be utilized for a single HARQ process, a set of HARQ processes, or all HARQ processes.
  • base station 105 and/or UE 115 may be enabled to signal a HARQ process identification (ID) in an A/N retransmission trigger.
  • ID HARQ process identification
  • base station 105 and/or UE 115 may be enabled to signal which HARQ processes are subject to an A/N
  • base station 105 and/or UE 115 may refrain from indicating which HARQ process are involved with an A/N retransmission trigger
  • FIG. 5 shows a block diagram 500 of a wireless device 505 that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • Wireless device 505 may be an example of aspects of a user equipment (UE) 115 as described herein.
  • Wireless device 505 may include receiver 510, UE
  • Wireless device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).
  • Receiver 510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to robust acknowledgement retransmissions (e.g., TB indications), etc.). Information may be passed on to other components of the device.
  • the receiver 510 may utilize a single antenna or a set of antennas.
  • the receiver 510 may be an example of aspects of the transceiver 735 described with reference to FIG. 7.
  • Receiver 510 may receive DL grants and associated TBs of data, A/N retransmission requests, and TB indications as described with reference to FIGs. 1-4.
  • UE communications manager 515 and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof.
  • the functions of the UE communications manager 515 and/or at least some of its various subcomponents may be executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • the UE communications manager 515 and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices.
  • UE communications manager 515 and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure. In other examples, UE communications manager 515 and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure. UE communications manager 515 may be an example of aspects of the UE communications manager 715 described with reference to FIG. 7.
  • UE communications manager 515 may attempt to decode TBs of data, process A/N retransmission requests and TB indications, may compare TB indications with other information to identify an appropriate A/N retransmission response, and may generate TB indications, as described with reference to FIGs. 1-4.
  • Transmitter 520 may transmit signals generated by other components of the device.
  • the transmitter 520 may be collocated with a receiver 510 in a transceiver module.
  • the transmitter 520 may be an example of aspects of the transceiver 735 described with reference to FIG. 7.
  • the transmitter 520 may utilize a single antenna or a set of antennas.
  • Transmitter 520 may transmit information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to robust acknowledgement retransmissions (e.g., TB indications), etc.). In some examples, transmitter 520 may transmit A/Ns, A/N retransmissions, and TB indications, as described with reference to FIGs. 1-4.
  • information channels e.g., control channels, data channels, and information related to robust acknowledgement retransmissions (e.g., TB indications), etc.
  • transmitter 520 may transmit A/Ns, A/N retransmissions, and TB indications, as described with reference to FIGs. 1-4.
  • FIG. 6 shows a block diagram 600 of a UE communications manager 615 that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • the UE communications manager 615 may be an example of aspects of a UE communications manager 515, or a UE communications manager 715 described with reference to FIGs. 5 and 7.
  • the UE communications manager 615 may include a TB indication manager 620 and an A/N manager 625. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).
  • TB indication manager 620 may process TB indications received with A/N retransmission requests from base station 105 and compare the TB indications to TB information of TBs that the UE has received to determine whether wireless device 505 has missed a DL grant and associated data transmitted from base station 105, as described above with reference to FIG. 3.
  • TB indication manager 620 may also generate TB indications that are to be transmitted to base station 105, together with A/N retransmissions, to inform base station 105 as to the TB of data the A/N retransmission pertains, as described above with reference to FIG. 4.
  • A/N manager 625 may manage the generation of A/N messages to be transmitted to base station 105 in response to receiving DL grants and processing associated TBs of data, as described with reference to FIGs. 1-5. A/N manager 625 may also manage the generation of A/N retransmission messages in response to receiving A/N retransmission requests, as described with reference to FIGs. 1-5.
  • FIG. 7 shows a diagram of a system 700 including a device 705 that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • Device 705 may be an example of or include the components of wireless device 705, or a UE 115 as described above, e.g., with reference to FIGs. 1 through 6.
  • Device 705 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including UE communications manager 715, processor 720, memory 725, software 730, transceiver 735, antenna 740, and I/O controller 745. These components may be coupled to each other (e.g., in electronic communication) via one or more buses (e.g., bus 710).
  • Device 705 may communicate wirelessly with one or more base stations 105.
  • Processor 720 may include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof).
  • processor 720 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into processor 720.
  • Processor 720 may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting robust acknowledgement retransmissions).
  • Memory 725 may include random access memory (RAM) and read only memory (ROM).
  • the memory 725 may store computer-readable, computer-executable software 730 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 725 may contain, among other things, a basic input/output system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic input/output system
  • Software 730 may include code to implement aspects of the present disclosure, including code to support robust acknowledgement retransmissions.
  • Software 730 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software 730 may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • Transceiver 735 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 735 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 735 may also include a modem to modulate the packets and provide the modulated packets to the antennas for
  • the wireless device may include a single antenna 740.
  • the device may have more than one antenna 740, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • I/O controller 745 may manage input and output signals for device 705. I/O controller 745 may also manage peripherals not integrated into device 705. In some cases, I/O controller 745 may represent a physical connection or port to an external peripheral. In some cases, I O controller 745 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In other cases, I/O controller 745 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, I/O controller 745 may be implemented as part of a processor. In some cases, a user may interact with device 705 via I/O controller 745 or via hardware components controlled by I/O controller 745.
  • I/O controller 745 may be implemented as part of a processor. In some cases, a user may interact with device 705 via I/O controller 745 or via hardware components controlled by I/O controller 745
  • FIG. 8 shows a block diagram 600 of a wireless device 805 that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • Wireless device 805 may be an example of aspects of a base station 105 as described herein.
  • Wireless device 805 may include receiver 810, base station communications manager 815, and transmitter 820.
  • Wireless device 805 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).
  • Receiver 810 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to robust acknowledgement retransmissions (e.g., A/N messages and retransmissions, TB indications), etc.). Information may be passed on to other components of the device.
  • the receiver 810 may utilize a single antenna or a set of antennas.
  • the receiver 810 may be an example of aspects of the transceiver 1035 described with reference to FIG. 10.
  • receiver 810 may receive A/N transmissions, A/N retransmissions and TB indications, as described with reference to FIGs. 1 through 7.
  • Base station communications manager 815 and/or at least some of its various subcomponents may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the base station communications manager 815 and/or at least some of its various sub-components may be executed by a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • the base station communications manager 815 and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices.
  • base station communications manager 815 and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • Base station communications manager 815 may be an example of aspects of the base station communications manager 1015 described with reference to FIG. 10.
  • Base station communications manager 815 may process data received from UE 115 (or device 505), process A/N transmissions, A/N retransmissions, and TB indications, may compare TB indications with other information to identify whether an A/N retransmission corresponds to a correct TB of to which an A/N retransmission request was directed, and may generate TB indications, as described with reference to FIGs. 1-7.
  • Transmitter 820 may transmit signals generated by other components of the device.
  • the transmitter 820 may be collocated with a receiver 810 in a transceiver module.
  • the transmitter 820 may be an example of aspects of the transceiver 1035 described with reference to FIG. 10.
  • the transmitter 820 may utilize a single antenna or a set of antennas.
  • Transmitter 820 may transmit different types of information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to robust acknowledgement retransmissions (e.g., A/N retransmission requests, TB indications), etc.). Information may be passed on to other components of the device.
  • the transmitted 820 may utilize a single antenna or a set of antennas.
  • FIG. 9 shows a block diagram 900 of a base station communications manager 915 that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • the base station communications manager 915 may be an example of aspects of base station communications manager 815 described with reference to FIG. 8 and/or a base station communications manager 1015 described with reference to FIG 10.
  • the base station communications manager 915 may include TB indication manager 920 and A/N manager 925. Each of these modules may
  • TB indication manager 920 may generate TB indications that are to be transmitted with A/N retransmission requests to UE 115 (or wireless device 505) to inform UE 115 as to the TB of data the A/N retransmission request pertains, as described above with reference to FIG. 3.
  • TB indication manager 920 may also process TB indications received with A/N retransmission from UE 115 (or wireless device 505) and compare the TB indications to TB information of a TB of data that corresponds to an A/N retransmission request to determine whether that UE 115 has missed a DL grant and associated data transmitted to UE 115, as described above with reference to FIG. 4.
  • A/N manager 925 may process A/N messages received from UEs 115 (or wireless devices 505) and may generate A/N retransmission requests based on received A/N messages, as described with reference to FIGs. 1-8.
  • FIG. 10 shows a diagram of a system 1000 including a device 1005 that supports robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • Device 1005 may be an example of or include the components of base station 105 as described above, e.g., with reference to FIGs. 1-4.
  • Device 1005 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including base station communications manager 1015, processor 1020, memory 1025, software 1030, transceiver 1035, antenna 1040, network communications manager 1045, and inter- station communications manager 1050. These components may be in electronic communication via one or more buses (e.g., bus 1010).
  • Device 1005 may communicate wirelessly with one or more UEs 115.
  • Processor 1020 may include an intelligent hardware device, (e.g., a general- purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a
  • processor 1020 may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor 1020. Processor 1020 may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting robust acknowledgement retransmissions).
  • Memory 1025 may include RAM and ROM.
  • the memory 1025 may store computer-readable, computer-executable software 1030 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 1025 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • Software 1030 may include code to implement aspects of the present disclosure, including code to support robust acknowledgement retransmissions.
  • Software 1030 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software 1030 may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • Transceiver 1035 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1035 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1035 may also include a modem to modulate the packets and provide the modulated packets to the antennas for
  • the wireless device may include a single antenna 1040.
  • the device may have more than one antenna 1040, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • Network communications manager 1045 may manage communications with the core network (e.g., via one or more wired backhaul links). For example, the network communications manager 1045 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • Inter-station communications manager 1050 may manage communications with other base station(s) 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. For example, the inter- station communications manager 1050 may coordinate scheduling for transmissions to UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-station communications manager 1050 may provide an X2 interface within an Long Term Evolution
  • LTE Long Term Evolution
  • LTE-A wireless communication network technology to provide communication between base stations 105.
  • FIG. 11 shows a flowchart illustrating a method 1100 for robust
  • method 1100 may be implemented by a UE 115 or its components as described herein. For example, one or more of the operations of method 1100 may be performed by a UE communications manager as described with reference to FIGs. 5-7.
  • UE 115 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, UE 115 may perform aspects of the functions described below using special-purpose hardware.
  • UE 115 may receive a TB of data from a network (e.g., from base station 105).
  • the operations of block 1105 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1105 may be performed by a receiver as described with reference to FIGs. 5-7.
  • UE 115 may decode the TB of data.
  • the operations of block 1110 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1110 may be performed by a UE communications manager and/or a processor as described with reference to FIGs. 5-7.
  • UE 115 may transmit to the network a first A/N based on the results of the decoding.
  • the operations of block 1115 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1115 may be performed by a transmitter as described with reference to FIGs. 5-7.
  • UE 115 may receive a signal from the network that includes an A/N retransmission request and a TB indication that indicates a TB of data to which the A/N retransmission request relates.
  • the operations of block 1120 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1120 may be performed by a receiver as described with reference to FIGs. 5-7.
  • UE 115 may determine a second A/N based on the A/N retransmission request and the TB indication.
  • the operations of block 1125 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1125 may be performed by UE communications manager, including a TB indication manager and/or an A/N manager, as described with reference to FIGs. 5-7. Example operations that may be performed at block 1125 are also further described below with reference to FIG. 12. [0119]
  • UE 115 may transmit the second A/N to the network. The operations of block 1130 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1130 may be performed by a transmitter as described with reference to FIGs. 5-7.
  • FIG. 12 shows a flowchart illustrating example details of steps that may be performed in connection with block 1125 of FIG. 11.
  • UE 115 may compare the transport block indication with the last transport block that UE 115 received. Examples of types of TB indications (e.g., NDIs, slot numbers) are further described above with reference to FIG. 3.
  • the UE 115 determines whether the TB indication received from base station 105 indicates (corresponds to) the last TB received by UE 115 based on the comparison at block 1205. If the TB indication corresponds to the last TB received (i.e., a "YES" decision), UE 115 retransmits the first acknowledgement as the second acknowledgement at block 1215.
  • UE 115 transmits a NAK (or a tri-state A/N signal explicitly indicating that a DL grant was missed) to base station 105 at block 1220.
  • NAK or a tri-state A/N signal explicitly indicating that a DL grant was missed
  • FIG. 13 shows a flowchart illustrating a method 1300 for robust
  • method 1300 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1300 may be performed by a base station communications manager as described with reference to FIGs. 8-10.
  • a base station 105 may execute a set of codes to control the functional elements of the device to perform the functions described below.
  • the base station 105 may perform aspects of the functions described below using special-purpose hardware.
  • base station 105 may transmit a DL grant and TB of data associated with the DL grant to UE 115.
  • the operations of block 1305 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1305 may be performed by a transmitter as described with reference to FIGs. 8-10.
  • base station 105 may transmit a signal to UE 115 that includes an acknowledgement retransmission request and a TB indication related to the acknowledgement retransmission request.
  • the TB indication may identify the TB of data transmitted to UE 115.
  • Base station 105 may transmit the signal in response to not receiving an A/N message from UE 115 at an expected resource.
  • the operations of block 1310 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1310 may be performed by a transmitter and/or a base station communications manager as described with reference to FIGs. 8- 10.
  • base station 105 receives an A/N from UE 115 for the TB of data.
  • the operations of block 1315 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1315 may be performed by a receiver as described with reference to FIGs. 8-10.
  • FIG. 14 shows a flowchart illustrating a method 1400 for robust
  • method 1400 may be implemented by a UE 115 or its components as described herein. For example, one or more of the operations of method 1400 may be performed by a UE communications manager as described with reference to FIGs. 5-7.
  • UE 115 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, UE 115 may perform aspects of the functions described below using special-purpose hardware.
  • UE 115 may receive a TB of data from a network (e.g., from base station 105).
  • the operations of block 1405 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1405 may be performed by a receiver as described with reference to FIGs. 5-7.
  • UE 115 may decode the TB of data.
  • the operations of block 1410 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1410 may be performed by a UE communications manager as described with reference to FIGs. 5-7.
  • UE 115 may transmit to the network a first A/N based on the results of the decoding.
  • the operations of block 1415 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1415 may be performed by a transmitter as described with reference to FIGs. 5-7.
  • UE 115 may receive a signal from the network that includes an A/N retransmission request.
  • the operations of block 1420 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1420 may be performed by a receiver as described with reference to FIGs. 5-7.
  • UE 115 may transmit to base station 105 a signal including the first A/N and a TB indication that indicates that the first A/N is associated with the TB of data that UE 115 received at block 1405.
  • the operations of block 1425 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1425 may be performed by UE communications manager, including a TB indication manager and/or an A/N manager, as described with reference to FIGs. 5-7.
  • FIG. 15 shows a flowchart illustrating a method 1500 for robust acknowledgement retransmissions in accordance with aspects of the present disclosure.
  • the operations of method 1500 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1500 may be performed by a base station communications manager as described with reference to FIGs. 8-10.
  • a base station 105 may execute a set of codes to control the functional elements of the device to perform the functions described below.
  • the base station 105 may perform aspects of the functions described below using special-purpose hardware.
  • base station 105 may transmit a DL grant and TB of data associated with the DL grant to UE 115.
  • the operations of block 1505 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1505 may be performed by a transmitter as described with reference to FIGs. 8-10.
  • base station 105 may transmit to UE 115 a signal that includes an acknowledgement retransmission request. In this example, the signal does not include a TB indication.
  • the operations of block 1510 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1510 may be performed by a transmitter and/or a base station communications manager as described with reference to FIGs. 8-10.
  • base station 105 receives from UE 115 a signal that includes an A/N and a TB indication.
  • the TB indication may identify the TB of data to which the A/N of the signal relates.
  • the operations of block 1515 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1515 may be performed by a receiver as described with reference to FIGs. 8-10.
  • base station 105 may determine whether the A/N is related to the TB of data sent at block 1505 based on the TB indication received at block 1515.
  • the operations of block 1520 may be performed according to the methods described herein. In certain examples, aspects of the operations of block 1520 may be performed by base station communications manager, including a TB indication manager and/or an A/N manager, as described with reference to FIGs. 8-10. Example operations that may be performed at block 1520 are also further described below with reference to FIG. 16.
  • FIG. 16 shows a flowchart illustrating example details of steps that may be performed in connection with block 1520 of FIG. 15.
  • base station 105 may compare the transport block indication received from UE 115 with transport block information associated with TB sent at block 1505. Examples of types of TB
  • base station 105 determines whether the TB indication received from UE 115 indicates (corresponds to) the last TB transmitted by base station 105 based on the comparison at block 1605. If the TB indication corresponds to the last TB transmitted (i.e., a "YES" decision), base station 105 follows a normal HARQ procedure and responds appropriately to the ACK or NAK received at block 1615.
  • base station 105 interprets the A/N received from UE 115 as a NAK regardless of the true state of the A/N. For example, in response to block 1620, base station 105 may retransmit the DL grant and TB of data to UE 115.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • a CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc.
  • CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
  • IS-2000 Releases may be commonly referred to as CDMA2000 IX, IX, etc.
  • IS-856 TIA-856) is commonly referred to as CDMA2000 lxEV-DO, High Rate Packet Data (HRPD), etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • a TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM).
  • GSM Global System for Mobile Communications
  • An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc.
  • UMB Ultra Mobile Broadband
  • E-UTRA Evolved UTRA
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS).
  • LTE and LTE-A are releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, NR, and GSM are described in documents from the organization named "3rd Generation Partnership Project" (3 GPP).
  • CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • the techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies. While aspects of an LTE or an NR system may be described for purposes of example, and LTE or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE or NR applications.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 115 with service subscriptions with the network provider.
  • a small cell may be associated with a lower- powered base station 105, as compared with a macro cell, and a small cell may operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells.
  • Small cells may include pico cells, femto cells, and micro cells according to various examples.
  • a pico cell for example, may cover a small geographic area and may allow unrestricted access by UEs 115 with service subscriptions with the network provider.
  • a femto cell may also cover a small geographic area (e.g., a home) and may provide restricted access by UEs 115 having an association with the femto cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 for users in the home, and the like).
  • An eNB for a macro cell may be referred to as a macro eNB.
  • An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB.
  • An eNB may support one or multiple (e.g., two, three, four, and the like) cells, and may also support communications using one or multiple component carriers.
  • the wireless communications system 100 or systems described herein may support synchronous or asynchronous operation.
  • the base stations 105 may have similar frame timing, and transmissions from different base stations 105 may be approximately aligned in time.
  • the base stations 105 may have different frame timing, and transmissions from different base stations 105 may not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • electromagnetic waves magnetic fields or particles, optical fields or particles, or any combination thereof.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field- programmable gate array
  • PLD programmable logic device
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.
  • non-transitory computer-readable media may comprise random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general- purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs de communication sans fil. Un équipement d'utilisateur (UE) peut recevoir un bloc de transport (TB) de données en provenance d'un réseau, décoder le TB de données, envoyer au réseau un premier accusé de réception d'après un résultat du décodage, recevoir en provenance du réseau un signal qui comprend une demande de réémission d'accusé de réception et une indication de TB qui indique un TB de données auquel se rapporte la demande de réémission d'accusé de réception, déterminer un second accusé de réception d'après la demande de réémission d'accusé de réception et l'indication de TB, et envoyer le second accusé de réception au réseau.
EP18807810.9A 2017-11-06 2018-11-06 Réémission robuste d'accusés de réception Active EP3707844B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201762581906P 2017-11-06 2017-11-06
US16/181,141 US10727986B2 (en) 2017-11-06 2018-11-05 Robust acknowledgement retransmission
PCT/US2018/059462 WO2019090337A1 (fr) 2017-11-06 2018-11-06 Réémission robuste d'accusés de réception

Publications (2)

Publication Number Publication Date
EP3707844A1 true EP3707844A1 (fr) 2020-09-16
EP3707844B1 EP3707844B1 (fr) 2022-12-21

Family

ID=66327738

Family Applications (1)

Application Number Title Priority Date Filing Date
EP18807810.9A Active EP3707844B1 (fr) 2017-11-06 2018-11-06 Réémission robuste d'accusés de réception

Country Status (4)

Country Link
US (2) US10727986B2 (fr)
EP (1) EP3707844B1 (fr)
CN (1) CN111279641B (fr)
WO (1) WO2019090337A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10727986B2 (en) * 2017-11-06 2020-07-28 Qualcomm Incorporated Robust acknowledgement retransmission
US11362770B2 (en) * 2019-01-15 2022-06-14 Qualcomm Incorporated Trigger retransmission of a feedback in unlicensed spectrum
US12034544B2 (en) * 2020-04-17 2024-07-09 Qualcomm Incorporated Methods and apparatus to facilitate a multiple bit new data indicator
US11848780B2 (en) 2020-04-17 2023-12-19 Qualcomm Incorporated Methods and apparatus to facilitate a HARQ flush indicator for transmissions
US11923980B2 (en) 2020-04-17 2024-03-05 Qualcomm Incorporated HARQ flush indicator for uplink transmissions and sidelink transmissions
US11678343B2 (en) 2021-05-07 2023-06-13 Qualcomm Incorporated Transport block size determination for retransmission

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998015140A1 (fr) 1996-09-30 1998-04-09 Motorola Inc. Systeme de radiocommunication bidirectionnel
JP4343220B2 (ja) 2004-02-27 2009-10-14 シャープ株式会社 通信装置、通信方法、通信プログラム、および通信プログラムを記録した記録媒体
TW200713895A (en) * 2005-09-21 2007-04-01 Asustek Comp Inc Method and apparatus for improving transmission delay of status report in a wireless communications system
WO2008135238A1 (fr) * 2007-05-02 2008-11-13 Nokia Siemens Networks Oy Gestion d'acquittement robuste
CA2757465C (fr) * 2009-04-01 2015-11-10 Qualcomm Atheros, Inc. Gestion de transmissions parmi des noeuds communiquant sur un support de communication partage
EP2988447B1 (fr) * 2010-03-29 2017-05-03 LG Electronics, Inc. Procédé efficace et dispositif de transmission d'informations de commande pour supporter une transmission multi-antenne en liaison montante
WO2012110957A1 (fr) * 2011-02-14 2012-08-23 Telefonaktiebolaget L M Ericsson (Publ) Gestion de requête harq lors de la reconfiguration d'un nœud relais
JP5724745B2 (ja) * 2011-08-12 2015-05-27 富士通株式会社 基地局
US9197390B2 (en) * 2011-08-12 2015-11-24 Panasonic Intellectual Property Corporation Of America Communication device, and retransmission control method
US8792462B2 (en) * 2012-06-11 2014-07-29 Telefonaktiebolaget L M Ericsson (Publ) Radio base station and method for switching TTI bundling
US20150327295A1 (en) * 2014-05-12 2015-11-12 Qualcomm Incorporated Inter radio access technology measurement gap
US10903943B2 (en) * 2014-06-13 2021-01-26 Apple Inc. Enhanced LTE UL HARQ feedback indication for power saving and range improvement
CN107078857B (zh) * 2014-10-13 2020-03-27 瑞典爱立信有限公司 基于从资源指配消息复制的镜像信息的harq反馈报告
US20160226628A1 (en) * 2015-01-30 2016-08-04 Huawei Technologies Co., Ltd. System and method for data retransmission
CN114172622A (zh) * 2016-02-03 2022-03-11 交互数字专利控股公司 用于调度子帧和harq反馈的方法、系统和装置
CN109690994B (zh) * 2017-01-05 2020-05-22 北京欧珀通信有限公司 传输反馈信息的方法、网络设备和终端设备
US11121821B2 (en) * 2017-02-06 2021-09-14 Telefonaktiebolaget Lm Ericsson (Publ) Enhancements for retransmission due to conflicting transmissions for different services
US11601229B2 (en) * 2017-03-03 2023-03-07 Telefonaktiebolaget Lm Ericsson (Publ) Re-transmission timing for acknowledgment signaling
RU2731035C1 (ru) * 2017-05-03 2020-08-28 Идак Холдингз, Инк. СПОСОБ И УСТРОЙСТВО ДЛЯ УЛУЧШЕНИЯ ЭФФЕКТИВНОСТИ ОБРАТНОЙ СВЯЗИ ГИБРИДНОГО АВТОМАТИЧЕСКОГО ЗАПРОСА ПОВТОРНОЙ ПЕРЕДАЧИ (HARQ) УЛУЧШЕННОЙ МОБИЛЬНОЙ ШИРОКОПОЛОСНОЙ СВЯЗИ (eMBB) В УСЛОВИЯХ ТРАФИКА С НИЗКОЙ ЗАДЕРЖКОЙ
US20180367263A1 (en) * 2017-06-15 2018-12-20 Sharp Laboratories Of America, Inc. Downlink Control Signaling to Enable Preemption and CBG-Based (Re)Transmission
JP2019004362A (ja) * 2017-06-16 2019-01-10 シャープ株式会社 端末装置、基地局装置、および、通信方法
US10707995B2 (en) * 2017-06-29 2020-07-07 Qualcomm Incorporated Method and apparatus for downlink retransmission under unreliable code block group (CBG) level feedback
WO2019006742A1 (fr) * 2017-07-07 2019-01-10 Oppo广东移动通信有限公司 Procédé d'indication de données et produit associé
US10727986B2 (en) * 2017-11-06 2020-07-28 Qualcomm Incorporated Robust acknowledgement retransmission

Also Published As

Publication number Publication date
US20190140783A1 (en) 2019-05-09
EP3707844B1 (fr) 2022-12-21
CN111279641A (zh) 2020-06-12
CN111279641B (zh) 2022-09-02
US11362768B2 (en) 2022-06-14
US20200313810A1 (en) 2020-10-01
US10727986B2 (en) 2020-07-28
WO2019090337A1 (fr) 2019-05-09

Similar Documents

Publication Publication Date Title
AU2019217447B2 (en) Collision avoidance for scheduling requests and uplink control information
US11070310B2 (en) Rate-matching across downlink transmission repetitions in wireless communications
CN112313902B (zh) 子时隙物理下行链路控制信道监测和下行链路抢占指示
US11258546B2 (en) Acknowledgment feedback techniques in wireless communications
WO2019217575A1 (fr) Transmission de liaison montante autonome basée sur un groupe de blocs de code
EP3834326B1 (fr) Signalisation de groupe pour des communications ultra fiable à faible latence
EP3729895B1 (fr) Transmission en liaison descendante sans octroi de ressources
EP3912299B1 (fr) Conception de livre de codes de canal de commande de liaison montante pour nouvelle radio sans licence
EP3776962A1 (fr) Procédure de commutation de faisceau dans un canal de commande de liaison montante
US11362768B2 (en) Robust acknowledgement retransmission
WO2020227131A1 (fr) Rétroaction pour communications en multidiffusion
WO2019210238A1 (fr) Canal physique de commande de groupe destiné à des transmissions en liaison montante autonomes
WO2020150094A1 (fr) Conception de livre de codes de canal de commande de liaison montante dans une nouvelle radio sans licence
US10848276B2 (en) Carrier aggregation for downlink throughput enhancement in shortened transmission time interval operation
US20210014898A1 (en) Transmitting uplink control information in a two-step random access procedure
WO2020256934A1 (fr) Techniques pour effectuer une retransmission sur la base d'un balayage de faisceau
WO2021037043A1 (fr) Retour d'informations d'accusé de réception pour l'agrégation de porteuses
WO2020256891A1 (fr) Techniques de mise à jour de faisceaux dans des transmissions périodiques
US11166274B2 (en) User equipment-specific hybrid automatic repeat request timeline offset

Legal Events

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

Free format text: STATUS: UNKNOWN

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

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

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20200330

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20220531

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602018044559

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1539669

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230115

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20221221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230321

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1539669

Country of ref document: AT

Kind code of ref document: T

Effective date: 20221221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230322

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230421

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230421

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602018044559

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

26N No opposition filed

Effective date: 20230922

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230925

Year of fee payment: 6

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231013

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230828

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20231106

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20231130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20221221

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20231106

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20231130

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20231130

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20231106

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20231130