WO2021248076A1 - Procédures de transmission de requête de planification de détection de blocage de faisceau - Google Patents

Procédures de transmission de requête de planification de détection de blocage de faisceau Download PDF

Info

Publication number
WO2021248076A1
WO2021248076A1 PCT/US2021/036016 US2021036016W WO2021248076A1 WO 2021248076 A1 WO2021248076 A1 WO 2021248076A1 US 2021036016 W US2021036016 W US 2021036016W WO 2021248076 A1 WO2021248076 A1 WO 2021248076A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling request
blocking detection
beam blocking
downlink
base station
Prior art date
Application number
PCT/US2021/036016
Other languages
English (en)
Inventor
Konstantinos Dimou
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 WO2021248076A1 publication Critical patent/WO2021248076A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0621—Feedback content
    • H04B7/063—Parameters other than those covered in groups H04B7/0623 - H04B7/0634, e.g. channel matrix rank or transmit mode selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0868—Hybrid systems, i.e. switching and combining
    • H04B7/088—Hybrid systems, i.e. switching and combining using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the following relates generally to wireless communications and more specifically to beam blocking detection scheduling request transmission procedures.
  • 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 UE may report feedback to a base station based on a decoding outcome of a communication at the UE. For example, the UE may transmit a positive acknowledgement (ACK) when the decoding is successful, or the UE may transmit a negative acknowledgement (NACK) when the decoding is unsuccessful.
  • ACK positive acknowledgement
  • NACK negative acknowledgement
  • a base station may clear a retransmission buffer based on receiving an ACK.
  • a base station may also determine to retransmit the communication associated with the feedback based on receiving a NACK.
  • the base station may use different parameters for the retransmission than those used for the initial transmission. Efficient retransmission may be based on the parameters chosen by the base station, which may be based on the reasons that the initial transmission was not received or decoded properly at the UE.
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support beam blocking detection scheduling request transmission procedures.
  • the described techniques provide for efficient link adaptation upon beam blocking determination.
  • a UE may be configured to identify that the UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam, and that the failure was the result of beam blocking. Once the UE determines that the failure was due to beam blocking, the UE may transmit, to the base station and based on the determination, a beam blocking detection scheduling request.
  • the UE transmits the beam blocking detection scheduling request in a physical uplink control channel (PUCCH).
  • the UE may be configured to determine a cyclic shift to apply to the PUCCH based on the determination that the failure is due to beam blocking, or based on the format of the PUCCH, or a combination thereof.
  • the beam blocking scheduling request may be transmitted with a negative acknowledgement (NACK) message.
  • the scheduling request may request a grant for the UE to transmit a channel state information (CSI) report to the base station that includes beam blocking detection information.
  • the UE may receive, pursuant to the beam blocking detection scheduling request, the grant for transmission of a CSI report including beam blocking detection information and transmit the CSI report to the base station in accordance with the grant.
  • CSI channel state information
  • the base station may utilize the beam blocking detection information included in the CSI report to adjust one or more communication parameters to retransmit the one or more scheduled downlink transmissions to the UE.
  • a method of wireless communications at a UE is described. The method may include identifying that the UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam, determining that the failure is due to the first downlink beam being beam blocked, and transmitting, to a base station and based on the determination, a beam blocking detection scheduling request.
  • 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 identify that a UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam, determine that the failure is due to the first downlink beam being beam blocked, and transmit, to a base station and based on the determination, a beam blocking detection scheduling request.
  • the apparatus may include means for identifying that a UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam, determining that the failure is due to the first downlink beam being beam blocked, and transmitting, to a base station and based on the determination, a beam blocking detection scheduling request.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by a processor to identify that a UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam, determine that the failure is due to the first downlink beam being beam blocked, and transmit, to a base station and based on the determination, a beam blocking detection scheduling request.
  • transmitting the beam blocking detection scheduling request further may include operations, features, means, or instructions for selecting a cyclic shift to apply to a PUCCH message that includes the beam blocking detection scheduling request, where the cyclic shift may be selected based on inclusion of the beam blocking detection scheduling request in the PUCCH message, and transmitting the PUCCH message in accordance with the cyclic shift.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, in response to the beam blocking detection scheduling request, a grant for transmission of a channel state information report comprising beam blocking detection information, and transmitting the channel state information report to the base station in accordance with the grant.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the base station, a retransmission of the one or more scheduled downlink transmissions on a second downlink beam in a set of active beams utilized by the UE.
  • the second downlink beam is based at least in part on the channel state information report transmitted to the base station.
  • transmitting the beam blocking detection scheduling request further may include operations, features, means, or instructions for transmitting the beam blocking detection scheduling request multiplexed with a hybrid automatic repeat request feedback message, a different scheduling request, or a combination thereof.
  • the hybrid automatic repeat request feedback message may be one or two bits, the different scheduling request may be one bit, and the beam blocking detection scheduling request may be one bit.
  • the beam blocking detection scheduling request may have a higher priority than the different scheduling request.
  • transmitting the beam blocking detection scheduling request further may include operations, features, means, or instructions for transmitting the beam blocking detection scheduling request multiplexed with other information included in a PUCCH message.
  • transmitting the beam blocking detection scheduling request further may include operations, features, means, or instructions for transmitting the beam blocking detection scheduling request instead of transmitting a beam failure scheduling request.
  • determining that the failure is due to the first downlink beam being beam blocked further may include operations, features, means, or instructions for determining that beam blocking is a cause of the failure by distinguishing the cause from at least one of fading or interference.
  • transmitting the beam blocking detection scheduling request may include operations, features, means, or instructions for transmitting a PUCCH message that includes the beam blocking detection scheduling request, where a format of the PUCCH message may be one of format 0, format 1, format 2, format 3, or format 4, the PUCCH message including an additional bit for the beam blocking detection scheduling request.
  • transmitting the beam blocking detection scheduling request further may include operations, features, means, or instructions for transmitting the beam blocking detection scheduling request on a set of uplink beams.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, pursuant to the beam blocking detection scheduling request, a grant for transmission of a CSI report including beam blocking detection information, and transmitting the CSI report to the base station in accordance with the grant.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the base station, a retransmission of the one or more scheduled downlink transmissions on a second downlink beam based on the CSI report transmitted to the base station.
  • the grant may be received via a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) message on a second downlink beam.
  • SPS semi-persistent scheduling
  • PDSCH physical downlink shared channel
  • the CSI report may be transmitted on an uplink beam that may have reciprocity with the second downlink beam.
  • a method of wireless communications at a base station may include transmitting, to a UE, one or more scheduled downlink transmissions on a first downlink beam and receiving, from the UE, a beam blocking detection scheduling request indicative that the UE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • 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, to a UE, one or more scheduled downlink transmissions on a first downlink beam and receive, from the UE, a beam blocking detection scheduling request indicative that the UE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • the apparatus may include means for transmitting, to a UE, one or more scheduled downlink transmissions on a first downlink beam and receiving, from the UE, a beam blocking detection scheduling request indicative that the UE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by a processor to transmit, to a UE, one or more scheduled downlink transmissions on a first downlink beam and receive, from the UE, a beam blocking detection scheduling request indicative that the UE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • receiving the beam blocking detection scheduling request further may include operations, features, means, or instructions for receiving a PUCCH message that includes the beam blocking detection scheduling request, where the PUCCH message includes a cyclic shift that may be indicative of inclusion of the beam blocking detection scheduling request in the PUCCH message.
  • receiving the beam blocking detection scheduling request further may include operations, features, means, or instructions for receiving the beam blocking detection scheduling request multiplexed with a hybrid automatic repeat request feedback message, a different scheduling request, or a combination thereof.
  • the hybrid automatic repeat request feedback message may be one or two bits, the different scheduling request may be one bit, and the beam blocking detection scheduling request may be one bit.
  • the beam blocking detection scheduling request may have a higher priority than the different scheduling request.
  • receiving the beam blocking detection scheduling request further may include operations, features, means, or instructions for receiving the beam blocking detection scheduling request multiplexed with other information included in a PUCCH message.
  • receiving the beam blocking detection scheduling request further may include operations, features, means, or instructions for receiving the beam blocking detection scheduling request instead of receiving a beam failure scheduling request.
  • receiving the beam blocking detection scheduling request may include operations, features, means, or instructions for receiving a PUCCH message that includes the beam blocking detection scheduling request, where a format of the PUCCH message may be one of format 0, format 1, format 2, format 3, or format 4, the PUCCH message including an additional bit for the beam blocking detection scheduling request.
  • receiving the beam blocking detection scheduling request further may include operations, features, means, or instructions for receiving the beam blocking detection scheduling request on a set of uplink beams.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, pursuant to the beam blocking detection scheduling request, a grant for uplink transmission of a CSI report including beam blocking detection information, and receiving the CSI report from the UE in accordance with the grant.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the UE, a retransmission of the one or more scheduled downlink transmissions on a second downlink beam based on the CSI report received by the base station.
  • the grant may be transmitted via a SPS PDSCH message on a second downlink beam.
  • the CSI report may be received on an uplink beam that may have reciprocity with the second downlink beam.
  • FIGs. 1 through 3 illustrate examples of systems for wireless communications that support beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example of a communications procedure that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • FIGs. 5A through 5C and 6A through 6C illustrate examples of phase rotation diagrams that support beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • FIG. 7 illustrates an example of a process flow that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • FIGs. 8 and 9 show block diagrams of devices that support beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • FIG. 10 shows a block diagram of a communications manager that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • FIG. 11 shows a diagram of a system including a device that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • FIGs. 12 and 13 show block diagrams of devices that support beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • FIG. 14 shows a block diagram of a communications manager that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • FIG. 15 shows a diagram of a system including a device that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • FIGs. 16 through 19 show flowcharts illustrating methods that support beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • a user equipment may be configured to perform beam blocking detection and to include additional information in a feedback message for improved link adaptation based on the beam blocking detection.
  • a base station may receive a negative acknowledgement (NACK) from a UE indicating that the UE was unable to successfully decode a transmission from the base station (e.g., as part of a beam failure recovery procedure).
  • NACK negative acknowledgement
  • the base station may be capable of adapting the modulation and coding scheme (MCS), the resource block group (RBG), and the transmission configuration indicator (TCI) state (e.g., beam) to attempt a successful retransmission.
  • MCS modulation and coding scheme
  • RBG resource block group
  • TCI transmission configuration indicator
  • the base station may not be able to determine why the transmission was not decoded successfully.
  • the base station may determine a link adaptation without sufficient information about the failure from the UE.
  • This link adaptation may be excessive or unable to improve the link between the base station and the UE.
  • a base station may unnecessarily determine to perform a beam sweep to switch to a new beam based on receiving a NACK from the UE.
  • the decoding failure at the UE, prompting the beam sweep at the base station may have been due to temporary interference from a neighbor cell.
  • a retransmission from the base station on the same beam in a different resource might have been a better link adaptation than switching beams, as the beam switch could change other cell interference in the system, which may require inter-cell coordination.
  • the inefficient link adaptation and beam failure recovery procedure described above may be avoided by configuring a UE to transmit beam blocking detection information to the base station in addition to NACK feedback.
  • the UE may transmit a beam blocking detection scheduling request message along with a NACK to the base station, such as in a physical uplink control channel (PUCCH).
  • the UE may be configured to determine a cyclic shift to apply to the PUCCH based on the determination that the failure to decode is based on beam blocking.
  • the UE may transmit the beam blocking detection scheduling request over one or more uplink beams via beam sweeping.
  • the beam blocking scheduling request message may request a grant for the UE to transmit a channel state information (CSI) report to the base station that includes the beam blocking detection information.
  • the UE may receive the grant from the base station, and transmit the beam blocking detection CSI report (e.g., wideband CSI report and related CSI statistics) to the base station based on the received grant.
  • the base station may adapt one or more communication parameters for communications with the UE based on the beam blocking detection CSI report.
  • a UE and base station may avoid unnecessary power consuming procedures (e.g., beam sweeping) when configured for beam blocking detection.
  • the configuration of beam blocking detection and reporting may allow the UE and base station to communicate with improved reliability when compared to no beam blocking detection and reporting based on informed beam switching that results in reduced errors.
  • a base station may be transmitting high priority information (e.g., ultra-reliable latency communications (URLLC)), or some other information, and as such, if a UE fails to successfully receive the transmission, the base station may need to retransmit the transmission quickly (e.g., within a couple milliseconds).
  • the UE may be configured to perform a beam failure recovery procedure in response to failing to receive a transmission.
  • a beam failure recovery procedure may include the UE and base station reestablishing a connection (and take more than a couple of milliseconds, such as 10 milliseconds, for example).
  • a UE and/or base station may be configured to at least first perform beam blocking detection (e.g., to determine whether the UE failed to receive a transmission due to beam blocking (rather than beam failure, interference, fading). If the failure to receive the scheduled transmission was due to beam blocking, the UE may transmit a beam blocking indication to the base station (e.g., where the UE and base station may perform the beam blocking detection and indication procedure in one or more milliseconds).
  • the configuration of beam blocking detection and reporting may allow the UE and base station to communicate with improved reliability (e.g., such as to perform URLLC communications). Accordingly, there may be improved system spectral efficiency due to less interference from less beam switching and fewer retransmissions.
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspect are then described with respect to a communications procedure, phase rotation diagrams, 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 beam blocking detection scheduling request transmission procedures.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports beam blocking detection scheduling request transmission procedures 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 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., JV ⁇ ) 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 the network operators IP services 150.
  • the operators IP services 150 may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a 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 base station 105 or a UE 115 may use beam sweeping techniques as part of beam forming operations.
  • a base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with aUE 115.
  • Some signals e.g., synchronization signals, reference signals, beam selection signals, or other control signals
  • the base station 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission.
  • Transmissions in different beam directions may be used to identify (e.g., by a transmitting device, such as a base station 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the base station 105.
  • a transmitting device such as a base station 105
  • a receiving device such as a UE 115
  • Some signals may be transmitted by a base station 105 in a single beam direction (e.g., a direction associated with the receiving device, such as a UE 115).
  • the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted in one or more beam directions.
  • a UE 115 may receive one or more of the signals transmitted by the base station 105 in different directions and may report to the base station 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
  • transmissions by a device may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from a base station 105 to a UE 115).
  • the UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across a system bandwidth or one or more sub-bands.
  • the base station 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a CSI reference signal (CSI-RS)), which may be precoded or unprecoded.
  • a reference signal e.g., a cell-specific reference signal (CRS), a CSI reference signal (CSI-RS)
  • the UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook).
  • PMI precoding matrix indicator
  • codebook-based feedback e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook.
  • a receiving device may try multiple receive configurations (e.g., directional listening) when receiving various signals from the base station 105, such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • receive configurations e.g., directional listening
  • a receiving device may try multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions.
  • receive beamforming weight sets e.g., different directional listening weight sets
  • a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal).
  • the single receive configuration may be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).
  • SNR signal-to-noise ratio
  • the UEs 115 and the base stations 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly over a communication link 125.
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)).
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the medium access control (MAC) layer in poor radio conditions (e.g., low signal-to-noise conditions).
  • MAC medium access control
  • a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • a UE 115 may be configured to transmit beam blocking detection information to a base station 105 in addition to NACK feedback upon a failure by the UE 115 to decode one or more scheduled downlink transmissions.
  • the beam blocking detection information may be based on a beam blocking detection procedure.
  • a UE 115 may attempt to decode one or more scheduled physical downlink shared channel (PDSCH) messages (e.g., a semi-persistent scheduling (SPS) PDSCH message). If the UE 115 is able to decode the one or more scheduled PDSCH messages successfully, the UE 115 may transmit a positive acknowledgment (ACK) to the base station 105.
  • PDSCH physical downlink shared channel
  • SPS semi-persistent scheduling
  • the UE 115 may perform a beam blocking evaluation such that the UE 115 may determine whether a set of signal strength parameters associated with the one or more scheduled PDSCH messages are each below preconfigured thresholds, where each signal strength parameter may be associated with a preconfigured threshold. If the UE 115 determines that signal strength parameters are each below the preconfigured thresholds, the UE 115 may determine that the UE 115 failed to decode the one or more scheduled PDSCH messages due to beam blocking (e.g., partial beam blocking, full beam blocking).
  • beam blocking e.g., partial beam blocking, full beam blocking
  • the UE 115 may transmit a beam blocking detection scheduling request message multiplexed with a NACK to the base station, such as in a PUCCH.
  • the UE 115 may be configured to determine a cyclic shift to apply to the PUCCH based on the determination that the failure to decode is based on beam blocking.
  • the UE 115 may transmit the beam blocking detection scheduling request over one or more uplink beams via beam sweeping to avoid transmitting solely on a beam that may be blocked.
  • the beam blocking scheduling request message may request a grant for the UE 115 to transmit a CSI report to the base station 105 that includes the beam blocking detection information.
  • the UE 115 may receive the grant from the base station 105 and transmit the beam blocking detection CSI report (e.g., wideband CSI report) to the base station 105 based on the received grant.
  • the base station 105 may adapt one or more communication parameters for communications with the UE 115 based on the beam blocking detection CSI report.
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • wireless communications system 200 may implement aspects of wireless communications system 100.
  • Wireless communications system 200 may include UE 115-a and base station 105-a, which may be respective examples of a UE 115 and a base station 105, as described with reference to FIG. 1.
  • UE 115-a may implement a beam blocking detection procedure and indicate beam blocking detection information to base station 105-a.
  • other wireless devices such as base station 105-a, may implement a beam blocking detection and indication procedure.
  • base station 105-a and UE 115-a may be in communication with one another.
  • base station 105-a may transmit information to UE 115-a on downlink 205-a
  • UE 115-a may transmit information to base station 105-a on uplink 205-b.
  • Base station 105-a may configure UE 115-a (e.g., via a radio resource control (RRC) message) to perform beam blocking detection and report the findings of the detection back to base station 105-a with feedback (e.g., ACK and NACK).
  • RRC radio resource control
  • an information element (IE) may be included in an RRC message, such as a CSI measurement configuration RRC message or a different configuration message.
  • the configuration may include parameters to use for beam blocking detection, such as one or more power thresholds or an indication of when to transmit NACK via uplink beam sweeping.
  • downlink 205-a and uplink 205-b may be configured for URLLC.
  • Base station 105-a may transmit PDSCH 210 using multiple TRPs. Specifically, a first transmission of PDSCH 210-a may be transmitted at a first time via beam 215-a, and a second transmission of PDSCH 210-b may be transmitted at a second time via beam 215-b.
  • the transmissions PDSCH 210-a and 210-b may include the same data packet and may both be assigned a same sequence number.
  • PDSCH 210 may be semi- persistently scheduled by base station 105-a, and wireless communications system 200 may be an internet of things (IoT) system that communicates semi-persistently using a small packet size periodically (e.g., every N milliseconds (ms)). In some cases, the traffic may not change in the IoT system.
  • IoT internet of things
  • UE 115-a may attempt to decode PDSCH 210. For example, UE 115-a may attempt a joint decoding of PDSCH 210-a and 210-b. In some cases, UE 115-a may not be able to successfully decode one or both PDSCH 210. Unsuccessful decoding may be a result of beam blocking, downlink interference, cross link interference, fading, as well as many other reasons. Accordingly, UE 115-a may evaluate if the decoding failure was due to beam blocking of downlink 205-a.
  • UE 115-a may determine if complete beam blocking occurred during the transmission of PDSCH 210 based on comparing one or more signal parameters to one or more power thresholds (e.g., layer 1 or layer 3 reference signal received power (RSRP)). If beam blocking occurred (e.g., complete beam blocking, or partial beam blocking), UE 115-a may report the blocking (e.g., in a CSI-RS report) and request a new downlink beam from base station 105-a for retransmission along with a NACK in PUCCH 220 via an uplink beam sweep 215-c.
  • RSRP reference signal received power
  • UE 115-a may request a grant to transmit the CSI report rather than waiting for a preconfigured periodic CSI reporting occasion or waiting for base station 105-a to trigger a CSI reporting occasion.
  • UE 115-a may transmit a beam blocking detection scheduling request in a PUCCH along with the NACK.
  • UE 115-a may be configured to determine a cyclic shift to apply to the PUCCH based on the PUCCH including the beam blocking detection scheduling request.
  • Base station 105-a may receive the PUCCH including the beam blocking detection scheduling request and transmit a grant to UE 115-a. Based on receiving the grant, UE 115-a may transmit a CSI report including the beam blocking detection information including an indication of whether the decoding failure was due to beam blocking, a request for a new downlink beam, etc.
  • UE 115-a may request either a lower MCS relative to the MCS used for PDSCH 210 and a same downlink beam, or the same or different MCS for retransmission on a new beam different from beams 215-a and 215-b.
  • UE 115-a may report this information in the NACK of PUCCH 220 or a CSI-RS report to base station 105-a. This determination may indicate that the decoding failure was a result of slow fading or downlink interference from another cell, which may benefit from a lower MCS but may not benefit from a new beam.
  • Base station 105-a may receive the NACK, beam blocking detection scheduling request, and beam detection information via one or more PUCCH messages 220. Consequently, base station 105-a may perform a retransmission using adjusted communication parameters, such as MCS or TCI state, based on the beam detection information. Thus, base station 105-a may make an informed decision about what communication adaptation actions to take to efficiently retransmit to UE 115-a, and to transmit other transmissions to UE 115-a.
  • adjusted communication parameters such as MCS or TCI state
  • the base station 105 may be transmitting high priority information (e.g., URLLC), or some other information, and as such, if the UE 115 fails to successfully receive a high priority transmission, the base station 105 may need to retransmit the transmission quickly (e.g., within a couple milliseconds).
  • the UE 115 may be configured to perform a beam failure recovery procedure in response to failing to receive a transmission.
  • a beam failure recovery procedure may include the UE 115 and base station 105 reestablishing a connection (and take more than a couple of milliseconds (e.g., 10 milliseconds, for example).
  • a UE 115 and/or base station 105 may be configured to perform beam blocking detection and indication procedure (e.g., to determine whether the UE 115 failed to receive a transmission due to beam blocking (rather than beam failure, interference, fading). If the failure to receive the scheduled transmission was due to beam blocking, the UE 115 may transmit a beam blocking indication to the base station 105 (e.g., where the UE 115 and base station may perform the beam blocking detection and indication procedure in one or more milliseconds).
  • the configuration of beam blocking detection and reporting may allow the UE 115 and base station 105 to communicate with improved reliability (e.g., such as to perform URLLC communications).
  • the UE 115 may perform beam blocking detection and transmit a beam blocking detection scheduling request. In some cases, the UE 115 may receive the retransmission as a result of transmitting the beam blocking detection scheduling request (e.g., without performing a beam failure recovery procedure). In some implementations, if the UE 115 fails to receive the retransmission in response to the beam blocking detection scheduling request, the UE 115 may then transmit a second beam blocking detection scheduling request, or perform a beam failure recovery procedure (e.g., in which the UE 115 may transmit a beam failure recovery request).
  • a beam failure recovery procedure e.g., in which the UE 115 may transmit a beam failure recovery request.
  • FIG. 3 illustrates an example of a wireless communications system 300 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • wireless communications system 300 may implement aspects of wireless communications systems 100 and 200.
  • Wireless communications system 300 may include UE 115-b and base station 105-b, which may be respective examples of a UE 115 and a base station 105, as described with reference to FIGs. 1 and 2.
  • UE 115-b may implement a beam blocking detection procedure and indicate beam blocking detection information to base station 105-b.
  • other wireless devices such as base stations 105-b, may implement a beam blocking detection and indication procedure.
  • UE 115-b may be configured to communicate with base station 105-a.
  • Base station may be capable of transmitting one or more downlink messages via downlink beams 310-a, 310-b, 310-c, and 310-d.
  • Downlink beams 310-a, 310-b, 310-c, and 310-d may be reciprocal with uplink beams 315-a, 315-b, 315-c, and 315-d, respectively.
  • UE 115-b may be configured to receive downlink messages from base station 105-b via downlink beam 310-a.
  • base station 105-b may attempt a multi-TRP transmission of one or more PDSCH messages.
  • base station 105-b may transmit a PDSCH message to UE 115-b via at least beam 310-a.
  • an object 305 e.g., machine, person, equipment
  • base station 105-b and UE 115-b may be in an industrial environment (e.g., factory, warehouse) or some other mobile environment in which objects frequently move.
  • a beam may be blocked if there is a fast decrease in useful signal strength received (e.g., SbeamiD) from a number (e.g., #N) of adjacent beams to the currently used beam, M, (e.g., beamlD e Set: ⁇ M,M + N ⁇ ).
  • a beam may be blocked if there is degradation across the whole system bandwidth, W for a given duration, T.
  • a beam may be blocked if the useful signal strength from a potentially blocked beam (e.g., with beamlD S beamID e Set: ⁇ M, M + N ⁇ ) is below a noise floor, RxsensitiyLevei.
  • a beam may be blocked if erroneous reception occurs (e.g., signal to interference plus noise ratio (SINR) ⁇ SINRThreshoid).
  • SINRThreshoid signal to interference plus noise ratio
  • SbeamiD with beamlD g Set: ⁇ M,M + N ⁇ ) is above a noise floor, RxsensitiyLevei.
  • beam switching may provide a viable link.
  • detecting and adapting communications to account for beam blocking may be a higher priority than detecting and adapting communications to account for interference. For example, if beam blocking occurs, interference may have little to no additional impact on the system. If erroneous reception occurs (e.g., SINR ⁇ SINRThreshoid) with low interference (e.g., I ⁇ SINRThreshoid) then the erroneous reception is likely due to beam blocking.
  • UE 115-b may perform a decoding procedure for the PDSCH message, but the decoding may be unsuccessful (e.g., decoding failure).
  • UE 115-b may perform a beam blocking detection procedure to determine whether the cause of the decoding failure (e.g., beam blocking, interference, fading), because not all causes may be solved by changing downlink beams or TCI states. For example, if the cause of the decoding failure is due to interference or fading, the PDSCH may be successfully retransmitted and decoded if the PDSCH is transmitted at a lower MCS without changing beams. Changing downlink beams in the cases of interference and fading may result in an inefficient use of resources.
  • the cause of the decoding failure e.g., beam blocking, interference, fading
  • UE 115-b may perform a beam blocking detection procedure to determine whether the cause of the decoding failure was due to beam blocking.
  • the beam blocking detection procedure may include UE 115-b comparing a set of signal strength parameters to a set of thresholds (e.g., power thresholds) defined for each signal strength parameter. For example, UE 115-b may perform comparison 1, comparison 2, comparison 3, or a combination thereof. In some cases, comparisons 1 through 3 may be associated with layer 3 (L3) signal measurements. If the signal strength parameter for one or more of the comparisons is below the defined threshold, UE 115-a may determine that unsuccessful decoding is due to beam blocking.
  • L3 layer 3
  • UE 115-b may determine whether the received signal strength associated with downlink beam 310-a that is averaged over the bandwidth of the system, or BWP and is averaged over a beam blocking duration (e.g., beam block coherence time) is below a threshold.
  • a beam blocking duration e.g., beam block coherence time
  • UE 115-b may determine whether the maximum received signal strength associated with downlink beams 310, among the resource blocks, that is averaged over a beam blocking duration (e.g., beam blocking coherence time) is below a threshold.
  • a beam blocking duration e.g., beam blocking coherence time
  • UE 115-b may determine whether the received signal strength associated with downlink beam 310-a, on at least a preconfigured number of, X, physical resource blocks (PRBs), or a preconfigured percentage (e.g., Y%) of PRBs within a BWP, that are averaged over a beam blocking duration (e.g., beam blocking coherence time) is below a threshold.
  • PRBs physical resource blocks
  • a preconfigured percentage e.g., Y%
  • UE 115-b may be configured to perform one or more additional comparisons. For example, UE 115-b may perform comparison 4, comparison 5, comparison 6, or a combination thereof to strengthen the determination that unsuccessful decoding was due to beam blocking. In some cases, comparisons 4 through 6 may be associated with layer 1 (LI) signal measurements. For comparison 4, UE 115-b may determine whether an instantaneous received signal strength associated with downlink beam 310-a that is averaged over a system bandwidth is below a threshold. Comparison 4 is as follows:
  • UE 115-b may determine whether an instantaneous maximum received signal strength that is associated with downlink beams 310 among the resource blocks is below a threshold. Comparison 5 is as follows:
  • UE 115-b may determine whether a significant decrease in received signal strength associated with downlink beams 310 that is averaged over a system bandwidth is below a threshold. Comparison 6 is as follows:
  • UE 115-b and base station 105-b may communicate via downlink beam 310-a and a reciprocal uplink beam, such as uplink beam 315-a.
  • a reciprocal uplink beam such as uplink beam 315-a.
  • an object 305 may move to a location such that object 305 partially or completely blocks downlink beam 310-a and due to reciprocity, object 305 may block the corresponding uplink beam 315-a.
  • base station 105-b may transmit a scheduled downlink transmission to UE 115-b via downlink beam 310-a.
  • UE 115-b may attempt to receive the scheduled downlink transmission (e.g., PDSCH, SPS PDSCH) on downlink beam 310-a and UE 115-b may fail to successfully decode the downlink transmission.
  • UE 115-b may perform the beam blocking detection procedure and determine that UE 115-b could not successfully decode the downlink transmission due to beam blocking. Based on the determination that downlink beam 310-a is being blocked at time 320-a, UE 115-b may determine that reciprocal uplink beam 315-a may also be blocked.
  • UE 115-b may transmit a beam blocking detection scheduling request to base station 105-b over multiple uplink beams 315 in a beam sweeping manner to ensure the beam blocking detection scheduling request is received by base station 105-b.
  • Base station 105-b may receive the beam blocking scheduling request over one or more of the uplink beams 315 and select a downlink beam 310 that is reciprocal to an uplink beam 315 that base station 105-b received the beam blocking detection scheduling request on. In some cases, base station 105-b may select the downlink beam 310 based on one or more measurements of the received uplink beams 315, such as beam strength measurements, beam quality measurements, etc. The selection may be based on the strongest beam.
  • base station 105-b may transmit a grant over the selected downlink beam 310, where the grant may provide UE 115-b with a set of resources to transmit a beam blocking detection CSI report to base station 105-b to indicate that the failure to successfully decode the scheduled downlink transmission was due to beam blocking.
  • UE 115-b may be configured to perform one time beam blocking detection (e.g., aperiodic beam blocking detection).
  • UE 115-b may be configured to receive a downlink transmission from base station 105-b, such as an SPS transmission (e.g., SPS PDSCH).
  • UE 115-b may be configured with a number of, N, downlink beams for downlink transmission and a number of, K, downlink and uplink beams prepared for reference signal transmission (e.g., phase tracking reference signal (PTRS)).
  • PTRS phase tracking reference signal
  • the uplink beams and the downlink beams may have reciprocity.
  • UE 115-b may perform a beam blocking detection procedure.
  • UE 115-b may be able to quickly determine that beam blocking is occurring to mitigate the number of erroneous signals UE 115-b may receive.
  • UE 115-b may be configured to perform periodic beam blocking detection.
  • UE 115-b may be configured to perform beam blocking detection procedures after receiving a preconfigured number of, L (e.g., more than 1), erroneous receptions.
  • L e.g., more than 1
  • UE 115-b may transmit a NACK after each erroneous reception, then, upon determination that L erroneous receptions have occurred, UE 115-b may perform the beam blocking detection procedure.
  • UE 115-b may be configured to perform partial beam blocking detection.
  • partial beam blocking may occur when an object 305 partially blocks a beam 310 or 315.
  • the partially blocked beam may reflect off the object 305 and result in a weaker path to the receiving device (e.g., UE 115-b, or base station 105-b) than the original path associated with the original un-blocked beam.
  • UE 115-b may perform partial beam blocking procedures upon receiving a single erroneous transmission (e.g., one time blocking detection) or upon receiving a preconfigured number of, L (e.g., great that 1) erroneous transmissions (e.g., periodic blocking detection).
  • UE 115-b may be configured to distinguish between partial beam blocking and fading. Upon the determination that the one or more erroneous transmissions are due to partial beam blocking, UE 115-b may apply or request a lower MCS or apply or request a new beam allocation, with the same MCS.
  • FIG. 4 illustrates an example of a communications procedure 400 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • communication procedure 400 may be performed in wireless communications systems 100 through 300.
  • Communication procedure 400 may be performed between UE 115-c and base station 105-c, which may be respective examples of a UE 115 and a base station 105, as described with reference to FIGs. 1 through 3.
  • UE 115-c may implement a beam blocking detection procedure and trigger the transmission of beam blocking detection information by transmitting a beam blocking detections scheduling request to base station 105-c.
  • other wireless devices such as base stations 105-c, may implement a beam blocking detection and indication procedure.
  • a UE 115 (e.g., UE 115-c) and a base station (e.g., 105-c) may communicate in a wireless communication environment (e.g., 5GNR, industrial IoT).
  • base station 105-c may transmit an SPS PDSCH 405 per cycle 445 on a preconfigured downlink beam 430 to indicate resource allocation, such as a PRB allocation.
  • base station 105-c may transmit SPS PDSCH 405-a on downlink beam 430-a in cycle 445-a that schedules the resources in cycle 445-a
  • base station 105-c may transmit SPS PDSCH 405-b on downlink beam 430-a that schedules the resources in cycle 445-b
  • base station 105-c may transmit SPS PDSCH 405-c on downlink beam 430-a in cycle 445-c.
  • UE 115-c may transmit an ACK or NACK to base station 105-c to indicate whether UE 115-c was able to successfully decode the SPS PDSCH transmission 405.
  • UE 115-c may transmit the ACK or NACK in a PUCCH transmission 420.
  • UE 115-c successfully decoded SPS PDSCH transmission 405-a and may transmit an ACK to base station 105-c in PUCCH 420-a.
  • UE 115-c may transmit PUCCH 420-a on uplink beam 435-a that has reciprocity with downlink beam 430-a.
  • base station 105-c may transmit an RRC Reconfiguration message 410 to modify an RRC connection.
  • base station 105-c may transmit RRC Reconfiguration message 410-a to UE 115-c to establish, modify, or release radio bearers, to perform handover, to setup, modify, or release measurements, or to indicate other communication information to UE 115-c, or a combination thereof.
  • RRC reconfiguration message 410-a may indicate CSI reporting configurations such as whether CSI reporting is configured periodically and at what periodicity, or semi-persistently, or aperiodically.
  • RRC reconfiguration message 410-a may indicate PUCCH formats to UE 115-c (e.g., whether UE 115-c should use format 0, 1, 2, 3, or 4 to transmit each PUCCH 420).
  • RRC reconfiguration message 410-a may configure communications for at least cycle 445-a, 445-b, and 445-c.
  • UE 115-c may transmit RRC Reconfiguration Complete message 425-a to indicate successful reconfiguration according to the information include in RRC Reconfiguration message 410-a.
  • a PUCCH may contain uplink control information (UCI), where the UCI may include one or more indications of ACK/NACK, one or more scheduling requests (e.g., a beam blocking detection scheduling request, beam failure related scheduling request, or some other scheduling request), or CSI, or some combination thereof.
  • the PUCCH may be transmitted according to one of five PUCCH formats, such as format 0, format 1, format 2, format 3, or format 4, where the format that is used may be determined and transmitted by the base station 105 to the UE 115.
  • the PUCCH format indication may be included in a configuration message, such as RRC Reconfiguration message 410-a.
  • the base station 105 may determine which PUCCH format the UE 115 should use based on the information the UE 115 is configured to include in the PUCCH. For example, the base station 105 may select the PUCCH format based on the number of bits configured to be carried in the PUCCH, or based on how many symbols the PUCCH is configured with, or a combination thereof.
  • formats 0 and 2 may be referred to as short PUCCH formats, as they may occupy at most two OFDM symbols.
  • PUCCH format 0 may be capable of transmitting at most two bits and span one or two OFDM symbols. This format can, for example, be used to transmit a hybrid-ARQ ACK/NACK of a downlink data transmission or to transmit a scheduling request.
  • PUCCH format 2 may be capable of transmitting more than two bits and may span one or two OFDM symbols.
  • PUCCH format 2 can, for example, be used to transmit CSI reports or for multi-bit hybrid-ARQ ACK/NACKs in the case that the UE 115 receives multiple downlink transmissions.
  • formats 1, 3 and 4 may be referred to as long PUCCH formats as each may occupy between 4 and fourteen OFDM symbols.
  • PUCCH format 1 may be capable of transmitting at most, 2 bits, and PUCCH formats 3 and 4 may be both capable of transmitting more than two bits but may differ in multiplexing capacity.
  • UE 115-c may be configured to perform periodic CSI reporting. For example, in cycle 445-a, base station 105-c and UE 115-c may perform CSI reporting procedure 440-a.
  • Base station 105-c may transmit CSI-RSs on one or more downlinks beams 430, such as on downlink beams 430-a, 430-b, 430-c, 430-d, and 430-e.
  • UE 115-c may perform one or more measurements (e.g., RSRP, received signal strength indicator (RSSI), reference signal received quality (RSRQ)) on the received CSI-RSs.
  • RSRP received signal strength indicator
  • RSSI reference signal received quality
  • UE 115-c may transmit a CSI report to base station 105-c to indicate the one or more measurements.
  • the CSI report may be included in a PUCCH 420, such as PUCCH 420-a.
  • UE 115-a may determine one or more preferred beams and explicitly or implicitly indicate the one or more preferred beams to base station 105-c.
  • UE 115-c may transmit a CSI report in PUCCH 420-a on uplink beam 435-a which may be reciprocal with a preferred downlink beam 430 determined by UE 115-c.
  • base station 105-c may transmit downlink control information (DCI) to UE 115-c via DCI message 415-a.
  • DCI message 415-a may include TCI preparation information.
  • base station 105-c may transmit SPS PDSCH message 405-b to UE 115-c using downlink beam 430-a.
  • UE 115-c may successfully receive and decode SPS PDSCH message 405-b and transmit an ACK in PUCCH message 420-c using beam 435-a.
  • base station 105-c and UE 115-c may perform another CSI reporting procedure 440-b.
  • the preferred beams may not change.
  • base station 105-c may transmit SPS PDSCH message 405-c to UE 115-c on downlink beam 430-a.
  • UE 115-c may attempt to receive and decode SPS message PDSCH 405-c.
  • UE 115-c may be unable to successfully decode SPS PDSCH message 405-c.
  • UE 115-c may perform a downlink detection procedure to determine whether UE 115-c failed to decode the downlink transmissions due to beam blocking.
  • the UE 115 may be configured to indicate beam blocking detection information in a CSI report.
  • UE 115-c may transmit CSI reports periodically, semi-persistently, or aperiodically, as configured in RRC Reconfiguration message 410-a.
  • a base station 105 may configure a UE 115 to transmit CSI reports periodically at a certain periodicity, such that the UE 115 transmits a CSI report based on the periodicity.
  • the base station 105 may configure the UE 115 to transmit the CSI report aperiodically, such that the UE 115 may transmit a CSI report upon being prompted by the base station 105.
  • the base station 105 may transmit a trigger to the UE 115, and in response to receiving the trigger, the UE 115 may transmit the CSI report.
  • waiting to transmit the beam blocking detection information in a CSI report until a CSI trigger is received from the base station or based on a configured CSI periodicity may be inefficient because communications on the blocked beam may continue until the beam blocking detection information is received by the base station 105.
  • the UE 115 may be configured to transmit a beam blocking detection scheduling request to the base station 105 in response to detecting the beam blocking.
  • the beam blocking detection scheduling request may trigger a CSI reporting occasion such that the scheduling request may request a set of uplink resources the UE 115 may use to transmit a CSI report (e.g., a wideband CSI report) that includes the beam blocking detection information (e.g., an indication that beam blocking occurred, a duration that UE 115 has detected the beam blocking, a request to change beams, a beam change recommendation).
  • UE 115-c may be configured to transmit the beam blocking detection scheduling request in a PUCCH 420, such a PUCCH 420-d.
  • uplink beam 435-a may also be blocked.
  • UE 115-c may transmit PUCCH 420-d in a beam sweeping manner, using multiple uplink beams 435, such as uplink beams 435-a, 435-b, 435-c, 435-d, or 435-e, or a combination thereof.
  • UE 115-c may determine a cyclic shift to apply to PUCCH message 420-d based on whether UE 115-c has a scheduling request to transmit and based on the PUCCH format UE 115-c was configured with.
  • Base station 105-c may receive the beam blocking detection scheduling request on one or more of the uplink beams 435.
  • Base station 105-c may determine a new downlink beam 430 for communications with UE 115-c. For example, base station 105-c may determine to communicate with UE 115-c via downlink beam 430-d.
  • new downlink beam 430-d may be determined based on a preferred beam that base station 105-c received PUCCH 420-d on.
  • base station may transmit DCI message 415-b on downlink beam 430-d that may indicate a beam change for PUCCH transmissions 420 (e.g., a new beam for wideband CSI reporting).
  • base station 105-c may transmit an SPS PDSCH message 405-d to UE 115-c on the downlink beam 430-d.
  • SPS PDSCH message 405-d may include a grant that may implicitly or explicitly indicate a set of uplink resources UE 115-c may use to transmit the CSI report including the beam blocking detection information.
  • the grant may indicate the resources for UE 115-c to transmit the CSI report in PUCCH message 420-e.
  • UE 115-c may transmit PUCCH 420-e on uplink beam 435-d.
  • uplink beam 435-d may have reciprocity with downlink beam 430-d.
  • base station 105-c may configure UE 115-c with PUCCH format 2, format 3, or format 4.
  • the beam blocking detection scheduling request may be multiplexed with HARQ ACK/NACK, CSI reporting, other scheduling requests, or other information, or a combination thereof.
  • base station 105-c may configure UE 115-c with PUCCH format 0 or format 1.
  • the PUCCH 420 may be configured to include an additional bit.
  • UE 115-c may be configured to select a cyclic shift to apply to the PUCCH 420 carrying the beam blocking detection scheduling request.
  • FIGs. 5A, 5B, and 5C illustrate examples of phase rotation diagrams 500, 501, and 502, respectively that support beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • phase rotation diagrams 500, 501, and 502 may implemented in wireless communications systems 100 through 300.
  • Phase rotation diagrams 500, 501, and 502 may be utilized by a UE or base station, which may be respective examples of a UE and a base station, as described with reference to FIGs. 1 through 4.
  • a UE may implement a beam blocking detection procedure and transmit a beam blocking detection scheduling request to a base station by determining a cyclic shift according to the phase rotation diagrams 500, 501, and 502.
  • Phase rotation diagrams 500, 501, and 502 may be referred to as constellation diagrams, cyclic shift diagrams, etc.
  • other wireless devices such as a base station, may implement a beam blocking detection and indication procedure using the phase rotation diagrams 500, 501, and 502.
  • Phase rotation diagrams 500, 501, and 502 may represent how a signal is modulated by a digital modulation scheme, such as quadrature amplitude modulation or phase-shift keying.
  • the signal may be displayed as a two-dimensional diagram, where the angle of a point around the diagram represents the phase shift of the carrier wave from a reference phase. The distance of a point from the origin may represent a measure of the amplitude or power of the signal.
  • Each symbol, representing a number of bits of information may be encoded as a different combination of amplitude and phase of the carrier. As such, each symbol may be represented by a point on the phase rotation diagram.
  • the phase rotation diagrams may illustrate the possible symbols that may be transmitted by a device as a collection of points. As such, a receiving device may receive a transmission and determine the information included in the transmission based on the phase shift at which the signal was transmitted.
  • a UE may be configured with PUCCH format 0 or 1 and UE 115 may utilize PUCCH formats 0 or 1 to transmit a beam blocking detection scheduling request.
  • the UE may determine a cyclic shift (e.g., sequence shift, phase rotation shift) to apply to PUCCH formats 0 and 1.
  • the information bits e.g., number of downlink transmissions, HARQ ACK value, type of scheduling request
  • a cyclic shift may be applied to other PUCCH formats.
  • the UE may determine whether to apply a cyclic shift to the PUCCH transmission. If the UE determines to apply a cyclic shift to the PUCCH, the UE may determine which cyclic shift to apply. In some cases, the UE may be configured with cyclic shift mappings to determine the cyclic shifts. The mappings may be the same or different between PUCCH formats, such as PUCCH format 0 and format 1. The mappings may be stored as a lookup table in memory or using some other format. In some cases, the number of downlink transmissions the UE is scheduled to receive, decode, and transmit HARQ feedback for may determine which lookup table the UE uses.
  • a UE may be scheduled to receive multiple (e.g., two) downlink transmissions from a base station corresponding to a same HARQ feedback opportunity. As such the UE may attempt to receive and decode both downlink transmissions and transmit HARQ feedback to the base station indicating whether the UE was able to decode one or more of the downlink transmissions. Based on the two scheduled downlink transmissions, the UE may use the lookup tables and phase rotation diagrams as described with reference to FIGs. 5A, 5B, and 5C.
  • the HARQ feedback may be included in a PUCCH that may also include one scheduling request such as a beam blocking detection scheduling request or some other scheduling request.
  • the type of scheduling request the UE determines to transmit may determine which lookup table, value in a lookup table, or phase rotation diagram the UE uses to generate the HARQ feedback signal. For example, if the UE does not have a scheduling request to transmit, the UE may refer to phase rotation diagram 500. If the UE determines to transmit a non-beam blocking detection scheduling request, the UE may refer to phase rotation diagram 501. If the UE determines to transmit a beam blocking detection scheduling request, the UE may refer to phase rotation diagram 502.
  • phase rotation diagram 502 may support any combination of HARQ feedback signaling — for example, the phase rotation diagram 502 may support transmitting an ACK or NACK for a first downlink message, an ACK or NACK for a second downlink message, a scheduling request or no scheduling request, a beam blocking detection scheduling request or no beam blocking detection scheduling request, or any combination thereof. If the UE is configured to receive one scheduled transmission, the UE may use the lookup table(s) and phase rotation diagram(s) as described with reference to FIGs. 6A, 6B, and 6C.
  • FIG. 5A illustrates the case where the UE is configured with PUCCH format 0, has two downlink transmissions to submit feedback for, and does not have a scheduling request message to transmit.
  • the UE may be configured to transmit a beam blocking detection scheduling request periodically.
  • the UE may transmit a beam blocking detection scheduling request after a certain number of unsuccessful decoding of downlink transmission.
  • the UE may transmit HARQ ACK/NACKs to the base station without scheduling requests.
  • the UE may not refer to a lookup table, and may not apply a cyclic shift to the PUCCH.
  • the UE may transmit (NACK, ACK) in the PUCCH according to position 11 of phase rotation diagram 500 such that no cyclic shift is applied. If the UE does not successfully decode either the first downlink transmission or the second downlink transmission, the UE may transmit (NACK, NACK) in the PUCCH according to position 2 of phase rotation diagram 500 such that a 90 degree phase shift is applied. If the UE successfully decoded the first downlink transmission and did not successfully decode the second downlink transmission, the UE may transmit (ACK, NACK) in the PUCCH according to position 5 of phase rotation diagram 500 such that a phase shift of 180 degrees is applied.
  • the UE may transmit (ACK, ACK) in the PUCCH according to position 8 of phase rotation diagram 500 such that a 270 degree phase shift is applied.
  • PUCCH format 1 may be configured similarly.
  • the UE may refer to Table 1.
  • a similar table may be configured for PUCCH format 1 or some other PUCCH format.
  • FIG. 5B illustrates Table 1.
  • a zero may refer to a NACK and a one may refer to an ACK.
  • an inability to successfully decode a first transmission and a second transmissions may result in a ⁇ 0,0 ⁇ , where the UE may determine to shift the PUCCH transmission according to a cyclic shift of 1 based on Table 1 and as illustrated in FIG. 5B.
  • the UE may apply a cyclic shift of 4 to the PUCCH.
  • the UE may apply a cyclic shift of 7 to the PUCCH. In another example, if the UE does not successfully decode the first downlink transmission and successfully decodes the second downlink transmission, the UE may apply a cyclic shift of 10 to the PUCCH.
  • a positive indication in the phase rotation diagrams (e.g., +SR, +BDSR) may represent that the UE is transmitting the scheduling request, a negative indication in the phase rotation diagrams (e.g., -SR, -BDSR) may represent that the UE is not transmitting the scheduling request.
  • UE In the cases that the UE is configured with PUCCH format 0, has two downlink transmissions to submit feedback for, and has one beam blocking detection scheduling request (e.g., +BDSR) to transmit, UE may refer to Table 2. A similar table may be configured for PUCCH format 1.
  • FIG. 5C illustrates a combination of Table 1 and Table 2.
  • a zero may refer to a NACK and a one may refer to an ACK.
  • an inability to successfully decode a first transmission and a second transmissions may result in a ⁇ 0,0 ⁇ , where the UE may determine to shift the PUCCH transmission according to a cyclic shift of 3 based on Table 2 and as illustrated in FIG. 5C.
  • the UE may apply a cyclic shift of 6 to the PUCCH.
  • the UE may apply a cyclic shift of 9 to the PUCCH. In another example, if the UE does not successfully decode the first downlink transmission and successfully decodes the second downlink transmission, the UE may apply a cyclic shift of 0 to the PUCCH.
  • FIGs. 6A, 6B, and 6C illustrate examples of phase rotation diagrams 600, 601, and 602 that support beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • phase rotation diagrams 600, 601, and 602 may implemented in wireless communications systems 100 through 300.
  • Phase rotation diagrams 600, 601, and 602 may be utilized by a UE or base station, which may be respective examples of a UE and a base station, as described with reference to FIGs. 1 through 4.
  • a UE may implement a beam blocking detection procedure and transmit a beam blocking detection scheduling request to a base station by determining a cyclic shift according to the phase rotation diagrams 600, 601, and 602.
  • Phase rotation diagrams 600, 601, and 602 may be referred to as constellation diagrams, cyclic shift diagrams, etc. Additionally or alternatively, other wireless devices, such as a base station, may implement a beam blocking detection and indication procedure using the phase rotation diagrams 600, 601, and 602.
  • a UE may be configured with PUCCH format 0 or 1 and UE 115 may utilize PUCCH formats 0 or 1 to transmit a beam blocking detection scheduling request.
  • the UE may determine a cyclic shift (e.g., sequence shift, phase rotation shift) to apply to PUCCH formats 0 and 1, or some other PUCCH format.
  • the information bits e.g., number of downlink transmissions, HARQ ACK value, type of scheduling request
  • the information bits e.g., number of downlink transmissions, HARQ ACK value, type of scheduling request
  • the UE may determine whether to apply a cyclic shift to the PUCCH transmission. If the UE determines to apply a cyclic shift to the PUCCH, the UE may determine which cyclic shift to apply. In some cases, the UE may be configured with cyclic shift mappings to determine the cyclic shifts. The mappings may be the same or different between PUCCH formats, such as PUCCH formats 0 and format 1. The mappings may be referred to as a lookup table. In some cases, the number of downlink transmissions the UE is scheduled to receive, decode, and transmit HARQ feedback for may determine which lookup table the UE uses.
  • a UE may be scheduled to receive one downlink transmission from a base station. As such the UE may attempt to receive and decode the downlink transmission and transmit HARQ feedback to the base station indicating whether the UE was able to decode the downlink transmissions. Based on the single scheduled downlink transmission, the UE may use the look tables and phase rotation diagrams as described with reference to FIGs. 6A, 6B, and 6C.
  • the HARQ feedback may be included in a PUCCH that may also include an indication of one scheduling request or an indication of two scheduling requests such as a beam blocking detection scheduling request or some other scheduling request.
  • the type of scheduling request the UE determines to transmit may determine which lookup table or phase rotation diagram the UE uses. In the case that the UE is configured to indicate one scheduling request in a 2-bit PUCCH, if the UE determines to transmit a non-beam blocking detection scheduling request, the UE may refer to phase rotation diagram 602. Similarly, if the UE determines to transmit a beam blocking detection scheduling request, the UE may refer to phase rotation diagram 601. In the case that the UE is configured to transmit an indication of two scheduling requests in a 3 -bit PUCCH, the UE may refer to phase rotation diagram 602. In some cases, the UE may determine not to transmit a scheduling request. In such cases, the UE may not apply a cyclic shift to the PUCCH transmission the includes the HARQ feedback.
  • the UE may refer to Table 3.
  • a similar table may be configured for PUCCH format 1 or some other PUCCH format.
  • FIG. 6A illustrates Table 3.
  • a zero may refer to a NACK and a one may refer to an ACK.
  • an inability to successfully decode the scheduled transmission may result in the UE applying a cyclic shift of 3 to the PUCCH based on Table 3 and as illustrated in FIG. 6A.
  • the UE may apply a cyclic shift of 9 to the PUCCH.
  • the UE In the case that the UE is configured with PUCCH format 0, has a single downlink transmission to submit feedback for, and has one beam blocking detection scheduling request to transmit, UE may refer to Table 4.
  • a similar table may be configured for PUCCH format 1 or some other PUCCH format.
  • FIG. 6B illustrates Table 4.
  • a zero may refer to a NACK and a one may refer to an ACK.
  • an inability to successfully decode the scheduled transmission may result in the UE applying a cyclic shift of 4 to the PUCCH based on Table 4 and as illustrated in FIG. 6B.
  • the UE may apply a cyclic shift of 10 to the PUCCH.
  • FIG. 6C illustrates the example where the UE is configured to transmit a 3-bit PUCCH to the base station, where 1 bit is allocated for HARQ feedback, one bit is allocated for a non-beam blocking detection scheduling request, and another bit is allocated for a beam blocking detection scheduling request.
  • the UE may be configured to refer to both Table 3 and Table 4.
  • FIG. 7 illustrates an example of a process flow 700 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the process flow 700 may illustrate an example beam blocking detection and reporting procedure.
  • UE 115-d may perform a beam blocking detection procedure and transmit a beam blocking detection scheduling request to base station 105-d.
  • Base station 105-d and UE 115-d may be examples of the corresponding wireless devices described with reference to FIGs. 1 through 6.
  • a different type of wireless device e.g., a base station 105 may perform a beam blocking detection procedure.
  • base station 105-d may transmit, to UE 115-d, one or more scheduled downlink transmissions on a first downlink beam.
  • the one or more scheduled downlink transmissions are each an SPS PDSCH transmission.
  • UE 115-d may identify that UE 115-d failed to decode one or more scheduled downlink transmissions directed to UE 115-d on the first downlink beam.
  • the failure to decode the one or more scheduled downlink transmission may be due to beam blocking, interference, fading, etc.
  • UE 115-d may determine that the failure is due to the first downlink beam being beam blocked. To determine that the failure is due to beam blocking, UE 115-d may perform a beam blocking detection procedure. For example, UE 115-d may compare one or more signal strength parameters to an associated threshold. If each signal strength parameter is below the threshold, then UE 115-d may determine that beam blocking (e.g., partial beam blocking, complete beam blocking) is occurring.
  • beam blocking e.g., partial beam blocking, complete beam blocking
  • UE 115-d may transmit, to base station 105-d and based on the determination, a beam blocking detection scheduling request. In some cases, UE 115-d may transmit the beam blocking detection scheduling request on a set of uplink beams. In some cases, to transmit to the beam blocking detection scheduling request, UE 115-d may select a cyclic shift to apply to a PUCCH message that may include the beam blocking detection scheduling request, where the cyclic shift is selected based on inclusion of the beam blocking detection scheduling request in the PUCCH message. UE 115-d may transmit the PUCCH message in accordance with the cyclic shift.
  • UE 115-d may transmit the beam blocking detection scheduling request multiplexed with a HARQ feedback message, a different scheduling request, or a combination thereof.
  • the HARQ feedback message may be one or two bits.
  • the different scheduling request may be one bit, and the beam blocking detection scheduling request may be one bit.
  • the beam blocking detection scheduling request may have a higher priority than the different scheduling request.
  • UE 115-d may transmit the beam blocking detection scheduling request multiplexed with other information included in the PUCCH message.
  • UE 115-d may transmit the beam blocking detection scheduling request instead of transmitting a beam failure scheduling request.
  • transmitting the beam blocking detection scheduling request may include transmitting a PUCCH message that includes the beam blocking detection scheduling request, where a format of the PUCCH message is one of format 0, format 1, format 2, format 3, or format 4.
  • the PUCCH message may include an additional bit for the beam blocking detection scheduling request.
  • UE 115-d may receive, pursuant to the beam blocking detection scheduling request, a grant for transmission of a CSI report including beam blocking detection information. UE 115-d may transmit the CSI report to the base station in accordance with the grant. UE 115-d may receive, from base station 105-d, a retransmission of the one or more scheduled downlink transmissions on a second downlink beam based on the CSI report transmitted to base station 105-d. In some cases, UE 115-d may receive the grant via an SPS PDSCH message on the second downlink beam. In some cases, the CSI report may be transmitted on an uplink beam that has reciprocity with the second downlink beam.
  • FIG. 8 shows a block diagram 800 of a device 805 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the device 805 may be an example of aspects of a UE 115 as described herein.
  • the device 805 may include a receiver 810, a communications manager 815, and a transmitter 820.
  • the device 805 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).
  • the receiver 810 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to beam blocking detection scheduling request transmission procedures, etc.). Information may be passed on to other components of the device 805.
  • the receiver 810 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11.
  • the receiver 810 may utilize a single antenna or a set of antennas.
  • the communications manager 815 may identify that the UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam, determine that the failure is due to the first downlink beam being beam blocked, and transmit, to a base station and based on the determination, a beam blocking detection scheduling request.
  • the communications manager 815 may be an example of aspects of the communications manager 1110 described herein.
  • the communications manager 815 may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communications manager 815, or its sub-components may be executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field- programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field- programmable gate array
  • the communications manager 815 may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components.
  • the communications manager 815, or its sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the communications manager 815, or its sub-components may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • I/O input/output
  • the transmitter 820 may transmit signals generated by other components of the device 805.
  • the transmitter 820 may be collocated with a receiver 810 in a transceiver module.
  • the transmitter 820 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11.
  • the transmitter 820 may utilize a single antenna or a set of antennas.
  • the communications manager 815 as described herein may be implemented to realize one or more potential advantages.
  • One implementation may allow the device 805 to more efficiently indicate feedback information. For example, a device 805 may determine that a failure to decode one or more downlink transmissions directed to the device 805 may be due to beam blocking, and the device 505 may indicate this to the transmitting device through a beam blocking detection scheduling request multiplexed with other feedback information.
  • a processor of a UE 115 may increase reliability and efficiency in the adaptation of communication parameters and the retransmission of scheduled transmissions between a UE 115 and a base station.
  • FIG. 9 shows a block diagram 900 of a device 905 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the device 905 may be an example of aspects of a device 805, or a UE 115 as described herein.
  • the device 905 may include a receiver 910, a communications manager 915, and a transmitter 935.
  • 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 receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to beam blocking detection scheduling request transmission procedures, etc.). Information may be passed on to other components of the device 905.
  • the receiver 910 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11.
  • the receiver 910 may utilize a single antenna or a set of antennas.
  • the communications manager 915 may be an example of aspects of the communications manager 815 as described herein.
  • the communications manager 915 may include a decoding failure identifier module 920, a beam blocking determination module 925, and a scheduling request module 930.
  • the communications manager 915 may be an example of aspects of the communications manager 1110 described herein.
  • the decoding failure identifier module 920 may identify that the UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam.
  • the beam blocking determination module 925 may determine that the failure is due to the first downlink beam being beam blocked.
  • the scheduling request module 930 may transmit, to a base station and based on the determination, a beam blocking detection scheduling request.
  • the transmitter 935 may transmit signals generated by other components of the device 905.
  • the transmitter 935 may be collocated with a receiver 910 in a transceiver module.
  • the transmitter 935 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11.
  • the transmitter 935 may utilize a single antenna or a set of antennas.
  • FIG. 10 shows a block diagram 1000 of a communications manager 1005 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the communications manager 1005 may be an example of aspects of a communications manager 815, a communications manager 915, or a communications manager 1110 described herein.
  • the communications manager 1005 may include a decoding failure identifier module 1010, a beam blocking determination module 1015, a scheduling request module 1020, a cyclic shift selection module 1025, an uplink control channel module 1030, a grant reception module 1035, a CSI report module 1040, and a retransmission reception module 1045. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).
  • the decoding failure identifier module 1010 may identify that the UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam.
  • the beam blocking determination module 1015 may determine that the failure is due to the first downlink beam being beam blocked.
  • the scheduling request module 1020 may transmit, to a base station and based on the determination, a beam blocking detection scheduling request.
  • the cyclic shift selection module 1025 may select a cyclic shift to apply to a PUCCH message that includes the beam blocking detection scheduling request, where the cyclic shift is selected based on inclusion of the beam blocking detection scheduling request in the PUCCH message.
  • the scheduling request module 1020 may transmit the PUCCH message in accordance with the cyclic shift.
  • the scheduling request module 1020 may transmit the beam blocking detection scheduling request multiplexed with a hybrid automatic repeat request feedback message, a different scheduling request, or a combination thereof.
  • the hybrid automatic repeat request feedback message is one or two bits
  • the different scheduling request is one bit
  • the beam blocking detection scheduling request is one bit.
  • the beam blocking detection scheduling request has a higher priority than the different scheduling request.
  • the scheduling request module 1020 may transmit the beam blocking detection scheduling request multiplexed with other information included in a PUCCH message. In some examples, the scheduling request module 1020 may transmit the beam blocking detection scheduling request instead of transmitting a beam failure scheduling request.
  • the uplink control channel module 1030 may transmit a PUCCH message that includes the beam blocking detection scheduling request, where a format of the PUCCH message is one of format 0, format 1, format 2, format 3, or format 4, the PUCCH message including an additional bit for the beam blocking detection scheduling request.
  • the scheduling request module 1020 may transmit the beam blocking detection scheduling request on a set of uplink beams.
  • the grant reception module 1035 may receive, pursuant to the beam blocking detection scheduling request, a grant for transmission of a CSI report including beam blocking detection information.
  • the CSI report module 1040 may transmit the CSI report to the base station in accordance with the grant.
  • the beam blocking determination module 1015 may determine that beam blocking is a cause of the failure by distinguishing the cause from at least one of fading or interference.
  • the retransmission reception module 1045 may receive, from the base station, a retransmission of the one or more scheduled downlink transmissions on a second downlink beam based on the CSI report transmitted to the base station.
  • the grant is received via a SPS PDSCH message on a second downlink beam.
  • the CSI report is transmitted on an uplink beam that has reciprocity with the second downlink beam.
  • the grant reception module 1035 may receive, in response to the beam blocking detection scheduling request, a grant for transmission of a channel state information report comprising beam blocking detection information.
  • the CSI report module 1040 may transmit the channel state information report to the base station in accordance with the grant.
  • the retransmission reception module 1045 may receive, from the base station, a retransmission of the one or more scheduled downlink transmissions on a second downlink beam in a set of active beams utilized by the UE.
  • the second downlink beam may be based on the channel state information report transmitted to the base station.
  • FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the device 1105 may be an example of or include the components of device 805, device 905, or a UE 115 as described herein.
  • the device 1105 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager 1110, an I/O controller 1115, a transceiver 1120, an antenna 1125, memory 1130, and a processor 1140. These components may be in electronic communication via one or more buses (e.g., bus 1145).
  • buses e.g., bus 1145
  • the communications manager 1110 may identify that the UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam, determine that the failure is due to the first downlink beam being beam blocked, and transmit, to a base station and based on the determination, a beam blocking detection scheduling request.
  • the I/O controller 1115 may manage input and output signals for the device 1105.
  • the I/O controller 1115 may also manage peripherals not integrated into the device 1105.
  • the I/O controller 1115 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1115 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system.
  • the EO controller 1115 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1115 may be implemented as part of a processor.
  • a user may interact with the device 1105 via the I/O controller 1115 or via hardware components controlled by the I/O controller 1115.
  • the transceiver 1120 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1120 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1120 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1125. However, in some cases the device may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 1130 may include random-access memory (RAM) and read-only memory (ROM).
  • RAM random-access memory
  • ROM read-only memory
  • the memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 1130 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 1140 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 1140 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1140.
  • the processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting beam blocking detection scheduling request transmission procedures).
  • the code 1135 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 1135 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1135 may not be directly executable by the processor 1140 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • FIG. 12 shows a block diagram 1200 of a device 1205 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the device 1205 may be an example of aspects of a base station 105 as described herein.
  • the device 1205 may include a receiver 1210, a communications manager 1215, and a transmitter 1220.
  • the device 1205 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).
  • the receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to beam blocking detection scheduling request transmission procedures, etc.). Information may be passed on to other components of the device 1205.
  • the receiver 1210 may be an example of aspects of the transceiver 1520 described with reference to FIG. 15.
  • the receiver 1210 may utilize a single antenna or a set of antennas.
  • the communications manager 1215 may transmit, to a UE, one or more scheduled downlink transmissions on a first downlink beam and receive, from the UE, a beam blocking detection scheduling request indicative that the UE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • the communications manager 1215 may be an example of aspects of the communications manager 1510 described herein.
  • the communications manager 1215 may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communications manager 1215, or its sub-components may be executed by a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.
  • the communications manager 1215 may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components.
  • the communications manager 1215, or its sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the communications manager 1215, or its sub-components may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • I/O input/output
  • the transmitter 1220 may transmit signals generated by other components of the device 1205.
  • the transmitter 1220 may be collocated with a receiver 1210 in a transceiver module.
  • the transmitter 1220 may be an example of aspects of the transceiver 1520 described with reference to FIG. 15.
  • the transmitter 1220 may utilize a single antenna or a set of antennas.
  • FIG. 13 shows a block diagram 1300 of a device 1305 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the device 1305 may be an example of aspects of a device 1205, or a base station 105 as described herein.
  • the device 1305 may include a receiver 1310, a communications manager 1315, and a transmitter 1330.
  • the device 1305 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 1310 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to beam blocking detection scheduling request transmission procedures, etc.). Information may be passed on to other components of the device 1305.
  • the receiver 1310 may be an example of aspects of the transceiver 1520 described with reference to FIG. 15.
  • the receiver 1310 may utilize a single antenna or a set of antennas.
  • the communications manager 1315 may be an example of aspects of the communications manager 1215 as described herein.
  • the communications manager 1315 may include a downlink transmission manager 1320 and a scheduling request manager 1325.
  • the communications manager 1315 may be an example of aspects of the communications manager 1510 described herein.
  • the downlink transmission manager 1320 may transmit, to a UE, one or more scheduled downlink transmissions on a first downlink beam.
  • the scheduling request manager 1325 may receive, from the UE, a beam blocking detection scheduling request indicative that the UE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • the transmitter 1330 may transmit signals generated by other components of the device 1305.
  • the transmitter 1330 may be collocated with a receiver 1310 in a transceiver module.
  • the transmitter 1330 may be an example of aspects of the transceiver 1520 described with reference to FIG. 15.
  • the transmitter 1330 may utilize a single antenna or a set of antennas.
  • FIG. 14 shows a block diagram 1400 of a communications manager 1405 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the communications manager 1405 may be an example of aspects of a communications manager 1215, a communications manager 1315, or a communications manager 1510 described herein.
  • the communications manager 1405 may include a downlink transmission manager 1410, a scheduling request manager 1415, an uplink control channel manager 1420, a grant transmission manager 1425, a CSI report manager 1430, and a retransmission manager 1435. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).
  • the downlink transmission manager 1410 may transmit, to a UE, one or more scheduled downlink transmissions on a first downlink beam.
  • the scheduling request manager 1415 may receive, from the UE, a beam blocking detection scheduling request indicative that the UE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • the scheduling request manager 1415 may receive a PUCCH message that includes the beam blocking detection scheduling request, where the PUCCH message includes a cyclic shift that is indicative of inclusion of the beam blocking detection scheduling request in the PUCCH message.
  • the scheduling request manager 1415 may receive the beam blocking detection scheduling request multiplexed with a hybrid automatic repeat request feedback message, a different scheduling request, or a combination thereof.
  • the hybrid automatic repeat request feedback message is one or two bits
  • the different scheduling request is one bit
  • the beam blocking detection scheduling request is one bit.
  • the beam blocking detection scheduling request has a higher priority than the different scheduling request.
  • the scheduling request manager 1415 may receive the beam blocking detection scheduling request multiplexed with other information included in a PUCCH message. In some examples, the scheduling request manager 1415 may receive the beam blocking detection scheduling request instead of receiving a beam failure scheduling request.
  • the uplink control channel manager 1420 may receive a PUCCH message that includes the beam blocking detection scheduling request, where a format of the PUCCH message is one of format 0, format 1, format 2, format 3, or format 4, the PUCCH message including an additional bit for the beam blocking detection scheduling request.
  • the scheduling request manager 1415 may receive the beam blocking detection scheduling request on a set of uplink beams.
  • the grant transmission manager 1425 may transmit, pursuant to the beam blocking detection scheduling request, a grant for uplink transmission of a CSI report including beam blocking detection information.
  • the CSI report manager 1430 may receive the CSI report from the UE in accordance with the grant.
  • the retransmission manager 1435 may transmit, to the UE, a retransmission of the one or more scheduled downlink transmissions on a second downlink beam based on the CSI report received by the base station.
  • the grant is transmitted via a SPS PDSCH message on a second downlink beam.
  • the CSI report is received on an uplink beam that has reciprocity with the second downlink beam.
  • FIG. 15 shows a diagram of a system 1500 including a device 1505 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the device 1505 may be an example of or include the components of device 1205, device 1305, or abase station 105 as described herein.
  • the device 1505 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager 1510, a network communications manager 1515, a transceiver 1520, an antenna 1525, memory 1530, a processor 1540, and an inter-station communications manager 1545. These components may be in electronic communication via one or more buses (e.g., bus 1550).
  • buses e.g., bus 1550
  • the communications manager 1510 may transmit, to a UE, one or more scheduled downlink transmissions on a first downlink beam and receive, from the UE, a beam blocking detection scheduling request indicative that the UE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • the network communications manager 1515 may manage communications with the core network (e.g., via one or more wired backhaul links). For example, the network communications manager 1515 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the transceiver 1520 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1520 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1520 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1525. However, in some cases the device may have more than one antenna 1525, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 1530 may include RAM, ROM, or a combination thereof.
  • the memory 1530 may store computer-readable code 1535 including instructions that, when executed by a processor (e.g., the processor 1540) cause the device to perform various functions described herein.
  • a processor e.g., the processor 1540
  • the memory 1530 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 1540 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 1540 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into processor 1540.
  • the processor 1540 may be configured to execute computer- readable instructions stored in a memory (e.g., the memory 1530) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting beam blocking detection scheduling request transmission procedures).
  • the inter-station communications manager 1545 may manage communications with other base station 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. For example, the inter-station communications manager 1545 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 1545 may provide an X2 interface within an LTE/LTE-A wireless communication network technology to provide communication between base stations 105.
  • the code 1535 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 1535 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1535 may not be directly executable by the processor 1540 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • FIG. 16 shows a flowchart illustrating a method 1600 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the operations of method 1600 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1600 may be performed by a communications manager as described with reference to FIGs. 8 through 11.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may identify that the UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam.
  • the operations of 1605 may be performed according to the methods described herein.
  • aspects of the operations of 1605 may be performed by a decoding failure identifier module as described with reference to FIGs. 8 through 11.
  • the UE may determine that the failure is due to the first downlink beam being beam blocked.
  • the operations of 1610 may be performed according to the methods described herein. In some examples, aspects of the operations of 1610 may be performed by a beam blocking determination module as described with reference to FIGs. 8 through 11.
  • the UE may transmit, to a base station and based on the determination, a beam blocking detection scheduling request.
  • the operations of 1615 may be performed according to the methods described herein. In some examples, aspects of the operations of 1615 may be performed by a scheduling request module as described with reference to FIGs. 8 through 11.
  • FIG. 17 shows a flowchart illustrating a method 1700 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the operations of method 1700 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1700 may be performed by a communications manager as described with reference to FIGs. 8 through 11.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may identify that the UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam.
  • the operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operations of 1705 may be performed by a decoding failure identifier module as described with reference to FIGs. 8 through 11.
  • the UE may determine that the failure is due to the first downlink beam being beam blocked.
  • the operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be performed by a beam blocking determination module as described with reference to FIGs. 8 through 11.
  • the UE may transmit, to a base station and based on the determination, a beam blocking detection scheduling request.
  • the operations of 1715 may be performed according to the methods described herein. In some examples, aspects of the operations of 1715 may be performed by a scheduling request module as described with reference to FIGs. 8 through 11.
  • the UE may receive, pursuant to the beam blocking detection scheduling request, a grant for transmission of a CSI report including beam blocking detection information.
  • the operations of 1720 may be performed according to the methods described herein. In some examples, aspects of the operations of 1720 may be performed by a grant reception module as described with reference to FIGs. 8 through 11.
  • the UE may transmit the CSI report to the base station in accordance with the grant.
  • the operations of 1725 may be performed according to the methods described herein. In some examples, aspects of the operations of 1725 may be performed by a CSI report module as described with reference to FIGs. 8 through 11.
  • FIG. 18 shows a flowchart illustrating a method 1800 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the operations of method 1800 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1800 may be performed by a communications manager as described with reference to FIGs. 12 through 15.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below.
  • a base station may perform aspects of the functions described below using special-purpose hardware.
  • the base station may transmit, to a UE, one or more scheduled downlink transmissions on a first downlink beam.
  • the operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be performed by a downlink transmission manager as described with reference to FIGs. 12 through 15.
  • the base station may receive, from the UE, a beam blocking detection scheduling request indicative that the UE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • the operations of 1810 may be performed according to the methods described herein. In some examples, aspects of the operations of 1810 may be performed by a scheduling request manager as described with reference to FIGs. 12 through 15.
  • FIG. 19 shows a flowchart illustrating a method 1900 that supports beam blocking detection scheduling request transmission procedures in accordance with aspects of the present disclosure.
  • the operations of method 1900 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1900 may be performed by a communications manager as described with reference to FIGs. 12 through 15.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below.
  • a base station may perform aspects of the functions described below using special-purpose hardware.
  • the base station may transmit, to a UE, one or more scheduled downlink transmissions on a first downlink beam.
  • the operations of 1905 may be performed according to the methods described herein. In some examples, aspects of the operations of 1905 may be performed by a downlink transmission manager as described with reference to FIGs. 12 through 15.
  • the base station may receive, from the UE, a beam blocking detection scheduling request indicative that the UE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • the operations of 1910 may be performed according to the methods described herein. In some examples, aspects of the operations of 1910 may be performed by a scheduling request manager as described with reference to FIGs. 12 through 15.
  • the base station may receive a PUCCH message that includes the beam blocking detection scheduling request, where a format of the PUCCH message is one of format 0, format 1, format 2, format 3, or format 4, the PUCCH message including an additional bit for the beam blocking detection scheduling request.
  • the operations of 1915 may be performed according to the methods described herein. In some examples, aspects of the operations of 1915 may be performed by an uplink control channel manager as described with reference to FIGs. 12 through 15.
  • Example 1 A method for wireless communications at a UE, comprising: identifying that the UE failed to decode one or more scheduled downlink transmissions directed to the UE on a first downlink beam; determining that the failure is due to the first downlink beam being beam blocked; and transmitting, to a base station and based at least in part on the determination, a beam blocking detection scheduling request.
  • Example 2 The method of example 1, wherein transmitting the beam blocking detection scheduling request further comprises: selecting a cyclic shift to apply to a PUCCH message that comprises the beam blocking detection scheduling request, wherein the cyclic shift is selected based at least in part on inclusion of the beam blocking detection scheduling request in the PUCCH message; and transmitting the PUCCH message in accordance with the cyclic shift.
  • Example 3 The method of any of examples 1 or 2, wherein transmitting the beam blocking detection scheduling request further comprises: transmitting the beam blocking detection scheduling request multiplexed with a hybrid automatic repeat request feedback message, a different scheduling request, or a combination thereof.
  • Example 4 The method of example 3, wherein the hybrid automatic repeat request feedback message is one or two bits, the different scheduling request is one bit, and the beam blocking detection scheduling request is one bit.
  • Example 5 The method of any of examples 3 or 4, wherein the beam blocking detection scheduling request has a higher priority than the different scheduling request.
  • Example 6 The method of any of examples 1 to 5, wherein transmitting the beam blocking detection scheduling request further comprises: transmitting the beam blocking detection scheduling request multiplexed with other information included in a PUCCH message.
  • Example 7 The method of any of examples 1 to 6, wherein transmitting the beam blocking detection scheduling request further comprises: transmitting the beam blocking detection scheduling request instead of transmitting a beam failure scheduling request
  • Example 8 The method of any of examples 1 to 7, wherein transmitting the beam blocking detection scheduling request comprises: transmitting a PUCCH message that includes the beam blocking detection scheduling request, wherein a format of the PUCCH message is one of format 0, format 1, format 2, format 3, or format 4, the PUCCH message comprising an additional bit for the beam blocking detection scheduling request.
  • Example 9 The method of any of examples 1 to 8, wherein transmitting the beam blocking detection scheduling request further comprises: transmitting the beam blocking detection scheduling request on a plurality of uplink beams.
  • Example 10 The method of any of examples 1 to 9, further comprising: receiving, pursuant to the beam blocking detection scheduling request, a grant for transmission of a CSI report comprising beam blocking detection information; and transmitting the CSI report to the base station in accordance with the grant.
  • Example 11 The method of example 10, further comprising: receiving, from the base station, a retransmission of the one or more scheduled downlink transmissions on a second downlink beam based at least in part on the CSI report transmitted to the base station.
  • Example 12 The method of any of examples 10 or 11, wherein the grant is received via a semi-persistent scheduling PDSCH message on a second downlink beam.
  • Example 13 The method of example 12, wherein the CSI report is transmitted on an uplink beam that has reciprocity with the second downlink beam.
  • Example 14 The method of any of examples 1 to 13, wherein determining that the failure is due to the first downlink beam being beam blocked further comprises: determining that beam blocking is a cause of the failure by distinguishing the cause from at least one of fading or interference.
  • Example 15 An apparatus comprising at least one means for performing a method of any of examples 1 to 14.
  • Example 16 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 examples 1 to 14.
  • Example 17 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 examples 1 to 14.
  • Example 18 A method for wireless communications at a base station, comprising: transmitting, to a user equipment (EGE), one or more scheduled downlink transmissions on a first downlink beam; and receiving, from the EGE, a beam blocking detection scheduling request indicative that the EGE failed to decode at least one of the one or more scheduled downlink transmissions due to the first downlink beam being beam blocked.
  • EGE user equipment
  • Example 19 The method of example 18, wherein receiving the beam blocking detection scheduling request further comprises: receiving a PE1CCH message that includes the beam blocking detection scheduling request, wherein the PUCCH message includes a cyclic shift that is indicative of inclusion of the beam blocking detection scheduling request in the PE1CCH message.
  • Example 20 The method of any of examples 18 or 19, wherein receiving the beam blocking detection scheduling request further comprises: receiving the beam blocking detection scheduling request multiplexed with a hybrid automatic repeat request feedback message, a different scheduling request, or a combination thereof.
  • Example 21 The method of example 20, wherein the hybrid automatic repeat request feedback message is one or two bits, the different scheduling request is one bit, and the beam blocking detection scheduling request is one bit.
  • Example 22 The method of any of examples 20 or 21, wherein the beam blocking detection scheduling request has a higher priority than the different scheduling request.
  • Example 23 The method of any of examples 18 to 22, wherein receiving the beam blocking detection scheduling request further comprises: receiving the beam blocking detection scheduling request multiplexed with other information included in a PUCCH message.
  • Example 24 The method of any of examples 18 to 23, wherein receiving the beam blocking detection scheduling request further comprises: receiving the beam blocking detection scheduling request instead of receiving a beam failure scheduling request.
  • Example 25 The method of any of examples 18 to 24, wherein receiving the beam blocking detection scheduling request comprises: receiving a PUCCH message that includes the beam blocking detection scheduling request, wherein a format of the PUCCH message is one of format 0, format 1, format 2, format 3, or format 4, the PUCCH message comprising an additional bit for the beam blocking detection scheduling request.
  • Example 26 The method of any of examples 18 to 25, wherein receiving the beam blocking detection scheduling request further comprises: receiving the beam blocking detection scheduling request on a plurality of uplink beams.
  • Example 27 The method of any of examples 18 to 26, further comprising: transmitting, pursuant to the beam blocking detection scheduling request, a grant for uplink transmission of a CSI report comprising beam blocking detection information; and receiving the CSI report from the UE in accordance with the grant.
  • Example 28 The method of example 27, further comprising: transmitting, to the UE, a retransmission of the one or more scheduled downlink transmissions on a second downlink beam based at least in part on the CSI report received by the base station.
  • Example 29 The method of any of examples 27 or 28, wherein the grant is transmitted via a semi-persistent scheduling PDSCH message on a second downlink beam.
  • Example 30 The method of example 29, wherein the CSI report is received on an uplink beam that has reciprocity with the second downlink beam.
  • Example 31 An apparatus comprising at least one means for performing a method of any of examples 18 to 30.
  • Example 32 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 examples 18 to 30.
  • Example 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 examples 18 to 30.
  • 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).
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that 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. Also, any connection is properly termed a computer-readable medium.
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrically erasable programmable ROM
  • CD compact disk
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (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 identifier une défaillance pour décoder des transmissions de liaison descendante planifiées dirigées vers l'UE sur un premier faisceau. L'UE peut déterminer si la défaillance est due au premier faisceau qui est un faisceau bloqué. Si la défaillance est due au blocage de faisceau, l'UE peut transmettre, à la station de base, une requête de planification de détection de blocage de faisceau qui peut demander un ensemble de ressources de liaison montante pour l'UE pour transmettre un rapport d'informations d'état de canal (CSI) comportant les informations de détection de blocage de faisceau. L'UE peut transmettre la requête de planification de détection de blocage de faisceau sur un ensemble de faisceaux de liaison montante. L'UE peut être configuré pour déterminer un décalage cyclique à appliquer au PUCCH sur la base de la détermination du fait que la défaillance est due au blocage de faisceau, ou sur la base du format du PUCCH, ou d'une combinaison de ceux-ci.
PCT/US2021/036016 2020-06-05 2021-06-04 Procédures de transmission de requête de planification de détection de blocage de faisceau WO2021248076A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GR20200100316 2020-06-05
GR20200100316 2020-06-05

Publications (1)

Publication Number Publication Date
WO2021248076A1 true WO2021248076A1 (fr) 2021-12-09

Family

ID=76695870

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/036016 WO2021248076A1 (fr) 2020-06-05 2021-06-04 Procédures de transmission de requête de planification de détection de blocage de faisceau

Country Status (1)

Country Link
WO (1) WO2021248076A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023237177A1 (fr) * 2022-06-06 2023-12-14 Telefonaktiebolaget Lm Ericsson (Publ) Partage de demande de planification pour formation de faisceau hybride

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019031903A1 (fr) * 2017-08-10 2019-02-14 Samsung Electronics Co., Ltd. Procédé et appareil de gestion d'une reprise sur panne de faisceau dans un système de communication sans fil
US20190075573A1 (en) * 2017-09-07 2019-03-07 Futurewei Technologies, Inc. System and Method for HARQ Acknowledgement
KR20190054978A (ko) * 2017-11-13 2019-05-22 주식회사 윌러스표준기술연구소 무선 통신 시스템의 통신을 위한 빔 운영 방법 및 이를 이용하는 장치
EP3509373A1 (fr) * 2018-01-09 2019-07-10 Comcast Cable Communications LLC Sélection de faisceau dans une retransmission de demande de reprise après défaillance de faisceau

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019031903A1 (fr) * 2017-08-10 2019-02-14 Samsung Electronics Co., Ltd. Procédé et appareil de gestion d'une reprise sur panne de faisceau dans un système de communication sans fil
US20190075573A1 (en) * 2017-09-07 2019-03-07 Futurewei Technologies, Inc. System and Method for HARQ Acknowledgement
KR20190054978A (ko) * 2017-11-13 2019-05-22 주식회사 윌러스표준기술연구소 무선 통신 시스템의 통신을 위한 빔 운영 방법 및 이를 이용하는 장치
EP3509373A1 (fr) * 2018-01-09 2019-07-10 Comcast Cable Communications LLC Sélection de faisceau dans une retransmission de demande de reprise après défaillance de faisceau

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ASTRI ET AL: "Beam blockage detection and recovery for NR MIMO", vol. RAN WG1, no. Spokane, USA; 20170403 - 20170407, 2 April 2017 (2017-04-02), XP051244060, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20170402] *
AT&T: "Beam Failure (BF) and Radio Link Interruption (RLI)", vol. RAN WG2, no. Spokane, USA; 20170403 - 20170407, 3 April 2017 (2017-04-03), XP051244830, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170403] *
HUAWEI ET AL: "Design of PRACH-based beam failure recovery", vol. RAN WG1, no. Reno, USA; 20171127 - 20171201, 18 November 2017 (2017-11-18), XP051369548, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F91/Docs/> [retrieved on 20171118] *
SAMSUNG: "Short PUCCH for UCI of 1 or 2 Bits", vol. RAN WG1, no. Nagoya, Japan; 20170918 - 20170921, 17 September 2017 (2017-09-17), XP051339447, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20170917] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023237177A1 (fr) * 2022-06-06 2023-12-14 Telefonaktiebolaget Lm Ericsson (Publ) Partage de demande de planification pour formation de faisceau hybride

