WO2022251067A1 - Techniques de planification pour une transmission de rétroaction de liaison montante - Google Patents

Techniques de planification pour une transmission de rétroaction de liaison montante Download PDF

Info

Publication number
WO2022251067A1
WO2022251067A1 PCT/US2022/030306 US2022030306W WO2022251067A1 WO 2022251067 A1 WO2022251067 A1 WO 2022251067A1 US 2022030306 W US2022030306 W US 2022030306W WO 2022251067 A1 WO2022251067 A1 WO 2022251067A1
Authority
WO
WIPO (PCT)
Prior art keywords
time gap
message
request
uplink
downlink
Prior art date
Application number
PCT/US2022/030306
Other languages
English (en)
Inventor
Konstantinos Dimou
Seyedkianoush HOSSEINI
Yan Zhou
Tao Luo
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
Publication of WO2022251067A1 publication Critical patent/WO2022251067A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • Patent Application No. 20210100344 by DIMOU et al. entitled “TECHNIQUES FOR SCHEDULING AN UPLINK FEEDBACK TRANSMISSION,” filed May 25, 2021, assigned to the assignee hereof.
  • the following relates to wireless communications, including techniques for scheduling an uplink feedback transmission.
  • 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 one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE).
  • UE user equipment
  • a base station may transmit, to a UE, a physical downlink control channel (PDCCH) message including downlink control information (DCI).
  • the DCI may indicate information, such as scheduling information, for one or more uplink transmissions by the UE, such as a physical uplink control channel (PUCCH) transmission and/or a physical uplink shared channel (PUSCH) transmission.
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for scheduling an uplink feedback transmission.
  • a base station may schedule a UE to transmit one or more uplink messages (e.g., a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH)) based on receipt of an associated downlink message (e.g., a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), respectively).
  • the UE may transmit a message to the base station requesting a time gap value between a downlink message and associated uplink message.
  • the base station may schedule one or more uplink messages based on the requested time gap value. For example, a UE may transmit a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink transmission.
  • the request may include a requested time gap value provided by the UE for consideration by the base station in specifying the time gap.
  • the UE may receive, from the base station and in response to the request, an indication of the time gap.
  • the UE may transmit the uplink message (e.g., a PUCCH, a PUSCH) based on receipt of the downlink message (e.g., a PDSCH, a PDCCH, respectively) and in accordance with the time gap.
  • the uplink message e.g., a PUCCH, a PUSCH
  • the downlink message e.g., a PDSCH, a PDCCH, respectively
  • a method for wireless communications at a UE may include transmitting a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap, receiving, from the base station and in response to the request, an indication of the time gap, and transmitting the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • An apparatus for wireless communications is described.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to transmit a request for a base station to specify to a UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the EE for consideration by the base station in specifying the time gap, receive, from the base station and in response to the request, an indication of the time gap, and transmit the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • the apparatus may include means for transmitting a request for a base station to specify to a EE a time gap to be applied by the EE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the EE for consideration by the base station in specifying the time gap, means for receiving, from the base station and in response to the request, an indication of the time gap, and means for transmitting the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by a processor to transmit a request for a base station to specify to a EE a time gap to be applied by the EE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the EE for consideration by the base station in specifying the time gap, receive, from the base station and in response to the request, an indication of the time gap, and transmit the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • transmitting the request may include operations, features, means, or instructions for transmitting the requested time gap value for the time gap which may be between receipt of a downlink shared channel and transmission of feedback via an uplink control channel, where the downlink message may be the downlink shared channel and the uplink message may be the uplink control channel.
  • transmitting the request may include operations, features, means, or instructions for transmitting the requested time gap value for the time gap which may be between receipt of a downlink control channel and transmission of an uplink shared channel, where the downlink message may be the downlink control channel and the uplink message may be the uplink shared channel.
  • transmitting the request may include operations, features, means, or instructions for including in the request that the base station specify to the UE a set of multiple time gaps to be applied by the UE between receipt of a corresponding set of multiple downlink messages from the base station and transmission of the uplink message, where the uplink message includes multiplexed content associated with each of the set of multiple downlink messages, the time gap being one of the set of multiple time gaps and the downlink message being one of the set of multiple downlink messages.
  • transmitting the request may include operations, features, means, or instructions for transmitting the requested time gap value during a radio resource control connection establishment procedure.
  • transmitting the request may include operations, features, means, or instructions for transmitting the requested time gap value via a random access preamble message, the requested time gap value indicated by a random access channel signature.
  • transmitting the request may include operations, features, means, or instructions for transmitting the requested time gap value via an information element in a radio resource control connection setup message.
  • transmitting the request may include operations, features, means, or instructions for transmitting the requested time gap value via a radio resource control setup complete message.
  • transmitting the request may include operations, features, means, or instructions for transmitting the requested time gap value during a radio resource control session.
  • transmitting the request may include operations, features, means, or instructions for transmitting the requested time gap value via a radio resource control message, a medium access control element message, an uplink control information message, or a combination thereof.
  • transmitting the request may include operations, features, means, or instructions for transmitting the requested time gap value via a scheduling request included in an uplink control information message based on an uplink control channel format.
  • transmitting the request may include operations, features, means, or instructions for transmitting a first set of bits of the requested time gap value via an uplink control information message and a second set of bits of the requested time gap value in accordance with a cyclic shift based on an uplink control channel format.
  • the method, apparatuses, and non-transitory computer- readable medium described herein may further include operations, features, means, or instructions for determining the requested time gap value based on a minimum time gap value, a frequency range, a processing capability, a subcarrier spacing, or a combination thereof.
  • the uplink message includes hybrid automatic repeat request feedback associated with the downlink message.
  • a method for wireless communications at a base station may include receiving, from a UE, a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap, transmitting, to the UE and in response to the request, an indication of the time gap, and receiving the uplink message based on transmission of the downlink message and in accordance with the time gap.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to receive, from a UE, a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap, transmit, to the UE and in response to the request, an indication of the time gap, and receive the uplink message based on transmission of the downlink message and in accordance with the time gap.
  • the apparatus may include means for receiving, from a UE, a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap, means for transmitting, to the UE and in response to the request, an indication of the time gap, and means for receiving the uplink message based on transmission of the downlink message and in accordance with the time gap.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by a processor to receive, from a UE, a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap, transmit, to the UE and in response to the request, an indication of the time gap, and receive the uplink message based on transmission of the downlink message and in accordance with the time gap.
  • receiving the request may include operations, features, means, or instructions for receiving the requested time gap value for the time gap which may be between receipt of a downlink shared channel and transmission of feedback via an uplink control channel, where the downlink message may be the downlink shared channel and the uplink message may be the uplink control channel.
  • receiving the request may include operations, features, means, or instructions for receiving the requested time gap value for the time gap which may be between receipt of a downlink control channel and transmission of an uplink shared channel, where the downlink message may be the downlink control channel and the uplink message may be the uplink shared channel.
  • receiving the request may include operations, features, means, or instructions for identifying in the request an indication that the base station specify to the UE a set of multiple time gaps to be applied by the UE between receipt of a corresponding set of multiple downlink messages from the base station and transmission of the uplink message, where the uplink message includes multiplexed content associated with each of the set of multiple downlink messages, the time gap being one of the set of multiple time gaps and the downlink message being one of the set of multiple downlink messages.
  • receiving the request may include operations, features, means, or instructions for receiving the requested time gap value during a radio resource control connection establishment procedure.
  • receiving the request may include operations, features, means, or instructions for receiving the requested time gap value via a random access preamble message, the requested time gap value indicated by a random access channel signature.
  • receiving the request may include operations, features, means, or instructions for receiving the requested time gap value via an information element in a radio resource control connection setup message.
  • receiving the request may include operations, features, means, or instructions for receiving the requested time gap value via a radio resource control setup complete message.
  • receiving the request may include operations, features, means, or instructions for receiving the requested time gap value during a radio resource control session.
  • receiving the request may include operations, features, means, or instructions for receiving the requested time gap value via a radio resource control message, a medium access control element message, an uplink control information message, or a combination thereof.
  • receiving the request may include operations, features, means, or instructions for receiving the requested time gap value via a scheduling request included in an uplink control information message based on an uplink control channel format.
  • receiving the request may include operations, features, means, or instructions for receiving a first set of bits of the requested time gap value via an uplink control information message and a second set of bits of the requested time gap value in accordance with a cyclic shift based on an uplink control channel format.
  • the uplink message includes hybrid automatic repeat request feedback associated with the downlink message.
  • FIG. 1 illustrates an example of a wireless communications system that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • FIG. 2 illustrates an example of a wireless communications system that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • FIGs. 3 A and 3B illustrate examples of communication timelines that support techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example of a process flow that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • FIGs. 5 and 6 show block diagrams of devices that support techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • FIG. 7 shows a block diagram of a communications manager that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • FIG. 8 shows a diagram of a system including a device that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • FIGs. 9 and 10 show block diagrams of devices that support techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • FIG. 11 shows a block diagram of a communications manager that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • FIG. 12 shows a diagram of a system including a device that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • FIGs. 13 through 16 show flowcharts illustrating methods that support techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • a base station may transmit, to a UE, a physical downlink control channel (PDCCH) message including downlink control information (DCI).
  • the DCI may indicate information for an associated physical downlink shared channel (PDSCH) and/or information for an uplink transmission by the UE, such as a physical uplink control channel (PUCCH) transmission and/or a physical uplink shared channel (PUSCH) transmission.
  • PDSCH physical downlink shared channel
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • scheduling information e.g., a K1 value, K2 value, time resources, frequency resources.
  • the DCI may schedule a PDSCH, and in this case, the DCI may also indicate a K1 value (e.g., a PDSCH-to-hybrid automatic repeat request (HARQ) value) which may define a time interval between receipt of the PDSCH and transmission, by the UE, of feedback pertaining to the PDSCH (e.g., included in a PUCCH).
  • the DCI may schedule a PUSCH transmission, and in this case, the DCI may also indicate a K2 value (e.g., a PUSCH Preparation Time value) which may define a time interval between receipt of the DCI (e.g., receipt of the PUCCH) and transmission of the PUSCH.
  • HARQ hybrid automatic repeat request
  • the UE may receive the DCI and identify the scheduling information (e.g., the type of uplink transmission, the location of the uplink transmission relative to a downlink transmission). Based on the scheduling information, the UE may determine uplink resources (e.g., time and/or frequency resources) allocated to the UE for transmission of the uplink signal (e.g., a PUCCH, or a PUSCH).
  • the scheduling information e.g., the type of uplink transmission, the location of the uplink transmission relative to a downlink transmission.
  • the UE may determine uplink resources (e.g., time and/or frequency resources) allocated to the UE for transmission of the uplink signal (e.g., a PUCCH, or a PUSCH).
  • the UE may receive a first DCI including scheduling information for a first uplink signal, and the UE may receive a second DCI including scheduling information for a second uplink signal.
  • the UE may determine that the first uplink signal and the second uplink signal are allocated to the same time and/or frequency resources (e.g., the same one or more symbols, slots, etc.). The UE may determine whether the UE is allocated with enough resources to multiplex and transmit the first and second uplink signals in the same resource allocation. If the UE is not configured with enough resources, the UE may refrain from transmitting (e.g., drop) one of the uplink signals based on the resource limitation.
  • the UE may determine which uplink signal to drop based on priority.
  • the first uplink signal may be a low priority (e.g., lower priority) transmission and the second uplink signal may be a high priority (e.g., high priority, such as ultra reliable low-latency communications (URLLC)) transmission. Accordingly, the UE may refrain from transmitting the first uplink signal in favor of the second uplink signal.
  • the first uplink signal may be a low priority (e.g., lower priority) transmission and the second uplink signal may be a high priority (e.g., high priority, such as ultra reliable low-latency communications (URLLC)) transmission.
  • URLLC ultra reliable low-latency communications
  • a UE may request that the base station schedule an uplink transmission (e.g., a PUCCH, a PUSCH) after a certain duration following an associated downlink transmission (e.g., a PDCCH, a PDSCH). For example, the UE may transmit a request for a time gap value between a downlink transmission and associated uplink transmission, where, in some cases, the UE may transmit a request for a K1 value, or a K2 value, or both. In some cases, the UE may request the time gap value so that each uplink transmission that the UE is configured to transmit is scheduled in separate resources (e.g., slots, symbols).
  • the UE may request the time gap value so that multiple uplink transmissions are scheduled in the same one or more resources such that the UE may multiplex the multiple uplink transmissions in the case that the UE is configured with sufficient resources.
  • the UE may transmit the requested time gap value during a radio resource control (RRC) establishment procedure, or during an RRC session.
  • the UE may transmit the request in RRC signaling, medium access control (MAC) control element (MAC-CE) signaling, uplink control information (UCI), or a combination thereof.
  • RRC radio resource control
  • MAC-CE medium access control element
  • UCI uplink control information
  • Particular aspects of the subject matter described herein may be implemented to realize one or more advantages.
  • the described techniques may support improvements in uplink communications by improving reliability and efficiency, among other advantages.
  • supported techniques may include improved network operations and, in some examples, may promote network efficiencies, among other benefits.
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspects are then described with reference to communication timelines and a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to techniques for scheduling an uplink feedback transmission.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more base stations 105, one or more 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-A Pro
  • NR New Radio
  • the wireless communications system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low- complexity devices, or any combination thereof.
  • ultra-reliable e.g., mission critical
  • the base stations 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may be devices in different forms or having different capabilities.
  • the base stations 105 and the UEs 115 may wirelessly communicate via one or more communication links 125.
  • Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base station 105 may establish one or more communication links 125.
  • the coverage area 110 may be an example of a geographic area over which a base station 105 and a UE 115 may support the communication of signals according to one or more radio access technologies.
  • the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
  • the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115, the base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as shown in FIG. 1.
  • network equipment e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment
  • the base stations 105 may communicate with the core network 130, or with one another, or both.
  • the base stations 105 may interface with the core network 130 through one or more backhaul links 120 (e.g., via an SI, N2, N3, or other interface).
  • the base stations 105 may communicate with one another over the backhaul links 120 (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), or both.
  • the backhaul links 120 may be or include one or more wireless links.
  • One or more of the base stations 105 described herein may include or may be referred to by a person having ordinary skill 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 a giga-NodeB (either of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or other suitable terminology.
  • a base transceiver station a radio base station
  • an access point a radio transceiver
  • a NodeB an eNodeB (eNB)
  • eNB eNodeB
  • next-generation NodeB or a giga-NodeB either of which may be referred to as a gNB
  • gNB giga-NodeB
  • a UE 115 may include or may 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, among other examples.
  • a UE 115 may also include or may be referred to as 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 include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the base stations 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the base stations 105 may wirelessly communicate with one another via one or more communication links 125 over one or more carriers.
  • carrier may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links 125.
  • a carrier used for a communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR).
  • Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling.
  • the wireless communications system 100 may support communication with a UE 115 using 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 frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (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
  • 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 coding rate of the modulation scheme, or both).
  • 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 or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE 115.
  • Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).
  • SFN system frame number
  • Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots.
  • each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing.
  • Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period).
  • a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI).
  • TTI duration e.g., the number of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).
  • 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 one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM- FDM techniques.
  • a control region e.g., a control resource set (CORESET)
  • CORESET control resource set
  • One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to a number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
  • 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, but the different geographic coverage areas 110 may be supported by the same base station 105.
  • the overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105.
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.
  • the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
  • the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications.
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions).
  • Ultra-reliable communications may include private communication or group communication and may be supported by one or more mission critical services such as mission critical push-to-talk (MCPTT), mission critical video (MCVideo), or mission critical data (MCData).
  • MCPTT mission critical push-to-talk
  • MCVideo mission critical video
  • MCData mission critical data
  • Support for mission critical functions may include prioritization of services, and mission critical services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, mission critical, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may also be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol).
  • D2D device-to-device
  • P2P peer-to-peer
  • One or more 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 the 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. In other cases, D2D communications are carried out between the UEs 115 without the involvement of a base station 105.
  • 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) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)).
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the base stations 105 associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to IP services 150 for one or more network operators.
  • the IP services 150 may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet- Switched Streaming Service.
  • IMS IP Multimedia Subsystem
  • Packet- Switched Streaming Service Packet- Switched Streaming Service
  • Some of the network devices may include subcomponents such as an access network entity 140, which may be an example of an access node controller (ANC).
  • Each access network entity 140 may communicate with the UEs 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs).
  • Each access network transmission entity 145 may include one or more antenna panels.
  • various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station 105).
  • the 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 because the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors.
  • the transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) 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
  • the wireless communications system 100 may utilize both licensed and unlicensed radio frequency spectrum bands.
  • the 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 industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the base stations 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • 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, P2P transmissions, or D2D transmissions, among other examples.
  • a base station 105 or a 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.
  • the antennas of a base station 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, 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.
  • an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port.
  • 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, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a 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 some 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 amplitude offsets, phase offsets, or both to signals carried via 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 UE 115 and a base station 105 may communicate.
  • the base station 105 may schedule the UE 115 to transmit one or more uplink signals (e.g., PUCCH, PUSCH) based on an associated downlink signal (e.g., PDSCH, PDCCH, respectively).
  • the UE 115 may transmit a message to the base station 105 requesting a time gap value between a downlink transmission and associated uplink transmission.
  • the base station 105 may schedule one or more uplink transmissions based on the requested time gap value.
  • a UE 115 may transmit a request for a base station 105 to specify to the UE 115 a time gap to be applied by the UE 115 between receipt of a downlink transmission from the base station 105 and transmission of an uplink transmission that is associated with the downlink transmission.
  • the request may include a requested time gap value provided by the UE 115 for consideration by the base station 105 in specifying the time gap.
  • the UE 115 may receive, from the base station 105 and in response to the request, an indication of the time gap.
  • the UE 115 may transmit the uplink transmission (e.g., an uplink control channel, an uplink shared channel) based on receipt of the downlink transmission (e.g., a downlink shared channel, a downlink control channel, respectively) and in accordance with the time gap.
  • the uplink transmission e.g., an uplink control channel, an uplink shared channel
  • the downlink transmission e.g., a downlink shared channel, a downlink control channel, respectively
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the wireless communications system 200 may include base station 105-a and UE 115-a, which may be examples of a base station 105 and a UE 115 as described with reference to FIG. 1.
  • Base station 105-a may serve a geographic coverage area 110-a.
  • UE 115-a may implement a time gap value request procedure for scheduling one or more uplink transmissions.
  • other wireless devices such as base station 105-a, may participate in the same or similar time gap value request procedure.
  • a UE 115 may communicate (e.g., receive and/or transmit control and/or data information) with a base station 105-a.
  • UE 115-a may transmit one or more uplink transmissions to base station 105-a via communication link 205-a (e.g., an uplink communications link), and base station 105-a may transmit one or more downlink transmissions to UE 115-a via communications link 205-b (e.g., a downlink communications link).
  • base station 105-a may transmit information to UE 115-a indicating one or more scheduled uplink transmissions to be transmitted by UE 115-a.
  • a base station 105 may transmit, to a UE 115, a downlink control message, such as a PDCCH, which may include DCI.
  • the DCI may schedule a PDSCH.
  • the DCI may also indicate a K1 value which may define a time interval between receipt of a PDSCH and transmission, by the UE 115, of feedback pertaining to the PDSCH.
  • the K1 value may define an offset (e.g., a number of slots or symbols, or a number of seconds, milliseconds, etc.) from the PDSCH to an associated PUCCH.
  • the UE 115 may receive the DCI, and identify the scheduled PDSCH.
  • the UE 115 may attempt to receive the scheduled PDSCH and configure a feedback message (e.g., HARQ feedback) indicating whether the UE 115 successfully received and decoded the scheduled PDSCH.
  • the UE 115 may transmit the feedback message in a PUCCH accordance with the indicated K1 value.
  • the DCI may schedule a PUSCH transmission.
  • the DCI may also indicate a K2 value which may define a time interval between receipt of the DCI and transmission of the PUSCH.
  • the K2 value may define an offset (e.g., a number of slots or symbols, or a number of seconds, milliseconds, etc.) from the PDCCH (e.g., DCI) to an associated PUSCH.
  • the UE may receive the DCI, and identify the scheduled PUSCH.
  • the UE 115 may transmit the scheduled PUSCH in accordance with indicated K2 value.
  • the base station 105 may (e.g., inadvertently) schedule multiple uplink transmissions (e.g., PUSCHs, PUCCHs, or both) to occur at the same time, as described with reference to FIG. 3 A.
  • multiple uplink transmissions e.g., PUSCHs, PUCCHs, or both
  • Such scenario may occur if the base station sends multiple DCIs, each scheduling an uplink transmission, and if the K1 values in the DCIs are different, or alternatively when the K2 values in the DCIs are different. Having different K1 values in different DCIs or different K2 values in different DCIs may result in multiple uplink transmissions being scheduled for the same resources. If, however, the resources are not sufficient for the multiply-scheduled uplink transmissions, then the UE 115 may drop one or more of the uplink transmissions.
  • UE 115-a may request values for K1 and/or K2 (e.g., a requested time gap).
  • UE 115-a may request one time gap value to be used for multiple uplink transmissions, in which case the multiple uplink transmissions may be transmitted in separate uplink resources (e.g., slots, symbols, TTIs).
  • UE 115-a may request multiple different time gap values so that the corresponding transmissions are either each directed to different uplink resources or to a same (e.g., sufficiently large) uplink resource.
  • K1 and/or K2 e.g., a requested time gap.
  • UE 115-a may determine the requested time gap value based on a minimum processing duration for UE 115-a.
  • the minimum processing capability may be equal to or based on a PDSCH processing capability of UE 115-a, subcarrier spacing, frequency range (e.g., LTE, FR2, FR4), a time difference between PDCCHs, or a combination thereof.
  • UE 115-a may request a time gap value such that the requested time gap value is less than the minimum processing time (e.g., minimum K1 or K2) plus a time difference between scheduled downlink transmissions that initiate the duration.
  • UE 115-a may determine the requested time gap value to be any value. In some implementations, UE 115-a may determine multiple time gap values, each associated with a consecutive downlink message (e.g., PDCCH, PDSCH), so that the UE may multiplex the uplink messages (e.g., PUSCH, PUCCH, respectively) associated with the consecutive downlink messages and transmit the multiplex uplink messages in a single uplink transmission.
  • a consecutive downlink message e.g., PDCCH, PDSCH
  • the uplink messages e.g., PUSCH, PUCCH, respectively
  • UE 115-a may determine one or more time gap values (e.g., one or more K1 values, one or more K2 values, or both), and UE 115-a may transmit one or more requested time gap value requests 210 to base station 105-a via communication link 205-a.
  • Base station 105-a may receive the one or more time gap value requests 210, and determine whether to implement the requested time gap values for scheduling or more uplink transmissions.
  • Base station 105-a may transmit a time gap indication 215 via communication link 205-b to UE 115-a, where the indicated time gap may or may not be equal to a requested time gap value.
  • UE 115-a may then transmit one or more uplink messages in accordance with the indicated time gap value.
  • FIGs. 3A and 3B illustrate examples of communication timelines 300, and 301, respectively, that support techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the communication timeline 300 may include base station 105-b and UE 115-b
  • communication timeline 301 may include base station 105-c and UE 115-c, which may be examples of base stations 105 and UEs 115 as described with reference to FIGs. 1 and 2.
  • UE 115-b and/or UE 115-c may implement a time gap value request procedure for scheduling one or more uplink transmissions.
  • other wireless devices such as base station 105-b and/or base station 105-c, may implement the same or similar time gap value request procedure.
  • a base station 105 may transmit information to a UE 115 indicating one or more scheduled uplink messages to be transmitted by the UE 115.
  • base station 105-b may transmit, to UE 115-b, a downlink control channel 310-a, such as a PDCCH, which may include DCI.
  • the DCI may schedule a downlink shared channel 315-a, such as a PDSCH.
  • UE 115-b may be configured to attempt to receive the downlink shared channel 315-a based on the DCI and may be configured to transmit an uplink control channel 320-a to base station 105-b that includes feedback information indicating whether UE 115-b successfully received and decoded the downlink shared channel 315-a.
  • the DCI may also indicate a K1 value which may define a time interval (e.g., a time gap 325) between receipt of a downlink shared channel 315-a and transmission, by UE 115-b, of feedback (e.g., via an uplink control channel 320-a) pertaining to the downlink shared channel 315-a.
  • the K1 value may define an offset (e.g., a number of slots or symbols, or a number of seconds, milliseconds, etc.) from the PDSCH to an associated PUCCH.
  • UE 115-b may receive downlink control channel 310-a in slot 305-a, which may include DCF
  • the DCI may indicate that a downlink shared channel 315-a in slot 305-a is scheduled and indicate a time gap 325-a (e.g., a K1 value).
  • UE 115-b may attempt to receive the scheduled downlink shared channel 315-a in slot 305-a and configure a feedback message (e.g., HARQ feedback) indicating whether UE 115-b successfully received and decoded the scheduled downlink shared channel 315-a.
  • UE 115-a may transmit the feedback message in an uplink control channel 320-a in slot 305-c in accordance with the indicated time gap 325-a.
  • base station 105-b may (e.g., inadvertently) schedule multiple uplink control channels 320-a to be transmitted in the same resources. Such scenario may occur if base station 105-b transmits multiple DCIs, each scheduling an uplink transmission, and if the time gaps 325 (e.g., K1 values) in the DCIs are different. Having different time gaps 325 in different DCIs may result in multiple uplink transmissions being scheduled for the same resources. For example, UE 115-b may receive downlink control channel 310-a in slot 305-a indicating scheduled downlink shared channel 315-a in slot 305-a and a time gap 325-a.
  • time gaps 325 e.g., K1 values
  • UE 115-b may receive downlink control channel 310-a in slot 305-b indicating scheduled downlink shared channel 315-a in slot 305-b and a time gap 325-b.
  • Time gap 325-a and 325-b may be different.
  • time gap 325-a may be equal to a minimum time gap (e.g., minimum K1 value) plus one slot
  • time gap 325-b may be equal to the minimum time gap value.
  • the uplink control channels associated with each are allocated to the same resource (e.g., the same one or more symbols in slot 305-c).
  • the time gap 325 may be determined based on priority of the associated uplink and/or downlink transmission.
  • downlink control channel 310-a in slot 305-a may schedule low priority (or relatively lower priority) transmissions (e.g., low priority downlink shared channel 315-a, low priority uplink control channel 320-a) and as such, may be associated with a time gap 325-a that is greater than the minimum time gap.
  • downlink control channel 310-a in slot 305-b may schedule high priority (or relatively higher priority) transmissions (e.g., high priority downlink shared channel 315-a, high priority uplink control channel 320-a) and as such, may be associated with a time gap 325-b that is equal to the minimum time gap.
  • UE 115-b may drop one or more of the uplink control channel transmissions.
  • the DCI received in slot 305-a may indicate allocated resources (e.g., time and/or frequency resources) for UE 115-b to transmit the associated uplink control channel 320-a on.
  • the DCI received in slot 305-b may indicate allocated resources (e.g., time and/or frequency resources) for UE 115-b to transmit the associated uplink control channel 320-a on.
  • UE 115-a may determine to drop one or both of the uplink control channels 320-a. For example, in the case the DCI in slot 305-a schedules low priority information and the DCI in slot 305-b schedules high priority information (e.g., URLLC), then UE 115-b may refrain from transmitting the uplink control channel 320-a associated with slot 305-a (e.g., the low priority uplink control channel 320-a) in favor of transmitting uplink control channel 320-a associated with slot 305-b (e.g., the high priority uplink control channel 320-a).
  • the uplink control channel 320-a associated with slot 305-a e.g., the low priority uplink control channel 320-a
  • uplink control channel 320-a associated with slot 305-b e.g., the high priority uplink control channel 320-a
  • DCI may schedule an uplink shared channel transmission.
  • the DCI may also indicate a K2 value which may define a time interval (e.g., a time gap 325) between receipt of the DCI and transmission of the uplink shared channel (e.g., PDSCH).
  • the K2 value may define an offset (e.g., a number of slots or symbols, or a number of seconds, milliseconds, etc.) from the downlink control channel to an associated uplink shared channel.
  • a UE 115 may receive the DCI in a downlink control channel, and identify the scheduled uplink shared channel. The UE 115 may transmit the scheduled uplink shared channel in accordance with indicated K2 value.
  • two different DCI messages may each schedule an uplink message (e.g., uplink shared channel transmission), where the multiple uplink messages may be scheduled to be transmitted in the same one or more resources (e.g., same one or more time resource such as symbols, slots, etc. and frequency resources) in accordance with two different time gaps 325.
  • the UE 115 may not be configured with enough resources to transmit both uplink messages in the same one or more resources and as such, the UE 115 may refrain from transmitting (e.g., drop) one or more uplink messages.
  • a UE 115 may request values for K1 and/or K2 (e.g., a requested time gap value).
  • the UE 115 may determine the requested time gap value based on a minimum processing duration for the UE 115.
  • the minimum processing capability may be equal to or based on a PDSCH processing capability of the UE 115, subcarrier spacing, frequency range (e.g., LTE, FR2, FR4), a time difference between PDCCHs, or a combination thereof.
  • a UE 115 may request one time gap value to be used for multiple uplink transmissions, in which case the multiple uplink transmissions may be transmitted in separate uplink resources (e.g., slots, symbols, TTIs). For example, UE 115 may transmit a time gap value request and indicate the request be used for one or more specific transmissions. In another example, the UE 115 may transmit a requested time gap value which may apply until the UE 115 transmits a second time gap value. In some cases, UE 115-a may request multiple different time gap values so that the corresponding transmissions are either each directed to different uplink resources or to a same (e.g., sufficiently large) uplink resource. In some cases, the UE 115 may request a K1 value, a K2 value, or both.
  • the UE 115 may request a K1 value, a K2 value, or both.
  • the UE 115 may request that a time gap value be equal to a minimum time gap value associated with a frequency range.
  • a minimum K1 value may be equal to a first number of TTIs (e.g., 20 symbols, or 102-symbol sub slots) for a first frequency range (e.g., FR2) and/or a first PDSCH processing capability (e.g., UE PDSCH processing capability 1).
  • the UE 115 may request that the time gap value (e.g., Kl) be equal to the first number of TTIs based on the frequency range in which the UE 115 is communicating and/or a PDSCH processing capability of the UE 115.
  • a minimum Kl value may be equal to a second number of TTIs (e.g., 4.5 symbols, or 3 2-symbol sub-slots) for a first subcarrier spacing (e.g.,
  • the UE 115 may request that the time gap value (e.g., Kl) be equal to the second number of TTIs based on the subcarrier for which the UE 115 is communicating and/or a PDSCH processing capability of the UE 115.
  • a minimum K2 value may be equal to a third number of TTIs (e.g., 36 symbols, or 18 2-symbol sub-slots) for the first frequency range.
  • the UE 115 may request that the time gap value (e.g., K2) be equal to the third number of TTIs based on the frequency range in which the UE 115 is communicating.
  • the UE 115 may request a time gap value (e.g.,
  • UE 115-c may request that the time gap value be equal to a minimum time gap value (e.g., minimum Kl) plus one slot (due to the one slot different between downlink control channel 310-b in slot 305-d and downlink control channel 310-b in slot 305-e).
  • the UE 115 may request a time gap value (e.g., Kl, K2) to be any value.
  • the UE 115 may request multiple time gap values (e.g., Kl, K2), where each time gap value of the multiple is based on scheduling multiple uplink messages associated with consecutive downlink messages to the same one or more resources. For example, the UE 115 may request multiple time gap values (e.g., Kl) where each time gap value is associated with a different downlink shared channel 315. The UE 115 may determine the multiple time gap values so that the corresponding uplink control channels 320 are scheduled for the same one or more resources, where the UE 115 may request or be configured with a sufficiently large resource allocation to transmit each uplink control channel 320 in the same uplink transmission.
  • Kl time gap values
  • the UE 115 may multiplex the multiple uplink control channels 320 and transmit the multiplexed information in a single uplink control channel transmission on the one or more allocated resources.
  • the UE 115 may request multiple time gap values (e.g., K2) where each time gap value is associated with a different downlink control channel.
  • the UE 115 may determine the multiple time gap values so that the corresponding uplink shared channels are scheduled for the same one or more resources, where the UE 115 may request or be configured with a sufficiently large resource allocation to transmit each uplink shared channel in the same uplink transmission.
  • the UE 115 may multiplex the multiple uplink shared channels and transmit the multiplexed information in a single uplink shared channel transmission on the one or more allocated resources.
  • the UE 115 may transmit the request upon radio resource control (RRC) establishment.
  • the UE 115 may transmit the requested time gap value via a random access preamble message (e.g., upon random access transmission).
  • the UE 115 may indicate the requested time gap value by a random access channel signature.
  • the random access channel (RACH) procedure may issue as a response to paging (e.g., a base station 105 may page the UE 115), and the UE 115 may respond with a RACH preamble message (e.g., RACH MSG 1).
  • the UE 115 may select a RACH signature from a set of RACH signatures to apply to the RACH preamble, where the RACH signature may refer to a pattern applied to the message.
  • the UE may be configured with a (e.g., new or existing) RACH signature in the set of RACH signatures that may indicate a time gap value request. Accordingly, the UE 115 may apply the selected RACH signature to the RACH preamble and transmit the RACH preamble.
  • the base station 105 may receive the RACH preamble and identify the requested time gap value based on the RACH signature applied to the RACH preamble.
  • the UE 115 may transmit the requested time gap value upon RRC connection setup, such as with an IE.
  • the UE 115 may transmit the requested time gap value via an information element in a radio resource control connection setup message.
  • the UE 115 may transmit an RRC Setup Request IE and indicate a cause for establishment (e.g., Establishment Cause) of the RRC connection.
  • the UE 115 may indicate mobile terminal (MT) access as the establishment cause (e.g., mt-Access) and as such may indicate a time gap value request (e.g., PDSCH-to-HARQ value Request).
  • MT mobile terminal
  • the UE 115 may indicate that high priority access as the establishment cause (e.g., highPriority Access) and as such may indicate a time gap value request (e.g., PDSCH-to-HARQ value Request).
  • the UE 115 may transmit the requested time gap value via a radio resource control setup complete message.
  • the UE 115 may use an IE (e.g., RRCSetUpComplete-vl710-Ies) of the RRC setup complete message to indicate high priority access (e.g., highPriority Access) and include a time gap value request (e.g., PDSCH-to-HARQ value Request).
  • an IE e.g., RRCSetUpComplete-vl710-Ies
  • the UE 115 may transmit the request during an RRC session.
  • the UE 115 may transmit the requested time gap value via a radio resource control message, a medium access control element message, an uplink control information message, or a combination thereof.
  • the UE 115 may dynamically, semi-statically, or aperiodically determine whether to transmit a time gap value request.
  • the UE 115 may transmit an RRC reconfiguration complete message (e.g., RRCReconfigurationComplete), where an IE (e.g., RRCReconfigurationComplete-vl710-IEs) in the message may indicate high priority access (e.g., highPriority Access) and include a time gap value request (e.g., PDSCH-to- HARQ value Request).
  • RRC reconfiguration complete message e.g., RRCReconfigurationComplete
  • an IE e.g., RRCReconfigurationComplete-vl710-IEs
  • a time gap value request e.g., PDSCH-to- HARQ value Request
  • the UE 115 may transmit an RRC reestablishment complete message (e.g., RRCReestablishmentComplete), where an IE (e.g., RRCReestablishmentComplete-vl710-IEs) in the message may indicate high priority access (e.g., highPriority Access) and include a time gap value request (e.g., PDSCH-to-HARQ value Request).
  • RRC resume message e.g., RRCResumeRequest, RRCResumeRequestl, RRCResumeComplete.
  • the UE 115 may transmit the requested time gap value via a scheduling request included in an uplink control information message.
  • the time gap value request included in UCI may be based on the size of the request and an uplink control channel format (e.g., PUCCH format).
  • the UE 115 may transmit a first set of bits of the requested time gap value via an uplink control information message and a second set of bits of the requested time gap value in accordance with a cyclic shift based on an uplink control channel format.
  • the UE 115 may include one time gap value request bit in the UCI and one or more remaining bits may be coded separately with a different phase shift.
  • the UE 115 may include the time gap value request (e.g., the complete time gap value request) in the UCI.
  • the UCI may be configured with a specific bit location (e.g., after the specified scheduling request locations) for including the time gap value request.
  • UE 115-c may transmit one or more time gap value requests to base station 105-c.
  • Base station 105-c may schedule one or more uplink transmissions based on the requests.
  • base station 105-c may transmit downlink control channel 310-b in slot 305-d, which may include DCI indicating downlink shared channel 315-b in slot 305-d and a time gap 325-c (e.g., a K1 value), where the time gap 325-c is equal to the requested time gap value.
  • a time gap 325-c e.g., a K1 value
  • Base station 105-c may also transmit downlink control channel 310-b in slot 305-e, which may include DCI indicating downlink shared channel 315-b in slot 305-e and a time gap 325-d (e.g., a K1 value), where the time gap 325-d may be equal to the requested time gap value.
  • UE 115-c may transmit uplink control channel 320-b in slot 305-f in accordance with time gap 325-c and transmit uplink control channel 320-b in slot 305-g in accordance with time gap 325-d.
  • FIG. 3B is depicted to describe an example of a time gap value request procedure and it should be understood that the time gap value request procedure may be implemented by any device, apply to K1 values and/or K2 values, is not limited to consecutive downlink transmissions or consecutive uplink transmissions.
  • FIG. 4 illustrates an example of a process flow 400 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the process flow 400 may illustrate an example time gap request procedure.
  • UE 115-d may transmit a message to base station 105-d including a request for a time gap value (e.g., a K1 value, a K2 value).
  • Base station 105-d and UE 115-d may be examples of the corresponding wireless devices described with reference to FIGs. 1 through 3B.
  • a different type of device e.g., a base station 105
  • Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.
  • UE 115-d may transmit a request for base station 105-d to specify to UE 115-d a time gap to be applied by UE 115-d between receipt of a downlink message (e.g., a PDSCH, PDCCH) from base station 105-d and transmission of an uplink message (e.g., a PUCCH, a PUSCH, respectively) that is associated with the downlink message.
  • the request may include a requested time gap value (e.g., a requested K1 value, or K2 value, or both) provided by UE 115-d for consideration by base station 105-d in specifying the time gap.
  • UE 115-d may determine the requested time gap value based at least in part on a minimum time gap value (e.g., minimum Kl, minimum K2), a frequency range (e.g., sub 6, FR2, FR4), a processing capability (e.g., PDSCH processing capability of UE 115-d), a subcarrier spacing, or a combination thereof.
  • a minimum time gap value e.g., minimum Kl, minimum K2
  • a frequency range e.g., sub 6, FR2, FR4
  • a processing capability e.g., PDSCH processing capability of UE 115-d
  • a subcarrier spacing e.g., a subcarrier spacing, or a combination thereof.
  • transmitting the request may include transmitting the requested time gap value for the time gap which is between receipt of a downlink shared channel (e.g., PDSCH) and transmission of feedback (e.g., HARQ feedback) via an uplink control channel (e.g., PUCCH).
  • a downlink shared channel e.g., PDSCH
  • feedback e.g., HARQ feedback
  • uplink control channel e.g., PUCCH
  • transmitting the request may include transmitting the requested time gap value for the time gap which is between receipt of a downlink control channel (e.g., PDCCH) and transmission of an uplink shared channel (e.g., PUSCH).
  • a downlink control channel e.g., PDCCH
  • an uplink shared channel e.g., PUSCH
  • UE 115-d may include in the request that base station 105-d specify to UE 115-d a plurality of time gaps to be applied by UE 115-d between receipt of a corresponding plurality of downlink messages from base station 105-d and transmission of the uplink message.
  • the uplink message may include multiplexed content associated with each of the plurality of downlink messages, where the time gap is one of the plurality of time gaps and the downlink message is one of the plurality of downlink messages.
  • UE 115-d may transmit the requested time gap value during a radio resource control connection establishment procedure. In some implementations, UE 115-d may transmit the requested time gap value via a random access preamble message, where the requested time gap value may be indicated by a random access channel signature. In some implementations, UE 115-d may transmit the requested time gap value via an information element in a radio resource control connection setup message. In some implementations, UE 115-d may transmit the requested time gap value via a radio resource control setup complete message.
  • UE 115-d may transmit the requested time gap value during a radio resource control session. In some implementations, UE 115-d may transmit the requested time gap value via a radio resource control message, a medium access control element message, an uplink control information message, or a combination thereof. In some implementations, UE 115-d may transmit the requested time gap value via a scheduling request included in an uplink control information message based at least in part on an uplink control channel format. In some implementations, UE 115-d may transmit a first set of bits of the requested time gap value via an uplink control information message and a second set of bits of the requested time gap value in accordance with a cyclic shift based at least in part on an uplink control channel format.
  • base station 105-d may determine whether to configure one or more time gaps to be equal to the requested time gap value.
  • UE 115-d may receive, from base station 105-d and in response to the request, an indication of the time gap. In some cases, UE 115-d may receive the indication in DCI.
  • UE 115-d may transmit the uplink message based at least in part on receipt of the downlink message and in accordance with the time gap.
  • the uplink message may include HARQ feedback associated with the downlink message.
  • FIG. 5 shows a block diagram 500 of a device 505 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the device 505 may be an example of aspects of a UE 115 as described herein.
  • the device 505 may include a receiver 510, a transmitter 515, and a communications manager 520.
  • the device 505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).
  • the receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling an uplink feedback transmission). Information may be passed on to other components of the device 505.
  • the receiver 510 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 515 may provide a means for transmitting signals generated by other components of the device 505.
  • the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling an uplink feedback transmission).
  • the transmitter 515 may be co-located with a receiver 510 in a transceiver module.
  • the transmitter 515 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of techniques for scheduling an uplink feedback transmission as described herein.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry).
  • the hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).
  • the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the
  • the communications manager 520 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both.
  • the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 520 may support wireless communications at a UE in accordance with examples as disclosed herein.
  • the communications manager 520 may be configured as or otherwise support a means for transmitting a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap.
  • the communications manager 520 may be configured as or otherwise support a means for receiving, from the base station and in response to the request, an indication of the time gap.
  • the communications manager 520 may be configured as or otherwise support a means for transmitting the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • the device 505 e.g., a processor controlling or otherwise coupled to the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof
  • the device 505 may support techniques for more efficient utilization of communication resources.
  • FIG. 6 shows a block diagram 600 of a device 605 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the device 605 may be an example of aspects of a device 505 or a UE 115 as described herein.
  • the device 605 may include a receiver 610, a transmitter 615, and a communications manager 620.
  • the device 605 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 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling an uplink feedback transmission). Information may be passed on to other components of the device 605.
  • the receiver 610 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 615 may provide a means for transmitting signals generated by other components of the device 605.
  • the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling an uplink feedback transmission).
  • the transmitter 615 may be co-located with a receiver 610 in a transceiver module.
  • the transmitter 615 may utilize a single antenna or a set of multiple antennas.
  • the device 605, or various components thereof may be an example of means for performing various aspects of techniques for scheduling an uplink feedback transmission as described herein.
  • the communications manager 620 may include a time gap value request manager 625, a time gap indication manager 630, an uplink message manager 635, or any combination thereof.
  • the communications manager 620 may be an example of aspects of a communications manager 520 as described herein.
  • the communications manager 620, or various components thereof may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both.
  • the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 620 may support wireless communications at a UE in accordance with examples as disclosed herein.
  • the time gap value request manager 625 may be configured as or otherwise support a means for transmitting a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap.
  • the time gap indication manager 630 may be configured as or otherwise support a means for receiving, from the base station and in response to the request, an indication of the time gap.
  • the uplink message manager 635 may be configured as or otherwise support a means for transmitting the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • FIG. 7 shows a block diagram 700 of a communications manager 720 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein.
  • the communications manager 720, or various components thereof, may be an example of means for performing various aspects of techniques for scheduling an uplink feedback transmission as described herein.
  • the communications manager 720 may include a time gap value request manager 725, a time gap indication manager 730, an uplink message manager 735, an RRC connection establishment manager 740, an RRC connection establishment manager 745, an RRC session manager 750, a time gap value determination manager 755, or any combination thereof.
  • Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).
  • the communications manager 720 may support wireless communications at a UE in accordance with examples as disclosed herein.
  • the time gap value request manager 725 may be configured as or otherwise support a means for transmitting a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap.
  • the time gap indication manager 730 may be configured as or otherwise support a means for receiving, from the base station and in response to the request, an indication of the time gap.
  • the uplink message manager 735 may be configured as or otherwise support a means for transmitting the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • the time gap value request manager 725 may be configured as or otherwise support a means for transmitting the requested time gap value for the time gap which is between receipt of a downlink shared channel and transmission of feedback via an uplink control channel, where the downlink message is the downlink shared channel and the uplink message is the uplink control channel.
  • the time gap value request manager 725 may be configured as or otherwise support a means for transmitting the requested time gap value for the time gap which is between receipt of a downlink control channel and transmission of an uplink shared channel, where the downlink message is the downlink control channel and the uplink message is the uplink shared channel.
  • the time gap value request manager 725 may be configured as or otherwise support a means for including in the request that the base station specify to the UE a set of multiple time gaps to be applied by the UE between receipt of a corresponding set of multiple downlink messages from the base station and transmission of the uplink message, where the uplink message includes multiplexed content associated with each of the set of multiple downlink messages, the time gap being one of the set of multiple time gaps and the downlink message being one of the set of multiple downlink messages.
  • the RRC connection establishment manager 740 may be configured as or otherwise support a means for transmitting the requested time gap value during a radio resource control connection establishment procedure.
  • the RRC connection establishment manager 745 may be configured as or otherwise support a means for transmitting the requested time gap value via a random access preamble message, the requested time gap value indicated by a random access channel signature.
  • the RRC connection establishment manager 745 may be configured as or otherwise support a means for transmitting the requested time gap value via an information element in a radio resource control connection setup message.
  • the RRC connection establishment manager 745 may be configured as or otherwise support a means for transmitting the requested time gap value via a radio resource control setup complete message.
  • the RRC session manager 750 may be configured as or otherwise support a means for transmitting the requested time gap value during a radio resource control session.
  • the RRC session manager 750 may be configured as or otherwise support a means for transmitting the requested time gap value via a radio resource control message, a medium access control element message, an uplink control information message, or a combination thereof.
  • the RRC session manager 750 may be configured as or otherwise support a means for transmitting the requested time gap value via a scheduling request included in an uplink control information message based on an uplink control channel format.
  • the RRC session manager 750 may be configured as or otherwise support a means for transmitting a first set of bits of the requested time gap value via an uplink control information message and a second set of bits of the requested time gap value in accordance with a cyclic shift based on an uplink control channel format.
  • the time gap value determination manager 755 may be configured as or otherwise support a means for determining the requested time gap value based on a minimum time gap value, a frequency range, a processing capability, a subcarrier spacing, or a combination thereof.
  • the uplink message includes hybrid automatic repeat request feedback associated with the downlink message.
  • FIG. 8 shows a diagram of a system 800 including a device 805 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the device 805 may be an example of or include the components of a device 505, a device 605, or a UE 115 as described herein.
  • the device 805 may communicate wirelessly with one or more base stations 105, UEs 115, or any combination thereof.
  • the device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input/output (I/O) controller 810, a transceiver 815, an antenna 825, a memory 830, code 835, and a processor 840.
  • These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).
  • the I/O controller 810 may manage input and output signals for the device 805.
  • the I/O controller 810 may also manage peripherals not integrated into the device 805.
  • the I/O controller 810 may represent a physical connection or port to an external peripheral.
  • the EO controller 810 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system.
  • the I/O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the EO controller 810 may be implemented as part of a processor, such as the processor 840.
  • a user may interact with the device 805 via the I/O controller 810 or via hardware components controlled by the I/O controller 810.
  • the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 815 may communicate bi-directionally, via the one or more antennas 825, wired, or wireless links as described herein.
  • the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825.
  • the transceiver 815 may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.
  • the memory 830 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the processor 840, cause the device 805 to perform various functions described herein.
  • the code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 835 may not be directly executable by the processor 840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 830 may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the processor 840 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 840 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 840.
  • the processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting techniques for scheduling an uplink feedback transmission).
  • the device 805 or a component of the device 805 may include a processor 840 and memory 830 coupled to the processor 840, the processor 840 and memory 830 configured to perform various functions described herein.
  • the communications manager 820 may support wireless communications at a UE in accordance with examples as disclosed herein.
  • the communications manager 820 may be configured as or otherwise support a means for transmitting a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap.
  • the communications manager 820 may be configured as or otherwise support a means for receiving, from the base station and in response to the request, an indication of the time gap.
  • the communications manager 820 may be configured as or otherwise support a means for transmitting the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • the device 805 may support techniques for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved coordination between devices.
  • the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof.
  • the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the processor 840, the memory 830, the code 835, or any combination thereof.
  • the code 835 may include instructions executable by the processor 840 to cause the device 805 to perform various aspects of techniques for scheduling an uplink feedback transmission as described herein, or the processor 840 and the memory 830 may be otherwise configured to perform or support such operations.
  • FIG. 9 shows a block diagram 900 of a device 905 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the device 905 may be an example of aspects of a base station 105 as described herein.
  • the device 905 may include a receiver 910, a transmitter 915, and a communications manager 920.
  • the device 905 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 910 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling an uplink feedback transmission). Information may be passed on to other components of the device 905.
  • the receiver 910 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 915 may provide a means for transmitting signals generated by other components of the device 905.
  • the transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling an uplink feedback transmission).
  • the transmitter 915 may be co-located with a receiver 910 in a transceiver module.
  • the transmitter 915 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of techniques for scheduling an uplink feedback transmission as described herein.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry).
  • the hardware may include a processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).
  • the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).
  • the communications manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both.
  • the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to receive information, transmit information, or perform various other operations as described herein.
  • the communications manager 920 may be configured as or otherwise support a means for receiving, from a UE, a request for the base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap.
  • the communications manager 920 may be configured as or otherwise support a means for transmitting, to the UE and in response to the request, an indication of the time gap.
  • the communications manager 920 may be configured as or otherwise support a means for receiving the uplink message based on transmission of the downlink message and in accordance with the time gap.
  • the device 905 e.g., a processor controlling or otherwise coupled to the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof
  • the device 905 may support techniques for more efficient utilization of communication resources.
  • FIG. 10 shows a block diagram 1000 of a device 1005 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the device 1005 may be an example of aspects of a device 905 or a base station 105 as described herein.
  • the device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020.
  • the device 1005 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 1010 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling an uplink feedback transmission). Information may be passed on to other components of the device 1005.
  • the receiver 1010 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005.
  • the transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to techniques for scheduling an uplink feedback transmission).
  • the transmitter 1015 may be co-located with a receiver 1010 in a transceiver module.
  • the transmitter 1015 may utilize a single antenna or a set of multiple antennas.
  • the device 1005, or various components thereof may be an example of means for performing various aspects of techniques for scheduling an uplink feedback transmission as described herein.
  • the communications manager 1020 may include a time gap value request component 1025, a time gap indication component 1030, an uplink message component 1035, or any combination thereof.
  • the communications manager 1020 may be an example of aspects of a communications manager 920 as described herein.
  • the communications manager 1020, or various components thereof may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both.
  • the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to receive information, transmit information, or perform various other operations as described herein.
  • the time gap value request component 1025 may be configured as or otherwise support a means for receiving, from a UE, a request for the base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the EE for consideration by the base station in specifying the time gap.
  • the time gap indication component 1030 may be configured as or otherwise support a means for transmitting, to the EE and in response to the request, an indication of the time gap.
  • the uplink message component 1035 may be configured as or otherwise support a means for receiving the uplink message based on transmission of the downlink message and in accordance with the time gap.
  • FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein.
  • the communications manager 1120, or various components thereof may be an example of means for performing various aspects of techniques for scheduling an uplink feedback transmission as described herein.
  • the communications manager 1120 may include a time gap value request component 1125, a time gap indication component 1130, an uplink message component 1135, an RRC connection establishment component 1140, an RRC session component 1145, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).
  • the time gap value request component 1125 may be configured as or otherwise support a means for receiving, from a UE, a request for the base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap.
  • the time gap indication component 1130 may be configured as or otherwise support a means for transmitting, to the UE and in response to the request, an indication of the time gap.
  • the uplink message component 1135 may be configured as or otherwise support a means for receiving the uplink message based on transmission of the downlink message and in accordance with the time gap.
  • the time gap value request component 1125 may be configured as or otherwise support a means for receiving the requested time gap value for the time gap which is between receipt of a downlink shared channel and transmission of feedback via an uplink control channel, where the downlink message is the downlink shared channel and the uplink message is the uplink control channel.
  • the time gap value request component 1125 may be configured as or otherwise support a means for receiving the requested time gap value for the time gap which is between receipt of a downlink control channel and transmission of an uplink shared channel, where the downlink message is the downlink control channel and the uplink message is the uplink shared channel.
  • the time gap value request component 1125 may be configured as or otherwise support a means for identifying in the request an indication that the base station specify to the UE a set of multiple time gaps to be applied by the UE between receipt of a corresponding set of multiple downlink messages from the base station and transmission of the uplink message, where the uplink message includes multiplexed content associated with each of the set of multiple downlink messages, the time gap being one of the set of multiple time gaps and the downlink message being one of the set of multiple downlink messages.
  • the RRC connection establishment component 1140 may be configured as or otherwise support a means for receiving the requested time gap value during a radio resource control connection establishment procedure.
  • the RRC connection establishment component 1140 may be configured as or otherwise support a means for receiving the requested time gap value via a random access preamble message, the requested time gap value indicated by a random access channel signature.
  • the RRC connection establishment component 1140 may be configured as or otherwise support a means for receiving the requested time gap value via an information element in a radio resource control connection setup message.
  • the RRC connection establishment component 1140 may be configured as or otherwise support a means for receiving the requested time gap value via a radio resource control setup complete message.
  • the RRC session component 1145 may be configured as or otherwise support a means for receiving the requested time gap value during a radio resource control session.
  • the RRC session component 1145 may be configured as or otherwise support a means for receiving the requested time gap value via a radio resource control message, a medium access control element message, an uplink control information message, or a combination thereof.
  • the RRC session component 1145 may be configured as or otherwise support a means for receiving the requested time gap value via a scheduling request included in an uplink control information message based on an uplink control channel format.
  • the RRC session component 1145 may be configured as or otherwise support a means for receiving a first set of bits of the requested time gap value via an uplink control information message and a second set of bits of the requested time gap value in accordance with a cyclic shift based on an uplink control channel format.
  • the uplink message includes hybrid automatic repeat request feedback associated with the downlink message.
  • FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the device 1205 may be an example of or include the components of a device 905, a device 1005, or a base station 105 as described herein.
  • the device 1205 may communicate wirelessly with one or more base stations 105, UEs 115, or any combination thereof.
  • the device 1205 may include components for bi directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1220, a network communications manager 1210, a transceiver 1215, an antenna 1225, a memory 1230, code 1235, a processor 1240, and an inter-station communications manager 1245.
  • These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1250).
  • the network communications manager 1210 may manage communications with a core network 130 (e.g., via one or more wired backhaul links). For example, the network communications manager 1210 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the device 1205 may include a single antenna 1225. However, in some other cases the device 1205 may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 1215 may communicate bi-directionally, via the one or more antennas 1225, wired, or wireless links as described herein.
  • the transceiver 1215 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1215 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1225 for transmission, and to demodulate packets received from the one or more antennas 1225.
  • the transceiver 1215 may be an example of a transmitter 915, a transmitter 1015, a receiver 910, a receiver 1010, or any combination thereof or component thereof, as described herein.
  • the memory 1230 may include RAM and ROM.
  • the memory 1230 may store computer-readable, computer-executable code 1235 including instructions that, when executed by the processor 1240, cause the device 1205 to perform various functions described herein.
  • the code 1235 may be stored in a non-transitory computer- readable medium such as system memory or another type of memory.
  • the code 1235 may not be directly executable by the processor 1240 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1230 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 1240 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 1240 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1240.
  • the processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1230) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting techniques for scheduling an uplink feedback transmission).
  • the device 1205 or a component of the device 1205 may include a processor 1240 and memory 1230 coupled to the processor 1240, the processor 1240 and memory 1230 configured to perform various functions described herein.
  • the inter-station communications manager 1245 may manage communications with other base stations 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 1245 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 1245 may provide an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between base stations 105.
  • the communications manager 1220 may be configured as or otherwise support a means for receiving, from a UE, a request for the base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap.
  • the communications manager 1220 may be configured as or otherwise support a means for transmitting, to the UE and in response to the request, an indication of the time gap.
  • the communications manager 1220 may be configured as or otherwise support a means for receiving the uplink message based on transmission of the downlink message and in accordance with the time gap.
  • the device 1205 may support techniques for improved communication reliability, reduced latency, more efficient utilization of communication resources, and improved coordination between devices.
  • the communications manager 1220 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1215, the one or more antennas 1225, or any combination thereof.
  • the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the processor 1240, the memory 1230, the code 1235, or any combination thereof.
  • the code 1235 may include instructions executable by the processor 1240 to cause the device 1205 to perform various aspects of techniques for scheduling an uplink feedback transmission as described herein, or the processor 1240 and the memory 1230 may be otherwise configured to perform or support such operations.
  • FIG. 13 shows a flowchart illustrating a method 1300 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the operations of the method 1300 may be implemented by a UE or its components as described herein.
  • the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap.
  • the operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a time gap value request manager 725 as described with reference to FIG. 7.
  • the method may include receiving, from the base station and in response to the request, an indication of the time gap. The operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a time gap indication manager 730 as described with reference to FIG. 7.
  • the method may include transmitting the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • the operations of 1315 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by an uplink message manager 735 as described with reference to FIG. 7.
  • FIG. 14 shows a flowchart illustrating a method 1400 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the operations of the method 1400 may be implemented by a UE or its components as described herein.
  • the operations of the method 1400 may be performed by a UE 115 as described with reference to FIGs. 1 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message.
  • the operations of 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a time gap value request manager 725 as described with reference to FIG. 7.
  • the method may include transmitting a requested time gap value for the time gap which is between receipt of a downlink shared channel and transmission of feedback via an uplink control channel, where the downlink message is the downlink shared channel and the uplink message is the uplink control channel.
  • the operations of 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a time gap value request manager 725 as described with reference to FIG. 7.
  • the method may include receiving, from the base station and in response to the request, an indication of the time gap. The operations of 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a time gap indication manager 730 as described with reference to FIG. 7.
  • the method may include transmitting the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • the operations of 1420 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed by an uplink message manager 735 as described with reference to FIG. 7.
  • FIG. 15 shows a flowchart illustrating a method 1500 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the operations of the method 1500 may be implemented by a UE or its components as described herein.
  • the operations of the method 1500 may be performed by a UE 115 as described with reference to FIGs. 1 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message.
  • the operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a time gap value request manager 725 as described with reference to FIG. 7.
  • the method may include transmitting a requested time gap value for the time gap which is between receipt of a downlink control channel and transmission of an uplink shared channel, where the downlink message is the downlink control channel and the uplink message is the uplink shared channel.
  • the operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a time gap value request manager 725 as described with reference to FIG. 7.
  • the method may include receiving, from the base station and in response to the request, an indication of the time gap. The operations of 1515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by a time gap indication manager 730 as described with reference to FIG. 7.
  • the method may include transmitting the uplink message based on receipt of the downlink message and in accordance with the time gap.
  • the operations of 1520 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed by an uplink message manager 735 as described with reference to FIG. 7.
  • FIG. 16 shows a flowchart illustrating a method 1600 that supports techniques for scheduling an uplink feedback transmission in accordance with aspects of the present disclosure.
  • the operations of the method 1600 may be implemented by a base station or its components as described herein.
  • the operations of the method 1600 may be performed by a base station 105 as described with reference to FIGs. 1 through 4 and 9 through 12.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving, from a UE, a request for the base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request including a requested time gap value provided by the UE for consideration by the base station in specifying the time gap.
  • the operations of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a time gap value request component 1125 as described with reference to FIG. 11.
  • the method may include transmitting, to the UE and in response to the request, an indication of the time gap.
  • the operations of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a time gap indication component 1130 as described with reference to FIG. 11.
  • the method may include receiving the uplink message based on transmission of the downlink message and in accordance with the time gap. The operations of 1615 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed by an uplink message component 1135 as described with reference to FIG. 11.
  • a method for wireless communications at a UE comprising: transmitting a request for a base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request comprising a requested time gap value provided by the UE for consideration by the base station in specifying the time gap; receiving, from the base station and in response to the request, an indication of the time gap; and transmitting the uplink message based at least in part on receipt of the downlink message and in accordance with the time gap.
  • Aspect 2 The method of aspect 1, wherein transmitting the request further comprises: transmitting the requested time gap value for the time gap which is between receipt of a downlink shared channel and transmission of feedback via an uplink control channel, wherein the downlink message is the downlink shared channel and the uplink message is the uplink control channel.
  • Aspect 3 The method of any of aspects 1 through 2, wherein transmitting the request further comprises: transmitting the requested time gap value for the time gap which is between receipt of a downlink control channel and transmission of an uplink shared channel, wherein the downlink message is the downlink control channel and the uplink message is the uplink shared channel.
  • Aspect 4 The method of any of aspects 1 through 3, wherein transmitting the request further comprises: including in the request that the base station specify to the UE a plurality of time gaps to be applied by the UE between receipt of a corresponding plurality of downlink messages from the base station and transmission of the uplink message, wherein the uplink message includes multiplexed content associated with each of the plurality of downlink messages, the time gap being one of the plurality of time gaps and the downlink message being one of the plurality of downlink messages.
  • Aspect 5 The method of any of aspects 1 through 4, wherein transmitting the request further comprises: transmitting the requested time gap value during a radio resource control connection establishment procedure.
  • Aspect 6 The method of any of aspects 1 through 5, wherein transmitting the request further comprises: transmitting the requested time gap value via a random access preamble message, the requested time gap value indicated by a random access channel signature.
  • Aspect 7 The method of any of aspects 1 through 6, wherein transmitting the request further comprises: transmitting the requested time gap value via an information element in a radio resource control connection setup message.
  • Aspect 8 The method of any of aspects 1 through 7, wherein transmitting the request further comprises: transmitting the requested time gap value via a radio resource control setup complete message.
  • Aspect 9 The method of any of aspects 1 through 8, wherein transmitting the request further comprises: transmitting the requested time gap value during a radio resource control session.
  • Aspect 10 The method of any of aspects 1 through 9, wherein transmitting the request further comprises: transmitting the requested time gap value via a radio resource control message, a medium access control element message, an uplink control information message, or a combination thereof.
  • Aspect 11 The method of any of aspects 1 through 10, wherein transmitting the request further comprises: transmitting the requested time gap value via a scheduling request included in an uplink control information message based at least in part on an uplink control channel format.
  • Aspect 12 The method of any of aspects 1 through 11, wherein transmitting the request further comprises: transmitting a first set of bits of the requested time gap value via an uplink control information message and a second set of bits of the requested time gap value in accordance with a cyclic shift based at least in part on an uplink control channel format.
  • Aspect 13 The method of any of aspects 1 through 12, further comprising: determining the requested time gap value based at least in part on a minimum time gap value, a frequency range, a processing capability, a subcarrier spacing, or a combination thereof.
  • Aspect 14 The method of any of aspects 1 through 13, wherein the uplink message comprises hybrid automatic repeat request feedback associated with the downlink message.
  • a method for wireless communications at a base station comprising: receiving, from a UE, a request for the base station to specify to the UE a time gap to be applied by the UE between receipt of a downlink message from the base station and transmission of an uplink message that is associated with the downlink message, the request comprising a requested time gap value provided by the UE for consideration by the base station in specifying the time gap; transmitting, to the UE and in response to the request, an indication of the time gap; and receiving the uplink message based at least in part on transmission of the downlink message and in accordance with the time gap.
  • Aspect 16 The method of aspect 15, wherein receiving the request further comprises: receiving the requested time gap value for the time gap which is between receipt of a downlink shared channel and transmission of feedback via an uplink control channel, wherein the downlink message is the downlink shared channel and the uplink message is the uplink control channel.
  • Aspect 17 The method of any of aspects 15 through 16, wherein receiving the request further comprises: receiving the requested time gap value for the time gap which is between receipt of a downlink control channel and transmission of an uplink shared channel, wherein the downlink message is the downlink control channel and the uplink message is the uplink shared channel.
  • Aspect 18 The method of any of aspects 15 through 17, wherein receiving the request further comprises: identifying in the request an indication that the base station specify to the UE a plurality of time gaps to be applied by the UE between receipt of a corresponding plurality of downlink messages from the base station and transmission of the uplink message, wherein the uplink message includes multiplexed content associated with each of the plurality of downlink messages, the time gap being one of the plurality of time gaps and the downlink message being one of the plurality of downlink messages.
  • Aspect 19 The method of any of aspects 15 through 18, wherein receiving the request further comprises: receiving the requested time gap value during a radio resource control connection establishment procedure.
  • Aspect 20 The method of any of aspects 15 through 19, wherein receiving the request further comprises: receiving the requested time gap value via a random access preamble message, the requested time gap value indicated by a random access channel signature.
  • Aspect 21 The method of any of aspects 15 through 20, wherein receiving the request further comprises: receiving the requested time gap value via an information element in a radio resource control connection setup message.
  • Aspect 22 The method of any of aspects 15 through 21, wherein receiving the request further comprises: receiving the requested time gap value via a radio resource control setup complete message.
  • Aspect 23 The method of any of aspects 15 through 22, wherein receiving the request further comprises: receiving the requested time gap value during a radio resource control session.
  • Aspect 24 The method of any of aspects 15 through 23, wherein receiving the request comprises: receiving the requested time gap value via a radio resource control message, a medium access control element message, an uplink control information message, or a combination thereof.
  • Aspect 25 The method of any of aspects 15 through 24, wherein receiving the request further comprises: receiving the requested time gap value via a scheduling request included in an uplink control information message based at least in part on an uplink control channel format.
  • Aspect 26 The method of any of aspects 15 through 25, wherein receiving the request further comprises: receiving a first set of bits of the requested time gap value via an uplink control information message and a second set of bits of the requested time gap value in accordance with a cyclic shift based at least in part on an uplink control channel format.
  • Aspect 27 The method of any of aspects 15 through 26, wherein the uplink message comprises hybrid automatic repeat request feedback associated with the downlink message.
  • Aspect 28 An apparatus for wireless communications, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 14.
  • Aspect 29 An apparatus for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 14.
  • Aspect 30 A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 14.
  • Aspect 31 An apparatus for wireless communications, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 15 through 27.
  • Aspect 32 An apparatus for wireless communications, comprising at least one means for performing a method of any of aspects 15 through 27.
  • Aspect 33 A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by a processor to perform a method of any of aspects 15 through 27.
  • LTE, LTE-A, LTE-A Pro, or NR 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 networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • 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 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).
  • 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.
  • non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, 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 may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
  • determining encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (such as receiving information), accessing (such as accessing data in a memory) and the like. Also, “determining” can include resolving, selecting, choosing, establishing and other such similar actions.

