WO2018085717A1 - Demande de répétition automatique hybride et mise à jour d'une fenêtre de contention permettant une transmission autonome - Google Patents

Demande de répétition automatique hybride et mise à jour d'une fenêtre de contention permettant une transmission autonome Download PDF

Info

Publication number
WO2018085717A1
WO2018085717A1 PCT/US2017/060039 US2017060039W WO2018085717A1 WO 2018085717 A1 WO2018085717 A1 WO 2018085717A1 US 2017060039 W US2017060039 W US 2017060039W WO 2018085717 A1 WO2018085717 A1 WO 2018085717A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq process
transmission
process ids
ids
harq
Prior art date
Application number
PCT/US2017/060039
Other languages
English (en)
Inventor
Wenting CHANG
Huaning Niu
Jeongho Jeon
Qiaoyang Ye
Original Assignee
Intel IP Corporation
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 Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2018085717A1 publication Critical patent/WO2018085717A1/fr

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/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks

Definitions

  • a variety of wireless cellular communication systems have been implemented, or are being proposed, including a 3rd Generation Partnership Project (3GPP) Universal Mobile Telecommunications System (UMTS), a 3GPP Long-Term Evolution (LTE) system, and a 3 GPP LTE-Advanced (LTE- A) system.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long-Term Evolution
  • LTE- A 3 GPP LTE-Advanced
  • next-generation wireless cellular communication systems based upon LTE and LTE-A systems are being developed, such as a fifth generation (5G) wireless systems, New Radio (NR) wireless systems, and 5G/NR mobile networks system.
  • communication systems may provide support for higher bandwidths in part by using unlicensed spectrum
  • FIG. 1 illustrates a scenario of mixed scheduled and autonomous Uplink (UL) transmission, in accordance with some embodiments of the disclosure.
  • Fig. 2 illustrates scenarios of Contention Window Size (CWS) updating, in accordance with some embodiments of the disclosure.
  • FIG. 3 illustrates an Evolved Node B (eNB) and a User Equipment (UE), in accordance with some embodiments of the disclosure.
  • eNB Evolved Node B
  • UE User Equipment
  • FIG. 4 illustrates hardware processing circuitries for a UE for autonomous
  • FIGs. 5A and 5B illustrate methods for a UE for autonomous HARQ and CW updating, in accordance with some embodiments of the disclosure.
  • FIGs. 6A and 6B illustrate methods for a UE for autonomous HARQ and CW updating, in accordance with some embodiments of the disclosure.
  • FIG. 7 illustrates example components of a device, in accordance with some embodiments of the disclosure.
  • Fig. 8 illustrates example interfaces of baseband circuitry, in accordance with some embodiments of the disclosure.
  • 3GPP 3rd Generation Partnership Project
  • UMTS Universal Mobile Telecommunications Systems
  • LTE Long-Term Evolution
  • LTE-A 3rd Generation Partnership Project
  • 5G 5th Generation
  • NR New Radio
  • 5G/NR mobile network systems 3rd Generation Partnership Project
  • LAA Licensed- Assisted Access
  • CA Carrier Aggregation
  • LTE operation in unlicensed spectrum may potentially include (without being limited to) LTE operation in unlicensed spectrum via Dual Connectivity (DC), which may be termed DC-based LAA, and standalone LTE operation in unlicensed spectrum, in which LTE-based technology operates in unlicensed spectrum without requiring an "anchor" in licensed spectrum (such as in MulteFireTM technology by MulteFire Alliance of Fremont California, USA).
  • Standalone LTE operation in unlicensed spectrum may combine performance benefits of LTE technology with a relative simplicity of Wi-Fi®-like deployments. (Wi-Fi® is a registered trademark of the Wi-Fi Alliance of Austin, Texas, USA.) Standalone LTE operation may accordingly be an advantageous technology in meeting demands of ever-increasing wireless traffic.
  • Uplink (UL) may be limited for a variety of reasons.
  • 4-millisecond (ms) processing times e.g., of legacy LTE systems
  • TxOPs transmit opportunities
  • LBT Listen-Before-Talk
  • eNB Evolved Node-B
  • PDCCH Physical Downlink Control Channel
  • UE User Equipment
  • autonomous standalone LTE operation may advantageously improve UL data rates.
  • a Contention Window (CW) or Contention Window Size (CWS) may be updated based on an Acknowledgement (ACK) / Negative Acknowledgement (NACK) state of one reference Hybrid Automatic Repeat Request (HARQ) process Identifier (ID).
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • ID Hybrid Automatic Repeat Request
  • two types of UL transmission modes may exist: one based on scheduled access, and the other based on UE-initiated, autonomous transmission.
  • the two types of UL transmissions may have different collision probabilities, since the collision probability of a scheduling based UL transmission may be controlled by an eNB to some degree by configuring UL grants (e.g., via Downlink Control Information (DO)).
  • DO Downlink Control Information
  • CW updating (which may include CWS updating), which may advantageously improve efficient management of transmissions and CWS adaptation.
  • Various embodiments may support UEs running the two types of UL transmission modes concurrently (e.g., scheduling- based channel access and autonomous, UE-initiated channel access).
  • Some embodiments may comprise separate HARQ process ID configuration.
  • Some embodiments may comprise reference HARQ process ID configuration and CW updating.
  • Some embodiments may comprise cross re-transmission, between scheduled transmissions and autonomous transmissions.
  • signals are represented with lines. Some lines may be thicker, to indicate a greater number of constituent signal paths, and/or have arrows at one or more ends, to indicate a direction of information flow. Such indications are not intended to be limiting. Rather, the lines are used in connection with one or more exemplary embodiments to facilitate easier understanding of a circuit or a logical unit. Any represented signal, as dictated by design needs or preferences, may actually comprise one or more signals that may travel in either direction and may be implemented with any suitable type of signal scheme.
  • connection means a direct electrical, mechanical, or magnetic connection between the things that are connected, without any intermediary devices.
  • coupled means either a direct electrical, mechanical, or magnetic connection between the things that are connected or an indirect connection through one or more passive or active intermediary devices.
  • circuit or “module” may refer to one or more passive and/or active components that are arranged to cooperate with one another to provide a desired function.
  • signal may refer to at least one current signal, voltage signal, magnetic signal, or data/clock signal.
  • the transistors in various circuits, modules, and logic blocks are Tunneling FETs (TFETs).
  • Some transistors of various embodiments may comprise metal oxide semiconductor (MOS) transistors, which include drain, source, gate, and bulk terminals.
  • MOS metal oxide semiconductor
  • the transistors may also include Tri-Gate and FinFET transistors, Gate All Around Cylindrical Transistors, Square Wire, or Rectangular Ribbon Transistors or other devices implementing transistor functionality like carbon nanotubes or spintronic devices.
  • MOSFET symmetrical source and drain terminals i.e., are identical terminals and are interchangeably used here.
  • a TFET device on the other hand, has asymmetric Source and Drain terminals.
  • Bi-polar junction transistors-BJT PNP/NPN, BiCMOS, CMOS, etc. may be used for some transistors without departing from the scope of the disclosure.
  • A, B, and/or C means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).
  • combinatorial logic and sequential logic discussed in the present disclosure may pertain both to physical structures (such as AND gates, OR gates, or XOR gates), or to synthesized or otherwise optimized collections of devices implementing the logical structures that are Boolean equivalents of the logic under discussion.
  • the term “eNB” may refer to a legacy LTE capable Evolved Node-B (eNB), a centimeter-wave (cmWave) capable eNB or a cmWave small cell, a millimeter-wave (mmWave) capable eNB or an mmWave small cell, an Access Point (AP), and/or another base station for a wireless communication system.
  • eNB may refer to a 5G-capable or NR-capable eNB, and the term eNB may also encompass a gNB.
  • the term "UE” may refer to a legacy LTE capable User Equipment (UE), an mmWave capable UE, a cmWave capable UE, a Station (STA), and/or another mobile equipment for a wireless communication system.
  • UE may also refer to a 5G capable UE or NR-capable UE.
  • Various embodiments of eNBs and/or UEs discussed below may process one or more transmissions of various types. Some processing of a transmission may comprise demodulating, decoding, detecting, parsing, and/or otherwise handling a transmission that has been received.
  • an eNB or UE processing a transmission may determine or recognize the transmission's type and/or a condition associated with the transmission. For some embodiments, an eNB or UE processing a transmission may act in accordance with the transmission's type, and/or may act conditionally based upon the transmission's type. An eNB or UE processing a transmission may also recognize one or more values or fields of data carried by the transmission.
  • Processing a transmission may comprise moving the transmission through one or more layers of a protocol stack (which may be implemented in, e.g., hardware and/or software-configured elements), such as by moving a transmission that has been received by an eNB or a UE through one or more layers of a protocol stack.
  • a protocol stack which may be implemented in, e.g., hardware and/or software-configured elements
  • Various embodiments of eNBs and/or UEs discussed below may also generate one or more transmissions of various types. Some generating of a transmission may comprise modulating, encoding, formatting, assembling, and/or otherwise handling a transmission that is to be transmitted. In some embodiments, an eNB or UE generating a transmission may establish the transmission's type and/or a condition associated with the transmission. For some embodiments, an eNB or UE generating a transmission may act in accordance with the transmission's type, and/or may act conditionally based upon the transmission's type. An eNB or UE generating a transmission may also determine one or more values or fields of data carried by the transmission.
  • Generating a transmission may comprise moving the transmission through one or more layers of a protocol stack (which may be implemented in, e.g., hardware and/or software-configured elements), such as by moving a transmission to be sent by an eNB or a UE through one or more layers of a protocol stack.
  • a protocol stack which may be implemented in, e.g., hardware and/or software-configured elements
  • resources may span various Resource Blocks (RBs),
  • PRBs Physical Resource Blocks
  • time periods e.g., frames, subframes, and/or slots
  • allocated resources e.g., channels, Orthogonal Frequency -Division Multiplexing (OFDM) symbols, subcarrier frequencies, resource elements (REs), and/or portions thereof
  • OFDM Orthogonal Frequency -Division Multiplexing
  • REs resource elements
  • allocated resources e.g., channels, OFDM symbols, subcarrier frequencies, REs, and/or portions thereof
  • allocated resources e.g., channels, OFDM symbols, subcarrier frequencies, REs, and/or portions thereof
  • MulteFireTM systems may support two types of UL transmission modes.
  • Fig. 1 illustrates a scenario of mixed scheduled and autonomous UL transmission, in accordance with some embodiments of the disclosure.
  • a scenario 100 may comprise a competing channel activity 110 in unlicensed spectrum (e.g., a Wi-Fi® transmission). Competing channel activity 110 may be followed by a first DL burst 1 11 and a first UL burst 1 12 (which may be DL and UL bursts in a MulteFireTM, such as scheduled transmissions or autonomous transmissions).
  • a first UE may attempt to initiate a first autonomous UL transmission.
  • the first UE may undertake a first LBT procedure 113 (which may be a Category-4 LBT), and if first LBT procedure 113 determines that the channel is available, the first UE may transmit a Physical Uplink Shared Channel (PUSCH) 114, which may comprise UL control signaling.
  • PUSCH Physical Uplink Shared Channel
  • An eNB may then transmit first Downlink (DL) control 115, which may comprise an ACK/NACK indicator and/or UL Channel State Information (CSI) for autonomous UL transmission.
  • DL Downlink
  • CSI UL Channel State Information
  • a second LBT procedure 123 may then establish that the channel is available, and following a second DL control 125, a second DL burst 121 and a second UL burst 122 may be transmitted.
  • a second UE may attempt to initiate a second autonomous UL transmission.
  • the second UE may undertake a third LBT procedure 133, third LBT procedure 133 determines that the channel is available, and traffic on the wireless channel may proceed accordingly.
  • one or more UEs may perform autonomous UL transmissions in addition to scheduled channel accesses, so that systems supporting standalone LTE operation (like MulteFireTM systems) may have higher probability of occupying the channel, and may transmit as much UL data as possible.
  • systems supporting standalone LTE operation like MulteFireTM systems
  • an eNB may schedule multiple UEs to simultaneously transmit on orthogonal resources, and one or more UEs may perform LBT to further reduce collisions (due to, e.g., the hidden node problem).
  • a UE may try to occupy a channel by itself, and collision probabilities may be higher than for scheduled UL transmissions, since a UE's autonomous transmissions may contend with its own network nodes, such as one or more eNBs and one or more other UEs in the same cell.
  • a UE may support both modes of UL transmissions, unified mechanisms and methods for implementing autonomous HARQ and/or updating CWS may be advantageous.
  • HARQ process IDs for autonomous UL transmissions and scheduled UL transmissions may be separated, or exclusively assigned and managed.
  • some HARQ process IDs may be reserved for purposes of autonomous transmissions, and may be configured by an eNB through signaling, such as via Master Information Block (MIB), via System Information Block (SIB), via Radio Resource Control (RRC) signaling, via DCI, or via any higher-layer signaling.
  • MIB Master Information Block
  • SIB System Information Block
  • RRC Radio Resource Control
  • HARQ process IDs for autonomous UL transmission may be pre-defined (or otherwise predetermined). Once an eNB enables autonomous UL transmission for one or more UEs, the pre-defined HARQ process IDs may be used by the UEs (and use of the pre-defined HARQ process IDs may also be accounted for by the eNB).
  • bitmap-based signaling may be utilized to indicate which transmission modes may be used for a set of HARQ process IDs.
  • a bitmap may include a set of one or more bits respectively corresponding to a set of one or more HARQ process IDs. If a bit in the bitmap has a first value (e.g., a value of "0"), the corresponding HARQ process ID may be indicated as being for scheduled UL transmissions, while if the bit has a second value (e.g., a value of "1"), the corresponding HARQ process ID may be indicated as being for autonomous UL transmission.
  • a first value e.g., a value of "0”
  • the corresponding HARQ process ID may be indicated as being for scheduled UL transmissions
  • a second value e.g., a value of "1
  • contiguous HARQ process IDs may be configured.
  • HARQ process IDs in a first range may be indicated as being for scheduled UL transmissions
  • HARQ process IDs in a second range may be indicated as being for autonomous UL transmissions
  • a break point index (e.g., an index Ni) may be configured by an eNB via, for example, Layer 1 (LI) / Layer 2 (L2) signaling (either UE-specific or cell- specific), via Media Access Control (MAC) Control Elements (CEs), via RRC, or via any higher-layer signaling.
  • the break-point index may then establish a dividing line between the first range and the second range.
  • new HARQ process IDs may be introduced for autonomous UL transmission.
  • a Frequency Division Duplex (FDD) system may have 8 HARQ process ID indices, of which four may be for scheduled UL transmissions (e.g., from an index 0 to an index 3), and four may be for autonomous UL transmissions (e.g., from an index 4 to an index 7).
  • one autonomous data burst may contain four subframes, where each subframe may correspond to one HARQ process ID.
  • a UE may be disposed to waiting for ACK/NACK feedback before performing a subsequent autonomous UL transmission.
  • a UE may select a HARQ process ID by itself according to HARQ process IDs previously used for scheduled UL transmissions. For instance, an eNB may perform duplicated scheduling for one or more HARQ process IDs out of a set of HARQ process IDs, and a UE may then select a remaining HARQ process ID for autonomous UL transmission. In some embodiments, once an eNB detects that a HARQ process ID has been selected by a UE for autonomous UL transmission, that HARQ process ID nay be categorized as an autonomous UL transmission HARQ process ID, and may be incorporated into a set of autonomous UL transmission HARQ process IDs.
  • an eNB may utilize HARQ process IDs having various indices previous UL grants related to scheduled UL transmissions (e.g., having indexes of 0, 1, and 2), and a UE may then select a HARQ process ID not used by the eNB for scheduled UL transmissions to use for autonomous UL transmissions (e.g., having an index of 3, instead of 0, 1, or 2).
  • reference HARQ process ID HARQ process ID
  • FIG. 2 illustrates scenarios of Contention Window Size (CWS) updating, in accordance with some embodiments of the disclosure.
  • An initial scenario 210 may pertain to a UE performing an LBT procedure (e.g., a Category-4 LBT), then transmitting a data burst if the channel is free.
  • Initial scenario 210 may accordingly comprise an LBT procedure followed by a first data burst 21 1 (associated with a HARQ process ID having an index of HARQ ID ref).
  • First data burst 21 1 may then be followed by a second data burst 212 (associated with a HARQ process ID having an index of HARQ IDo), a third data burst 213 (associated with a HARQ process ID having an index of HARQ IDi), and a fourth data burst 214 (associated with a HARQ process ID having an index of HARQ ID2), which may end at a time to.
  • a second data burst 212 associated with a HARQ process ID having an index of HARQ IDo
  • a third data burst 213 associated with a HARQ process ID having an index of HARQ IDi
  • a fourth data burst 214 associated with a HARQ process ID having an index of HARQ ID2
  • An eNB may then report ACK/NACK information to the UE, while the UE may start another LBT procedure (e.g., a Category-4 LBT) for a subsequent autonomous UL transmission.
  • Initial scenario 210 may accordingly be followed (at time to) by either a first subsequent scenario 220 or a second subsequent scenario 230.
  • First subsequent scenario 220 may comprise an ACK/NACK 225 of the
  • HARQ process ID HARQ ID ref which may be received during the LBT procedure.
  • a CWS may be updated accordingly.
  • Second subsequent scenario 230 may comprise a first data burst 231
  • First data burst 231 may be followed by a second data burst 232 (associated with a HARQ process ID having an index of HARQ IDo), then an ACK/NACK 235 of the HARQ process ID HARQ ID ref.
  • second subsequent scenario 230 if the ACK/NACK is received after the subsequent autonomous UL transmission, the CWS may be maintained.
  • two reference HARQ process IDs can be configured by eNB, one of which may be associated with autonomous UL transmissions, and the other of which may be associated with scheduled UL transmissions.
  • a UE may then perform an LBT procedure (e.g., a Category -4 LBT procedure) and may transmit a data burst if the channel is free. Subsequently, the UE may start another LBT procedure for a subsequent autonomous UL transmission. After detecting a UL data burst, an eNB may report ACK/NACK of a reference HARQ process ID. If the data ACK/NACK is received before the subsequent autonomous UL transmission, a CWS (e.g., for Category -4 LBT) may be updated accordingly. Otherwise, the ACK/NACK may be utilized for CWS updating later.
  • an LBT procedure e.g., a Category -4 LBT procedure
  • the CW may be updated at a subframe n+N after receiving ACK/NACK of for HARQ process ID HARQ ID ref at a subframe n.
  • the number N may be configured by the eNB, or may be pre-defined (or otherwise predetermined).
  • cross re-transmission e.g., retransmission between scheduled UL transmissions and autonomous UL transmissions
  • scheduled UL transmissions may be utilized to retransmit data associated with HARQ process IDs for autonomous UL transmissions.
  • an eNB acquires the channel, it may instruct a to re-transmit the data packet, which may help the UE finish the transmission as soon as possible.
  • HARQ ID refauto (which may be for autonomous UL transmissions) might not be retransmitted in a scheduling-based fashion.
  • a data packet related to the HARQ process ID index HARQ ID refauto may be re-transmitted in a scheduling-based fashion, but the corresponding ACK/NACK feedback might not be utilized for CW updating.
  • an initial scheduling-based scheme may be retransmitted in autonomous-based transmissions. If an eNB receives it and correctly demodulates it, a New Data Indicator (NDI) bit may be toggled for a new transmission. If the eNB fails to correctly demodulate it or to receive it, the NDI bit might not be toggled, and the eNB may still schedule it in the re-transmission way.
  • NDI New Data Indicator
  • HARQ ID refscheduiing (which may be for scheduled UL transmissions) might not be retransmitted in an autonomous UL transmission fashion.
  • a data packet related to the HARQ process ID index HARQ ID refscheduiing may be re-transmitted in an autonomous UL transmission, but a corresponding ACK/NCK feedback might not be utilized for CW updating.
  • one CW size may be maintained for autonomous UL transmissions and scheduled UL transmissions.
  • such a CW size may be updated merely based on a scheduling-based transmission with a Category-4 LBT as an eLAA system.
  • such a CW size may be updated based on an
  • Fig. 3 illustrates an eNB and a UE, in accordance with some embodiments of the disclosure.
  • Fig. 3 includes block diagrams of an eNB 310 and a UE 330 which are operable to co-exist with each other and other elements of an LTE network. High-level, simplified architectures of eNB 310 and UE 330 are described so as not to obscure the embodiments. It should be noted that in some embodiments, eNB 310 may be a stationary non-mobile device.
  • eNB 310 is coupled to one or more antennas 305, and UE 330 is similarly coupled to one or more antennas 325.
  • eNB 310 may incorporate or comprise antennas 305, and UE 330 in various embodiments may incorporate or comprise antennas 325.
  • antennas 305 and/or antennas 325 may comprise one or more directional or omni-directional antennas, including monopole antennas, dipole antennas, loop antennas, patch antennas, microstrip antennas, coplanar wave antennas, or other types of antennas suitable for transmission of RF signals.
  • antennas 305 are separated to take advantage of spatial diversity.
  • eNB 310 and UE 330 are operable to communicate with each other on a network, such as a wireless network.
  • eNB 310 and UE 330 may be in communication with each other over a wireless communication channel 350, which has both a downlink path from eNB 310 to UE 330 and an uplink path from UE 330 to eNB 310.
  • eNB 310 may include a physical layer circuitry 312, a MAC (media access control) circuitry 314, a processor 316, a memory 318, and a hardware processing circuitry 320.
  • physical layer circuitry 312 includes a transceiver 313 for providing signals to and from UE 330.
  • Transceiver 313 provides signals to and from UEs or other devices using one or more antennas 305.
  • MAC circuitry 314 controls access to the wireless medium.
  • Memory 318 may be, or may include, a storage media/medium such as a magnetic storage media (e.g., magnetic tapes or magnetic disks), an optical storage media (e.g., optical discs), an electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory-based storage media), or any tangible storage media or non-transitory storage media.
  • Hardware processing circuitry 320 may comprise logic devices or circuitry to perform various operations.
  • processor 316 and memory 318 are arranged to perform the operations of hardware processing circuitry 320, such as operations described herein with reference to logic devices and circuitry within eNB 310 and/or hardware processing circuitry 320.
  • eNB 310 may be a device comprising an application processor, a memory, one or more antenna ports, and an interface for allowing the application processor to communicate with another device.
  • UE 330 may include a physical layer circuitry 332, a MAC circuitry 334, a processor 336, a memory 338, a hardware processing circuitry 340, a wireless interface 342, and a display 344.
  • a physical layer circuitry 332 may include a physical layer circuitry 332 and a graphics processing circuitry 334.
  • physical layer circuitry 332 includes a transceiver 333 for providing signals to and from eNB 310 (as well as other eNBs).
  • Transceiver 333 provides signals to and from eNBs or other devices using one or more antennas 325.
  • MAC circuitry 334 controls access to the wireless medium.
  • Memory 338 may be, or may include, a storage media/medium such as a magnetic storage media (e.g., magnetic tapes or magnetic disks), an optical storage media (e.g., optical discs), an electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory -based storage media), or any tangible storage media or non-transitory storage media.
  • Wireless interface 342 may be arranged to allow the processor to communicate with another device.
  • Display 344 may provide a visual and/or tactile display for a user to interact with UE 330, such as a touch-screen display.
  • Hardware processing circuitry 340 may comprise logic devices or circuitry to perform various operations.
  • processor 336 and memory 338 may be arranged to perform the operations of hardware processing circuitry 340, such as operations described herein with reference to logic devices and circuitry within UE 330 and/or hardware processing circuitry 340.
  • UE 330 may be a device comprising an application processor, a memory, one or more antennas, a wireless interface for allowing the application processor to communicate with another device, and a touch-screen display.
  • FIG. 4 and 7-8 also depict embodiments of eNBs, hardware processing circuitry of eNBs, UEs, and/or hardware processing circuitry of UEs, and the embodiments described with respect to Fig. 3 and Figs. 4 and 7-8 can operate or function in the manner described herein with respect to any of the figures.
  • eNB 310 and UE 330 are each described as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements and/or other hardware elements.
  • the functional elements can refer to one or more processes operating on one or more processing elements. Examples of software and/or hardware configured elements include Digital Signal Processors (DSPs), one or more microprocessors, DSPs, Field-Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Radio-Frequency Integrated Circuits (RFICs), and so on.
  • DSPs Digital Signal Processors
  • FPGAs Field-Programmable Gate Arrays
  • ASICs Application Specific Integrated Circuits
  • RFICs Radio-Frequency Integrated Circuits
  • FIG. 4 illustrates hardware processing circuitries for a UE for autonomous
  • a UE may include various hardware processing circuitries discussed herein (such as hardware processing circuitry 400), which may in turn comprise logic devices and/or circuitry operable to perform various operations.
  • UE 330 (or various elements or components therein, such as hardware processing circuitry 340, or combinations of elements or components therein) may include part of, or all of, these hardware processing circuitries.
  • one or more devices or circuitries within these hardware processing circuitries may be implemented by combinations of software-configured elements and/or other hardware elements.
  • processor 336 and/or one or more other processors which UE 330 may comprise
  • memory 338 and/or other elements or components of UE 330 (which may include hardware processing circuitry 340) may be arranged to perform the operations of these hardware processing circuitries, such as operations described herein with reference to devices and circuitry within these hardware processing circuitries.
  • processor 336 (and/or one or more other processors which UE 330 may comprise) may be a baseband processor.
  • an apparatus of UE 330 (or another UE or mobile handset), which may be operable to communicate with one or more eNBs on a wireless network, may comprise hardware processing circuitry 400.
  • hardware processing circuitry 400 may comprise one or more antenna ports 405 operable to provide various transmissions over a wireless communication channel (such as wireless
  • Antenna ports 405 may be coupled to one or more antennas 407 (which may be antennas 325).
  • antennas 407 which may be antennas 325.
  • hardware processing circuitry 400 may incorporate antennas 407, while in other embodiments, hardware processing circuitry 400 may merely be coupled to antennas 407.
  • Antenna ports 405 and antennas 407 may be operable to provide signals from a UE to a wireless communications channel and/or an eNB, and may be operable to provide signals from an eNB and/or a wireless communications channel to a UE.
  • antenna ports 405 and antennas 407 may be operable to provide transmissions from UE 330 to wireless communication channel 350 (and from there to eNB 310, or to another eNB).
  • antennas 407 and antenna ports 405 may be operable to provide transmissions from a wireless communication channel 350 (and beyond that, from eNB 310, or another eNB) to UE 330.
  • Hardware processing circuitry 400 may comprise various circuitries operable in accordance with the various embodiments discussed herein. With reference to Fig. 4, hardware processing circuitry 400 may comprise a first circuitry 410, a second circuitry 420, a third circuitry 430, and/or a fourth circuitry 440.
  • first circuitry 410 may be operable to identify one or more first HARQ process IDs and one or more second HARQ process IDs.
  • Second circuitry 420 may be operable to generate a first UL transmission for transmission in unlicensed spectrum in accordance with a scheduled transmission mode, the first UL transmission carrying one of the first HARQ process IDs.
  • Second circuitry 420 may also be operable to generate a second UL transmission for transmission in unlicensed spectrum in accordance with an autonomous transmission mode, the second UL transmission carrying one of the second HARQ process IDs.
  • First circuitry 410 may be operable to provide indicators of the first HARQ process IDs and second HARQ process IDs to second circuitry 420 via an interface 415.
  • Hardware processing circuitry 400 may also comprise an interface for sending the first UL transmission and the second UL transmission to a transmission circuitry.
  • the first HARQ process IDs and the second HARQ process IDs may be predetermined.
  • third circuitry 430 may be operable to configure a bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs.
  • the HARQ process IDs of the set of one or more HARQ process IDs may be first HARQ process IDs when respectively corresponding bits of the bitmap indicator have a first value.
  • the HARQ process IDs of the set of one or more HARQ process IDs may be second HARQ process IDs when respectively corresponding bits of the bitmap indicator have a second value.
  • third circuitry 430 may be operable to configure a first-
  • HARQ-process-ID bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs.
  • the HARQ process IDs of the set of one or more HARQ process IDs may be first HARQ process IDs when respectively corresponding bits of the first-HARQ-process-ID bitmap indicator have a predetermined value.
  • third circuitry 430 may be operable to configure a second- HARQ-process-ID bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs.
  • the HARQ process IDs of the set of one or more HARQ process IDs may be second HARQ process IDs when respectively corresponding bits of the second-HARQ-process-ID bitmap indicator have a predetermined value.
  • third circuitry 430 may be operable to configure a break-point HARQ process ID for the UE corresponding with one of a set of HARQ process IDs.
  • HARQ process IDs from a lowest HARQ process ID number up to the break-point HARQ process ID number may be the first HARQ process IDs.
  • HARQ process IDs from a HARQ process ID following the break-point HARQ process ID up to a highest HARQ process ID number may be the second HARQ process IDs.
  • one or more of the first HARQ process IDs may be selected from a subset of HARQ process IDs corresponding with one or more scheduled transmissions, and one or more of the second HARQ process IDs may be selected from a subset of HARQ process IDs not corresponding with one or more scheduled transmissions.
  • fourth circuitry 440 may be operable to process a DL transmission carrying an ACK/NACK indicator for a UL transmission corresponding with a selected HARQ process ID.
  • Third circuitry 430 may be operable to update a CWS a number of subframes N after processing the DL transmission.
  • the UL transmission corresponding with the selected HARQ process ID may be for transmission in accordance with the scheduled transmission mode, or the autonomous transmission mode.
  • Third circuitry 430 may be operable to provide HARQ process ID
  • Fourth circuitry 440 may be operable to provide indicators related to processing DL transmissions to third circuitry 430 via an interface 415.
  • first circuitry 410 may be operable to identify one or more first HARQ process IDs for transmission in unlicensed spectrum in accordance with a scheduled transmission mode. First circuitry 410 may also be operable to identify one or more second HARQ process IDs for transmission in unlicensed spectrum in accordance with an autonomous transmission mode. Second circuitry 420 may be operable to generate a first UL transmission carrying one of the first HARQ process IDs. Second circuitry 420 may also be operable to generate a second UL transmission carrying one of the second HARQ process IDs. First circuitry 410 may be operable to provide indicators of the first HARQ process IDs and second HARQ process IDs to second circuitry 420 via an interface 415.
  • First circuitry 410 may be operable to provide indicators of the first HARQ process IDs and second HARQ process IDs to second circuitry 420 via interface 415.
  • Hardware processing circuitry 400 may also comprise an interface for sending the first UL transmission and the second UL transmission to a transmission circuitry.
  • second circuitry 420 may be operable to generate a UL retransmission in accordance with the scheduled transmission mode, the UL retransmission carrying data associated with one of the second HARQ process IDs.
  • fourth circuitry 440 may be operable to process a DL transmission carrying an ACK/NACK indicator for the UL retransmission corresponding with a selected HARQ process ID.
  • Third circuitry 430 may be operable to refrain from updating a CWS based upon the ACK/NACK indicator after processing the DL transmission.
  • second circuitry 420 may be operable to generate a
  • fourth circuitry 440 may be operable to process a DL transmission carrying an ACK/NACK indicator for the UL retransmission corresponding with a selected HARQ process ID.
  • Third circuitry 430 may be operable to refrain from updating a CWS based upon the ACK/NACK indicator after processing the DL transmission.
  • first circuitry 410 may be operable to identify a CWS for both transmissions in the scheduled transmission mode and transmissions in the autonomous transmission mode.
  • third circuitry 430 may be operable to update the CWS based on ACK/NACK indicators for UL transmissions in unlicensed spectrum in accordance with the scheduled transmission mode.
  • Fourth circuitry 440 may be operable to refrain from updating the CWS based ACK/NACK indicators for UL
  • third circuitry 430 may be operable to update the CWS based on ACK/NACK indicators, both for UL transmissions in unlicensed spectrum in accordance with the scheduled transmission mode and for UL transmissions in unlicensed spectrum in accordance with the autonomous transmission mode.
  • Fourth circuitry 440 may be operable to provide indicators related to processing DL transmissions (e.g., ACK/NACK indicators related to selected HARQ process IDs) to third circuitry 430 via interface 415.
  • indicators related to processing DL transmissions e.g., ACK/NACK indicators related to selected HARQ process IDs
  • first circuitry 410 second circuitry 420, third circuitry
  • first circuitry 410, second circuitry 420, third circuitry 430, and/or fourth circuitry 440 may be implemented as separate circuitries.
  • first circuitry 410, second circuitry 420, third circuitry 430, and/or fourth circuitry 440 may be combined and implemented together in a circuitry without altering the essence of the embodiments.
  • FIGs. 5A and 5B illustrate methods for a UE for autonomous HARQ and CW updating, in accordance with some embodiments of the disclosure.
  • Figs. 6A and 6B illustrate methods for a UE for autonomous HARQ and CW updating, in accordance with some embodiments of the disclosure.
  • FIG. 5A and 5B and method 600 of Figs. 6A and 6B are discussed herein.
  • FIG. 5A and 5B and method 600 of Figs. 6A and 6B are shown in a particular order, the order of the actions can be modified.
  • the illustrated embodiments can be performed in a different order, and some actions may be performed in parallel.
  • Some of the actions and/or operations listed in Figs. 5A and 5B and Figs. 6A and 6B are optional in accordance with certain embodiments.
  • machine readable storage media may have executable instructions that, when executed, cause UE 430 and/or hardware processing circuitry 440 to perform an operation comprising the methods of Figs. 5A and 5B and Figs. 6A and 6B.
  • Such machine readable storage media may include any of a variety of storage media, like magnetic storage media (e.g., magnetic tapes or magnetic disks), optical storage media (e.g., optical discs), electronic storage media (e.g., conventional hard disk drives, solid-state disk drives, or flash-memory -based storage media), or any other tangible storage media or non-transitory storage media.
  • magnetic storage media e.g., magnetic tapes or magnetic disks
  • optical storage media e.g., optical discs
  • electronic storage media e.g., conventional hard disk drives, solid-state disk drives, or flash-memory -based storage media
  • any other tangible storage media or non-transitory storage media e.g., hard disk drives, solid-state disk drives, or flash-memory -based storage media
  • an apparatus may comprise means for performing various actions and/or operations of the methods of Figs. 5A and 5B and Figs. 6A and 6B.
  • a method 500 may comprise an identifying 510, a generating 515, and a generating 520.
  • Method 500 may also comprise a configuring 530, a configuring 540, a configuring 550, a configuring 560, a processing 570, and/or an updating 575.
  • one or more first HARQ process IDs and one or more second HARQ process IDs may be identified.
  • a first UL transmission may be generated for transmission in unlicensed spectrum in accordance with a scheduled transmission mode, the first UL transmission carrying one of the first HARQ process IDs.
  • a second UL transmission may be generated for transmission in unlicensed spectrum in accordance with an autonomous transmission mode, the second UL transmission carrying one of the second HARQ process IDs.
  • the first HARQ process IDs and/or the second HARQ process IDs may be predetermined.
  • a bitmap indicator for the UE may be configured, the bitmap indicator having one or more bits respectively corresponding with a set of one or more HARQ process IDs.
  • the HARQ process IDs of the set of one or more HARQ process IDs may be first HARQ process IDs when respectively corresponding bits of the bitmap indicator have a first value.
  • the HARQ process IDs of the set of one or more HARQ process IDs may be second HARQ process IDs when respectively corresponding bits of the bitmap indicator have a second value.
  • a first-HARQ-process-ID bitmap indicator for the UE may be configured, the first-HARQ-process-ID bitmap indicator having one or more bits respectively corresponding with a set of one or more HARQ process IDs.
  • the HARQ process IDs of the set of one or more HARQ process IDs may be first HARQ process IDs when respectively corresponding bits of the first-HARQ-process-ID bitmap indicator have a predetermined value.
  • a second-HARQ-process-ID bitmap indicator for the UE may be configured, the second-HARQ-process-ID bitmap indicator having one or more bits respectively corresponding with a set of one or more HARQ process IDs.
  • the HARQ process IDs of the set of one or more HARQ process IDs may be second HARQ process IDs when respectively corresponding bits of the second- HARQ-process-ID bitmap indicator have a predetermined value.
  • a break-point HARQ process ID for the UE may be configured, the break-point HARQ process ID corresponding with one of a set of HARQ process IDs.
  • HARQ process IDs from a lowest HARQ process ID number up to the break-point HARQ process ID number may be the first HARQ process IDs
  • HARQ process IDs from a HARQ process ID following the break-point HARQ process ID up to a highest HARQ process ID number may be the second HARQ process IDs.
  • one or more of the first HARQ process IDs may be selected from a subset of HARQ process IDs corresponding with one or more scheduled transmissions, and one or more of the second HARQ process IDs may be selected from a subset of HARQ process IDs not corresponding with one or more scheduled transmissions.
  • a DL transmission in processing 570, may be processed, the DL transmission carrying an ACK/NACK indicator for a UL transmission corresponding with a selected HARQ process ID.
  • a CWS may be updated a number of subframes N after processing the DL transmission.
  • the UL transmission corresponding with the selected HARQ process ID may be for transmission in accordance with the scheduled transmission mode, or the autonomous transmission mode.
  • a method 600 may comprise an identifying 610, a generating 615, and a generating 620.
  • Method 600 may also comprise a generating 630, a processing 640, a refraining 645, a generating 650, a processing 660, a refraining 665, an identifying 670, an updating 680, a refraining 685, and an updating 690.
  • one or more first HARQ process IDs and one or more second HARQ process IDs may be identified.
  • a first UL transmission may be generated for transmission in unlicensed spectrum in accordance with a scheduled transmission mode, the first UL transmission carrying one of the first HARQ process IDs.
  • a second UL transmission may be generated for transmission in unlicensed spectrum in accordance with an autonomous transmission mode, the second UL transmission carrying one of the second HARQ process IDs.
  • a UL retransmission in generating 630, may be generated in accordance with the scheduled transmission mode, the UL retransmission carrying data associated with one of the second HARQ process IDs.
  • a DL transmission may be processed, the DL transmission carrying an ACK/NACK indicator for the UL retransmission corresponding with a selected HARQ process ID.
  • an update to a CWS based upon the ACK/NACK after processing the DL transmission may be refrained from being made.
  • a UL retransmission in accordance with the autonomous transmission mode may be generated, the UL retransmission carrying data associated with one of the first HARQ process IDs.
  • ACK/NACK indicator for the UL retransmission corresponding with a selected HARQ process ID may be processed.
  • an update to a CWS based upon the ACK/NACK after processing the DL transmission may be refrained from being made.
  • a CWS for both transmissions in the scheduled transmission mode and transmissions in the autonomous transmission mode may be identified.
  • the CWS may be updated based on
  • ACK/NACK indicators for UL transmissions in unlicensed spectrum in accordance with the scheduled transmission mode may be refrained from being made.
  • the CWS may be updated based on
  • ACK/NACK indicators both for UL transmissions in unlicensed spectrum in accordance with the scheduled transmission mode and for UL transmissions in unlicensed spectrum in accordance with the autonomous transmission mode.
  • Fig. 7 illustrates example components of a device, in accordance with some embodiments of the disclosure.
  • the device 700 may include application circuitry 702, baseband circuitry 704, Radio Frequency (RF) circuitry 706, front- end module (FEM) circuitry 708, one or more antennas 710, and power management circuitry (PMC) 712 coupled together at least as shown.
  • the components of the illustrated device 700 may be included in a UE or a RAN node.
  • the device 700 may include less elements (e.g., a RAN node may not utilize application circuitry 702, and instead include a processor/controller to process IP data received from an EPC).
  • the device 700 may include additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
  • additional elements such as, for example, memory /storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • C-RAN Cloud-RAN
  • the application circuitry 702 may include one or more application processors.
  • the application circuitry 702 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, an so on).
  • the processors may be coupled with or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications or operating systems to run on the device 700.
  • processors of application circuitry 702 may process IP data packets received from an EPC.
  • the baseband circuitry 704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 704 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 706 and to generate baseband signals for a transmit signal path of the RF circuitry 706.
  • Baseband processing circuity 704 may interface with the application circuitry 702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 706.
  • the baseband circuitry 704 may include a third generation (3G) baseband processor 704A, a fourth generation (4G) baseband processor 704B, a fifth generation (5G) baseband processor 704C, or other baseband processor(s) 704D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), and so on).
  • the baseband circuitry 704 e.g., one or more of baseband processors 704A-D
  • baseband processors 704A-D may be included in modules stored in the memory 704G and executed via a Central Processing Unit (CPU) 704E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and so on.
  • signal modulation/demodulation e.g., a codec
  • encoding/decoding e.g., a codecation/frequency shifting, and so on.
  • modulation/demodulation circuitry of the baseband circuitry 704 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 704 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.
  • the baseband circuitry 704 may include one or more audio digital signal processor(s) (DSP) 704F.
  • the audio DSP(s) 704F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 704 and the application circuitry 702 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 704 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 704 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 704 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 706 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 706 may include switches, filters, amplifiers, and so on to facilitate the communication with the wireless network.
  • RF circuitry 706 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 704.
  • RF circuitry 706 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 708 for transmission.
  • the receive signal path of the RF circuitry 706 may include mixer circuitry 706A, amplifier circuitry 706B and filter circuitry 706C.
  • the transmit signal path of the RF circuitry 706 may include filter circuitry 706C and mixer circuitry 706A.
  • RF circuitry 706 may also include synthesizer circuitry 706D for synthesizing a frequency for use by the mixer circuitry 706A of the receive signal path and the transmit signal path.
  • the mixer circuitry 706A of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 708 based on the synthesized frequency provided by synthesizer circuitry 706D.
  • the amplifier circuitry 706B may be configured to amplify the down-converted signals and the filter circuitry 706C may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 704 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 706A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 706A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 706D to generate RF output signals for the FEM circuitry 708.
  • the baseband signals may be provided by the baseband circuitry 704 and may be filtered by filter circuitry 706C.
  • the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 706A of the receive signal path and the mixer circuitry 706A of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 704 may include a digital baseband interface to communicate with the RF circuitry 706.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 706D may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 706D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 706D may be configured to synthesize an output frequency for use by the mixer circuitry 706A of the RF circuitry 706 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 706D may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 704 or the applications processor 702 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 702.
  • Synthesizer circuitry 706D of the RF circuitry 706 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A).
  • the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 706D may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 706 may include an IQ/polar converter.
  • FEM circuitry 708 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 710, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 706 for further processing.
  • FEM circuitry 708 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 706 for transmission by one or more of the one or more antennas 710.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 706, solely in the FEM 708, or in both the RF circuitry 706 and the FEM 708.
  • the FEM circuitry 708 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 706).
  • the transmit signal path of the FEM circuitry 708 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 706), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 710).
  • PA power amplifier
  • the PMC 712 may manage power provided to the baseband circuitry 704.
  • the PMC 712 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 712 may often be included when the device 700 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 712 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • Fig. 7 shows the PMC 712 coupled only with the baseband circuitry 704.
  • the PMC 712 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 702, RF circuitry 706, or FEM 708.
  • the PMC 712 may control, or otherwise be part of, various power saving mechanisms of the device 700. For example, if the device 700 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 700 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 700 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, and so on.
  • the device 700 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 700 may not receive data in this state, in order to receive data, it must transition back to
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 702 and processors of the baseband circuitry 704 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 704 alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 704 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • Fig. 8 illustrates example interfaces of baseband circuitry, in accordance with some embodiments of the disclosure.
  • the baseband circuitry 704 of Fig. 7 may comprise processors 704A-704E and a memory 704G utilized by said processors.
  • Each of the processors 704A-704E may include a memory interface, 804A-804E, respectively, to send/receive data to/from the memory 704G.
  • the baseband circuitry 704 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 812 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 704), an application circuitry interface 814 (e.g., an interface to send/receive data to/from the application circuitry 702 of Fig. 7), an RF circuitry interface 816 (e.g., an interface to send/receive data to/from RF circuitry 706 of Fig.
  • a memory interface 812 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 704
  • an application circuitry interface 814 e.g., an interface to send/receive data to/from the application circuitry 702 of Fig. 7
  • an RF circuitry interface 816 e.g., an interface to send/receive data to/from RF circuitry 706 of Fig.
  • a wireless hardware connectivity interface 818 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components
  • a power management interface 820 e.g., an interface to send/receive power or control signals to/from the PMC 712.
  • DRAM Dynamic RAM
  • Example 1 provides an apparatus of a User Equipment (UE) operable to communicate with an Evolved Node B (eNB) on a wireless network, comprising: one or more processors to: identify one or more first Hybrid Automatic Repeat Request (HARQ) process Identities (IDs) and one or more second HARQ process IDs; generate a first Uplink (UL) transmission for transmission in unlicensed spectrum in accordance with a scheduled transmission mode, the first UL transmission carrying one of the first HARQ process IDs; and generate a second UL transmission for transmission in unlicensed spectrum in accordance with an autonomous transmission mode, the second UL transmission carrying one of the second HARQ process IDs; and an interface for sending the first UL transmission and the second UL transmission to a transmission circuitry.
  • HARQ Hybrid Automatic Repeat Request
  • example 2 the apparatus of example 1, wherein the first HARQ process IDs and the second HARQ process IDs are predetermined.
  • example 3 the apparatus of either of examples 1 or 2, wherein the one or more processors are to: configure a bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are first HARQ process IDs when respectively corresponding bits of the bitmap indicator have a first value; and wherein the HARQ process IDs of the set of one or more HARQ process IDs are second HARQ process IDs when respectively corresponding bits of the bitmap indicator have a second value.
  • example 4 the apparatus of either of examples 1 or 2, wherein the one or more processors are to: configure a first-HARQ-process-ID bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are first HARQ process IDs when respectively corresponding bits of the first-HARQ-process-ID bitmap indicator have a predetermined value.
  • example 5 the apparatus of either of examples 1 or 2, wherein the one or more processors are to: configure a second-HARQ-process-ID bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are second HARQ process IDs when respectively corresponding bits of the second-HARQ-process-ID bitmap indicator have a predetermined value.
  • example 6 the apparatus of any of examples 1 through 5, wherein the one or more processors are to: configure a break-point HARQ process ID for the UE
  • HARQ process IDs from a lowest HARQ process ID number up to the break-point HARQ process ID number are the first HARQ process IDs; and wherein HARQ process IDs from a HARQ process ID following the break-point HARQ process ID up to a highest HARQ process ID number are the second HARQ process IDs.
  • example 7 the apparatus of any of examples 1 through 6, wherein one or more of the first HARQ process IDs are selected from a subset of HARQ process IDs corresponding with one or more scheduled transmissions; and wherein one or more of the second HARQ process IDs are selected from a subset of HARQ process IDs not
  • example 8 the apparatus of any of examples 1 through 7, wherein the one or more processors are to: process a DL transmission carrying an Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicator for a UL transmission corresponding with a selected HARQ process ID; and update a Contention Window Size (CWS) a number of subframes N after processing the DL transmission, wherein the UL transmission corresponding with the selected HARQ process ID is for transmission in accordance with one of: the scheduled transmission mode, or the autonomous transmission mode.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • CWS Contention Window Size
  • Example 9 provides a User Equipment (UE) device comprising an application processor, a memory, one or more antennas, a wireless interface for allowing the application processor to communicate with another device, and a touch-screen display, the UE device including the apparatus of any of examples 1 through 8.
  • UE User Equipment
  • Example 10 provides a method comprising: identifying, for a User Equipment
  • UE User Equipment
  • HARQ Hybrid Automatic Repeat Request
  • IDs Hybrid Automatic Repeat Request
  • second HARQ process IDs Identities
  • UL Uplink
  • example 11 the method of example 10, wherein the first HARQ process
  • bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are first HARQ process IDs when respectively
  • the HARQ process IDs of the set of one or more HARQ process IDs are second HARQ process IDs when respectively corresponding bits of the bitmap indicator have a second value.
  • first-HARQ-process-ID bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are first HARQ process IDs when respectively corresponding bits of the first-HARQ-process-ID bitmap indicator have a predetermined value.
  • a second-HARQ-process-ID bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are second HARQ process IDs when respectively corresponding bits of the second-HARQ-process-ID bitmap indicator have a predetermined value.
  • example 15 the method of any of examples 10 through 14, comprising: configuring a break-point HARQ process ID for the UE corresponding with one of a set of HARQ process IDs, wherein HARQ process IDs from a lowest HARQ process ID number up to the break-point HARQ process ID number are the first HARQ process IDs; and wherein HARQ process IDs from a HARQ process ID following the break-point HARQ process ID up to a highest HARQ process ID number are the second HARQ process IDs.
  • example 16 the method of any of examples 10 through 15, wherein one or more of the first HARQ process IDs are selected from a subset of HARQ process IDs corresponding with one or more scheduled transmissions; and wherein one or more of the second HARQ process IDs are selected from a subset of HARQ process IDs not
  • example 17 the method of any of examples 10 through 16, comprising: processing a DL transmission carrying an Acknowledgement (ACK) / Negative
  • NACK Acknowledgement
  • CWS Contention Window Size
  • Example 18 provides machine readable storage media having machine executable instructions stored thereon that, when executed, cause one or more processors to perform a method according to any of examples 10 through 17.
  • Example 19 provides an apparatus of a User Equipment (UE) operable to communicate with an Evolved Node B (eNB) on a wireless network, comprising: means for identifying one or more first Hybrid Automatic Repeat Request (HARQ) process Identities (IDs) and one or more second HARQ process IDs; means for generating a first Uplink (UL) transmission for transmission in unlicensed spectrum in accordance with a scheduled transmission mode, the first UL transmission carrying one of the first HARQ process IDs; and means for generating a second UL transmission for transmission in unlicensed spectrum in accordance with an autonomous transmission mode, the second UL transmission carrying one of the second HARQ process IDs.
  • UE User Equipment
  • eNB Evolved Node B
  • the apparatus of either of examples 19 or 20, comprising: means for configuring a bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are first HARQ process IDs when respectively corresponding bits of the bitmap indicator have a first value; and wherein the HARQ process IDs of the set of one or more HARQ process IDs are second HARQ process IDs when respectively corresponding bits of the bitmap indicator have a second value.
  • example 22 the apparatus of either of examples 19 or 20, comprising: means for configuring a first-HARQ-process-ID bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are first HARQ process IDs when respectively corresponding bits of the first-HARQ-process-ID bitmap indicator have a predetermined value.
  • example 23 the apparatus of either of examples 19 or 20, comprising: means for configuring a second-HARQ-process-ID bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are second HARQ process IDs when respectively corresponding bits of the second-HARQ-process-ID bitmap indicator have a predetermined value.
  • example 24 the apparatus of any of examples 19 through 23, comprising: means for configuring a break-point HARQ process ID for the UE corresponding with one of a set of HARQ process IDs, wherein HARQ process IDs from a lowest HARQ process ID number up to the break-point HARQ process ID number are the first HARQ process IDs; and wherein HARQ process IDs from a HARQ process ID following the break-point HARQ process ID up to a highest HARQ process ID number are the second HARQ process IDs.
  • example 25 the apparatus of any of examples 19 through 24, wherein one or more of the first HARQ process IDs are selected from a subset of HARQ process IDs corresponding with one or more scheduled transmissions; and wherein one or more of the second HARQ process IDs are selected from a subset of HARQ process IDs not
  • example 26 the apparatus of any of examples 19 through 25, comprising: means for processing a DL transmission carrying an Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicator for a UL transmission corresponding with a selected HARQ process ID; and means for update a Contention Window Size (CWS) a number of subframes N after processing the DL transmission, wherein the UL transmission
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • CWS Contention Window Size
  • corresponding with the selected HARQ process ID is for transmission in accordance with one of: the scheduled transmission mode, or the autonomous transmission mode.
  • Example 27 provides machine readable storage media having machine executable instructions that, when executed, cause one or more processors of a User
  • UE operable to communicate with an Evolved Node-B (eNB) on a wireless network to perform an operation comprising: identify one or more first Hybrid Automatic Repeat Request (HARQ) process Identities (IDs) and one or more second HARQ process IDs; generate a first Uplink (UL) transmission for transmission in unlicensed spectrum in accordance with a scheduled transmission mode, the first UL transmission carrying one of the first HARQ process IDs; and generate a second UL transmission for transmission in unlicensed spectrum in accordance with an autonomous transmission mode, the second UL transmission carrying one of the second HARQ process IDs.
  • HARQ Hybrid Automatic Repeat Request
  • example 28 the machine readable storage media of example 27, wherein the first HARQ process IDs and the second HARQ process IDs are predetermined.
  • the operation comprising: configure a bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are first HARQ process IDs when respectively corresponding bits of the bitmap indicator have a first value; and wherein the HARQ process IDs of the set of one or more HARQ process IDs are second HARQ process IDs when respectively corresponding bits of the bitmap indicator have a second value.
  • the operation comprising: configure a second-HARQ-process-ID bitmap indicator for the UE having one or more bits respectively corresponding with a set of one or more HARQ process IDs, wherein the HARQ process IDs of the set of one or more HARQ process IDs are second HARQ process IDs when respectively corresponding bits of the second-HARQ- process-ID bitmap indicator have a predetermined value.
  • the machine readable storage media of any of examples 27 through 31 the operation comprising: configure a break-point HARQ process ID for the UE corresponding with one of a set of HARQ process IDs, wherein HARQ process IDs from a lowest HARQ process ID number up to the break-point HARQ process ID number are the first HARQ process IDs; and wherein HARQ process IDs from a HARQ process ID following the break-point HARQ process ID up to a highest HARQ process ID number are the second HARQ process IDs.
  • example 33 the machine readable storage media of any of examples 27 through 32, wherein one or more of the first HARQ process IDs are selected from a subset of HARQ process IDs corresponding with one or more scheduled transmissions; and wherein one or more of the second HARQ process IDs are selected from a subset of HARQ process IDs not corresponding with one or more scheduled transmissions.
  • example 34 the machine readable storage media of any of examples 27 through 33, the operation comprising: process a DL transmission carrying an
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • CWS Contention Window Size
  • Example 35 provides an apparatus of a User Equipment (UE) operable to communicate with an Evolved Node B (eNB) on a wireless network, comprising: one or more processors to: identify one or more first Hybrid Automatic Repeat Request (HARQ) process Identities (IDs) for transmission in unlicensed spectrum in accordance with a scheduled transmission mode; identify one or more second HARQ process IDs for transmission in unlicensed spectrum in accordance with an autonomous transmission mode; generate a first Uplink (UL) transmission carrying one of the first HARQ process IDs; and generate a second UL transmission carrying one of the second HARQ process IDs; and an interface for sending the first UL transmission and the second UL transmission to a transmission circuitry.
  • HARQ Hybrid Automatic Repeat Request
  • the apparatus of example 35 wherein the one or more processors are to: generate a UL retransmission in accordance with the scheduled transmission mode, the UL retransmission carrying data associated with one of the second HARQ process IDs.
  • the apparatus of example 36 wherein the one or more processors are to: process a DL transmission carrying an Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicator for the UL retransmission corresponding with a selected HARQ process ID; and refrain from updating a Contention Window Size (CWS) based upon the ACK/NACK indicator after processing the DL transmission.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • CWS Contention Window Size
  • example 38 the apparatus of any of examples 35 through 37, wherein the one or more processors are to: generate a UL retransmission in accordance with the autonomous transmission mode, the UL retransmission carrying data associated with one of the first HARQ process IDs.
  • the apparatus of example 38 wherein the one or more processors are to: process a DL transmission carrying an Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicator for the UL retransmission corresponding with a selected HARQ process ID; and refrain from updating a Contention Window Size (CWS) based upon the ACK/NACK indicator after processing the DL transmission.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • CWS Contention Window Size
  • example 40 the apparatus of any of examples 35 through 39, wherein the one or more processors are to: identify a Contention Window Size (CWS) for both transmissions in the scheduled transmission mode and transmissions in the autonomous transmission mode.
  • CWS Contention Window Size
  • example 41 the apparatus of examples 40, wherein the one or more processors are to: update the CWS based on Acknowledgement (ACK) / Negative
  • NACK Acknowledgement
  • example 42 the apparatus of example 40, wherein the one or more processors are to: update the CWS based on Acknowledgement (ACK) / Negative
  • NACK Acknowledgement
  • Example 43 provides a User Equipment (UE) device comprising an application processor, a memory, one or more antennas, a wireless interface for allowing the application processor to communicate with another device, and a touch-screen display, the UE device including the apparatus of any of examples 35 through 42.
  • UE User Equipment
  • Example 44 provides a method comprising: identifying, for a User Equipment, one or more first Hybrid Automatic Repeat Request (HARQ) process Identities (IDs) and one or more second HARQ process IDs; generating a first Uplink (UL) transmission for transmission in unlicensed spectrum in accordance with a scheduled transmission mode, the first UL transmission carrying one of the first HARQ process IDs; and generating a second UL transmission for transmission in unlicensed spectrum in accordance with an autonomous transmission mode, the second UL transmission carrying one of the second HARQ process IDs.
  • HARQ Hybrid Automatic Repeat Request
  • example 45 the method of example 44, comprising: generating a UL retransmission in accordance with the scheduled transmission mode, the UL retransmission carrying data associated with one of the second HARQ process IDs.
  • example 46 the method of example 45, comprising: processing a DL transmission carrying an Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicator for the UL retransmission corresponding with a selected HARQ process ID; and refraining from updating a Contention Window Size (CWS) based upon the ACK/NACK after processing the DL transmission.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • CWS Contention Window Size
  • example 47 the method of any of examples 44 through 46, comprising: generating a UL retransmission in accordance with the autonomous transmission mode, the UL retransmission carrying data associated with one of the first HARQ process IDs.
  • example 48 the method of example 47, comprising: processing a DL transmission carrying an Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicator for the UL retransmission corresponding with a selected HARQ process ID; and refraining from updating a Contention Window Size (CWS) based upon the ACK/NACK after processing the DL transmission.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • CWS Contention Window Size
  • example 49 the method of any of examples 44 through 48, comprising: identifying a Contention Window Size (CWS) for both transmissions in the scheduled transmission mode and transmissions in the autonomous transmission mode.
  • CWS Contention Window Size
  • example 50 the method of example 49, comprising: updating the CWS based on Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicators for UL transmissions in unlicensed spectrum in accordance with the scheduled transmission mode; and refraining from updating the CWS based ACK/NACK indicators for UL transmissions in unlicensed spectrum in accordance with the autonomous transmission mode.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • example 51 the method of example 49, comprising: updating the CWS based on Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicators, both for UL transmissions in unlicensed spectrum in accordance with the scheduled transmission mode and for UL transmissions in unlicensed spectrum in accordance with the autonomous transmission mode.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • Example 52 provides machine readable storage media having machine executable instructions stored thereon that, when executed, cause one or more processors to perform a method according to any of examples 44 through 51.
  • Example 53 provides an apparatus of a User Equipment (UE) operable to communicate with an Evolved Node B (eNB) on a wireless network, comprising: means for identifying one or more first Hybrid Automatic Repeat Request (HARQ) process Identities (IDs) and one or more second HARQ process IDs; means for generating a first Uplink (UL) transmission for transmission in unlicensed spectrum in accordance with a scheduled transmission mode, the first UL transmission carrying one of the first HARQ process IDs; and means for generating a second UL transmission for transmission in unlicensed spectrum in accordance with an autonomous transmission mode, the second UL transmission carrying one of the second HARQ process IDs.
  • UE User Equipment
  • eNB Evolved Node B
  • example 54 the apparatus of example 53, comprising: means for generating a UL retransmission in accordance with the scheduled transmission mode, the UL retransmission carrying data associated with one of the second HARQ process IDs.
  • the apparatus of example 54 comprising: means for processing a DL transmission carrying an Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicator for the UL retransmission corresponding with a selected HARQ process ID; and means for refraining from updating a Contention Window Size (CWS) based upon the ACK/NACK after processing the DL transmission.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • CWS Contention Window Size
  • example 56 the apparatus of any of examples 53 through 55, comprising: means for generating a UL retransmission in accordance with the autonomous transmission mode, the UL retransmission carrying data associated with one of the first HARQ process IDs.
  • example 57 the apparatus of example 56, comprising: means for processing a DL transmission carrying an Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicator for the UL retransmission corresponding with a selected HARQ process ID; and means for refraining from updating a Contention Window Size (CWS) based upon the ACK/NACK after processing the DL transmission.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • CWS Contention Window Size
  • the apparatus of any of examples 53 through 57 comprising: means for identifying a Contention Window Size (CWS) for both transmissions in the scheduled transmission mode and transmissions in the autonomous transmission mode.
  • CWS Contention Window Size
  • the apparatus of example 58 comprising: means for updating the CWS based on Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicators for UL transmissions in unlicensed spectrum in accordance with the scheduled transmission mode; and means for refraining from updating the CWS based ACK/NACK indicators for UL transmissions in unlicensed spectrum in accordance with the autonomous transmission mode.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • example 60 the apparatus of example 58, comprising: means for updating the CWS based on Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicators, both for UL transmissions in unlicensed spectrum in accordance with the scheduled transmission mode and for UL transmissions in unlicensed spectrum in accordance with the autonomous transmission mode.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • Example 61 provides machine readable storage media having machine executable instructions that, when executed, cause one or more processors of a User
  • UE operable to communicate with an Evolved Node-B (eNB) on a wireless network to perform an operation comprising: identify one or more first Hybrid Automatic Repeat Request (HARQ) process Identities (IDs) and one or more second HARQ process IDs; generate a first Uplink (UL) transmission for transmission in unlicensed spectrum in accordance with a scheduled transmission mode, the first UL transmission carrying one of the first HARQ process IDs; and generate a second UL transmission for transmission in unlicensed spectrum in accordance with an autonomous transmission mode, the second UL transmission carrying one of the second HARQ process IDs.
  • HARQ Hybrid Automatic Repeat Request
  • example 62 the machine readable storage media of example 61, the operation comprising: generate a UL retransmission in accordance with the scheduled transmission mode, the UL retransmission carrying data associated with one of the second HARQ process IDs.
  • the machine readable storage media of example 62 the operation comprising: process a DL transmission carrying an Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicator for the UL retransmission corresponding with a selected HARQ process ID; and refrain from updating a Contention Window Size (CWS) based upon the ACK/NACK after processing the DL transmission.
  • CWS Contention Window Size
  • the machine readable storage media of any of examples 61 through 63 the operation comprising: generate a UL retransmission in accordance with the autonomous transmission mode, the UL retransmission carrying data associated with one of the first HARQ process IDs.
  • example 65 the machine readable storage media of example 64, the operation comprising: process a DL transmission carrying an Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicator for the UL retransmission corresponding with a selected HARQ process ID; and refrain from updating a Contention Window Size (CWS) based upon the ACK/NACK after processing the DL transmission.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • CWS Contention Window Size
  • example 66 the machine readable storage media of any of examples 61 through 65, the operation comprising: identify a Contention Window Size (CWS) for both transmissions in the scheduled transmission mode and transmissions in the autonomous transmission mode.
  • CWS Contention Window Size
  • the machine readable storage media of example 66 comprising: update the CWS based on Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicators for UL transmissions in unlicensed spectrum in accordance with the scheduled transmission mode; and refrain from updating the CWS based ACK/NACK indicators for UL transmissions in unlicensed spectrum in accordance with the autonomous transmission mode.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • example 68 the machine readable storage media of example 66, the operation comprising: update the CWS based on Acknowledgement (ACK) / Negative Acknowledgement (NACK) indicators, both for UL transmissions in unlicensed spectrum in accordance with the scheduled transmission mode and for UL transmissions in unlicensed spectrum in accordance with the autonomous transmission mode.
  • ACK Acknowledgement
  • NACK Negative Acknowledgement
  • example 69 the apparatus of any of examples 1 through 8, and 35 through
  • the one or more processors comprise a baseband processor.
  • example 70 the apparatus of any of examples 1 through 8, and 35 through
  • example 71 the apparatus of any of examples 1 through 8, and 35 through
  • example 72 the apparatus of any of examples 1 through 8, and 35 through
  • transceiver circuitry for generating transmissions and processing transmissions.

Landscapes

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

Abstract

La présente invention concerne un appareil d'un équipement utilisateur (UE). L'appareil peut comprendre des premiers, deuxièmes et troisièmes circuits. Les premiers circuits peuvent servir à identifier une ou plusieurs premières identités (ID) de processus de demande de répétition automatique hybride (HARQ) et une ou plusieurs secondes ID de processus HARQ. Les deuxièmes circuits peuvent servir à générer une première transmission en liaison montante (UL) permettant une transmission dans un spectre sans licence en fonction d'un mode de transmission programmé, la première transmission UL véhiculant une ID parmi les premières ID de processus HARQ. Les troisièmes circuits peuvent servir à générer une seconde transmission UL permettant une transmission dans un spectre sans licence en fonction d'un mode de transmission autonome, la seconde transmission UL véhiculant une ID parmi les secondes ID de processus HARQ.
PCT/US2017/060039 2016-11-04 2017-11-03 Demande de répétition automatique hybride et mise à jour d'une fenêtre de contention permettant une transmission autonome WO2018085717A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2016104588 2016-11-04
CNPCT/CN2016/104588 2016-11-04

Publications (1)

Publication Number Publication Date
WO2018085717A1 true WO2018085717A1 (fr) 2018-05-11

Family

ID=60451181

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/060039 WO2018085717A1 (fr) 2016-11-04 2017-11-03 Demande de répétition automatique hybride et mise à jour d'une fenêtre de contention permettant une transmission autonome

Country Status (1)

Country Link
WO (1) WO2018085717A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020025858A1 (fr) * 2018-08-03 2020-02-06 Nokia Technologies Oy Planification de liaison montante pour nr-u
WO2021062551A1 (fr) * 2019-10-03 2021-04-08 Sierra Wireless, Inc. Procédé et appareil permettant de faciliter des transmissions dans un système de communication sans fil
US11419131B2 (en) 2018-08-09 2022-08-16 Sierra Wireless, Inc. Method and apparatus for multi-transport block grant transmissions
US11575472B2 (en) 2020-02-27 2023-02-07 Sierra Wireless, Inc. Methods and apparatuses for supporting multi transport block grant data transmission

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS: "Multi-subframe scheduling in LAA", vol. RAN WG1, no. Nanjing, China; 20160523 - 20160527, 14 May 2016 (2016-05-14), XP051096425, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_85/Docs/> [retrieved on 20160514] *
LG ELECTRONICS: "Summary of email discussion on multi-subframe scheduling", vol. RAN WG1, no. Nanjing, China; 20160523 - 20160527, 14 May 2016 (2016-05-14), XP051096424, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_85/Docs/> [retrieved on 20160514] *
NTT DOCOMO ET AL: "Discussion on UL scheduling design for eLAA", vol. RAN WG1, no. Nanjing, China; 20160523 - 20160527, 14 May 2016 (2016-05-14), XP051089819, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_85/Docs/> [retrieved on 20160514] *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020025858A1 (fr) * 2018-08-03 2020-02-06 Nokia Technologies Oy Planification de liaison montante pour nr-u
US11419131B2 (en) 2018-08-09 2022-08-16 Sierra Wireless, Inc. Method and apparatus for multi-transport block grant transmissions
US11595976B2 (en) 2018-08-09 2023-02-28 Sierra Wireless, Inc. Method and apparatus for multi-transport block grant transmissions
WO2021062551A1 (fr) * 2019-10-03 2021-04-08 Sierra Wireless, Inc. Procédé et appareil permettant de faciliter des transmissions dans un système de communication sans fil
US11381349B2 (en) 2019-10-03 2022-07-05 Sierra Wireless, Inc. Method and apparatus for facilitating transmissions in a wireless communication system
US11575472B2 (en) 2020-02-27 2023-02-07 Sierra Wireless, Inc. Methods and apparatuses for supporting multi transport block grant data transmission

Similar Documents

Publication Publication Date Title
EP3619860B1 (fr) Traitement de collision destiné à une transmission basée sur un créneau et basée sur un mini-créneau
US20190372719A1 (en) Design of downlink control information for wideband coverage enhancement
US11576142B2 (en) System and method for multiplexing of tracking reference signal and synchronization signal block
US11310813B2 (en) Maximum channel occupancy time sharing and co-existence
US11317398B2 (en) Semi-persistent scheduling for autonomous transmission activation and release
US11716729B2 (en) Resource mapping and multiplexing of uplink control channel and uplink data channel
US11985020B2 (en) Configurability and signaling for half-tone shift
WO2018085709A1 (fr) Indication de réciprocité de faisceau et gestion de faisceau de liaison descendante/montante conjointe
US11202313B2 (en) Method of uplink control signaling for non-scheduled uplink operation over unlicensed spectrum
US11388777B2 (en) Downlink control information (DCI) format for grant-less uplink transmission (GUL)
WO2018075963A1 (fr) Structure de signal de référence de démodulation et canal partagé de liaison montante physique basé sur la contention
WO2018085666A1 (fr) Restriction de schéma de modulation et de codage pour des combinaisons spécifiques de taille de bloc de transport et de nombre de blocs de ressources pour une mise en correspondance de débit tampon limitée
US11647563B2 (en) Physical downlink shared channel transmission for multi-point
WO2017131810A1 (fr) Système et procédé de transmission d&#39;informations système dans des systèmes autonomes à ondes millimétriques
WO2018085717A1 (fr) Demande de répétition automatique hybride et mise à jour d&#39;une fenêtre de contention permettant une transmission autonome
US11224023B2 (en) Timing advance for grantless uplink transmission
WO2018094175A1 (fr) Tranchage de ressources orthogonales à des fins de transmission autonome
WO2017099857A1 (fr) Procédés destinés à la réduction de latence entre l&#39;autorisation de liaison montante et transmission de canal partagé de liaison montante physique

Legal Events

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

Ref document number: 17804026

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17804026

Country of ref document: EP

Kind code of ref document: A1