WO2020155097A1 - Partage de procédure harq pour agrégation de porteuses - Google Patents

Partage de procédure harq pour agrégation de porteuses Download PDF

Info

Publication number
WO2020155097A1
WO2020155097A1 PCT/CN2019/074400 CN2019074400W WO2020155097A1 WO 2020155097 A1 WO2020155097 A1 WO 2020155097A1 CN 2019074400 W CN2019074400 W CN 2019074400W WO 2020155097 A1 WO2020155097 A1 WO 2020155097A1
Authority
WO
WIPO (PCT)
Prior art keywords
component carrier
transport block
resources
harq
grant
Prior art date
Application number
PCT/CN2019/074400
Other languages
English (en)
Inventor
Chao Wei
Yu Zhang
Hao Xu
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2019/074400 priority Critical patent/WO2020155097A1/fr
Publication of WO2020155097A1 publication Critical patent/WO2020155097A1/fr

Links

Images

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/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the following relates generally to wireless communications, and more specifically to hybrid automatic repeat request (HARQ) process sharing for carrier aggregation.
  • HARQ hybrid automatic repeat request
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include a number of base stations or network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • UE user equipment
  • one or more UEs served by a base station may be capable of transmitting or receiving on more than one component carrier in different frequencies.
  • the base station and the one or more UEs may utilize CA to increase peak data rates, and system efficiency.
  • messages or portions of messages received on a single carrier may not be successfully received by a UE, resulting in decreased user experience.
  • a transmission may be a low latency communication, and may correspond to enhanced timing requirements.
  • retransmissions of a transport block may use more resources than initial transmissions of the transport block. In such examples, conventional scheduling of retransmissions may be insufficient to satisfy low latency communication timing constraints.
  • a user equipment may receive a first downlink grant and a second downlink grant.
  • the first downlink grant may indicate a first set of resources on a first component carrier and the second downlink grant may indicate a second set of resources on a second component carrier.
  • the UE may determine that the first downlink grant and the second downlink grant are associated with the same transport block and a shared HARQ process.
  • the UE may monitor the indicated first and second set of resources on the first and second component carriers, respectively, and may send HARQ feedback for the transport block based on the monitoring of the indicated sets of resources and the shared HARQ process.
  • the shared HARQ process may result in improved reliability of wireless communications.
  • the UE may receive the transport block on the first component carrier and the second component carrier, and may perform a combining procedure.
  • a single HARQ acknowledgement (HARQ-ACK) message or one of two HARQ-ACK messages may be for the combination of the transport block received on the first and second component carriers. If the base station receives even one ACK message from the UE, the base station may determine that the UE has successfully received the transport block, and may not schedule a retransmission based on the determination.
  • HARQ-ACK HARQ acknowledgement
  • the shared HARQ process may allow a UE and a base station to satisfy timing constraints of low latency communication traffic, where a TTI length of a retransmission may be larger than that of the initial transmission in order to achieve a very low BLER target.
  • the UE may receive scheduling information and an initial transmission of a transport block corresponding to a shared HARQ process on a first component carrier, and may receive scheduling information for a retransmission of the same transport block on the second component carrier.
  • the first component carrier may be on frequency range 1 (FR1) and the second component carrier may be on frequency range 2 (FR2) with a different numerology from the first component carrier.
  • FIG. 1 illustrates an example of a system for wireless communications that supports hybrid automatic repeat request (HARQ) process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • HARQ hybrid automatic repeat request
  • FIG. 2 illustrates an example of a wireless communications system that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 3 illustrates an example of a layer diagram that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example of a resource allocation that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 5 illustrates an example of a HARQ process configuration that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 6 illustrates an example of a HARQ process configuration that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 7 illustrates an example of a timeline that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 8 illustrates an example of a timeline that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 9 illustrates an example of a process flow that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 10 illustrates an example of a process flow that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIGs. 11 and 12 show block diagrams of devices that support HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 13 shows a block diagram of a communications manager that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 14 shows a diagram of a system including a device that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIGs. 15 and 16 show block diagrams of devices that support HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 17 shows a block diagram of a communications manager that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIG. 18 shows a diagram of a system including a device that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • FIGs. 19 through 22 show flowcharts illustrating methods that support HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • a user equipment may be capable of simultaneously communicating via multiple component carriers associated with different frequencies.
  • a base station and one or more UEs may utilize carrier aggregation (CA) to increase peak data rates and system efficiency.
  • CA carrier aggregation
  • a first component carrier may be configured as a primary serving cell, and other component carriers may be configured as secondary serving cells.
  • a base station may transmit one or more grants included in one or more physical downlink control channels (PDCCHs) on the first component carrier, indicating resources for uplink or downlink transmissions on the first component carrier and other component carriers.
  • PDCCHs physical downlink control channels
  • the base station may transmit one or more downlink grants on multiple PDCCHs across multiple component carriers: one PDCCH carrying a grant on each component carrier, the grant indicating resources on that component carrier.
  • a UE may receive the one or more downlink grants, and may simultaneously monitor for and receive downlink transmission on multiple component carriers, or may simultaneously send uplink transmissions on multiple component carriers based on the downlink or uplink grants.
  • a UE and a base station may share one or more hybrid automatic repeat request (HARQ) feedback processes.
  • the UE may receive from the base station a HARQ process on a first component carrier that is associated with another HARQ process on another component carrier for transmitting the same transport block (e.g., the same media access control protocol data unit) .
  • a set of HARQ processes to be shared with other component carriers may be semi-statically configured, or dynamically configured.
  • a receiving UE may dynamically identify shared HARQ processes based on radio network temporary identifier (RNTI) values used for scrambling a received PDCCH cyclic redundancy check (CRC) .
  • RNTI radio network temporary identifier
  • CRC cyclic redundancy check
  • some HARQ processes may be shared while other HARQ processes may not be shared.
  • a base station and a UE may improve the reliability of wireless communications by utilizing shared HARQ process repetition across component carriers.
  • a base station may schedule and transmit a downlink signal on a first component carrier and may schedule and transmit a downlink signal on a second component carrier.
  • the scheduled transmissions may be for redundant copies of the same transport block, and may share a HARQ process.
  • the UE may receive the transport block on the first and second component carriers, and may generate HARQ feedback for the first and second component carriers.
  • the HARQ feedback may include separate HARQ acknowledgement (HARQ-ACK) messages for each component carrier using one or two physical uplink control channels (PUCCHs) .
  • HARQ-ACK HARQ acknowledgement
  • the HARQ feedback may be a joint HARQ-ACK message.
  • the UE may combine the transport block received on the first component carrier with the transport block received on the second component carrier (e.g., a soft-combining procedure) , and may transmit one of two separate HARQ-ACK messages based on the combining. That is, a first HARQ-ACK message may be for the transport block received on the first component carrier and the second HARQ-ACK message may be for the combination of the transport block received on the first component carrier with the transport block received on the second component carrier.
  • the contents of the two HARQ-ACK messages may or may not be the same depending on implementation and timing for the HARQ feedback.
  • the base station may receive one or both of the HARQ-ACK messages, but may refrain from scheduling a retransmission if at least one of the two HARQ-ACK messages are an ACK message.
  • the UE may be able to combine the transport block received on the first component carrier with the transport block received on the second component carrier, and may successfully receive the transport block.
  • the base station may avoid scheduling a retransmission that otherwise would be necessary, resulting in increased system efficiency and improved communications.
  • a base station and a UE may satisfy timing constraints for some types of traffic by utilizing shared HARQ processes.
  • a base station may schedule and send a transmission of a transport block to the UE on a first component carrier.
  • the scheduled traffic may include low latency communication (e.g., ultra-reliable low latency communication (URLLC) ) and the initial transmission may be scheduled using a two-symbols mini-slot.
  • the UE may send HARQ feedback on the first component carrier. If the base station determines, based on the HARQ feedback to send a retransmission of the transport block, it may do so under timing constraints for low latency communication.
  • URLLC ultra-reliable low latency communication
  • the TTI length (e.g., one slot duration with up to 14 symbols) for a retransmission of low latency communication may be large in order to achieve a very low BLER target (e.g., 10 -5 ) .
  • scheduling the retransmission on the first component carrier may not satisfy the timing constraints associated with the low latency communication.
  • the first component carrier and the second component carrier may correspond to different frequency ranges (e.g., FR1 and FR2, respectively) . Scheduling the retransmission of the low latency communication transport block on the first component carrier may result in a delay that exceeds the latency budget of the low latency communication transport block.
  • the base station may schedule a retransmission of the transport block on the second component carrier with a larger subcarrier spacing and thus a smaller slot duration (e.g., FR2) , where the PDSCH that carries the transport block has a shared HARQ process with the initial transmission of the transport block in a PDSCH on the first component carrier.
  • the retransmission may satisfy the timing constraints of the low latency communication.
  • the UE may combine the initial transmission of the first component carrier with the retransmission on the second component carrier based on the shared HARQ process to increase the likelihood that the transport block will be successfully received by the UE.
  • aspects of the disclosure are initially described in the context of a wireless communications system. Aspects of the disclosure are further illustrated by and described with reference to resource allocations, HARQ process configurations, timelines, and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to HARQ process sharing for carrier aggregation.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the wireless communications system 100 includes base stations 105, UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • NR New Radio
  • wireless communications system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low-cost and low-complexity devices.
  • ultra-reliable e.g., mission critical
  • Base stations 105 may wirelessly communicate with UEs 115 via one or more base station antennas.
  • Base stations 105 described herein may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a Home NodeB, a Home eNodeB, or some other suitable terminology.
  • Wireless communications system 100 may include base stations 105 of different types (e.g., macro or small cell base stations) .
  • the UEs 115 described herein may be able to communicate with various types of base stations 105 and network equipment including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like.
  • Each base station 105 may be associated with a particular geographic coverage area 110 in which communications with various UEs 115 is supported. Each base station 105 may provide communication coverage for a respective geographic coverage area 110 via communication links 125, and communication links 125 between a base station 105 and a UE 115 may utilize one or more carriers. Communication links 125 shown in wireless communications system 100 may include uplink transmissions from a UE 115 to a base station 105, or downlink transmissions from a base station 105 to a UE 115. Downlink transmissions may also be called forward link transmissions while uplink transmissions may also be called reverse link transmissions.
  • the geographic coverage area 110 for a base station 105 may be divided into sectors making up a portion of the geographic coverage area 110, and each sector may be associated with a cell.
  • each base station 105 may provide communication coverage for a macro cell, a small cell, a hot spot, or other types of cells, or various combinations thereof.
  • a base station 105 may be movable and therefore provide communication coverage for a moving geographic coverage area 110.
  • different geographic coverage areas 110 associated with different technologies may overlap, and overlapping geographic coverage areas 110 associated with different technologies may be supported by the same base station 105 or by different base stations 105.
  • the wireless communications system 100 may include, for example, a heterogeneous LTE/LTE-A/LTE-A Pro or NR network in which different types of base stations 105 provide coverage for various geographic coverage areas 110.
  • the term “cell” refers to a logical communication entity used for communication with a base station 105 (e.g., over a carrier) , and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) ) operating via the same or a different carrier.
  • a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., machine-type communication (MTC) , narrowband Internet-of-Things (NB-IoT) , enhanced mobile broadband (eMBB) , or others) that may provide access for different types of devices.
  • MTC machine-type communication
  • NB-IoT narrowband Internet-of-Things
  • eMBB enhanced mobile broadband
  • the term “cell” may refer to a portion of a geographic coverage area 110 (e.g., a sector) over which the logical entity operates.
  • UEs 115 may be dispersed throughout the wireless communications system 100, and each UE 115 may be stationary or mobile.
  • a UE 115 may also be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client.
  • a UE 115 may also be a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may also refer to a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or an MTC device, or the like, which may be implemented in various articles such as appliances, vehicles, meters, or the like.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC massive machine type communications
  • Some UEs 115 may be low cost or low complexity devices, and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station 105 without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application program that can make use of the information or present the information to humans interacting with the program or application.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception simultaneously) . In some examples half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for UEs 115 include entering a power saving “deep sleep” mode when not engaging in active communications, or operating over a limited bandwidth (e.g., according to narrowband communications) . In some cases, UEs 115 may be designed to support critical functions (e.g., mission critical functions) , and a wireless communications system 100 may be configured to provide ultra-reliable communications for these functions.
  • critical functions e.g., mission critical functions
  • a UE 115 may also be able to communicate directly with other UEs 115 (e.g., using a peer-to-peer (P2P) or device-to-device (D2D) protocol) .
  • P2P peer-to-peer
  • D2D device-to-device
  • One or more of a group of UEs 115 utilizing D2D communications may be within the geographic coverage area 110 of a base station 105.
  • Other UEs 115 in such a group may be outside the geographic coverage area 110 of a base station 105, or be otherwise unable to receive transmissions from a base station 105.
  • groups of UEs 115 communicating via D2D communications may utilize a one-to-many (1: M) system in which each UE 115 transmits to every other UE 115 in the group.
  • a base station 105 facilitates the scheduling of resources for D2D communications.
  • D2D communications are carried out between UEs 115 without the involvement of a base
  • Base stations 105 may communicate with the core network 130 and with one another.
  • base stations 105 may interface with the core network 130 through backhaul links 132 (e.g., via an S1, N2, N3, or other interface) .
  • Base stations 105 may communicate with one another over backhaul links 134 (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130) .
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC) , which may include at least one mobility management entity (MME) , at least one serving gateway (S-GW) , and at least one Packet Data Network (PDN) gateway (P-GW) .
  • the MME may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the EPC.
  • User IP packets may be transferred through the S-GW, which itself may be connected to the P-GW.
  • the P-GW may provide IP address allocation as well as other functions.
  • the P-GW may be connected to the network operators IP services.
  • the operators IP services may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched (PS) Stream
  • At least some of the network devices may include subcomponents such as an access network entity, which may be an example of an access node controller (ANC) .
  • Each access network entity may communicate with UEs 115 through a number of other access network transmission entities, which may be referred to as a radio head, a smart radio head, or a transmission/reception point (TRP) .
  • TRP transmission/reception point
  • various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., a base station 105) .
  • Wireless communications system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band, since the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and environmental features. However, the waves may penetrate structures sufficiently for a macro cell to provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter range (e.g., less than 100 km) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • Wireless communications system 100 may also operate in a super high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter band.
  • SHF region includes bands such as the 5 GHz industrial, scientific, and medical (ISM) bands, which may be used opportunistically by devices that may be capable of tolerating interference from other users.
  • ISM bands 5 GHz industrial, scientific, and medical bands
  • Wireless communications system 100 may also operate in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band.
  • EHF extremely high frequency
  • wireless communications system 100 may support millimeter wave (mmW) communications between UEs 115 and base stations 105, and EHF antennas of the respective devices may be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate use of antenna arrays within a UE 115.
  • mmW millimeter wave
  • the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. Techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
  • wireless communications system 100 may utilize both licensed and unlicensed radio frequency spectrum bands.
  • wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz ISM band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz ISM band.
  • wireless devices such as base stations 105 and UEs 115 may employ listen-before-talk (LBT) procedures to ensure a frequency channel is clear before transmitting data.
  • LBT listen-before-talk
  • operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA) .
  • Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these.
  • Duplexing in unlicensed spectrum may be based on frequency division duplexing (FDD) , time division duplexing (TDD) , or a combination of both.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • base station 105 or UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
  • wireless communications system 100 may use a transmission scheme between a transmitting device (e.g., a base station 105) and a receiving device (e.g., a UE 115) , where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas.
  • MIMO communications may employ multipath signal propagation to increase the spectral efficiency by transmitting or receiving multiple signals via different spatial layers, which may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the multiple signals may be referred to as a separate spatial stream, and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams.
  • Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) where multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) where multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • MU-MIMO multiple-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105 or a UE 115) to shape or steer an antenna beam (e.g., a transmit beam or receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying certain amplitude and phase offsets to signals carried via each of the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • a base station 105 may use multiple antennas or antenna arrays to conduct beamforming operations for directional communications with a UE 115. For instance, some signals (e.g. synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a base station 105 multiple times in different directions, which may include a signal being transmitted according to different beamforming weight sets associated with different directions of transmission. Transmissions in different beam directions may be used to identify (e.g., by the base station 105 or a receiving device, such as a UE 115) a beam direction for subsequent transmission and/or reception by the base station 105.
  • some signals e.g. synchronization signals, reference signals, beam selection signals, or other control signals
  • Transmissions in different beam directions may be used to identify (e.g., by the base station 105 or a receiving device, such as a UE 115) a beam direction for subsequent transmission and/or reception by the base station 105.
  • Some signals may be transmitted by a base station 105 in a single beam direction (e.g., a direction associated with the receiving device, such as a UE 115) .
  • the beam direction associated with transmissions along a single beam direction may be determined based at least in in part on a signal that was transmitted in different beam directions.
  • a UE 115 may receive one or more of the signals transmitted by the base station 105 in different directions, and the UE 115 may report to the base station 105 an indication of the signal it received with a highest signal quality, or an otherwise acceptable signal quality.
  • a UE 115 may employ similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) , or transmitting a signal in a single direction (e.g., for transmitting data to a receiving device) .
  • a receiving device may try multiple receive beams when receiving various signals from the base station 105, such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a receiving device may try multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets applied to signals received at a plurality of antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at a plurality of antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive beams or receive directions.
  • a receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving a data signal) .
  • the single receive beam may be aligned in a beam direction determined based at least in part on listening according to different receive beam directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio, or otherwise acceptable signal quality based at least in part on listening according to multiple beam directions) .
  • the antennas of a base station 105 or UE 115 may be located within one or more antenna arrays, which may support MIMO operations, or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a base station 105 may be located in diverse geographic locations.
  • a base station 105 may have an antenna array with a number of rows and columns of antenna ports that the base station 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.
  • wireless communications system 100 may be a packet-based network that operate according to a layered protocol stack.
  • PDCP Packet Data Convergence Protocol
  • a Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels.
  • RLC Radio Link Control
  • a Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer may also use hybrid automatic repeat request (HARQ) to provide retransmission at the MAC layer to improve link efficiency.
  • HARQ hybrid automatic repeat request
  • the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a base station 105 or core network 130 supporting radio bearers for user plane data.
  • RRC Radio Resource Control
  • transport channels may be mapped to physical channels.
  • UEs 115 and base stations 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • HARQ feedback is one technique of increasing the likelihood that data is received correctly over a communication link 125.
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) .
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., signal-to-noise conditions) .
  • a wireless device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • the radio frames may be identified by a system frame number (SFN) ranging from 0 to 1023.
  • SFN system frame number
  • Each frame may include 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 ms.
  • a subframe may be further divided into 2 slots each having a duration of 0.5 ms, and each slot may contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . Excluding the cyclic prefix, each symbol period may contain 2048 sampling periods.
  • a subframe may be the smallest scheduling unit of the wireless communications system 100, and may be referred to as a transmission time interval (TTI) .
  • TTI transmission time interval
  • a smallest scheduling unit of the wireless communications system 100 may be shorter than a subframe or may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) or in selected component carriers using sTTIs) .
  • a slot may further be divided into multiple mini-slots containing one or more symbols.
  • a symbol of a mini-slot or a mini-slot may be the smallest unit of scheduling.
  • Each symbol may vary in duration depending on the subcarrier spacing or frequency band of operation, for example.
  • some wireless communications systems may implement slot aggregation in which multiple slots or mini-slots are aggregated together and used for communication between a UE 115 and a base station 105.
  • carrier refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communications over a communication link 125.
  • a carrier of a communication link 125 may include a portion of a radio frequency spectrum band that is operated according to physical layer channels for a given radio access technology.
  • Each physical layer channel may carry user data, control information, or other signaling.
  • a carrier may be associated with a pre-defined frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN) ) , and may be positioned according to a channel raster for discovery by UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • E-UTRA absolute radio frequency channel number
  • Carriers may be downlink or uplink (e.g., in an FDD mode) , or be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • signal waveforms transmitted over a carrier may be made up of multiple sub-carriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
  • MCM multi-carrier modulation
  • OFDM orthogonal frequency division multiplexing
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • the organizational structure of the carriers may be different for different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • communications over a carrier may be organized according to TTIs or slots, each of which may include user data as well as control information or signaling to support decoding the user data.
  • a carrier may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc. ) and control signaling that coordinates operation for the carrier.
  • acquisition signaling e.g., synchronization signals or system information, etc.
  • control signaling that coordinates operation for the carrier.
  • a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.
  • Physical channels may be multiplexed on a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • control information transmitted in a physical control channel may be distributed between different control regions in a cascaded manner (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces) .
  • a carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a number of predetermined bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz) .
  • each served UE 115 may be configured for operating over portions or all of the carrier bandwidth.
  • some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a predefined portion or range (e.g., set of subcarriers or RBs) within a carrier (e.g., “in-band” deployment of a narrowband protocol type) .
  • a narrowband protocol type that is associated with a predefined portion or range (e.g., set of subcarriers or RBs) within a carrier (e.g., “in-band” deployment of a narrowband protocol type) .
  • a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related.
  • the number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme) .
  • the more resource elements that a UE 115 receives and the higher the order of the modulation scheme the higher the data rate may be for the UE 115.
  • a wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers) , and the use of multiple spatial layers may further increase the data rate for communications with a UE 115.
  • a spatial resource e.g., spatial layers
  • Devices of the wireless communications system 100 may have a hardware configuration that supports communications over a particular carrier bandwidth, or may be configurable to support communications over one of a set of carrier bandwidths.
  • the wireless communications system 100 may include base stations 105 and/or UEs 115 that support simultaneous communications via carriers associated with more than one different carrier bandwidth.
  • Wireless communications system 100 may support communication with a UE 115 on multiple cells or carriers, a feature which may be referred to as carrier aggregation or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both FDD and TDD component carriers.
  • wireless communications system 100 may utilize enhanced component carriers (eCCs) .
  • eCC may be characterized by one or more features including wider carrier or frequency channel bandwidth, shorter symbol duration, shorter TTI duration, or modified control channel configuration.
  • an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have a suboptimal or non-ideal backhaul link) .
  • An eCC may also be configured for use in unlicensed spectrum or shared spectrum (e.g., where more than one operator is allowed to use the spectrum) .
  • An eCC characterized by wide carrier bandwidth may include one or more segments that may be utilized by UEs 115 that are not capable of monitoring the whole carrier bandwidth or are otherwise configured to use a limited carrier bandwidth (e.g., to conserve power) .
  • an eCC may utilize a different symbol duration than other component carriers, which may include use of a reduced symbol duration as compared with symbol durations of the other component carriers.
  • a shorter symbol duration may be associated with increased spacing between adjacent subcarriers.
  • a device such as a UE 115 or base station 105, utilizing eCCs may transmit wideband signals (e.g., according to frequency channel or carrier bandwidths of 20, 40, 60, 80 MHz, etc. ) at reduced symbol durations (e.g., 16.67 microseconds) .
  • a TTI in eCC may consist of one or multiple symbol periods. In some cases, the TTI duration (that is, the number of symbol periods in a TTI) may be variable.
  • Wireless communications system 100 may be an NR system that may utilize any combination of licensed, shared, and unlicensed spectrum bands, among others.
  • the flexibility of eCC symbol duration and subcarrier spacing may allow for the use of eCC across multiple spectrums.
  • NR shared spectrum may increase spectrum utilization and spectral efficiency, specifically through dynamic vertical (e.g., across the frequency domain) and horizontal (e.g., across the time domain) sharing of resources.
  • a UE 115 may receive a first downlink grant and a second downlink grant from a base station 105.
  • the first downlink grant may indicate a first set of resources on a first component carrier and the second downlink grant may indicate a second set of resources on a second component carrier.
  • UE 115 may determine that the first downlink grant and the second downlink grant are associated with the same transport block and a shared HARQ process.
  • UE 115 may monitor the indicated first and second set of resources on the first and second component carriers, respectively, and may send HARQ feedback for the transport block based on the monitoring of the indicated sets of resources and the shared HARQ process.
  • utilizing a shared HARQ process may result in improved reliability of wireless communications.
  • UE 115 may receive the transport block on the first component carrier and the second component carrier, and may perform a combining procedure.
  • a single HARQ-ACK message or one of two HARQ-ACK messages may be for the combination of the transport block received on the first and second component carriers. If base station 105 receives even one ACK message from UE 115, base station 105 may determine that UE 115 has successfully received the transport block, and may not schedule a retransmission based on the determination.
  • the shared HARQ process may allow a UE 115 and a base station 105 to satisfy timing constraints of low latency communication traffic, where a TTI length of a retransmission may be larger than that of the initial transmission in order to achieve a very low BLER target.
  • UE 115 may receive scheduling information and an initial transmission of a transport block corresponding to a shared HARQ process on a first component carrier, and may receive scheduling information for a retransmission of the same transport block on the second component carrier.
  • the first component carrier may be on frequency range 1 (FR1) and the second component carrier may be on frequency range 2 (FR2) with a different numerology from the first component carrier.
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • wireless communications system 200 may implement aspects of wireless communications system 100.
  • Wireless communications system 200 may include a base station 105-a and a UE 115-a, which may be examples of corresponding devices as illustrated and described with respect to wireless communications system 100.
  • UE 115-a may be capable of simultaneously transmitting or receiving on multiple component carriers 205.
  • wireless communications system 200 may support carrier aggregation, and base station 105-a may communicate with UE 115-a on resources of multiple component carriers 205.
  • first component carrier 205-a and second component carrier 205-a may cover different frequency ranges.
  • first component carrier 205-a may be a first frequency range (e.g., FR1) and second component carrier 205-b may be a second frequency range (e.g., FR2) .
  • FR1 may have a carrier frequency less than or equal to 6GHz and FR2 may have a carrier frequency larger than 6GHz.
  • the subcarrier spacing for FR1 may be 15kHz, 30kHz or 60kHz, and the subcarrier spacing for FR2 may be larger than the subcarrier spacing of FR1 (e.g., 60kHz or 120kHz) .
  • First component carrier 205-a and second component carrier 205-b may have different numerologies; that is, the duration of the TTIs used for communication on component carriers 205-a and 205-b may be different.
  • base station 105-a and UE 115-a may share one or more HARQ feedback processes.
  • UE 115-a may implement a HARQ process to provide HARQ feedback (e.g., acknowledgement (ACK) or negative acknowledgement (NACK) ) for a transport block.
  • UE 115 may implement a shared HARQ process, such that a HARQ process on one component carrier 205 is associated with another HARQ process on another component carrier 205 for a same transport block (e.g., a single transport block transmitted on first component carrier 205-a and second component carrier 205-b) .
  • Base station 105-a may transmit the same transport block (e.g., a same medium access control protocol data unit (MAC PDU) ) on first component carrier 205-a and on second component carrier 205-b, and the HARQ processes corresponding to the same transport block may be shared across component carrier 205-a and component carrier 205-b.
  • transport block e.g., a same medium access control protocol data unit (MAC PDU)
  • Base station 105-a may configure a set of HARQ processes to be shared between first component carrier 205-a and second component carrier 205-b.
  • the sets of HARQ processes may be semi-statically configured, or dynamically configured, as described in greater detail with respect to FIGs. 4, 5, and 6.
  • a receiving UE may dynamically identify shared HARQ processes based on radio network temporary identifier (RNTI) values used for scrambling a received PDCCH cyclic redundancy check (CRC) , as described in greater detail with respect to FIG. 6.
  • RNTI radio network temporary identifier
  • CRC cyclic redundancy check
  • some HARQ processes of a component carrier may be shared while other HARQ processes of a component carrier may not be shared.
  • a base station 105-a and a UE 115-a may improve the reliability of wireless communications by utilizing shared HARQ process repetition across component carriers 205.
  • a base station may schedule and transmit a downlink signal on first component carrier 205-a and may schedule and transmit a downlink signal or receive an uplink signal on second component carrier 205-b.
  • the scheduled transmissions may be for redundant copies of the same transport block, and may share a HARQ process.
  • UE 115-a may receive the transport block on the first and second component carriers, and may generate HARQ feedback for the first and second component carriers.
  • the HARQ feedback may include separate HARQ acknowledgement (HARQ-ACK) messages for each component carrier using one or two physical uplink control channels (PUCCHs) .
  • HARQ-ACK HARQ acknowledgement
  • the HARQ feedback may be a joint HARQ-ACK message.
  • UE 115-a may combine the transport block received on first component carrier 205-a with the transport block received on second component carrier 205-b (e.g., a soft-combining procedure) , and may transmit one of two separate HARQ-ACK messages based on the combining.
  • base station 105-a may receive one or both of the HARQ-ACK messages, but may refrain from scheduling a retransmission if at least one of the two HARQ-ACK messages are an ACK message.
  • UE 115-a may be able to combine the transport block received on first component carrier 205-a with the transport block received on second component carrier 205-b, and may successfully receive the transport block.
  • the base station may avoid scheduling a retransmission that otherwise would be necessary, resulting in increased system efficiency and improved communications, as described in greater detail with respect to FIG. 7.
  • base station 105-a and a UE 115-a may satisfy timing constraints for some types of traffic by utilizing shared HARQ processes. For example, to achieve higher reliability in low latency communications (e.g., ultra-reliable low latency communication) , a retransmission of a transport block may use more resource block resources than a first transmission of the transport block. For example, if a first transmission has a block error rate (BLER) target of ten percent, and the first transmission occupies 20 resource blocks, then the retransmission may occupy, for instance, seventy resource blocks to achieve a 10 -5 BLER target (e.g., in a two-hop HARQ system) .
  • BLER block error rate
  • a retransmission may occupy two to three times the number of resources used in an initial transmission.
  • a payload may be variable or large (e.g., 100-500 KB for a 1.5k video) .
  • two-symbol mini-slot scheduling may not be feasible for retransmission due to insufficient resource block resource and four-symbol mini-slot or one-slot scheduling may be required for retransmission of a large transport block size (TBS) .
  • TBS transport block size
  • base station 105-a may schedule and send a transmission of a transport block to UE 115-a on first component carrier 205-a.
  • the scheduled traffic may include low latency communication (e.g., ultra-reliable low latency communication (URLLC) ) .
  • UE 115-a may send HARQ feedback on first component carrier 205-a. If base station 105-adetermines, based on the HARQ feedback to send a retransmission of the transport block, it may do so under timing constraints for low latency communication. Further, the TTI length for a retransmission of low latency communication may be larger than that of the initial transmission (e.g., one-slot instead of a two-symbols mini-slot) .
  • scheduling the retransmission on first component carrier 205-a may not satisfy the timing constraints associated with the low latency communication. Instead, base station 105-a may schedule a retransmission of the transport block on second component carrier 205-b, where the PDSCH that carries the transport block has a shared HARQ process with the initial transmission of the transport block in a PDSCH on first component carrier 205-a. In such examples, the retransmission may satisfy the timing constraints of the low latency communication, as described in greater detail with respect to FIG. 8. Further, UE 115-a may combine the initial transmission of the first component carrier with the retransmission on the second component carrier based on the shared HARQ process to increase the likelihood that the transport block will be successfully received by UE 115-a.
  • FIG. 3 illustrates an example of a layer diagram 300 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • layer diagram 300 may be implemented or utilized by a base station 105 and a UE 115, which may be examples of corresponding devices as illustrated and described with respect to wireless communications systems 100 and 200.
  • Wireless communications links may include multiple layers and sublayers.
  • a layer of communications may include sublayers such as a data convergence protocol (PDCP) 305, a radio link control (RLC) 310, and a medium access control (MAC) 315.
  • PDCP data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • SAPs Service access points
  • PHY physical
  • MAC medium access control
  • PDCP 305 may perform header compression and decompression (e.g., robust header compression (ROHC) 320) , ciphering, delivery, and duplicate detection, security (e.g., security 325) and the like.
  • RLC 310 may provide functions such as segmentation, ARQ in-sequence delivery 330 and duplicate detection. Scheduling and priority handling 335 may be performed at MAC 315.
  • a UE 115 may be capable of carrier aggregation.
  • a first UE 115 may receive signaling on a first component carrier 205-c and a second component carrier 205-d.
  • UE 115 may perform multiplexing 340-a of the signaling received on both component carriers 205-c and 205-d.
  • a second UE 115 may receive signaling on a third component carrier 205-e and a fourth component carrier 205-f.
  • the second UE 115 may perform multiplexing 340-b of the signaling received on both component carriers 205-e and 205-f.
  • each component carrier may have its own independent HARQ entity 350.
  • HARQ processes may be shared, as described with respect to FIGs 5-8.
  • FIG. 4 illustrates an example of a resource allocation 400 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • resource allocation 400 may implement aspects of wireless communications system 100.
  • resource allocation 400 may be implemented by a base station 105 and a UE 115, which may be examples of corresponding devices as illustrated and described with respect to wireless communications systems 100 and 200.
  • a UE 115 may be capable of communicating simultaneously on more than one component carrier.
  • carrier aggregation may be utilized to increase peak data rates.
  • One component carrier may be configured as a primary serving cell (PCell)
  • other component carriers may be configured as secondary serving cells (SCells) .
  • SCells may be activated or deactivated by MAC signaling.
  • a UE 115 may receive downlink or uplink grants via cross-carrier scheduling. For instance, UE 115 may receive PDCCH 405 on component carrier 1 during transmission time interval (TTI) 401, PDCCH 410 on component carrier 2 during TTI 401, and PDCCH 415 on component carrier 3 during TTI 401.
  • PDCCH 410 may include scheduling information for other component carriers. For instance, PDCCH 410 may include grant 420 which may schedule a data transmission on component carrier 1, grant 425 which may schedule a data transmission on PDSCH 470, and grant 430 which may schedule a data transmission on PDSCH 475. In some examples, grants 420, 425, and 430 may schedule uplink transmissions on a PUSCH.
  • the cross-carrier scheduling included in PDCCH 410 may be communicated via an N-bit carrier indication field (CIF) included in each grant 420, 425, and 430.
  • CIF N-bit carrier indication field
  • each of the grants 420, 425, and 430 may carried on separate resources or messages within the PDCCH 410.
  • grants 420, 425, and 430 may be included in a single message which indicates the separate PDSCHs or PUSCHs on which data transmissions are scheduled.
  • a UE 115 may receive downlink or uplink grants via self-scheduling. That is, grants for data transmission on a component carrier may be received in a PDCCH transmitted on that component carrier.
  • PDCCH 435 which may include a grant 450, on component carrier 1 during TTI 402.
  • Grant 450 may indicate resources for data transmission (e.g., an uplink transmission) on PDSCH 480.
  • UE 115 may also receive PDCCH 440, which may include grant 455, on component carrier 2.
  • Grant 455 may include an indication of resources for an uplink transmission on PDSCH 485.
  • UE 115 may also receive PDCCH 445 during TTI 402, which may include grant 460. Grant 460 may indicate resources for an uplink transmission on PDSCH 490.
  • FIG. 5 illustrates an example of a HARQ process configuration 500 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • a base station 105 and a UE 115 may be examples of corresponding devices as illustrated and described with respect to wireless communications systems 100 and 200.
  • a base station 105 and a UE 115 may communicate utilizing HARQ process sharing across component carriers. That is, a HARQ process on one component carrier 505 may be associated with another HARQ process on another component carrier 510.
  • HARQ process 515 and HARQ process 520 may be shared HARQ processes.
  • HARQ process 515 and HARQ process 520 may occur simultaneously on component carrier 505 and component carrier 510, respectively.
  • HARQ process 525 and HARQ process 540 may be shared HARQ processes.
  • HARQ process 525 and HARQ process 540 may occur at different times.
  • other HARQ procedures are not shared. For instance, HARQ process 530 and HARQ process 535 may not be shared HARQ processes.
  • Shared HARQ processes may be configured for each component carrier semi-statically, or dynamically.
  • shared HARQ procedures ma bye semi-statically configured based on higher layer signaling (e.g., RRC signaling) .
  • a higher layer configured pair of HARQ process identifiers may be used for semi-statically configuration. For instance, a HARQ process identifier corresponding to HARQ 520 on component carrier 510 and a HARQ process identifier corresponding to HARQ process 515 on component carrier 505 may be configured as a pair of shared HARQ processes between component carrier 505 and component carrier 510.
  • the configuration information including the HARQ process identifiers may be send by the base station 105 to the UE 115 via higher layer signaling.
  • HARQ process sharing may be bandwidth part (BWP) dependent.
  • BWP bandwidth part
  • a HARQ process may be shared only in a subset of BWPs instead of all the BWPs.
  • the shared HARQ process may be scheduled individually on a per component carrier basis.
  • UE 115 may receive a PDCCH on component carrier 505 and a PDCCH on component carrier 510.
  • base stat ion105 may transmit scheduling information on only one component carrier in case on PDCCH is received, or may transmit scheduling information on both component carriers for two received PDCCHs. If component carrier 505 and component carrier 510 have the same numerology, then a single PDCCH may simultaneously schedule a pair of shared HARQ processes on component carrier 505 and component carrier 510, respectively.
  • base station 105 may send a PDCCH on component carrier 505.
  • the PDCCH may include downlink control information (DCI) .
  • DCI downlink control information
  • the DCI may include, for example, a one-bit field indicating the presence on only one of the component carriers, or on both of the component carriers. That is, the DCI may include a CIF that indicates whether a grant applies only to component carrier 505, or whether the grant applies to component carrier 505 and component carrier 510. If the one-bit field indicates the presence of a grant on both of the component carriers, then the CIF indicates that the grant applies to both component carrier 505 and component carrier 510, and the UE 115 may identify the same set of resources on both component carrier 505 and component carrier 510 and may communicate thereon (e.g., monitor and receive downlink communications in the case of a downlink grant or send an uplink transmission in the case of an uplink grant) . In some examples, retransmissions for a pair of shared HARQ processes may be scheduled only on one component carrier, even if the initial transmission was scheduled on both component carriers.
  • FIG. 6 illustrates an example of a HARQ process configuration 600 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • HARQ process configuration 600 may implement aspects of wireless communications system 100.
  • HARQ process configuration 600 may be implemented by a base station 105 and a UE 115, which may be examples of corresponding devices as illustrated and described with respect to wireless communications systems 100 and 200.
  • shared HARQ processes across component carriers may be configured dynamically based on RNTI values used for scrambling PDCCH CRC.
  • a dedicated RNTI (rather than C-RNTI) may be configured for indicating HARQ process sharing.
  • the associated DCI may indicate that a HARQ process corresponding to the PDCCH is shared with other HARQ processes on other component carriers (e.g., other HARQ processes corresponding to PDCCHs that have been scrambled with the configured RNTI) .
  • UE 115 may receive two PDCCHs on component carriers 601 and 602, respectively. The two PDCCHs may schedule a shared HARQ process, and UE 115 may determine the paired HARQ process on another component carrier based on the assumption of the same transport block size, and the same HARQ process number in the PDCCH.
  • a configured RNTI may indicate HARQ process sharing (and other RNTIs such as RNTI 2 may be used for other purposes) .
  • RNTI 1 may indicate HARQ process sharing (and other RNTIs such as RNTI 2 may be used for other purposes) .
  • UE 115 may receive PDCCH 610 on component carrier 601 and PDCCH 615 on component carrier 602.
  • UE 115 may begin to decode PDCCH 610 and PDCCH 615, and may determine that PDCCH 610 and PDCCH 615 are scrambled by RNTI 1. After decoding, UE 115 may identify one or more matching values.
  • UE 115 may determine that one or more of a TBS value, an NDI value, or a HARQ identifier value for PDCCH 610 matches a TBS value, an NDI value, or a HARQ identifier value for PDCCH 615 (although other information in the DCI of PDCCH 610 and PDCCH 615, respectively, may not be the same) .
  • UE 115 may determine that PDCCH 610 and PDCCH 615 are a pair of shared HARQ processes for sending or receiving the same MAC protocol data unit (PDU) across component carriers 601 and 602. Shared HARQ processes across component carriers may be used to improve reliability, as described in greater detail with respect to FIG. 7, or to satisfy timing constraints for low latency communications, as described in greater detail with respect to FIG. 8.
  • PDU MAC protocol data unit
  • FIG. 7 illustrates an example of a timeline 700 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • timeline 700 may implement aspects of wireless communications system 100.
  • Timeline 700 may be implemented by a base station 105 and a UE 115, which may be examples of corresponding devices as illustrated and described with respect to wireless communications systems 100 and 200.
  • a base station 105 and a UE 115 may improve the reliability of wireless communications by utilizing shared HARQ process repetition across component carriers.
  • UE 115 may receive a transport block via a first and second component carrier, and may send separate HARQ-ACK feedback per HARQ process using two PUCCHs (e.g., HARQ-ACK 1 for a first component carrier and HARQ-ACK 2 for a second component carrier) .
  • UE 15 may send joint HARQ-ACK feedback for a pair of shared HARQ processes with a single HARQ-ACK (e.g., a single PDCCH may schedule a pair of shared HARQ processes or separate PDCCHs may schedule the pair of shared HARQ processes, and DCI in the PDCCH or PDCCHs may indicate the presence of the paired HARQ process on the other component carrier) .
  • a single PDCCH may schedule a pair of shared HARQ processes or separate PDCCHs may schedule the pair of shared HARQ processes, and DCI in the PDCCH or PDCCHs may indicate the presence of the paired HARQ process on the other component carrier
  • UE 115 may receive grants for resources on one carrier (e.g., FR1) for uplink or downlink transmissions on another carrier (e.g., FR2) .
  • Each component carrier may have different numerologies.
  • FR1 may cover a range of frequencies, and may correspond to a first TTI duration (e.g., 0.5 ms FR1 slot 705 and 30 kHz subcarrier spacing) and FR2 may cover a range of frequencies and may correspond to a second TTI duration (e.g., 0.125 ms FR2 slot 710 and 120 kHz subcarrier spacing) .
  • TTI duration e.g., 0.5 ms FR1 slot 705 and 30 kHz subcarrier spacing
  • FR2 may cover a range of frequencies and may correspond to a second TTI duration (e.g., 0.125 ms FR2 slot 710 and 120 kHz subcarrier spacing) .
  • FIG. 7 illustrate an example of downlink grants and downlink data transmission
  • UE 115 may receive a PDCCH 715 from the base station on FR1.
  • PDCCH 715 may include a downlink grant which may indicate a set of resources on which to monitor and receive a transport block on PDSCH 725.
  • PDSCH 725 may be received during a two-symbol mini-slot 706.
  • UE 115 may also receive PDCCH 720 on FR2.
  • PDCCH 720 may include a downlink grant indicating resources to monitor and receive a transport block on PDSCH 730.
  • UE 115 may be aware that PDSCH 725 and PDSCH 730 correspond to a shared HARQ process.
  • UE 115 may identify the shared HARQ process using any of the configuration techniques described with respect to FIGs. 4-6.
  • UE 115 may send HARQ feedback to UE for the transport block received on PDSCH 725 on FR1 and for the same transport block received on PDSCH 730 on FR2.
  • the HARQ feedback may or may not be the same for FR1 and FR2 (e.g., depending on implementation and timing for HARQ-ACK feedback) .
  • UE 115 may perform a combining procedure 731 (e.g., a soft-combining procedure) on the transport block received on FR1 and the transport block received on FR2.
  • UE 115 may not successfully receive PDSCH 725 on FR1, and may configure a negative acknowledgement (NACK) message to send to base station 105 on PUCCH 735 on FR1.
  • NACK negative acknowledgement
  • UE 115 may successfully receive and decode the transport block.
  • UE 115 may send a ACK message on PUCCH 740. If base station 105 receives at least one ACK message (e.g., either on PUCCH 735 or on PUCCH 740) , then base station 105 may refrain from scheduling a retransmission of the transport block (e.g., may assume that a transport block associated with the pair of HARQ processes is successfully received by UE 115) . Alternatively, if neither of the HARQ-ACK messages received on PUCCH 735 and PUCCH 740 is a ACK message, then base station 105 may schedule a retransmission of the transport block. By performing soft combining based on the shared HARQ process, UE 115 may increase the likelihood that it will successfully receive the transport block, resulting in improved system efficiency.
  • UE 115 may detect the pair of shared HARQ processes on FR1 and FR2, and may transmit at least the later of the HARQ-ACK messages. For example, UE 115 may determine that PUCCH 740 (e.g., which is based on the combining procedure 731 and thus more likely to be a ACK message) is later than PUCCH 735. UE 115 may refrain from transmitting PUCCH 735, and instead transmit PUCCH 740. Or, UE 115 may transmit both PUCCH 735 and PUCCH 740. If UE 115 transmits both PUCCH 735 and PUCCH 740, the HARQ-ACK messages may or may not have the same content. For example, the two HARQ-ACK messages may share the same content when UE 115 completes decoding of the soft combined PDSCH prior to transmission of the PUCCH 735.
  • PUCCH 740 e.g., which is based on the combining procedure 731 and thus more likely to be a ACK message
  • Base station 105 may send PDCCH 745 during FR1 slot 705-b.
  • PDCCH 745 may carry a grant indicating resources for a downlink grant on PDSCH 755. If neither of the HARQ messages received on FR1 during FR1 slot 705-aare ACK messages, then the transport block on PDSCH 755 may be a retransmission of the transport block. But, if at least one of the HARQ-ACK messages received on FR1 during FR1 slot 705-ais an ACK message, then the transport block on PDSCH 755 may be a new transport block.
  • base station 105 may send PDCCH 750 during FR2 slot 710-f, indicating a downlink grant on PDSCH 760.
  • PDSCH 760 may include a new transport block or a retransmission, based on whether at least one of PUCCH 735 and PUCCH 740 included an ACK message.
  • FIG. 8 illustrates an example of a timeline 800 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • timeline 800 may implement aspects of wireless communications system 100.
  • timeline 800 may be implemented by a base station 105 and a UE 115, which may be examples of corresponding devices as illustrated and described with respect to wireless communications systems 100 and 200.
  • a base station may send an initial transmission on a first component carrier (e.g., FR1) and a retransmission on a second component carrier (e.g., FR2) .
  • the communication may be low latency communication type traffic (e.g., URLLC) .
  • URLLC low latency communication type traffic
  • Such low latency communication may have a large payload and a tight latency budget (e.g., 1 ms) .
  • UE 115 may receive grants for resources on one carrier (e.g., FR1) for uplink or downlink transmissions on another carrier (e.g., FR2) .
  • FR1 may cover a range of frequencies, and may correspond to a first TTI duration (e.g., 0.5 ms FR1 slot 805 and 30 kHz subcarrier spacing) and FR2 may cover a range of frequencies and may correspond to a second TTI duration (e.g., 0.125 ms FR2 slot 810 and 120 kHz subcarrier spacing) .
  • TTI duration e.g., 0.5 ms FR1 slot 805 and 30 kHz subcarrier spacing
  • FR2 may cover a range of frequencies and may correspond to a second TTI duration (e.g., 0.125 ms FR2 slot 810 and 120 kHz subcarrier spacing) .
  • FIG. 8 illustrate an example of downlink grants and downlink data transmissions, the method and techniques similarly apply to uplink grants
  • UE 115 may receive PDCCH 815.
  • PDCCH 815 may include a downlink grant, indicating a set of resources to be monitored for PDSCH 820 on FR1.
  • the latency budget for the low latency communication may require using a two-symbol mini-slot scheduling for an initial transmission. That is, PDCCH 815 may occupy one symbol of FR1 slot 805-a, and PDSCH may occupy two symbols of FR1 805-a.
  • UE 115 may send HARQ feedback on PUCCH 825. If UE 115 does not successfully receive or decode the transport block sent on PDSCH 820, UE 115 may send a NACK message on PUCCH 825. In such cases, base station 105 may schedule a retransmission of the transport block.
  • base station 105 may transmit a PDCCH 830, which may include a downlink grant for a retransmission of the transport block on FR2.
  • the UE may be aware that PDCCH 815 and PDCCH 830 are a pair of shared HARQ processes. If the downlink grant indicates resources on PDSCH 835-a, then UE 115 may not finish decoding PDSCH 835-auntil after FR2 slot 805-b (e.g., as a result of the 1-slot rescheduling timing constraint and large payload size of the low latency communication) .
  • Each FR2 slot 805 may have a duration of 0.5 ms.
  • the total latency for transmitting and retransmitting the transport block may exceed the timing constraints of the low latency communication (e.g., may be greater than 1 ms) . That is, a retransmission of low latency communication may have a large resource assignment (e.g., may use two or three times the amount of resources as an initial transmission) . Sending the retransmission on FR1 (which has a slot duration of 0.5 ms for 30 kHz subcarrier spacing) may take too much time (e.g., most or all of FR1 slot 805-b) .
  • FR2 may have a greater frequency range (e.g., a smaller slot duration of 0.125ms for 120 kHz subcarrier spacing) , and may therefore be able to carry a larger payload in less time.
  • base station 105 may perform cross-carrier scheduling with PDCCH 830. Instead of scheduling the retransmission on PDSCH 835-a on FR1, base station 105 may schedule the retransmission on PDSCH 835-b on FR2.
  • UE 115 may complete decoding during or by the expiration of FR2 slot 810-f.
  • the total latency for transmitting the transport block on FR1 and retransmitting the transport block on FR2 may satisfy the timing constraints of the low latency communication (e.g.
  • UE 115 and base station 105 may satisfy the time constraints of low latency communication despite the large payload size of retransmissions and small latency budget for low latency communication.
  • FIG. 9 illustrates an example of a process flow 900 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • process flow 900 may implement aspects of wireless communications system 100.
  • process flow 900 may include a base station 105-b and a UE 115-b, which may be examples of corresponding devices illustrated and described with respect to wireless communications systems 100 and 200.
  • base station 105-b may configure one or more shared HARQ processes across multiple component carriers.
  • Base station 105-b may configure and send downlink grants based at least in part on the shared HARQ processes.
  • base station 105-b may send a first downlink grant to UE 115-b.
  • the first downlink grant may be carried in a PDCCH, and may indicate a first set of resources on a first component carrier.
  • base station 105-b may send a second downlink grant to UE 115-b.
  • the second downlink grant may be carried in a PDCCH (e.g., the same PDCCH as the first downlink grant or a different PDCCH) .
  • the second downlink grant may be located on the same component carrier as the first downlink grant (e.g., cross-carrier scheduling) , or on a different component carrier (e.g., self-scheduling) .
  • the second downlink grant may indicate a second set of resources on a second component carrier.
  • UE 115-b may obtain the first downlink grant and the second downlink grant.
  • UE 115-b may determine that the first downlink grant and the second downlink grant are associated with the same transport block and a shared HARQ process. The determination may be based on semi-static configuration (e.g., RRC signaling) , dynamic configuration (e.g., a DCI indicator located in one or both of the first downlink grant and the second downlink grant, or dynamically configured based on the decoding of the PDCCH or PDCCHs carrying the first and second downlink grants (e.g., based on RNTI CRC scrambling of the PDCCHs as described in more detail with respect to FIG. 6) .
  • semi-static configuration e.g., RRC signaling
  • dynamic configuration e.g., a DCI indicator located in one or both of the first downlink grant and the second downlink grant
  • UE 115-b may monitor the first set of resources on the first component carrier to receive the transport block at 935.
  • UE 115-b may monitor the second set of resources on the second component carrier to receive the same transport block at 940.
  • UE 115-b may receive the transport block on the first component carrier at 935 and the transport block on the second component carrier at 940 simultaneously or during the same Such cases may improve the reliability of wireless communications based on shared HARQ processes, as described in greater detail with respect to FIG. 7. In such cases, UE 115-b may perform HARQ feedback at 945 based on a combining procedure. For example, UE 115-b may combine the transport block received on the first component carrier at 935 and the transport block received on the second component carrier at 940, and may output a first HARQ-ACK message for the first component carrier and a second HARQ-ACK message for the second component carrier.
  • At least one of the first HARQ-ACK message and the second HARQ ACK message is based on the combination of the transport block received on the first component carrier at 935 and the transport block received on the second component carrier at 940.
  • the HARQ feedback at 945 may include a single HARQ-ACK message that is based on the combination of the transport block received on the first component carrier at 935 and the transport block received on the second component carrier at 940.
  • UE 15-a may receive the transport block on the first component carrier at 935 as an initial transmission of the transport block, and may subsequently (e.g., in a next TTI) receive the transport block on the second component carrier at 940 as a retransmission.
  • the transport block may be associated with low latency communication type traffic with one or more timing constraints (e.g., a latency budget of 1 ms) .
  • receiving the retransmission of the transport block on the second component carrier at 940 may satisfy the timing constraints based on the shared HARQ process (e.g., because of the greater frequency range and shorter TTI duration of the second bandwidth) .
  • FIG. 10 illustrates an example of a process flow 1000 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • process flow 1000 may implement aspects of wireless communications system 100.
  • process flow 1000 may include a base station 105-c and a UE 115-c, which may be examples of corresponding devices illustrated and described with respect to wireless communications systems 100 and 200.
  • base station 105-c may configure one or more shared HARQ processes across multiple component carriers.
  • Base station 105-c may configure and send downlink grants based at least in part on the shared HARQ processes.
  • base station 105-c may send a first uplink grant to UE 115-c.
  • the first uplink grant may be carried in a PDCCH or an RRC signal, and may indicate a first set of resources on a first component carrier.
  • base station 105-c may send a second uplink grant to UE 115-c.
  • the second uplink grant may be carried in an RRC message or a PDCCH (e.g., the same PDCCH as the first downlink grant or a different PDCCH) .
  • the second uplink grant may be located on the same component carrier as the first uplink grant (e.g., cross-carrier scheduling) , or on a different uplink carrier (e.g., self-scheduling) .
  • the second uplink grant may indicate a second set of resources on a second component carrier.
  • UE 115-c may obtain the first uplink grant and the second uplink grant.
  • UE 115-c may determine that the first uplink grant and the second uplink grant are associated with the same transport block and a shared HARQ process. The determination may be based on semi-static configuration (e.g., RRC signaling) , dynamic configuration (e.g., a DCI indicator located in one or both of the first downlink grant and the second downlink grant, or dynamically configured based on the decoding of the PDCCH or PDCCHs carrying the first and second downlink grants (e.g., based on RNTI CRC scrambling of the PDCCHs as described in more detail with respect to FIG. 6) .
  • semi-static configuration e.g., RRC signaling
  • dynamic configuration e.g., a DCI indicator located in one or both of the first downlink grant and the second downlink grant
  • UE 115-c may send the transport block on the first component carrier using the resources indicated in the first uplink grant.
  • UE 115-c may send the second transport block on the second component carrier using the resources indicated in the second uplink grant.
  • UE 115-c may send the transport block on the first component carrier at 935 and the transport block on the second component carrier at 940 simultaneously or during the same TTI. Such cases may improve the reliability of wireless communications based on shared HARQ processes.
  • UE 115-b may receive HARQ feedback at 1035 based on a combining procedure. For example, base station 105-c may combine the transport block received on the first component carrier at 1025 and the transport block received on the second component carrier at 130, and may output a first HARQ-ACK message for the first component carrier and a second HARQ-ACK message for the second component carrier.
  • At least one of the first HARQ-ACK message and the second HARQ ACK message may be based on the combination of the transport block received on the first component carrier at 1025 and the transport block received on the second component carrier at 1030.
  • the HARQ feedback at 1035 may include a single HARQ-ACK message that is based on the combination of the transport block received on the first component carrier at 1025 and the transport block received on the second component carrier at 1030.
  • UE 115-c may send the transport block on the first component carrier at 1025 as an initial transmission of the transport block, and may subsequently (e.g., in a next TTI) send the transport block on the second component carrier at 1030 as a retransmission.
  • the transport block may be associated with low latency communication type traffic with one or more timing constraints (e.g., a latency budget of 1 ms) .
  • sending the retransmission of the transport block on the second component carrier at 1030 may satisfy the timing constraints based on the shared HARQ process (e.g., because of the greater frequency range and shorter TTI duration of the second bandwidth) .
  • FIG. 11 shows a block diagram 1100 of a device 1105 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the device 1105 may be an example of aspects of a UE 115 as described herein.
  • the device 1105 may include a receiver 1110, a communications manager 1115, and a transmitter 1120.
  • the device 1105 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1110 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to HARQ process sharing for carrier aggregation, etc. ) . Information may be passed on to other components of the device 1105.
  • the receiver 1110 may be an example of aspects of the transceiver 1420 described with reference to FIG. 14.
  • the receiver 1110 may utilize a single antenna or a set of antennas.
  • the communications manager 1115 may obtain a first downlink grant received from a base station by the UE and a second downlink grant received from the base station by the UE, the first downlink grant for a first set of resources on a first component carrier and the second downlink grant for a second set of resources on a second component carrier, determine that the first downlink grant and the second downlink grant are associated with a same transport block and a shared HARQ process, monitor the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block, and output, for transmission to the base station, HARQ-ACK feedback for the transport block based on the monitoring and the determining.
  • the communications manager 1115 may also obtain a first uplink grant received from a base station by the UE and a second uplink grant received from the base station by the UE, the first uplink grant for a first set of resources on a first component carrier and the second uplink grant for a second set of resources on a second component carrier, determine that the first uplink grant and the second uplink grant are associated with a same transport block and a shared HARQ process, output the transport block for transmission over the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block, and obtain HARQ-ACK feedback for the transport block received from the base station at the UE, based on the outputting and the determining.
  • the communications manager 1115 may be an example of aspects of the communications manager 1410 described herein.
  • the communications manager 1115 may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communications manager 1115, or its sub-components may be executed by a general-purpose processor, a DSP, an application-specific integrated circuit (ASIC) , a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • code e.g., software or firmware
  • ASIC application-specific integrated circuit
  • the communications manager 1115 may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components.
  • the communications manager 1115, or its sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the communications manager 1115, or its sub-components may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • I/O input/output
  • the transmitter 1120 may transmit signals generated by other components of the device 1105.
  • the transmitter 1120 may be collocated with a receiver 1110 in a transceiver module.
  • the transmitter 1120 may be an example of aspects of the transceiver 1420 described with reference to FIG. 14.
  • the transmitter 1120 may utilize a single antenna or a set of antennas.
  • FIG. 12 shows a block diagram 1200 of a device 1205 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the device 1205 may be an example of aspects of a device 1105, or a UE 115 as described herein.
  • the device 1205 may include a receiver 1210, acommunications manager 1215, and a transmitter 1245.
  • the device 1205 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to HARQ process sharing for carrier aggregation, etc. ) . Information may be passed on to other components of the device 1205.
  • the receiver 1210 may be an example of aspects of the transceiver 1420 described with reference to FIG. 14.
  • the receiver 1210 may utilize a single antenna or a set of antennas.
  • the communications manager 1215 may be an example of aspects of the communications manager 1115 as described herein.
  • the communications manager 1215 may include a grant manager 1220, a shared HARQ process manager 1225, a monitoring manager 1230, a HARQ feedback manager 1235, and a resource manager 1240.
  • the communications manager 1215 may be an example of aspects of the communications manager 1410 described herein.
  • the grant manager 1220 may obtain a first downlink grant received from a base station by the UE and a second downlink grant received from the base station by the UE, the first downlink grant for a first set of resources on a first component carrier and the second downlink grant for a second set of resources on a second component carrier.
  • the grant manager 1220 may obtain a first uplink grant received from a base station by the UE and a second uplink grant received from the base station by the UE, the first uplink grant for a first set of resources on a first component carrier and the second uplink grant for a second set of resources on a second component carrier.
  • the shared HARQ process manager 1225 may determine that the first downlink grant and the second downlink grant are associated with a same transport block and a shared HARQ process.
  • the shared HARQ process manager 1225 may determine that the first uplink grant and the second uplink grant are associated with a same transport block and a shared HARQ process.
  • the monitoring manager 1230 may monitor the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block.
  • the HARQ feedback manager 1235 may output, for transmission to the base station, HARQ-ACK feedback for the transport block based on the monitoring and the determining.
  • the HARQ feedback manager 1235 may obtain HARQ-ACK feedback for the transport block received from the base station at the UE, based on the outputting and the determining.
  • the resource manager 1240 may output the transport block for transmission over the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block.
  • the transmitter 1245 may transmit signals generated by other components of the device 1205.
  • the transmitter 1245 may be collocated with a receiver 1210 in a transceiver module.
  • the transmitter 1245 may be an example of aspects of the transceiver 1420 described with reference to FIG. 14.
  • the transmitter 1245 may utilize a single antenna or a set of antennas.
  • FIG. 13 shows a block diagram 1300 of a communications manager 1305 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the communications manager 1305 may be an example of aspects of a communications manager 1115, a communications manager 1215, or a communications manager 1410 described herein.
  • the communications manager 1305 may include a grant manager 1310, a shared HARQ process manager 1315, a monitoring manager 1320, a HARQ feedback manager 1325, a combiner 1330, a low latency communication manager 1335, a RNTI manager 1340, a BWP manager 1345, and a resource manager 1350.
  • Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the grant manager 1310 may obtain a first downlink grant received from a base station by the UE and a second downlink grant received from the base station by the UE, the first downlink grant for a first set of resources on a first component carrier and the second downlink grant for a second set of resources on a second component carrier.
  • the grant manager 1310 may obtain a first uplink grant received from a base station by the UE and a second uplink grant received from the base station by the UE, the first uplink grant for a first set of resources on a first component carrier and the second uplink grant for a second set of resources on a second component carrier.
  • the grant manager 1310 may obtain a first PDCCH, the first PDCCH including the first downlink grant, where the first downlink grant allocates the first set of resources on the first component carrier for an initial transmission of the transport block. In some examples, the grant manager 1310 may obtain a second PDCCH, the second PDCCH including the second downlink grant, where the second downlink grant allocates the second set of resources on the second component carrier for a retransmission of the transport block. In some examples, the grant manager 1310 may determine that the first downlink grant and the second downlink grant are associated with a same transport block and a shared HARQ process is based on semi-static configuration information obtained via higher layer signaling received by the UE.
  • the grant manager 1310 may obtain a first PDCCH, the first PDCCH including the first uplink grant, where the first uplink grant allocates the first set of resources on the first component carrier for an initial transmission of the transport block. In some examples, the grant manager 1310 may obtain a second PDCCH, the second PDCCH including the second uplink grant, where the second uplink grant allocates the second set of resources on the second component carrier for a retransmission of the transport block.
  • the first downlink grant is included in a first PDCCH and the second downlink grant is included in a second PDCCH.
  • the first uplink grant is included in a first PDCCH and the second uplink grant is included in a second PDCCH.
  • the shared HARQ process manager 1315 may determine that the first downlink grant and the second downlink grant are associated with a same transport block and a shared HARQ process. In some examples, the shared HARQ process manager 1315 may determine that the first uplink grant and the second uplink grant are associated with a same transport block and a shared HARQ process.
  • the shared HARQ process manager 1315 may identify a DCI in one or more physical downlink control channels (PDCCHs) corresponding to the first downlink grant and the second downlink grant, the DCI including an indication that the first downlink grant and the second downlink grant are associated with the shared HARQ process, where the determining is based on the indication.
  • the shared HARQ process manager 1315 may identify a downlink control information (DCI) in one or more physical downlink control channels (PDCCHs) corresponding to the first uplink grant and the second uplink grant, the DCI including an indication that the first uplink grant and the second uplink grant are associated with the shared HARQ process, where the determining is based on the indication.
  • DCI downlink control information
  • the shared HARQ process manager 1315 may determine that the first uplink grant and the second uplink grant are associated with a same transport block and a shared HARQ process is based on semi-static configuration information obtained via higher layer signaling received by the UE.
  • the first component carrier is on frequency range 1 (FR1) and the second component carrier is on frequency range 2 (FR2) with a different numerology from the first component carrier. In some cases, the first component carrier is on frequency range 1 (FR1) and the second component carrier is on frequency range 2 (FR2) with a different numerology from the first component carrier.
  • the monitoring manager 1320 may monitor the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block.
  • the HARQ feedback manager 1325 may output, for transmission to the base station, HARQ-ACK feedback for the transport block based on the monitoring and the determining. In some examples, the HARQ feedback manager 1325 may obtain HARQ-ACK feedback for the transport block received from the base station at the UE, based on the outputting and the determining.
  • the HARQ feedback manager 1325 may output, for transmission to the base station on one of the first component carrier or the second component carrier, a first HARQ-ACK message for the first component carrier.
  • the HARQ feedback manager 1325 may output, for transmission to the base station on the one of the first component carrier or the second component carrier, a second HARQ-ACK message for the second component carrier, where at least one of the first HARQ-ACK message and the second HARQ-ACK message is based on the combining. In some examples, the HARQ feedback manager 1325 may output, for transmission to the base station, a single HARK-ACK message for the first component carrier and the second component carrier, where the single HARQ-ACK message is based on the combining. In some examples, the HARQ feedback manager 1325 may obtain a first HARQ-ACK message for the first component carrier received by the UE on one of the first component carrier or the second component carrier.
  • the HARQ feedback manager 1325 may obtain a single HARK-ACK message received by the UE, where the HARK-ACK message is for the first component carrier and the second component carrier, and where the single HARQ-ACK message is based on a combination of the transport block transmitted over the first set of resources on the first component carrier and the transport block transmitted over the second set of resources on the second component carrier.
  • the resource manager 1350 may output the transport block for transmission over the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block.
  • the combiner 1330 may combine, based on the determining, the transport block received on the first set of resources on the first component carrier and the transport block received on the second set of resources on the transport block received on the second component carrier. In some examples, the combiner 1330 may obtain a second HARQ-ACK message for the second component carrier received by the UE on the one of the first component carrier or the second component carrier, where at least one of the first HARQ-ACK message and the second HARQ-ACK message is based on a combination of the transport block transmitted over the first set of resources on the first component carrier and the transport block transmitted over the second set of resources on the second component carrier.
  • the transport block is associated with a low latency communication type of traffic corresponding to one or more timing constraints, and where outputting the HARQ-ACK feedback for transmission and obtaining the retransmission of the transport block received by the UE on the second component carrier satisfies the timing constraints.
  • the transport block is associated with a low latency communication type of traffic corresponding to one or more timing constraints, and where outputting the HARQ-ACK feedback for transmission and obtaining the retransmission of the transport block received by the UE on the second component carrier satisfies the timing constraints.
  • the RNTI manager 1340 may decode, based on a dedicated radio network temporary identifier (RNTI) value, the first PDCCH and the second PDCCH. In some examples, the RNTI manager 1340 may determine, based on the decoding, that a first transport block size (TBS) value for the first PDCCH matches a second TBS value for the second PDCCH.
  • RNTI dedicated radio network temporary identifier
  • TBS transport block size
  • the RNTI manager 1340 may determine, based on the decoding, that a first HARQ process number value of the first PDCCH matches a second HARQ process number value of the second PDCCH, where determining that the first downlink grant and the second downlink grant are associated with a same transport block and a shared HARQ process is based on the matching TBS values and the matching HARQ process number values.
  • the RNTI manager 1340 may decode, based on a dedicated radio network temporary identifier (RNTI) value, the first PDCCH and the second PDCCH. In some examples, the RNTI manager 1340 may determine, based on the decoding, that a first transport block size (TBS) value for the first PDCCH matches a second TBS value for the second PDCCH.
  • RNTI dedicated radio network temporary identifier
  • TBS transport block size
  • the RNTI manager 1340 may determine, based on the decoding, that a first HARQ process number value of the first PDCCH matches a second HARQ process number value of the second PDCCH, where determining that the first uplink grant and the second uplink grant are associated with a same transport block and a shared HARQ process is based on the matching TBS values and the matching HARQ process number values.
  • the BWP manager 1345 may determine that the first downlink grant and the second downlink grant are associated with a same transport block and a shared HARQ process is based on one or more bandwidth part (BWP) configuration information.
  • BWP bandwidth part
  • the BWP manager 1345 may determine that the first uplink grant and the second uplink grant are associated with a same transport block and a shared HARQ process is based on one or more bandwidth part (BWP) configuration information.
  • BWP bandwidth part
  • FIG. 14 shows a diagram of a system 1400 including a device 1405 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the device 1405 may be an example of or include the components of device 1105, device 1205, or a UE 115 as described herein.
  • the device 1405 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager 1410, an I/O controller 1415, a transceiver 1420, an antenna 1425, memory 1430, and a processor 1440. These components may be in electronic communication via one or more buses (e.g., bus 1445) .
  • buses e.g., bus 1445
  • the communications manager 1410 may obtain a first downlink grant received from a base station by the UE and a second downlink grant received from the base station by the UE, the first downlink grant for a first set of resources on a first component carrier and the second downlink grant for a second set of resources on a second component carrier, determine that the first downlink grant and the second downlink grant are associated with a same transport block and a shared HARQ process, monitor the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block, and output, for transmission to the base station, HARQ-ACK feedback for the transport block based on the monitoring and the determining.
  • the communications manager 1410 may also obtain a first uplink grant received from a base station by the UE and a second uplink grant received from the base station by the UE, the first uplink grant for a first set of resources on a first component carrier and the second uplink grant for a second set of resources on a second component carrier, determine that the first uplink grant and the second uplink grant are associated with a same transport block and a shared HARQ process, output the transport block for transmission over the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block, and obtain HARQ-ACK feedback for the transport block received from the base station at the UE, based on the outputting and the determining.
  • the I/O controller 1415 may manage input and output signals for the device 1405.
  • the I/O controller 1415 may also manage peripherals not integrated into the device 1405.
  • the I/O controller 1415 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1415 may utilize an operating system such as or another known operating system.
  • the I/O controller 1415 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1415 may be implemented as part of a processor.
  • a user may interact with the device 1405 via the I/O controller 1415 or via hardware components controlled by the I/O controller 1415.
  • the transceiver 1420 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1420 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1420 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1425. However, in some cases the device may have more than one antenna 1425, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 1430 may include RAM and ROM.
  • the memory 1430 may store computer-readable, computer-executable code 1435 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 1430 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the processor 1440 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 1440 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1440.
  • the processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1430) to cause the device 1405 to perform various functions (e.g., functions or tasks supporting HARQ process sharing for carrier aggregation) .
  • the code 1435 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 1435 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1435 may not be directly executable by the processor 1440 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • FIG. 15 shows a block diagram 1500 of a device 1505 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the device 1505 may be an example of aspects of a base station 105 as described herein.
  • the device 1505 may include a receiver 1510, a communications manager 1515, and a transmitter 1520.
  • the device 1505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to HARQ process sharing for carrier aggregation, etc. ) . Information may be passed on to other components of the device 1505.
  • the receiver 1510 may be an example of aspects of the transceiver 1820 described with reference to FIG. 18.
  • the receiver 1510 may utilize a single antenna or a set of antennas.
  • the communications manager 1515 may output for transmission, by the base station to a UE, a first downlink grant for a first set of resources on a first component carrier and a second downlink grant for a second set of resources on a second component carrier, where the first downlink grant and the second downlink grant are associated with a same transport block and a shared feedback HARQ process, output the transport block for transmission on the first set of resources on the first component carrier and transmitting the transport block on the second set of resources on the second component carrier, and obtain HARQ-ACK feedback received from the UE for the transport block.
  • the communications manager 1515 may also output for transmission to a UE, a first uplink grant for a first set of resources on a first component carrier and a second uplink grant for a second set of resources on a second component carrier, where the first uplink grant and the second uplink grant are associated with a same transport block and a shared feedback HARQ process, obtain the transport block received by the base station over the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block, and output, for transmission to the UE, HARQ-ACK feedback for the transport block received from the UE.
  • the communications manager 1515 may be an example of aspects of the communications manager 1810 described herein.
  • the communications manager 1515 may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communications manager 1515, or its sub-components may be executed by a general-purpose processor, a DSP, an application-specific integrated circuit (ASIC) , a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • code e.g., software or firmware
  • ASIC application-specific integrated circuit
  • the communications manager 1515 may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components.
  • the communications manager 1515, or its sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the communications manager 1515, or its sub-components may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • I/O input/output
  • the transmitter 1520 may transmit signals generated by other components of the device 1505.
  • the transmitter 1520 may be collocated with a receiver 1510 in a transceiver module.
  • the transmitter 1520 may be an example of aspects of the transceiver 1820 described with reference to FIG. 18.
  • the transmitter 1520 may utilize a single antenna or a set of antennas.
  • FIG. 16 shows a block diagram 1600 of a device 1605 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the device 1605 may be an example of aspects of a device 1505, or a base station 105 as described herein.
  • the device 1605 may include a receiver 1610, a communications manager 1615, and a transmitter 1635.
  • the device 1605 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to HARQ process sharing for carrier aggregation, etc. ) . Information may be passed on to other components of the device 1605.
  • the receiver 1610 may be an example of aspects of the transceiver 1820 described with reference to FIG. 18.
  • the receiver 1610 may utilize a single antenna or a set of antennas.
  • the communications manager 1615 may be an example of aspects of the communications manager 1515 as described herein.
  • the communications manager 1615 may include a grant manager 1620, a resource manager 1625, and a HARQ feedback manager 1630.
  • the communications manager 1615 may be an example of aspects of the communications manager 1810 described herein.
  • the grant manager 1620 may output for transmission, by the base station to a UE, a first downlink grant for a first set of resources on a first component carrier and a second downlink grant for a second set of resources on a second component carrier, where the first downlink grant and the second downlink grant are associated with a same transport block and a shared feedback HARQ process.
  • the grant manager 1620 may output for transmission to a UE, a first uplink grant for a first set of resources on a first component carrier and a second uplink grant for a second set of resources on a second component carrier, where the first uplink grant and the second uplink grant are associated with a same transport block and a shared feedback HARQ process.
  • the resource manager 1625 may output the transport block for transmission on the first set of resources on the first component carrier and transmitting the transport block on the second set of resources on the second component carrier.
  • the resource manager 1625 may obtain the transport block received by the base station over the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block.
  • the HARQ feedback manager 1630 may obtain HARQ-ACK feedback received from the UE for the transport block.
  • the HARQ feedback manager 1630 may output, for transmission to the UE, HARQ-ACK feedback for the transport block received from the UE.
  • the transmitter 1635 may transmit signals generated by other components of the device 1605.
  • the transmitter 1635 may be collocated with a receiver 1610 in a transceiver module.
  • the transmitter 1635 may be an example of aspects of the transceiver 1820 described with reference to FIG. 18.
  • the transmitter 1635 may utilize a single antenna or a set of antennas.
  • FIG. 17 shows a block diagram 1700 of a communications manager 1705 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the communications manager 1705 may be an example of aspects of a communications manager 1515, a communications manager 1615, or a communications manager 1810 described herein.
  • the communications manager 1705 may include a grant manager 1710, a resource manager 1715, a HARQ feedback manager 1720, a low latency communication manager 1725, a shared HARQ process manager 1730, a RNTI manager 1735, a BWP manager 1740, and a combiner 1745. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the grant manager 1710 may output for transmission, by the base station to a UE, a first downlink grant for a first set of resources on a first component carrier and a second downlink grant for a second set of resources on a second component carrier, where the first downlink grant and the second downlink grant are associated with a same transport block and a shared feedback HARQ process.
  • the grant manager 1710 may output for transmission to a UE, a first uplink grant for a first set of resources on a first component carrier and a second uplink grant for a second set of resources on a second component carrier, where the first uplink grant and the second uplink grant are associated with a same transport block and a shared feedback HARQ process.
  • the grant manager 1710 may configure a first PDCCH including the first downlink grant, where the first downlink grant allocates the first set of resources on the first component carrier for an initial transmission of the transport block.
  • the grant manager 1710 may output for transmission, on the first component carrier, a second PDCCH including the second downlink grant, where the second downlink grant allocates the second set of resources on the second component carrier for a retransmission of the transport block.
  • the grant manager 1710 may configure a first PDCCH including the first uplink grant, where the first uplink grant allocates the first set of resources on the first component carrier for an initial transmission of the transport block.
  • the grant manager 1710 may output for transmission, on the first component carrier, a second PDCCH including the second uplink grant, where the second uplink grant allocates the second set of resources on the second component carrier for a retransmission of the transport block.
  • the grant manager 1710 may configure a DCI in one or more physical downlink control channels (PDCCHs) corresponding to the first uplink grant and the second uplink grant, the DCI including an indication that the first uplink grant and the second uplink grant are associated with the shared HARQ process.
  • PDCCHs physical downlink control channels
  • the resource manager 1715 may output the transport block for transmission on the first set of resources on the first component carrier and transmitting the transport block on the second set of resources on the second component carrier. In some examples, the resource manager 1715 may obtain the transport block received by the base station over the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block.
  • the resource manager 1715 may output for transmission, based on the second downlink grant, the retransmission of the transport block on the second component carrier. In some examples, the resource manager 1715 may obtain, based on the second uplink grant, the retransmission of the transport block received by the base station on the second component carrier.
  • the HARQ feedback manager 1720 may obtain HARQ-ACK feedback received from the UE for the transport block. In some examples, the HARQ feedback manager 1720 may output, for transmission to the UE, HARQ-ACK feedback for the transport block received from the UE. In some examples, the HARQ feedback manager 1720 may obtain a first HARQ-ACK message for the first component carrier received by the base station on one of the first component carrier or the second component carrier.
  • the HARQ feedback manager 1720 may obtain a second HARQ-ACK message for the second component carrier received by the base station on the one of the first component carrier or the second component carrier, where the second HARQ-ACK message is based on a combination of the transport block transmitted on the first component carrier and the transport block transmitted on the second component carrier.
  • the HARQ feedback manager 1720 may obtain from the UE a single HARQ-ACK message for the first component carrier and the second component carrier, where the HARQ-ACK message is based on the combining. In some examples, the HARQ feedback manager 1720 may output a first HARQ-ACK message for the first component carrier received by the base station on one of the first component carrier or the second component carrier. In some examples, the HARQ feedback manager 1720 may output a second HARQ-ACK message for the second component carrier for transmission to the UE on the one of the first component carrier or the second component carrier, where the second HARQ-ACK message is based on a combination of the transport block transmitted on the first component carrier and the transport block transmitted on the second component carrier.
  • the transport block is associated with a low latency communication type of traffic corresponding to one or more timing constraints, and obtaining the HARQ- ACK message and outputting the retransmission of the transport block on the second component carrier satisfies the timing constraints.
  • the shared HARQ process manager 1730 may configure a DCI in one or more physical downlink control channels corresponding to the first downlink grant and the second downlink grant, the DCI including an indication that the first downlink grant and the second downlink grant are associated with the shared HARQ process.
  • the shared HARQ process manager 1730 may output semi-static configuration information for transmission to the UE via higher layer signaling, the configuration information indicating that the first downlink grant and the second downlink grant are associated with a same transport block and a shared HARQ process.
  • the shared HARQ process manager 1730 may output semi-static configuration information for transmission to the UE via higher layer signaling, the configuration information indicating that the first uplink grant and the second uplink grant are associated with a same transport block and a shared HARQ process.
  • the first component carrier is on frequency range 1 (FR1) and the second component carrier is on frequency range 2 (FR2) with a different numerology from the first component carrier.
  • the RNTI manager 1735 may encode the first PDCCH and the second PDCCH based on a dedicated radio network temporary identifier (RNTI) value, where the first PDCCH and the second PDCCH share a common transport block size (TBS) value and a common HARQ process number value.
  • RNTI radio network temporary identifier
  • the BWP manager 1740 may configure the first downlink grant and the second downlink grant to be associated with the same transport block and a shared HARQ process based on one or more bandwidth part (BWP) configuration information.
  • BWP bandwidth part
  • the BWP manager 1740 may configure the first uplink grant and the second uplink grant to be associated with the same transport block and a shared HARQ process based on one or more bandwidth part (BWP) configuration information.
  • BWP bandwidth part
  • the combiner 1745 may output a single HARQ-ACK message for the first component carrier and the second component carrier, where the HARQ-ACK message is based on the combining.
  • FIG. 18 shows a diagram of a system 1800 including a device 1805 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the device 1805 may be an example of or include the components of device 1505, device 1605, or a base station 105 as described herein.
  • the device 1805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager 1810, a network communications manager 1815, a transceiver 1820, an antenna 1825, memory 1830, a processor 1840, and an inter-station communications manager 1845. These components may be in electronic communication via one or more buses (e.g., bus 1850) .
  • buses e.g., bus 1850
  • the communications manager 1810 may output for transmission, by the base station to a UE, a first downlink grant for a first set of resources on a first component carrier and a second downlink grant for a second set of resources on a second component carrier, where the first downlink grant and the second downlink grant are associated with a same transport block and a shared feedback HARQ process, output the transport block for transmission on the first set of resources on the first component carrier and transmitting the transport block on the second set of resources on the second component carrier, and obtain HARQ-ACK feedback received from the UE for the transport block.
  • the communications manager 1810 may also output for transmission to a UE, a first uplink grant for a first set of resources on a first component carrier and a second uplink grant for a second set of resources on a second component carrier, where the first uplink grant and the second uplink grant are associated with a same transport block and a shared feedback HARQ process, obtain the transport block received by the base station over the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block, and output, for transmission to the UE, HARQ-ACK feedback for the transport block received from the UE.
  • the network communications manager 1815 may manage communications with the core network (e.g., via one or more wired backhaul links) .
  • the network communications manager 1815 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the transceiver 1820 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1820 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1820 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1825. However, in some cases the device may have more than one antenna 1825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 1830 may include RAM, ROM, or a combination thereof.
  • the memory 1830 may store computer-readable code 1835 including instructions that, when executed by a processor (e.g., the processor 1840) cause the device to perform various functions described herein.
  • a processor e.g., the processor 1840
  • the memory 1830 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the processor 1840 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 1840 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into processor 1840.
  • the processor 1840 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1830) to cause the device 1805 to perform various functions (e.g., functions or tasks supporting HARQ process sharing for carrier aggregation) .
  • the inter-station communications manager 1845 may manage communications with other base station 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. For example, the inter-station communications manager 1845 may coordinate scheduling for transmissions to UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communications manager 1845 may provide an X2 interface within an LTE/LTE-Awireless communication network technology to provide communication between base stations 105.
  • the code 1835 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 1835 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1835 may not be directly executable by the processor 1840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • FIG. 19 shows a flowchart illustrating a method 1900 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the operations of method 1900 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1900 may be performed by a communications manager as described with reference to FIGs. 11 through 14.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally, or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may obtain a first downlink grant received from a base station by the UE and a second downlink grant received from the base station by the UE, the first downlink grant for a first set of resources on a first component carrier and the second downlink grant for a second set of resources on a second component carrier.
  • the operations of 1905 may be performed according to the methods described herein. In some examples, aspects of the operations of 1905 may be performed by a grant manager as described with reference to FIGs. 11 through 14.
  • the UE may determine that the first downlink grant and the second downlink grant are associated with a same transport block and a shared HARQ process.
  • the operations of 1910 may be performed according to the methods described herein. In some examples, aspects of the operations of 1910 may be performed by a shared HARQ process manager as described with reference to FIGs. 11 through 14.
  • the UE may monitor the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block.
  • the operations of 1915 may be performed according to the methods described herein. In some examples, aspects of the operations of 1915 may be performed by a monitoring manager as described with reference to FIGs. 11 through 14.
  • the UE may output, for transmission to the base station, HARQ-ACK feedback for the transport block based on the monitoring and the determining.
  • the operations of 1920 may be performed according to the methods described herein. In some examples, aspects of the operations of 1920 may be performed by a HARQ feedback manager as described with reference to FIGs. 11 through 14.
  • FIG. 20 shows a flowchart illustrating a method 2000 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the operations of method 2000 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 2000 may be performed by a communications manager as described with reference to FIGs. 15 through 18.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally, or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.
  • the base station may output for transmission to a UE, a first downlink grant for a first set of resources on a first component carrier and a second downlink grant for a second set of resources on a second component carrier, where the first downlink grant and the second downlink grant are associated with a same transport block and a shared feedback HARQ process.
  • the operations of 2005 may be performed according to the methods described herein. In some examples, aspects of the operations of 2005 may be performed by a grant manager as described with reference to FIGs. 15 through 18.
  • the base station may output the transport block for transmission on the first set of resources on the first component carrier and transmitting the transport block on the second set of resources on the second component carrier.
  • the operations of 2010 may be performed according to the methods described herein. In some examples, aspects of the operations of 2010 may be performed by a resource manager as described with reference to FIGs. 15 through 18.
  • the base station may obtain HARQ-ACK feedback received from the UE for the transport block.
  • the operations of 2015 may be performed according to the methods described herein. In some examples, aspects of the operations of 2015 may be performed by a HARQ feedback manager as described with reference to FIGs. 15 through 18.
  • FIG. 21 shows a flowchart illustrating a method 2100 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the operations of method 2100 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 2100 may be performed by a communications manager as described with reference to FIGs. 11 through 14.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally, or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may obtain a first uplink grant received from a base station and a second uplink grant received from the base station by the UE, the first uplink grant for a first set of resources on a first component carrier and the second uplink grant for a second set of resources on a second component carrier.
  • the operations of 2105 may be performed according to the methods described herein. In some examples, aspects of the operations of 2105 may be performed by a grant manager as described with reference to FIGs. 11 through 14.
  • the UE may determine that the first uplink grant and the second uplink grant are associated with a same transport block and a shared HARQ process.
  • the operations of 2110 may be performed according to the methods described herein. In some examples, aspects of the operations of 2110 may be performed by a shared HARQ process manager as described with reference to FIGs. 11 through 14.
  • the UE may output the transport block for transmission over the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block.
  • the operations of 2115 may be performed according to the methods described herein. In some examples, aspects of the operations of 2115 may be performed by a resource manager as described with reference to FIGs. 11 through 14.
  • the UE may obtain HARQ-ACK feedback for the transport block received from the base station at the UE, based on the outputting and the determining.
  • the operations of 2120 may be performed according to the methods described herein. In some examples, aspects of the operations of 2120 may be performed by a HARQ feedback manager as described with reference to FIGs. 11 through 14.
  • FIG. 22 shows a flowchart illustrating a method 2200 that supports HARQ process sharing for carrier aggregation in accordance with aspects of the present disclosure.
  • the operations of method 2200 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 2200 may be performed by a communications manager as described with reference to FIGs. 15 through 18.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally, or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.
  • the base station may output for transmission to a UE, a first uplink grant for a first set of resources on a first component carrier and a second uplink grant for a second set of resources on a second component carrier, where the first uplink grant and the second uplink grant are associated with a same transport block and a shared feedback HARQ process.
  • the operations of 2205 may be performed according to the methods described herein. In some examples, aspects of the operations of 2205 may be performed by a grant manager as described with reference to FIGs. 15 through 18.
  • the base station may obtain the transport block received over the first set of resources on the first component carrier and the second set of resources on the second component carrier for the transport block.
  • the operations of 2210 may be performed according to the methods described herein. In some examples, aspects of the operations of 2210 may be performed by a resource manager as described with reference to FIGs. 15 through 18.
  • the base station may output, for transmission to the UE, HARQ-ACK feedback for the transport block received from the UE.
  • the operations of 2215 may be performed according to the methods described herein. In some examples, aspects of the operations of 2215 may be performed by a HARQ feedback manager as described with reference to FIGs. 15 through 18.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • a CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA) , etc.
  • CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
  • IS-2000 Releases may be commonly referred to as CDMA2000 1X, 1X, etc.
  • IS-856 TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD) , etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • a TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB) , Evolved UTRA (E-UTRA) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, etc.
  • UMB Ultra Mobile Broadband
  • E-UTRA Evolved UTRA
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS) .
  • LTE, LTE-A, and LTE-A Pro are releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from the organization named “3rd Generation Partnership Project” (3GP
  • CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • 3GPP2 3rd Generation Partnership Project 2
  • the techniques described herein may be used for the systems and radio technologies mentioned herein as well as other systems and radio technologies. While aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR applications.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a small cell may be associated with a lower-powered base station, as compared with a macro cell, and a small cell may operate in the same or different (e.g., licensed, unlicensed, etc. ) frequency bands as macro cells.
  • Small cells may include pico cells, femto cells, and micro cells according to various examples.
  • a pico cell for example, may cover a small geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a femto cell may also cover a small geographic area (e.g., a home) and may provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG) , UEs for users in the home, and the like) .
  • An eNB for a macro cell may be referred to as a macro eNB.
  • An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB.
  • An eNB may support one or multiple (e.g., two, three, four, and the like) cells, and may also support communications using one or multiple component carriers.
  • the wireless communications systems described herein may support synchronous or asynchronous operation.
  • the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time.
  • the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.
  • non-transitory computer-readable media may include random-access memory (RAM) , read-only memory (ROM) , electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • flash memory compact disk (CD) ROM or other optical disk storage
  • magnetic disk storage or other magnetic storage devices
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

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