Similar Documents

Publication Publication Date Title
US11553374B2 (en) Identifying a hybrid automatic repeat request mode
WO2022115861A1 (fr) Sélection de ressources avec détection de récepteur de liaison latérale
EP4085555B1 (fr) Sélection de ressources à des fins de rétroaction de multidiffusion partagée par un équipement d&#39;utilisateur (ue)
EP4078872B1 (fr) Traitement sélectif de transmissions en multidiffusion et diffusion
WO2021162857A1 (fr) Indice d&#39;attribution de liaison descendante pour programmation de porteuses à éléments multiples
US11678394B2 (en) Techniques for multicast beam failure and recovery
EP4104372A1 (fr) Rétroaction d&#39;accusé de réception pour planification de porteuse à composants multiples avec des champs de commande associés à une rétroaction séparés
WO2022115556A1 (fr) Sélection de ressources avec détection d&#39;émetteur
EP4079100A1 (fr) Procédés et appareils de retransmission de données utilisant une diversité de liaison latérale
WO2021248076A1 (fr) Procédures de transmission de requête de planification de détection de blocage de faisceau
US11671980B2 (en) Techniques for enhanced coverage semi-persistent scheduling
US20230073645A1 (en) Acknowledgment reporting for multi-link transmissions
WO2021196068A1 (fr) Types de rapport d&#39;état de canal
EP4150806A1 (fr) Adaptation de liaison lors d&#39;une détermination de blocage de faisceau
WO2023108399A1 (fr) Livre de codes de demande automatique de répétition hybride de type 2 commun pour des communications de liaison descendante et de liaison latérale
WO2023108386A1 (fr) Livre de codes de demande automatique de répétition hybride de type 2 pour des communications de liaison descendante et de liaison latérale
US20230199535A1 (en) Error reason indication for reception failure
US20210298062A1 (en) Two-stage feedback procedures for multiple downlink transmissions
WO2022165785A1 (fr) Configuration de transmission en liaison descendante pour surfaces intelligentes reconfigurables
WO2022036493A1 (fr) Techniques de mesure d&#39;interférences entre liaisons parmi des technologies d&#39;accès radio
JP2023548076A (ja) トラフィックタイプ区別のための拡張復号フィードバック
WO2023091815A1 (fr) Procédure de gestion de faisceau entre stations de base
WO2022020360A1 (fr) Utilisation d&#39;un schéma de transmission d&#39;accusé de réception négatif configuré pour une indication de cause d&#39;erreur
WO2021126504A1 (fr) Techniques de diversité de fréquence pour réseaux à fréquence unique
CN116114214A (zh) 用于使用参考信号的服务小区激活和去激活的技术

Legal Events

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

Ref document number: 21736127

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

Country of ref document: EP

Kind code of ref document: A1