Landscapes

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

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs de communication sans fil. Un équipement utilisateur (UE) peut transmettre une demande afin qu'une station de base spécifie à l'UE un intervalle de temps à appliquer par l'UE entre la réception d'un message de liaison descendante provenant de la station de base et la transmission d'un message de liaison montante associé au message de liaison descendante. Dans certains cas, la demande peut comprendre une valeur d'intervalle de temps demandé fournie par l'UE pour une prise en compte par la station de base dans la spécification de l'intervalle de temps. L'UE peut recevoir, en provenance de la station de base et en réponse à la demande, une indication de l'intervalle de temps. L'UE peut transmettre le message de liaison montante (par exemple, un canal de commande de liaison montante, un canal partagé de liaison montante) en fonction de la réception du message de liaison descendante (par exemple, un canal partagé de liaison descendante, un canal de commande de liaison descendante, respectivement) et conformément à l'intervalle de temps.
PCT/US2022/030306 2021-05-25 2022-05-20 Techniques de planification pour une transmission de rétroaction de liaison montante WO2022251067A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GR20210100344 2021-05-25
GR20210100344 2021-05-25

Publications (1)

Publication Number Publication Date
WO2022251067A1 true WO2022251067A1 (fr) 2022-12-01

Family

ID=82115577

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/030306 WO2022251067A1 (fr) 2021-05-25 2022-05-20 Techniques de planification pour une transmission de rétroaction de liaison montante