Abstract

L'invention concerne des procédés, des systèmes, et des dispositifs destinés aux communications sans fil. Globalement, un équipement utilisateur (UE) peut recevoir une première autorisation de liaison descendante et une seconde autorisation de liaison descendante. La première autorisation de liaison descendante peut indiquer un premier ensemble de ressources sur une première porteuse composante, et la seconde autorisation de liaison descendante peut indiquer un second ensemble de ressources sur une seconde porteuse composante. L'UE peut déterminer que la première autorisation de liaison descendante et la seconde autorisation de liaison descendante sont associées au même bloc de transport et à une procédure HARQ partagée. L'UE peut surveiller les premier et second ensembles de ressources indiqués sur les première et seconde porteuses composantes respectivement, et peut envoyer une rétroaction HARQ pour le bloc de transport sur la base de la surveillance des ensembles indiqués de ressources et de la procédure HARQ partagée.
PCT/CN2019/074400 2019-02-01 2019-02-01 Partage de procédure harq pour agrégation de porteuses WO2020155097A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/074400 WO2020155097A1 (fr) 2019-02-01 2019-02-01 Partage de procédure harq pour agrégation de porteuses

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/074400 WO2020155097A1 (fr) 2019-02-01 2019-02-01 Partage de procédure harq pour agrégation de porteuses

Publications (1)

Publication Number Publication Date
WO2020155097A1 true WO2020155097A1 (fr) 2020-08-06

Family

ID=71841375

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/074400 WO2020155097A1 (fr) 2019-02-01 2019-02-01 Partage de procédure harq pour agrégation de porteuses

Country Status (1)

Country Link
WO (1) WO2020155097A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022056745A1 (fr) * 2020-09-16 2022-03-24 北京小米移动软件有限公司 Procédé et dispositif de transmission d'informations, et support de stockage
GB2615907A (en) * 2021-01-18 2023-08-23 Nokia Technologies Oy Configured grant

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017132842A1 (fr) * 2016-02-02 2017-08-10 Nec Corporation Procédé et appareil pour des communications avec agrégation de porteuses
WO2018082506A1 (fr) * 2016-11-04 2018-05-11 华为技术有限公司 Procédé de génération de livre de codes de demande de répétition automatique hybride (harq) et dispositif associé
WO2018157406A1 (fr) * 2017-03-03 2018-09-07 广东欧珀移动通信有限公司 Procédé de transmission de données, dispositif terminal, et dispositif de réseau

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017132842A1 (fr) * 2016-02-02 2017-08-10 Nec Corporation Procédé et appareil pour des communications avec agrégation de porteuses
WO2018082506A1 (fr) * 2016-11-04 2018-05-11 华为技术有限公司 Procédé de génération de livre de codes de demande de répétition automatique hybride (harq) et dispositif associé
WO2018157406A1 (fr) * 2017-03-03 2018-09-07 广东欧珀移动通信有限公司 Procédé de transmission de données, dispositif terminal, et dispositif de réseau

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022056745A1 (fr) * 2020-09-16 2022-03-24 北京小米移动软件有限公司 Procédé et dispositif de transmission d'informations, et support de stockage
CN114556844A (zh) * 2020-09-16 2022-05-27 北京小米移动软件有限公司 信息传输方法及装置、存储介质
GB2615907A (en) * 2021-01-18 2023-08-23 Nokia Technologies Oy Configured grant