Country Status (1)

Country Link
WO (1) WO2022251067A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022132390A1 (fr) * 2020-12-18 2022-06-23 Qualcomm Incorporated Techniques pour adapter une ligne de temps de planification à une grille de traitement

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022132390A1 (fr) * 2020-12-18 2022-06-23 Qualcomm Incorporated Techniques pour adapter une ligne de temps de planification à une grille de traitement

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ASUSTEK: "UE assistance information for power saving", vol. RAN WG1, no. Chongqing, China; 20191014 - 20191020, 4 October 2019 (2019-10-04), XP051808312, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG1_RL1/TSGR1_98b/Docs/R1-1911147.zip R1-1911147 UE assistance information for power saving.doc> [retrieved on 20191004] *
HUAWEI ET AL: "HARQ processing time", vol. RAN WG1, no. Qingdao, China; 20170627 - 20170630, 26 June 2017 (2017-06-26), XP051299189, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20170626] *
VIVO: "Procedure of cross-slot scheduling power saving techniques", vol. RAN WG1, no. Xi'an, China; 20190408 - 20190412, 2 April 2019 (2019-04-02), XP051707114, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F96b/Docs/R1%2D1904104%2Ezip> [retrieved on 20190402] *

Similar Documents

Publication Publication Date Title
US20210321299A1 (en) Out-of-order handling without flow control feedback
EP4091259A1 (fr) Signalisation pour configurer des transmissions de liaison descendante
EP4197268A1 (fr) Techniques de communication en liaison latérale utilisant un groupe de ressources de liaison latérale configuré pour une technologie d&#39;accès radio différente
US20230051721A1 (en) Short reference signals for sidelink communication
WO2021202976A1 (fr) Configurations d&#39;espace de recherche pour une planification à multiples porteuses composantes
WO2022159181A1 (fr) Ajustement de puissance de transmission pour retour en duplex intégral
US20220225379A1 (en) Techniques for performing uplink control channel beam hopping and repetition
US11909691B2 (en) On-demand negative acknowledgment resource request
US11546890B2 (en) Intra-symbol multiplexing with single carrier waveform
WO2022212057A1 (fr) Techniques de saut de fréquence pour répétitions de canal partagé de liaison montante
US11985649B2 (en) Modifications to uplink grant configurations
US11910381B2 (en) Multiplexing techniques for uplink transmissions
WO2022251067A1 (fr) Techniques de planification pour une transmission de rétroaction de liaison montante
WO2021139523A1 (fr) Transmission de commande d&#39;avance temporelle dans des informations de commande de liaison descendante pour la suspension d&#39;un groupe de cellules secondaires
US11558166B2 (en) Assignment indexes for dynamic feedback
US20230061073A1 (en) Timing management for inter-user equipment coordination
US20220240245A1 (en) Generating a feedback codebook
US20230224012A1 (en) Feedback codebook generation based on transmission scheduling rules
WO2021168770A1 (fr) Techniques d&#39;accès multiple avec écoute de porteuse pour systèmes de communication sans fil
WO2023024070A1 (fr) Re-sélection de ressources reposant sur une indication de pré-conflit
US20220377786A1 (en) Techniques for granting resources for internet of things communications
WO2023184334A1 (fr) Améliorations de réponse pour plusieurs procédures d&#39;accès aléatoire
WO2023050025A1 (fr) Sélection de porteuse pour des messages d&#39;accès aléatoire de liaison descendante
WO2023283057A1 (fr) Report de rétroaction programmée semi-persistante avec commutation de porteuses dans une agrégation de porteuses de liaison montante
WO2022203877A1 (fr) Techniques de saut de fréquence pour répétitions de canal de commande 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: 22731895

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

Country of ref document: EP

Kind code of ref document: A1