Similar Documents

Publication Publication Date Title
US11963144B2 (en) Feedback design for multi-transmission reception point transmission
US11109380B2 (en) Uplink control channel beam switch procedure
US11546858B2 (en) Power control techniques for uplink control information transmissions in wireless communications
US11240839B2 (en) Feedback transmissions using uplink shared channel
EP3815285A1 (fr) Conception d'association d'un signal de référence et d'un canal de commande de liaison montante
WO2020198467A1 (fr) Multiplexage de livres de codes générés pour des transmissions ayant différents types de services
WO2021007057A1 (fr) Fiabilité de transmission de données avec de multiples signaux d'informations de commande de liaison descendante
US11283548B2 (en) Physical downlink control channel retransmission for ultra-reliable low-latency communications
US20210377917A1 (en) Soft-combining for control channels
WO2020167523A2 (fr) Techniques de rétroaction d'accusé de réception dans des communications sans fils
WO2020028014A1 (fr) Périodes d'expiration pour des communications à faible latence
EP4038981A1 (fr) Déclenchement de modes d'économie d'énergie avec planificiation d'informations de commande de liaison descendante
WO2020252134A1 (fr) Regroupement de paquets de données permettant la perception du trafic dans une nouvelle radio
WO2021015885A1 (fr) Transmission conditionnelle d'accusé de réception négatif dans une communication à composantes porteuses multiples
WO2020142590A1 (fr) Commutation d'émetteur unique pour double connectivité
WO2020006059A1 (fr) Conception d'association d'un signal de référence et d'un canal de commande de liaison montante
WO2020155097A1 (fr) Partage de procédure harq pour agrégation de porteuses
EP4008076A1 (fr) Rétroaction basée sur un lot dans une nouvelle radio
EP3738258B1 (fr) Transmission de signaux de type uci en utilisant une technique de superposition
EP3994923A1 (fr) Commande de puissance basée sur une direction semi-statique pour une double connectivité
WO2021012247A1 (fr) Annulation de préemption de liaison montante avec des répétitions de canal partagé de liaison montante

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: 19912341

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: 19912341

Country of ref document: EP

Kind code of ref document: A1