WO2026020301A1 - Amélioration de signal de référence de sondage pour la gestion de faisceau de liaison montante - Google Patents

Amélioration de signal de référence de sondage pour la gestion de faisceau de liaison montante

Info

Publication number
WO2026020301A1
WO2026020301A1 PCT/CN2024/106899 CN2024106899W WO2026020301A1 WO 2026020301 A1 WO2026020301 A1 WO 2026020301A1 CN 2024106899 W CN2024106899 W CN 2024106899W WO 2026020301 A1 WO2026020301 A1 WO 2026020301A1
Authority
WO
WIPO (PCT)
Prior art keywords
srs
downlink
reference signal
uplink
receive
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/106899
Other languages
English (en)
Inventor
Shaozhen GUO
Mostafa KHOSHNEVISAN
Xiaoxia Zhang
Changhwan Park
Yan Zhou
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2024/106899 priority Critical patent/WO2026020301A1/fr
Publication of WO2026020301A1 publication Critical patent/WO2026020301A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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/0404—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas the mobile station comprising multiple antennas, e.g. to provide uplink diversity
    • 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
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/06966—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping using beam correspondence; using channel reciprocity, e.g. downlink beam training based on uplink sounding reference signal [SRS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource

Definitions

  • the following relates to wireless communications, including sounding reference signal enhancement for uplink beam management.
  • 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, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
  • UE user equipment
  • a method for wireless communications by a user equipment may include receiving one or more signals including an indication of a beam sweeping range to be applied during sounding reference signal (SRS) transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam and performing the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • SRS sounding reference signal
  • the UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories.
  • the one or more processors may individually or collectively be operable to execute the code to cause the UE to receive one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam and perform the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the UE may include means for receiving one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam and means for performing the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by one or more processors to receive one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam and perform the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the angular offset includes a horizontal angular offset, a vertical angular offset, or both.
  • receiving the one or more signals may include operations, features, means, or instructions for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources may be associated with a joint or uplink transmission configuration indication (TCI) state that identifies a source reference signal and the downlink receive beam may be identified in accordance with the source reference signal.
  • TCI uplink transmission configuration indication
  • receiving the one or more signals may include operations, features, means, or instructions for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources may be associated with a joint or uplink TCI state that identifies a pathloss reference signal and the downlink receive beam may be identified in accordance with the pathloss reference signal.
  • receiving the one or more signals may include operations, features, means, or instructions for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources may be associated with a joint or uplink TCI state where a specific joint or uplink TCI state may be used to identify the downlink reference signal for SRS resources in the set of SRS resources and the downlink receive beam may be identified in accordance with the downlink reference signal.
  • the downlink reference signal includes either a source reference signal or a pathloss reference signal in the specific joint or uplink TCI state that may be associated with a lowest resource identifier.
  • the downlink receive beam corresponding to the downlink reference signal may be configured or indicated on a per-SRS resource basis or on a per-SRS resource set basis.
  • the downlink receive beam corresponding to the downlink reference signal may be identified as a source reference signal in a current indicated joint or downlink TCI state associated with the downlink transmit point.
  • receiving the one or more signals may include operations, features, means, or instructions for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resources in the set of SRS resources may be associated with a joint or uplink TCI state that identifies the angular offset.
  • receiving the one or more signals may include operations, features, means, or instructions for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources may be associated with the angular offset.
  • receiving the one or more signals may include operations, features, means, or instructions for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where the set of SRS resources may be associated with a common angular offset and a set of delta values that, for each corresponding SRS resource in the set of SRS resources, identify the angular offset for the corresponding SRS resource.
  • each SRS resource in the set of SRS resources may be indicated with a corresponding delta value from the set of delta values.
  • each SRS resource in the set of SRS resources may be indicated with a same delta value from the set of delta values and a corresponding delta value for the corresponding SRS resource may be identified in accordance with an order or index of the corresponding SRS resource in the set of SRS resources.
  • Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a medium access control-control element (MAC-CE) that indicates an update to the downlink reference signal, to the angular offset, or both.
  • MAC-CE medium access control-control element
  • the update to the downlink reference signal, to the angular offset, or both may be associated with one or more joint or uplink TCI states.
  • the update to the downlink reference signal, to the angular offset, or both may be associated with one or more SRS resources.
  • the update to the downlink reference signal, to the angular offset, or both may be associated with one or more SRS resource sets.
  • a method for wireless communications by a network entity may include outputting, to a UE and via a downlink transmit point, one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam and obtaining the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories.
  • the one or more processors may individually or collectively be operable to execute the code to cause the network entity to output, to a UE and via a downlink transmit point, one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam and obtain the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the network entity may include means for outputting, to a UE and via a downlink transmit point, one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam and means for obtaining the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by one or more processors to output, to a UE and via a downlink transmit point, one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam and obtain the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the angular offset includes a horizontal angular offset, a vertical angular offset, or both.
  • outputting the one or more signals may include operations, features, means, or instructions for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources may be associated with a joint or uplink TCI state that identifies a source reference signal and the downlink receive beam may be identified in accordance with the source reference signal.
  • outputting the one or more signals may include operations, features, means, or instructions for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources may be associated with a joint or uplink TCI state that identifies a pathloss reference signal and the downlink receive beam may be identified in accordance with the pathloss reference signal.
  • outputting the one or more signals may include operations, features, means, or instructions for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of may be associated with a joint or uplink TCI state where a specific joint or uplink TCI state may be used to identify the downlink reference signal for SRS resources in the set of SRS resources and the downlink receive beam may be identified in accordance with the downlink reference signal.
  • the downlink reference signal includes either a source reference signal or a pathloss reference signal in the specific joint or uplink TCI state that may be associated with a lowest resource identifier.
  • the downlink receive beam corresponding to the downlink reference signal may be configured or indicated on a per-SRS resource basis or on a per-SRS resource set basis.
  • the downlink receive beam corresponding to the downlink reference signal may be identified as a source reference signal in a current indicated joint or downlink TCI state associated with the downlink transmit point.
  • outputting the one or more signals may include operations, features, means, or instructions for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resources in the set of SRS resources may be associated with a joint or uplink TCI state that identifies the angular offset.
  • outputting the one or more signals may include operations, features, means, or instructions for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources may be associated with the angular offset.
  • outputting the one or more signals may include operations, features, means, or instructions for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where the set of SRS resources may be associated with a common angular offset and a set of delta values that, for each corresponding SRS resource in the set of SRS resources, identify the angular offset for the corresponding SRS resource.
  • each SRS resource in the set of SRS resources may be indicated with a corresponding delta value from the set of delta values.
  • each SRS resource in the set of SRS resources may be indicated with a same delta value from the set of delta values and a corresponding delta value for the corresponding SRS resource may be identified in accordance with an order or index of the corresponding SRS resource in the set of SRS resources.
  • Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting a MAC-CE that indicates an update to the downlink reference signal, to the angular offset, or both.
  • the update to the downlink reference signal, to the angular offset, or both may be associated with one or more joint or uplink TCI states.
  • the update to the downlink reference signal, to the angular offset, or both may be associated with one or more SRS resources.
  • the update to the downlink reference signal, to the angular offset, or both may be associated with one or more SRS resource sets.
  • FIG. 1 shows an example of a wireless communications system that supports sounding reference signal (SRS) enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • SRS sounding reference signal
  • FIG. 2 shows an example of a wireless communications system that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • FIGs. 3A and 3B show examples of a medium access control-control element (MAC-CE) that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • MAC-CE medium access control-control element
  • FIG. 4 shows an example of a MAC-CE that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • FIG. 5 shows an example of a wireless communications system that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • FIG. 6 shows an example of a wireless communications system that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • FIGs. 7 and 8 show block diagrams of devices that support SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • FIG. 9 shows a block diagram of a communications manager that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • FIG. 10 shows a diagram of a system including a device that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • FIGs. 11 and 12 show block diagrams of devices that support SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • FIG. 13 shows a block diagram of a communications manager that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • FIG. 14 shows a diagram of a system including a device that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • FIGs. 15 through 18 show flowcharts illustrating methods that support SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • Wireless networks may use various transmission/reception points (TRPs) for communications between the network and user equipment (UE) .
  • TRPs transmission/reception points
  • Uplink and downlink TRPs may be collocated or non-collocated such that there may be a lack of beam correspondence between the downlink channel and the uplink channel.
  • the lack of beam correspondence may be due to an edge UE or due to different frequency ranges being used for the different channels.
  • the non-collocated example may mean that the propagation path between the UE and the downlink TRP is different from the propagation path between the UE and the uplink TRP.
  • the UE may use various beam sweeping techniques to identify, establish, and maintain a connection between the UE and the network (e.g., to identify uplink/downlink beam pairs at the UE and the network entity) .
  • the network e.g., to identify uplink/downlink beam pairs at the UE and the network entity
  • such wireless networks may not provide efficient or effective methods for such beam sweeping techniques to establish the uplink transmit beam between the UE and the uplink TRP.
  • aspects of the techniques described herein provide for efficient and effective sounding reference signal (SRS) transmissions from the UE for beam management.
  • the UE may receive or other obtain signal (s) that carry or otherwise convey an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions.
  • the beam sweeping status may include either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a plurality of narrow beam widths.
  • the plurality of narrow beam widths are within a range of the wide beamwidth of the transmit beam. Accordingly, the UE may perform the SRS transmissions according to the beam sweeping status.
  • aspects of the techniques described herein provide efficient and effective mechanisms for uplink beam management for an uplink TRP (e.g., in the non-beam correspondence scenario) .
  • a UE may receive signal (s) that carry or otherwise convey an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point.
  • the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of the downlink transmit point and an angular offset relative to the downlink receive beam.
  • the UE may perform the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to SRS enhancement for uplink beam management.
  • FIG. 1 shows an example of a wireless communications system 100 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 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, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • NR New Radio
  • the network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities.
  • a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature.
  • network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) .
  • a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125.
  • the coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
  • RATs 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 capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105) , as shown in FIG. 1.
  • a node of the wireless communications system 100 which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein.
  • a node may be a UE 115.
  • a node may be a network entity 105.
  • a first node may be configured to communicate with a second node or a third node.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a UE 115.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a network entity 105.
  • the first, second, and third nodes may be different relative to these examples.
  • reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node.
  • disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
  • network entities 105 may communicate with a core network 130, or with one another, or both.
  • network entities 105 may communicate with the core network 130 via backhaul communication link (s) 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) .
  • network entities 105 may communicate with one another via backhaul communication link (s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130) .
  • network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof.
  • the backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof.
  • a UE 115 may communicate with the core network 130 via a communication link 155.
  • One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) .
  • a base station 140 e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred
  • a network entity 105 may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .
  • a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • a disaggregated architecture e.g., a disaggregated base station architecture, a disaggregated RAN architecture
  • a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by
  • a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof.
  • a central unit such as a CU 160
  • DU distributed unit
  • RU such as an RU 170
  • a RAN Intelligent Controller (RIC) such as an RIC 175
  • a Near-Real Time RIC Near-RT RIC
  • Non-RT RIC Non-Real Time RIC
  • SMO Service Management and Orchestration
  • An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) .
  • one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • the split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof
  • a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack.
  • the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaptation protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaptation protocol
  • PDCP Packet Data Convergence Protocol
  • the CU 160 may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs) , or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control (MAC) layer
  • RLC radio link control
  • MAC medium access control
  • a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack.
  • the DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) .
  • a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) .
  • a CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • CU-CP CU control plane
  • CU-UP CU user plane
  • a CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) .
  • a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.
  • infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) .
  • IAB network architecture e.g., to a core network 130
  • one or more of the network entities 105 may be partially controlled by each other.
  • the IAB node (s) 104 may be referred to as a donor entity or an IAB donor.
  • a DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) .
  • the one or more donor entities may be in communication with one or more additional devices (e.g., IAB node (s) 104) via supported access and backhaul links (e.g., backhaul communication link (s) 120) .
  • IAB node (s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor.
  • IAB-MT IAB mobile termination
  • An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) .
  • the IAB node (s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) .
  • one or more components of the disaggregated RAN architecture e.g., the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.
  • an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB node (s) 104, and one or more UEs 115.
  • the IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130.
  • the IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) .
  • the IAB donor and IAB node (s) 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) .
  • the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.
  • IAB node (s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) .
  • a DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node (s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node (s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node (s) 104) .
  • IAB node (s) 104 may also be referred to as parent nodes or child nodes to other IAB node (s) 104, depending on the relay chain or configuration of the AN.
  • the IAB-MT entity of IAB node (s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node (s) 104) to receive signaling from a parent IAB node (e.g., the IAB node (s) 104) , and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.
  • a DU interface e.g., a DU 165
  • IAB node (s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both.
  • An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link (s) 120) to the core network 130 and may act as a parent node to IAB node (s) 104.
  • the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node (s) 104, or may directly signal transmissions to a UE 115, or both.
  • the CU 160 of the IAB donor may signal communication link establishment via an F1 interface to IAB node (s) 104, and the IAB node (s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165) . That is, data may be relayed to and from IAB node (s) 104 via signaling via an NR Uu interface to MT of IAB node (s) 104 (e.g., other IAB node (s) ) . Communications with IAB node (s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node (s) 104.
  • DUs e.g., DUs 165
  • one or more components of the disaggregated RAN architecture may be configured to support test as described herein.
  • some operations described as being performed by a UE 115 or a network entity 105 may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .
  • 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, vehicles, or 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 UEs 115 that may sometimes operate as relays, as well as the network entities 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.
  • devices such as UEs 115 that may sometimes operate as relays, as well as the network entities 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 network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers.
  • the term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125.
  • a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • a given RAT e.g., LTE, LTE-A, LTE-A Pro, NR
  • Each PHY 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.
  • Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105.
  • the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105 may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105) .
  • a network entity 105 e.g., a base station 140, a CU 160, a DU 165, a RU 170
  • another device e.g., directly or via one or more other network entities, such as one or more of the network entities 105
  • a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers.
  • a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • a carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT) .
  • the communication link (s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions.
  • Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • a carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
  • Devices of the wireless communications system 100 e.g., the network entities 105, the UEs 115, or both
  • the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths.
  • each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
  • Signal waveforms transmitted via 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 refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related.
  • the quantity 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) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication.
  • a wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
  • One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing ( ⁇ f) and a cyclic prefix.
  • a carrier may be divided into one or more BWPs having the same or different numerologies.
  • a UE 115 may be configured with multiple BWPs.
  • a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
  • 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 quantity of slots.
  • each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing.
  • Each slot may include a quantity 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 associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f ) 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., a quantity 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 for communication using a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed for signaling via 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 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 an amount 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 UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE) .
  • a network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof.
  • the term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) ) .
  • a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates.
  • Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105.
  • a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell.
  • a small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells.
  • Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) .
  • a network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.
  • a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
  • protocol types e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB)
  • NB-IoT narrowband IoT
  • eMBB enhanced mobile broadband
  • a network entity 105 may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110.
  • coverage areas 110 e.g., different coverage areas
  • coverage areas 110 may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105) .
  • overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105) .
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.
  • the wireless communications system 100 may support synchronous or asynchronous operation.
  • network entities 105 e.g., base stations 140
  • network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network entities 105) may, in some examples, not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • Some UEs 115 may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) .
  • half-duplex communications may be performed at a reduced peak rate.
  • Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques.
  • some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • 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) .
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions.
  • Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data.
  • Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) .
  • D2D device-to-device
  • P2P peer-to-peer
  • one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105.
  • one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105.
  • groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to one or more of the UEs 115 in the group.
  • a network entity 105 may facilitate the scheduling of resources for D2D communications.
  • D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
  • a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) .
  • vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these.
  • V2X vehicle-to-everything
  • V2V vehicle-to-vehicle
  • a vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system.
  • vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
  • roadside infrastructure such as roadside units
  • network nodes e.g., network entities 105, base stations 140, RUs 170
  • V2N vehicle-to-network
  • 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 network entities 105 (e.g., base stations 140) associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to IP services 150 for one or more network operators.
  • the IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • IMS IP Multimedia Subsystem
  • the wireless communications system 100 may operate using one or more frequency bands, which may be 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, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications 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 also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band.
  • SHF super high frequency
  • EHF extremely high frequency
  • the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas.
  • mmW millimeter wave
  • such techniques may facilitate using antenna arrays within a device.
  • EHF transmissions may be subject to even greater attenuation and shorter range than SHF or UHF transmissions.
  • the techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
  • the wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands.
  • the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using 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 network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) .
  • Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
  • a network entity 105 e.g., a base station 140, an RU 170
  • 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 network entity 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 network entity 105 may be located at diverse geographic locations.
  • a network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations.
  • an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
  • the network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers.
  • Such techniques may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) .
  • Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 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 along 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 network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations.
  • a network entity 105 e.g., a base station 140, an RU 170
  • Some signals e.g., synchronization signals, reference signals, beam selection signals, or other control signals
  • the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission.
  • Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
  • a transmitting device such as a network entity 105
  • a receiving device such as a UE 115
  • Some signals may be transmitted by a transmitting device (e.g., a network entity 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as another network entity 105 or UE 115) .
  • a transmitting device e.g., a network entity 105 or a UE 115
  • a single beam direction e.g., a direction associated with the receiving device, such as another network entity 105 or UE 115
  • the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions.
  • a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 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 beamforming to generate a combined beam for transmission (e.g., from a network entity 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 set of beams across a system bandwidth or one or more sub-bands.
  • the network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded.
  • a reference signal e.g., a cell-specific reference signal (CRS) , a channel state information 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
  • these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170)
  • a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
  • a receiving device may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a transmitting device e.g., a network entity 105
  • a receiving device may perform reception in accordance with 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.
  • 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 along 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) .
  • 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
  • the wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack.
  • communications at the bearer or PDCP layer may be IP-based.
  • An RLC layer may perform packet segmentation and reassembly to communicate via logical channels.
  • a MAC layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency.
  • an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data.
  • a PHY layer may map transport channels to physical channels.
  • the UEs 115 and the network entities 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 via a communication link (e.g., the communication link (s) 125, a D2D communication link 135) .
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) .
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal-to-noise conditions) .
  • a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • a UE 115 may receive or obtain one or more signals comprising an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status comprising either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a plurality of narrow beam widths, wherein the plurality of narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the UE 115 may transmit or perform the SRS transmissions according to the beam sweeping status.
  • a network entity 105 may transmit or output, to a UE 115, one or more signals comprising an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status comprising either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a plurality of narrow beam widths, wherein the plurality of narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the network entity 105 may receive or obtain the SRS transmissions according to the beam sweeping status.
  • a UE 115 may receive or obtain one or more signals comprising an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, wherein the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the UE 115 may transmit or perform the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • a network entity 105 may transmit or output, to a UE 115 and via a downlink transmit point, one or more signals comprising an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, wherein the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the network entity 105 may receive or obtain the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • FIG. 2 shows an example of a wireless communications system 200 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • Wireless communications system 200 may implement aspects of wireless communications system 100.
  • Wireless communications system 200 may include a UE 205 and a network entity 230, which may be examples of the corresponding devices described herein.
  • Wireless networks may support a dense uplink (UL) deployment in some scenarios.
  • the dense uplink deployment may improve the coverage and capacity of uplink transmissions from the UE 205.
  • the dense uplink deployment may be asymmetric in that there are more uplink transmissions than downlink transmissions.
  • the uplink transmissions from the UE 205 may be received at an uplink receive point (e.g., an UL-TRP) .
  • the downlink signals may be transmitted from the network entity 230 which is a different node (e.g., a macro node, a central node, a serving cell, a serving network entity, and the like) than the uplink receive point.
  • the uplink receive points may be associated with the network entity 230 (e.g., via a backhaul network) .
  • Such a deployment scenario may reduce the uplink pathloss, which may be helpful when the uplink coverage is a bottleneck for wireless communications within the network.
  • This deployment scenario may also assist in reducing network deployment cost and complexity since the uplink receive points may not transmit any downlink signals (e.g., they receive the uplink transmission and provide this to the network entity 230 with or without processing) .
  • this approach results in a different propagation path for uplink transmissions between the UE 205 and the uplink receive point and downlink transmissions between the UE 205 and the network entity 230.
  • Another deployment scenario may include collocated uplink and downlink (DL) TRPs where the UE 205 does not have beam correspondence between the uplink and downlink channels. That is, such deployment scenario may include symmetric downlink and uplink channels but without ideal beam correspondence. Thus, both the downlink and uplink signals may be transmitted or received by the same TRP, but beam correspondence is not supported. Examples of such collocated deployment scenarios without beam correspondence may include the downlink and uplink channels using different frequency ranges, an edge UE, or other situations where the reciprocity between the uplink and downlink channels is absent. Either deployment scenario creates issue with identifying the performance characteristics of the uplink channel since there is no correlation between the downlink channel and the uplink channel.
  • DL downlink and downlink
  • an SRS resource set applicability may be configured for the UE 205 using a higher layer parameter (e.g., usage in SRS-ResourceSet) .
  • the usage may be configured as any of beam management, codebook, non-codebook, or antenna switching) .
  • Each SRS resource set may be configured with up to 16, in some examples, SRS resources.
  • the time domain behavior for each SRS resource set may be one of periodic, semi-persistent, or aperiodic.
  • a periodic SRS resource set may be configured using higher layer signaling, such as via RRC signaling.
  • a semi-persistent SRS resource set may be configured using RRC signaling and then activated using a MAC-CE that indicates the SRS resource identifier (ID) in the MAC-CE.
  • An aperiodic SRS resource set may be configured using RRC signaling and then triggered by a DCI.
  • the aperiodic SRS resource set may be triggered using a downlink DCI (e.g., DCI format 1_1 or 1_2) , using an uplink DCI (e.g., DCI format 0_1 or 0_2) , or using a group common DCI (e.g., DCI format 2_3) .
  • An SRS request field in the DCI may indicate one or more SRS resource sets.
  • a mapping between the SRS resource sets and the SRS request codepoint (e.g., 00, 01, 10, or 11) may be provided as part of or otherwise correspond to an aperiodic SRS resource trigger or an aperiodic SRS resource trigger list.
  • the SRS resource set is set to beam management
  • this may be configured to the UE 205 so the UE 205 may try different uplink transmit beams and the network can select a suitable transmit/receive beam.
  • the transmit/receive beam for uplink transmissions needs to be identified based on the beam management SRS, but also a suitable uplink receive point.
  • SRS power control management may also be considered. In some wireless networks, this may be based on whether the UE 205 is provided with a TCI state (TCI-State) in a downlink or joint TCI state list or a TCI uplink state (TCI-UL-State) . For each indicated one or two TCI state or TCI uplink state of an SRS transmission occasion, different power control parameters may be determined. For example, if followUnifiedTCI-StateSRS is provided for a SRS resource set, the values of ⁇ SRS, b, f, c (q s ) and SRS power control adjustment state l are provided by p0AlphaSetforSRS associated with the indicated TCI-State or TCI-UL-State.
  • the values of ⁇ SRS, b, f, c (q s ) and SRS power control adjustment state l are provided by p0AlphaSetforSRS associated with TCI-State or TCI-UL-State of an SRS resource with lowest SRS-ResourceId in the SRS resource set and a RS index q d for obtaining a pathloss estimate for the SRS transmission is provided by pathlossReferenceRS-Id-r17 associated with or included in the TCI-State or TCI-UL-State of an SRS resource with lowest SRS-ResourceId in the SRS resource set.
  • the network entity 230 can configure or trigger the UE 205 to transmit SRS for beam management usage.
  • the uplink transmit beam for SRS transmissions may be determined as follows: for aperiodic SRS for beam management, if followUnifiedTCI-StateSRS is configured for an SRS resource set, the SRS resources in the SRS resource set apply the indicated uplink TCI state or joint TCI state.
  • the UE 205 may transmit the target SRS resource (s) within the SRS resource set according to the spatial relation, if applicable, with a reference to the reference signal used for determining uplink transmit spatial filter.
  • the reference signal is determined based on a reference signal configured with qcl-Type set to 'typeD' in QCL-Info of the indicated TCI-State or a reference signal in the indicated TCI-UL-State.
  • the reference signal (e.g., the source reference signal) in the indicated TCI state may be a CSI-RS.
  • the reference signal (e.g., the source reference signal) in the indicated uplink TCI state can be a CSI-RS, SSB or SRS for beam management.
  • SRS resources in any periodic/semi-persistent/aperiodic SRS resource sets for beam management can be configured with a TCI-state or TCI-UL-State or updated by MAC CE.
  • the reference signal (e.g., the source reference signal) in the TCI-state can be a CSI-RS.
  • the reference signal (e.g., the source reference signal) in the TCI-UL-State can be a CSI-RS, SSB or SRS for beam management.
  • the uplink TCI state for the UE 205 after the uplink transmit beam is known.
  • the uplink transmit beam is unknown and the intended uplink TRP is also unknown.
  • the SRS is either configured to follow unified TCI state (e.g., for aperiodic SRS for beam management) or configured/indicated with a joint/uplink TCI state (e.g., for periodic/semi-persistent SRS or for aperiodic SRS for beam management that is not configured to follow unified TCI state) .
  • the joint or uplink TCI state is configured, it is mandatory to configure the source reference signal.
  • some wireless networks may be configured such that the network does not configure SRS specific power control parameters, alpha (without suffix) , p0 (without suffix) or pathlossReferenceRS if unifiedTCI-StateType is configured for the serving cell.
  • each SRS should have a joint or uplink TCI state, either follow indicated TCI state or be configured/indicated with one joint or uplink TCI state by RRC or MAC CE signaling. That is, it is not possible to not configure or indicate any TCI state for an SRS in the case where the unified TCI state is configured. Otherwise, which power control parameters (e.g., p0, alpha or pathlossReferenceRS) to use is unclear given the power control parameters (p0, alpha and pathlossReferenceRS) are associated with unified TCI state.
  • power control parameters e.g., p0, alpha or pathlossReferenceRS
  • the source reference signal in the TCI state is mandatory in some wireless networks.
  • the uplink transmit beam and the intended uplink TRP are unknown.
  • there is no downlink reference signal from the UL-only TRP so it is unclear how to configure/indicate an uplink transmit beam for SRS for uplink discovery or beam management.
  • the downlink signals are transmitted from the downlink TRP. Therefore, the beam correspondence between the downlink and the uplink channels cannot be assumed. Additionally, for symmetric downlink and uplink deployment scenarios without beam correspondence, the uplink beam management may be needed. For example, in order to indicate the uplink transmit beam, a downlink reference signal (e.g., SSB/CRI-RS) may not be used.
  • the uplink beam management without beam correspondence may be done using SRS transmissions (e.g., SRS transmissions where the use case is set to beam management) .
  • the U1 beam refinement procedure may include the UE 205 performing uplink beam sweeping SRS transmissions using a small number of wide transmit beams.
  • the U1 procedure may include the UE 205 performing SRS transmissions using a transmit beam 210, a transmit beam 215, a transmit beam 220, and a transmit beam 225, which are wide transmit beams (e.g., have a wide beamwidth) in this example.
  • FIG. 2 shows four wide transmit beams in this U1 procedure example, it is to be understood that the U1 beam refinement procedure may include more or less than four transmit beams.
  • the network entity 230 may receive one or more of the SRS transmissions from the UE 205 using the transmit beams of the UE 205 and identify the best performing transmit beam (s) of the UE 205, such as the transmit beam (s) having or otherwise associated with a channel performance metric satisfying a performance threshold (e.g., reference signal receive power (RSRP) , reference signal receive quality (RSRQ) , reference signal strength indicator (RSSI) , signal-to-noise interference ratio (SINR) , or other metric that satisfies the performance threshold) .
  • the network entity 230 may transmit or otherwise output a report to the UE 205 that indicates or otherwise identifies the best performing transmit beam (s) of the UE 205 (e.g., at least including the transmit beam 215, in this example) .
  • the U2 beam refinement procedure may include, for a fixed wide beamwidth of the UE 205 that was identified during the U1 beam refinement procedure (the transmit beam 215, in this example) , the network entity 230 performing receive beam sweeping to find the best receive beam.
  • the UE 205 may perform (e.g., during one or more symbols) an SRS transmission or multiple SRS transmissions using the transmit beam 215 (e.g., the transmit beam identified in the U1 procedure that has a wide beamwidth) while the network entity 230 performs beam sweeping using a receive beam 235, a receive beam 240, a receive beam 245, and a receive bam 250 to identify or otherwise determine the receive beam (s) that satisfy a performance threshold (e.g., RSRP, RSRQ, RSSI, SINR, or other performance metric that satisfies the performance threshold) , which may correspond to the receive beam 240 in this example.
  • the network entity 230 may optionally report or otherwise indicate its best receive beam to the UE 205.
  • the U3 beam refinement procedure may provide for further uplink beam refinement using narrow transmit beam sweeping around the best wide beamwidth transmit beam identified during the U1 beam refinement procedure.
  • the U3 beam refinement procedure may include the UE 205 performing SRS transmissions (e.g., using SRS resources during one or more symbols) using a transmit beam 255, a transmit beam 260, a transmit beam 265, and a transmit beam 270, which correspondingly have a plurality of narrow beam widths in this example.
  • the transmit beams used to perform the SRS transmissions in the U3 beam refinement procedure may be selected such that their respective coverage area is within or within a range of the best performing wide beamwidth discovered during the U1 procedure (e.g., the transmit beam 215 in this example) .
  • the network entity 230 may use its receive beam 240 (e.g., as identified during the U2 beam refinement procedure) to identify or otherwise determine the best uplink transmit beam of the UE 205 from among the narrow beam width transmit beams.
  • wireless networks do not support such beam refinement procedures for SRS beam management (e.g., for SRS resources with the usage set to beam management) .
  • such networks may not provide a mechanism to distinguish between the U2 and the U3 beam refinement procedures.
  • a transmit beam needs to be indicated between the UE 205 and the network entity 230.
  • the UE 205 transmits SRS signals using the indicated transmit beam (e.g., the transmit beam 215, in this example) .
  • the UE 205 transmit SRS signals using different narrow transmit beams around the indicated transmit beam.
  • Wireless networks may not provide a mechanism so support such beam refinement procedures SRS-based beam refinement when the SRS resources usage is set to beam management.
  • aspects of the techniques described herein provide for SRS-based beam management (e.g., using the U1-U3 beam refinement procedure) .
  • this may include the UE 205 being configured or otherwise indicated with a transmit beam sweeping status that indicates whether the UE 205 should perform SRS transmissions using the SRS resources in an SRS resource set based on the indicated transmit beam or using different transmit beams within a range of the indicated transmit beam.
  • UE 205 may receive or otherwise obtain (and the network entity 230 may transmit or otherwise output) signal (s) that carry or otherwise convey an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions.
  • the transmit beam may generally correspond to a transmit beam associated with an SRS resource which is used for U1 beam sweeping or associated with a downlink reference signal of the downlink TRP.
  • the beam sweeping status may include either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam (e.g., the transmit beam 215, in this example, during the U2 procedure) or a second beam sweeping state where the SRS transmissions are performed using a plurality of narrow beam widths (e.g., corresponding to the transmit beam 255, the transmit beam 260, the transmit beam 265, and the transmit beam 270, in this example, that are used during the U3 beam refinement procedure) . That is, the plurality of narrow beam widths may be within or within a range of the wide beamwidth of the transmit beam. In this example, this may include the transmit beam 255, the transmit beam 260, the transmit beam 265, and the transmit beam 270 that are within or within the range of the wide beamwidth of the transmit beam 215.
  • a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam (e.g., the transmit beam 215,
  • the UE 205 may perform (e.g., transmit or otherwise output) the SRS transmissions according to the beam sweeping status.
  • the network entity 230 may receive or otherwise obtain the SRS transmissions from the UE 205 according to the beam sweeping status (e.g., according to the first beam sweeping state corresponding to the U2 beam refinement procedure or according to the second beam sweeping state corresponding to the U3 beam refinement procedure) .
  • the beam sweeping status may be indicated or otherwise configured on a per-SRS resource basis, on a per-SRS resource set basis, or on a joint or uplink TCI state basis.
  • a joint or uplink TCI state may be configured or otherwise indicated to identify the transmit beam.
  • the RRC-configured referenceSignal parameter associated with the joint or uplink TCI state may be an SRS used for U1 beam sweeping.
  • the transmit beam sweeping status is per-SRS resource set and the UE 205 may identify or otherwise determine the transmit beam (s) based on the beam sweeping status. For example, when the beam sweeping status is the first beam sweeping state (e.g., the transmit beam sweeping status is OFF) , the UE 205 may transmit in the SRS resource (e.g., perform the SRS transmissions using the SRS resource (s) ) in the SRS resource set using the spatial domain filter that is the same as the spatial domain filter associated with the source reference signal in the corresponding joint or uplink TCI state. For example, the UE 205 may receive or otherwise obtain an indication of the joint or uplink TCI state associated with each SRS resource in the SRS resource set.
  • the SRS resource e.g., perform the SRS transmissions using the SRS resource (s)
  • the UE 205 may receive or otherwise obtain an indication of the joint or uplink TCI state associated with each SRS resource in the SRS resource set.
  • the UE 205 may apply, for each SRS resources in the SRS resource set, a respective spatial domain filter to SRS resources in accordance with the respective joint or uplink TCI state associated with the SRS resources.
  • the spatial domain filter in this case, may be identified by, correspond to, or otherwise associated with the respective joint or uplink TCI state.
  • the respective joint or uplink TCI state associated with different SRS resources can be configured or indicated to be the same.
  • the UE 205 may transmit the SRS resources in the SRS resource set (e.g., perform the SRS transmissions using the SRS resource (s) ) associated with the joint or uplink TCI states using different spatial domain filters that are determined based on the spatial domain filter associated with the source reference signal in the corresponding joint or uplink TCI state. For example, the UE 205 may transmit in the SRS resources using different narrow transmit beams within the indicated wide beamwidth transmit beam to implement the U3 beam refinement sweeping procedure.
  • the SRS resource set e.g., perform the SRS transmissions using the SRS resource (s)
  • different spatial domain filters that are determined based on the spatial domain filter associated with the source reference signal in the corresponding joint or uplink TCI state.
  • the UE 205 may transmit in the SRS resources using different narrow transmit beams within the indicated wide beamwidth transmit beam to implement the U3 beam refinement sweeping procedure.
  • the UE 205 may receive or otherwise obtain, for each SRS resource in the SRS resource set, an indication of the joint or uplink TCI state associated with the SRS resource.
  • the UE 205 may apply a first respective spatial domain filter to each SRS resource in the SRS resource set in accordance with the corresponding joint or uplink TCI state.
  • the first respective spatial domain filter may be different from a second spatial domain filter associated with a source reference signal in the corresponding joint or uplink TCI state.
  • the transmit beam sweeping status is per-SRS resource and the UE 205 may identify or otherwise determine the transmit beam (s) based on the beam sweeping status. For example, the UE 205 may receive or otherwise obtain an indication of a joint of uplink TCI state associated with an SRS resource. The UE 205 may apply a spatial domain filter to the SRS resource in accordance with a source reference signal in the joint or uplink TCI state. For example, if the beam sweeping status is the first beam sweeping state (e.g., the beam sweeping status is OFF) , the UE 205 may transmit in the SRS resource using the spatial domain filter that is the same as the spatial domain filter associated with the source reference signal in the associated joint or uplink TCI state.
  • the beam sweeping status is the first beam sweeping state (e.g., the beam sweeping status is OFF)
  • the UE 205 may transmit in the SRS resource using the spatial domain filter that is the same as the spatial domain filter associated with the source reference signal in the associated joint or uplink T
  • the UE 205 may use different approaches for application of the spatial domain filters.
  • One approach may include the UE 205 transmitting in the SRS resources (e.g., perform the SRS transmissions using the SRS resource (s) ) using different spatial domain filters in different OFDM symbols that are determined based on the spatial domain filter associated with the source reference signal in the associated joint or uplink TCI state.
  • the UE 205 may receive or otherwise obtain an indication of the joint or uplink TCI state associated with the SRS resource and apply different spatial domain filters to the SRS resource during different symbols in accordance with the source reference signal in the joint or uplink TCI state.
  • Application of the different spatial domain filters during the different symbols may provide for or otherwise generate the plurality of narrow beam widths used during the SRS transmissions in the U3 beam refinement procedure.
  • Another approach may include the UE transmitting in the SRS resource using a spatial domain filter that is different from the spatial domain filter associated with the source reference signal in the associated joint or uplink TCI state. For example, this may include the UE 205 using a narrow beam width within the wide beamwidth transmit beam (e.g., the transmit beam 215) . Across multiple SRS resources associated with the same joint or uplink TCI state, the UE 205 may transmit different SRS resources using different spatial domain filters to implement the U3 beam refinement sweeping.
  • the UE 205 may receive or otherwise obtain the indication of the joint or uplink TCI state associated with an SRS resource and apply a unique spatial domain filter to the SRS resource during different symbols that is different from a spatial domain filter associated with the source reference signal in the joint or uplink TCI state.
  • Application of the unique spatial domain filter during the different symbol may include a narrow beam width (e.g., per-symbol) .
  • the transmit beam sweeping status is per-joint or uplink TCI state and the UE 205 determines the transmit beams accordingly. If the joint or uplink TCI state is per-SRS resource set and when the beam sweeping status is the first beam sweeping status (e.g., the beam sweeping status is OFF) , the UE 205 may transmit in the SRS resources in the SRS resource set using the spatial domain filter that is the same as the spatial domain filter associated with the source reference signal in the joint or uplink TCI state associated with the SRS resource set.
  • the first beam sweeping state may be configured on a per-joint or uplink TCI state basis.
  • the UE 205 may receive or otherwise obtain the indication of the joint or uplink TCI state associated with the SRS resource set and apply a unique spatial domain filter to the SRS resources in the SRS resource set in accordance with a source reference signal in the joint of uplink TCI state.
  • the UE 205 may transmit the SRS resources in the SRS resource set associated with a joint or uplink TCI state using different spatial domain filters that are determined based on the spatial domain filter associated with the source reference signal in the joint or uplink TCI state associated with the SRS resource set.
  • the second beam sweeping state may be configured on a per-joint or uplink TCI state basis.
  • the UE 205 may receive or otherwise obtain the indication of the joint or uplink TCI state associated with an SRS resource set and apply multiple spatial domain filters to SRS resources in the SRS resource set that are different from a spatial domain filter associated with the source reference signal in the joint or uplink TCI state.
  • Application of the multiple spatial domain filters to the SRS resources may include, provide for, or otherwise generate the plurality of narrow beam widths used for SRS transmissions during the U3 beam refinement procedure.
  • the UE 205 may determine the beam sweeping status by following the transmit beam sweeping status in the joint or uplink TCI state of the SRS resource with the lowest SRS resource identifier within the SRS resource set. For example, the UE 205 may receive or otherwise obtain the indication of the joint or uplink TCI state associated with an SRS resource and apply a beam sweeping status to the SRS resources within an SRS resource set in accordance with the beam sweeping status in the joint or uplink TCI state associated with a specific SRS resource.
  • the specific SRS resource in this example, may include the SRS resource with the lowest resource identifier within the SRS resource set.
  • various techniques may be used to define or otherwise quantify the plurality of narrow beam widths (e.g., to define what makes a specific beam a narrow beam width) that are within or within the range of the wide beamwidth.
  • One option may include the narrow beam width being based on whether the 3dB beamwidth of the narrow transmit beam is within the 3dB beamwidth of the corresponding wide beamwidth transmit beam.
  • the narrow beam width may be based on whether the 3dB beam width of the narrow transmit beam is within a certain range of the 3dB beamwidth of the corresponding wide transmit beam.
  • the plurality of narrow beam widths may be within or within a range of the wide beamwidth of the transmit beam in accordance with, for each narrow beam, a threshold power level (e.g., 3dB) associated with the wide beam width.
  • a threshold power level e.g., 3dB
  • Another option may include the narrow beam widths being based on whether the peak beam direction of the narrow transmit beam is within or within a certain range of the peak beam direction of the corresponding wide transmit beam.
  • the plurality of narrow beams may be within or within the range of the wide beamwidth of the transmit beam in accordance with, for each narrow beam, a threshold beam direction associated with the wide beamwidth.
  • aspects of the techniques described herein further provide for mechanisms for the network to identify or otherwise determine the number of SRS resources that can be configured for U1 and U3 beam sweeping.
  • One such mechanism may be based on UE capability signaling.
  • the UE 205 may transmit or otherwise output UE capability signaling that carries or otherwise conveys an indication of support for hierarchical beam management (e.g., the U1-U3 beam refinement procedure) and the network may configure the UE 205 with the signal (s) indicate the beam sweeping status based on the UE capability signaling.
  • the UE 205 may indicate whether it supports hierarchical beam refinement to the network.
  • the UE capability signaling may carry or otherwise convey an indication of the number or quantity of transmit beams or SRS resources that are supported for U1 beam sweeping, for U3 beam sweeping, or for both U1 and U3 beam sweeping (collectively or separately) .
  • the UE 205 may indicate the number of transmit beams or SRS resources that can be supported for U1 beam sweeping, for U3 beam sweeping, or for both beam sweeping and refinement procedures.
  • the signal (s) carrying the indication of the beam sweeping status may be conditioned based on whether the UE indicates support for hierarchical beam refinement. In an indicated candidate value is “0”(e.g., the UE 205 does not support beam sweeping) then the UE 205 may not need to explicitly indicate whether to support hierarchical beam refinement. In this scenario, if the indicated number or quantity of transmit beams for U3 beam sweeping is “0” the UE 205 doesn’t support hierarchical beam refinement. Otherwise, if the indicated number or quantity of transmit beams for U3 beam sweeping is non-zero, the UE 205 support for hierarchical beam refinement may be indicated to the network.
  • FIGs. 3A and 3B show examples of a MAC-CE 300 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • Aspects of MAC-CE 300 may be implemented at or implemented by wireless communications system 100 or wireless communications system 200.
  • aspects of MAC-CE 300 may be implemented at or implemented by a UE or a network entity, which may be examples of the corresponding devices described herein.
  • a UE to be configured with signal (s) that identify or otherwise indicate a transmit beam and a beam sweeping status.
  • the beam sweeping status may be either a first beam sweeping state where SRS transmissions are performed using a wide beamwidth (e.g., during a U2 beam refinement procedure where the beam sweeping status is OFF) or a second beam sweeping state where the SRS transmissions are performing using a plurality of narrow beam widths (e.g., during a U3 beam refinement procedure where the beam sweeping status is ON) .
  • the plurality of narrow beam widths may be within or within a range of the wide beamwidth of the transmit beam.
  • the UE may apply the beam sweeping status and the transmit beam indicated in the signal (s) during SRS transmissions. For example, the UE may perform the SRS transmissions according to the beam sweeping status (e.g., during the U2 beam refinement procedure or during the U3 beam refinement procedure) . As also discussed above, various techniques may be used to configure, indicate, or otherwise identify or map the transmit beam and the beam sweeping status for the UE.
  • the transmit beam sweeping status may be indicated by RRC signaling, via a MAC-CE, via DCI signaling, or any combination of such signaling.
  • the indication of the beam sweeping status may be received or otherwise provided in a MAC-CE.
  • the MAC-CE may be a new (e.g., newly defined or configured) MAC-CE or by the SRS TCI state indication carried or otherwise provided in the MAC-CE.
  • the transmit beam sweeping status is per-SRS resource set.
  • the UE may receive RRC signaling that indicates:
  • the RRC signaling configuring the SRS resource set (SRS-ResourceSet) for the UE may identify the SRS resource identifier (srs-ResourceSetId) as well as indicating that the beam sweeping status (BeamSweepStatus) , for example (e.g., either ON or OFF) for the SRS resources in the SRS resource set.
  • the MAC-CE 300 may include a first octet 305 that includes one bit (A/D) indicating whether the MAC-CE is an activation or deactivation MAC-CE.
  • the first octet 305 may also include five bits used to indicate the cell identifier for the SRS resource set and two bits used to indicate the BWP identifier for the SRS resource set.
  • the MAC-CE 300 may include a second octet 310 that includes two reserved (R) bits, one bit (C) that indicates whether the octets containing the resource serving cell identifier field (s) and resource BWP identifier field (s) are present, one bit that indicates whether the MAC-CE applies to the NUL carrier or to the scheduled uplink (SUL) carrier configuration, and four bits used to indicate the SRS resource set identifier.
  • the next pair of octets in the MAC-CE may be used to configure the first SRS resource in the SRS resource set.
  • the MAC-CE 300 may include a third octet 315 that includes one reserved (R) bit, five bits used to indicate the TCI state serving cell identifier, and two bits used to indicate the BWP identifier for the TCI state.
  • the MAC-CE 300 may include a fourth octet 320 that includes one reserved (R) bit and seven bits used to indicates the TCI state identifier.
  • This pair of octets may be for SRS resource 0 in the SRS resource set.
  • This octet pair scheme may continue until a fifth octet 325 that includes one reserved (R) bit, five bits used to indicate the TCI state serving cell identifier, and two bits used to indicate the BWP identifier for the TCI state.
  • the MAC-CE 300 may include a sixth octet 330 that includes one reserved (R) bit and seven bits used to indicates the TCI state identifier.
  • This pair of octets may be for SRS resource N-1 in the SRS resource set (e.g., the last SRS resource in the SRS resource set) .
  • one of the reserved (R) bits in the second octet 310 may be used to indicate the transmit beam sweeping status (e.g., either ON or OFF) for the SRS resources in the SRS resource set.
  • the beam sweeping status is on a per-SRS resource set basis and a bit in the MAC-CE (e.g., either (R) bit in the second octet 310) may be used to indicate either the first beam sweeping state (e.g., the beam sweeping status is OFF) or the second beam sweeping state (e.g., the beam sweeping status is ON) to the UE.
  • the transmit beam sweeping status is indicated or otherwise configured per-SRS resource.
  • the UE may be RRC configured with an indication of:
  • multiple reserved bits e.g., the reserved bit in the fourth octet 320 corresponding to SRS resource 0 and the sixth octet 330 corresponding to SRS resource N-1) in the SRS TCI state indication MAC-CE may be used where each reserved bit is used to indicate whether the transmit beam sweeping status is ON or OFF for the corresponding SRS resource.
  • the beam sweeping status is on a per-SRS resource basis and a set of bits (e.g., the reserved bits corresponding to each SRS resource) in the MAC-CE corresponding to SRS resources in the SRS resource set indicates, for each SRS resource, either the first beam sweeping state or the second beam sweeping state.
  • a set of bits e.g., the reserved bits corresponding to each SRS resource
  • the indication of the beam sweeping status may be received in a DCI where a bit in the DCI indicates either the first beam sweeping state or the second beam sweeping state for one or more SRS resource sets.
  • the transmit beam sweeping status may be indicated in the DCI that triggers aperiodic SRS resources for transmission.
  • One bit may be introduced in the DCI to indicate whether the transmit beam sweeping status is ON or OFF for the triggered SRS resource set (s) . In this case, among the triggered SRS resource set (s) the transmit beam sweeping status may apply to the SRS resource set with the usage set to beam management (e.g., beamManagement) .
  • beamManagement e.g., beamManagement
  • the presence of the one-bit field in the DCI may be RRC configured per-DCI format.
  • the network may control the DCI format 1_1 that has the new field while DCI formats 1_2, 0_1, and 0_2 do not have this field.
  • a default behavior e.g., no beam sweeping
  • the SRS transmissions may be aperiodic SRS transmissions associated with trigger state (s) where each trigger state is associated with a beam sweeping status that is configured for the UE via RRC signaling.
  • the UE may receive or otherwise obtain a DCI that activates the aperiodic SRS transmissions associated with a trigger state and the UE may apply the beam sweeping status associated with the trigger state during the aperiodic SRS transmissions.
  • RRC and DCI signaling may be used to indicate the transmit beam sweeping status.
  • the transmit beam sweeping status (e.g., either ON or OFF) may be configured for each trigger state (e.g., corresponding to SRS resource field 01, 10, or 11) and, depending on the value of the SRS request field, the UE may apply beam sweeping or no beam sweeping (e.g., using a fixed transmit beam) accordingly.
  • the transmit beam sweeping status may apply to the SRS resource set with the usage set to beam management.
  • FIG. 4 shows an example of a MAC-CE 400 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • Aspect of MAC-CE 400 may implement or be implemented by aspects of wireless communications system 100 or wireless communications system 200.
  • aspects of MAC-CE 400 may be implemented at or implemented by a UE or a network entity, which may be examples of the corresponding devices described herein.
  • a UE to be configured with signal (s) that identify or otherwise indicate a transmit beam and a beam sweeping status.
  • the beam sweeping status may be either a first beam sweeping state where SRS transmissions are performed using a wide beamwidth (e.g., during a U2 beam refinement procedure where the beam sweeping status is OFF) or a second beam sweeping state where the SRS transmissions are performing using a plurality of narrow beam widths (e.g., during a U3 beam refinement procedure where the beam sweeping status is ON) .
  • the plurality of narrow beam widths may be within a range of the wide beamwidth of the transmit beam.
  • the UE may apply the beam sweeping status and the transmit beam indicated in the signal (s) during SRS transmissions. For example, the UE may perform the SRS transmissions according to the beam sweeping status (e.g., during the U2 beam refinement procedure or during the U3 beam refinement procedure) . As also discussed above, various techniques may be used to configure, indicate, or otherwise identify or map the transmit beam and the beam sweeping status to the UE.
  • the transmit beam sweeping status may be indicated by RRC signaling, via a MAC-CE, via DCI signaling, or any combination of such signaling.
  • the UE may be configured or otherwise indicated with a joint or uplink TCI state per-SRS resource set.
  • the UE may receive or otherwise obtain an indication of the joint or uplink TCI state for an SRS resource set.
  • the indication of the joint or uplink TCI state may be received via RRC signaling, in a MAC-CE, or using both signaling techniques.
  • the joint or uplink TCI state may not be configured for each SRS resource in the SRS resource set. That is, the joint or uplink TCI state for the SRS resource set may omit or otherwise not include joint or uplink TCI state information or configurations for SRS resources in the SRS resource set.
  • the UE may transmit the SRS resources in the SRS resource set using different spatial domain filters that are identified or otherwise determined based on the spatial domain filter associated with the source reference signal in the joint or uplink TCI state.
  • the UE may transmit in the SRS resources using the spatial domain filter that is the same as the spatial domain filter associated with the source reference signal in the corresponding TCI state. That is, the UE being configured with the joint or uplink TCI state for the SRS resource set may carry or otherwise convey an indication that the beam sweeping status is the second beam sweeping state.
  • this may carry or otherwise convey and indication that the beam sweeping status is the first beam sweeping state.
  • the indication of the beams sweeping status may be carried or otherwise conveyed using RRC or MAC-CE signaling.
  • RRC Radio Resource Control
  • the UE may receive the MAC-CE 400 that carries or otherwise conveys the joint or uplink TCI state for the SRS resource set (e.g., on a per-SRS resource set basis) .
  • the MAC-CE 400 may include a first octet 405 that includes one bit (A/D) indicating whether the MAC-CE is an activation or deactivation MAC-CE.
  • the first octet 405 may also include five bits used to indicate the cell identifier for the SRS resource set and two bits used to indicate the BWP identifier for the SRS resource set.
  • the MAC-CE 400 may include a second octet 410 that includes two reserved (R) bits, one bit (C) that indicates whether the octets containing the resource serving cell identifier field (s) and resource BWP identifier field (s) are present, one bit that indicates whether the MAC-CE applies to the NUL carrier or to the SUL carrier configuration, and four bits used to indicate the SRS resource set identifier.
  • the next pair of octets in the MAC-CE 400 may be used to configure the SRS resources in the SRS resource set.
  • the MAC-CE 400 may include a third octet 415 that includes one reserved (R) bit, five bits used to indicate the TCI state serving cell identifier, and two bits used to indicate the BWP identifier for the TCI state.
  • the MAC-CE 400 may include a fourth octet 420 that includes one reserved (R) bit and seven bits used to indicate the TCI state identifier.
  • this pair of octets may carry or otherwise convey the indication of the joint or uplink TCI state for the SRS resource set (e.g., SRS set-level TCI indication) .
  • a set of power control parameters for SRS resources in the SRS resource set may be identified or otherwise determined based on the joint or uplink TCI state for the SRS resource set. For example, when the joint or uplink TCI state is configured or otherwise indicated per-SRS resource set, for each SRS resource in the SRS resource set, the power control parameters may be identified or otherwise determined based on the joint or uplink TCI state of the SRS resource set.
  • This may include the values of P0, ⁇ and the SRS power control adjustment state l being provided by p0AlphaSetforSRS associated with the TCI-State or TCI-UL-State of the SRS resource set and a reference signal index q d being used for obtaining a pathloss estimate for the SRS transmissions as provided by a pathlossReferenceRS-Id-r17 parameter associated with or included in the TCI-State or TCI-UL-State of the SRS resource set. If the joint or uplink TCI state is associated with a pathloss offset, the pathloss offset may be applied to each SRS resource in the SRS resource set.
  • this may include the UE receiving or otherwise obtaining an indication of a joint or uplink TCI state and a beam sweeping status for an SRS resource set.
  • one of the reserved bits (R) in the second octet 410, the third octet 415, or the fourth octet 420 may be used to indicate the transmit beam sweeping status for the SRS resources in the SRS resource set.
  • the UE may be configured or otherwise indicated with a joint or uplink TCI state and a beam sweeping status per-SRS resource set.
  • the indication may be provided via RRC signaling, in a MAC-CE, or using DCI signaling to the UE.
  • the UE may receive the following RRC signaling:
  • the UE may apply, for each SRS resource in the SRS resource set, a spatial domain filter in accordance with the joint of uplink TCI state for the SRS resource set. That is, if the transmit beam sweeping status is OFF, the UE may transmit in the SRS resources in the SRS resource set using the spatial domain filter that is the same as the spatial domain filter associated with the source reference signal in the joint or uplink TCI state associated with the SRS resource set.
  • the UE may apply spatial domain filters to SRS resources in the SRS resource set that are different from a spatial domain filter associated with the joint or uplink TCI state of the SRS resource set. That is, if the transmit beam sweeping status is ON, the UE may transmit in the SRS resources that are associated with the same joint or uplink TCI state using different spatial domain filters that are identified or otherwise determined based on the spatial domain filter associated with the source reference signal in the joint or uplink TCI state associated with the SRS resource set.
  • Application of the spatial domain filters may be used to generate or otherwise provide for the plurality of narrow beams used during SRS transmissions in the U3 beam refinement procedure.
  • the power control parameters may be determined based on the joint of uplink TCI state associated with the SRS resource set (e.g., rather than power control parameters configured per-SRS resource in the SRS resource set) .
  • FIG. 5 shows an example of a wireless communications system 500 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • Wireless communications system 500 may implement aspects of wireless communications system 100, or wireless communications system 200, or aspects of MAC-CE 300 or MAC-CE 400.
  • Wireless communications system 500 may include a UE 505, a network entity 510, and a network entity 515, which may be examples of the corresponding devices described herein.
  • the network entity 510 may be an example of a downlink TRP and the network entity 515 may be an example of an uplink TRP.
  • wireless communications system 500 illustrates an example of a lack of beam correspondence between the uplink and downlink channels of the UE.
  • the lack of beam correspondence may be due to the downlink TRP (e.g., the network entity 510) and the uplink TRP (e.g., the network entity 515) being non-collocated. That is, the downlink TRP and the uplink TRP may be geographically separated such that the downlink channel between the UE and the downlink TRP is different from the uplink channel between the UE and the uplink TRP.
  • initial beam acquisition after RRC connection establishment may become an issue due to the network entity (e.g., the downlink TRP, in this example) not having any prior information regarding which uplink TRP will perform satisfactorily with the UE.
  • the network entity e.g., the downlink TRP, in this example
  • one way to determine such information is for the UE to autonomously generate the transmit beam directionally and then for the network entity to select the best transmit beam direction, which may be implemented by not configuring a TCI state for beam management SRS or configuring a dummy TCI state for beam management SRS.
  • the network may provide a reference signal identifier for the selected downlink transmit beam and the UE may only be allowed to sweep the transmit beam within an indicated range of the corresponding receive beam. Restricting the uplink beam sweep range may reduce the overhead of the SRS used for uplink beam management.
  • aspects of the techniques described herein provide for a transmit/receive beam pattern for uplink beam management.
  • the described techniques enable uplink beam sweeping for both the transmit (e.g., the UE-side) and the receive (network entity-side) beam refinement with reasonable overhead.
  • the lack of beam correspondence may be based on the downlink TRP and the uplink TRP scenario shown in FIG. 5.
  • the receive beam e.g., receive beam 525 of the UE 505
  • a downlink reference signal transmit beam 520 of the downlink TRP used for transmission of the downlink reference signal
  • the downlink TRP e.g., the network entity 510
  • the UE 505 may receive or otherwise obtain (and the network entity 510 may transmit or otherwise output) signal (s) that carry or otherwise convey an indication of a beam sweeping range to be applied during SRS transmission to the uplink transmit point (e.g., the uplink TRP) .
  • the beam sweeping range may be indicated or otherwise defined in accordance with the downlink receive beam (e.g., the receive beam 525) corresponding to a downlink reference signal (e.g., a downlink reference signal transmitted using the transmit beam 520 of the downlink TRP) of a downlink transmit point (e.g., the downlink TRP) and an angular offset relative to the downlink receive beam.
  • a downlink reference signal e.g., a downlink reference signal transmitted using the transmit beam 520 of the downlink TRP
  • a downlink transmit point e.g., the downlink TRP
  • the angular offset may include a horizontal angular offset, a vertical angular offset, or both angular offsets.
  • the UE 505 may perform SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range. For example, the UE 505 may perform SRS transmissions using transmit beam 530, transmit beam 535, transmit beam 540, and transmit beam 545 (e.g., in a beam sweeping transmissions) to the uplink TRP.
  • the uplink TRP may identify or otherwise select an uplink receive beam (e.g., receive beam 550, in this example) based on the beam sweeping transmission from the UE 505, such as the receive beam associated with a channel performance metric that satisfies a performance threshold.
  • the UE 505 may use the indication of the downlink reference signal (e.g., corresponding to the downlink reference signal transmitted using transmit beam 520) and the angular offset to determine the transmit beam (s) to use for the SRS transmissions in the beam sweeping transmissions.
  • the indication of the downlink reference signal e.g., corresponding to the downlink reference signal transmitted using transmit beam 520
  • the angular offset to determine the transmit beam (s) to use for the SRS transmissions in the beam sweeping transmissions.
  • different techniques may be applied to carry or otherwise convey the indication of the downlink reference signal, the angular offset, or both, to the UE 505.
  • this may include the UE receiving or otherwise obtaining a configuration for a set of SRS resources (e.g., an SRS resource set) for performing the SRS transmissions.
  • the UE 505 may receive or otherwise obtain RRC signaling indicating the parameters below:
  • each SRS resource in the set of SRS resources may be associated with a joint or uplink TCI state that identifies a source reference signal.
  • the downlink reference signal and the corresponding downlink receive beam may be determined or otherwise identified based on the source refence signal. That is, in this example each SRS resource may be associated with a joint or uplink TCI state and the source reference signal in the joint or uplink TCI state associated with the SRS resources may be used as the downlink reference signal for determination of the downlink receive beam (e.g., the receive beam 525) .
  • this may include the UE receiving or otherwise obtaining a configuration for a set of SRS resources for performing the SRS transmissions.
  • each SRS resource in the set of SRS resources may be associated with a joint or uplink TCI state that identifies a pathloss reference signal.
  • the downlink reference signal and the corresponding downlink receive beam may be determined or otherwise identified based on the pathloss refence signal.
  • the UE 505 may receive or otherwise obtain RRC signaling indicating the parameters below:
  • each SRS resource may be associated with a joint or uplink TCI state and the pathloss reference signal in the joint or uplink TCI state associated with the SRS resources may be used as the downlink reference signal for determination of the downlink receive beam (e.g., the receive beam 525) .
  • this may include the UE receiving or otherwise obtaining a configuration for a set of SRS resources for performing the SRS transmissions.
  • each SRS resource in the set of SRS resources may be associated with a joint or uplink TCI state where a specific joint or uplink TCI state is used to identify the downlink reference signal for SRS resources in the set of SRS resources.
  • the downlink receive beam may be determined or otherwise identified based on the downlink refence signal. That is, in this example for SRS resources in an SRS resource set, a same downlink reference signal may be used as the downlink reference signal for determination of the downlink receive beam (e.g., the receive beam 525) .
  • the downlink reference signal may include either a source reference signal or a pathloss reference signal in the specific joint or uplink TCI state that is associated with the lowest resource identifier. That is, the source reference signal in the joint or uplink TCI state associated with the lowest SRS resource identifier may be used as the downlink reference signal for each SRS resource in the SRS resource set. Additionally, or alternatively, the pathloss reference signal in the joint or uplink TCI state associated with the lowest SRS resource identifier may be used as the downlink reference signal for each SRS resource in the SRS resource set.
  • this may include the downlink reference signal for receive beam determination being configured per-SRS resource (e.g., on a per-SRS resource basis) or per-SRS resource set (e.g., on a per-SRS resource set basis) .
  • the downlink reference signal may be indicated or otherwise configured as an SSB index, a CSI-RS index, or a pathloss reference signal identifier.
  • the UE 505 may receive or otherwise obtain RRC signaling indicating the parameters below:
  • each SRS resource may be configured with an associated downlink reference signal.
  • the UE 505 may also be configured with a serving cell identifier and a BWP identifier that the associated downlink reference signal is located in or otherwise associated with.
  • the UE 505 may receive or otherwise obtain RRC signaling indicating the parameters below:
  • each SRS resource set may be indicated or otherwise configured with an associated downlink reference signal.
  • the UE 505 may also be configured with a serving cell identifier and BWP identifier that the associated downlink reference signal is located in or otherwise associated with.
  • the downlink receive beam corresponding to the downlink reference signal may be indicated or otherwise identified as a source reference signal in a currently indicated joint of downlink TCI state associated with the downlink TRP. That is, the downlink reference signal may be identified or otherwise determined based on the latest source reference signal in the currently indicated or configured joint of downlink TCI state (e.g., corresponding to the downlink TRP) . Before an indicated joint or downlink TCI state is applied, the downlink reference signal may be identified or otherwise determined based on the SSB the UE 505 identified during the initial access procedure.
  • different techniques may be used to carry or otherwise convey the indication of the angular offset (e.g., the horizontal angular offset, the vertical angular offset, or both offsets) to the UE 505.
  • this may include the UE 505 receiving or otherwise obtaining a configuration for a set of SRS resources (e.g., an SRS resource set) to be used for performing the SRS transmission.
  • each SRS resource in the set of SRS resources may be associated with a joint or uplink TCI state that identifies the angular offset.
  • the UE 505 may receive or otherwise obtain RRC signaling indicating the parameters below:
  • the angular offset information (e.g., ⁇ offset , ⁇ offset ) may be configured in a joint or uplink TCI state.
  • the angular offset information in the associated joint or uplink TCI state may be used.
  • the angular offset information may be applied to SRS resources with usage set to beam management.
  • this may include the UE 505 receiving or otherwise obtaining a configuration for a set of SRS resources (e.g., an SRS resource set) for performing the SRS transmissions.
  • a set of SRS resources e.g., an SRS resource set
  • Each SRS resource in the set of SRS resources may be associated with the angular offset.
  • the UE 505 may receive or otherwise obtain RRC signaling indicating the parameters below:
  • the angular offset information (e.g., ⁇ offset , ⁇ offset ) may be configured per-SRS resource.
  • this may include the UE 505 receiving or otherwise obtaining a configuration for a set of SRS resources (e.g., an SRS resource set) for performing the SRS transmissions.
  • the set of SRS resources may be associated with a common angular offset and a set of delta values that, for each corresponding SRS resource in the set of SRS resources, carry or otherwise convey the indication of the angular offset for the corresponding SRS resource.
  • a common angular offset information e.g., ⁇ offset , ⁇ offset
  • a delta value with respect to the common angular offset may be indicated per-SRS resource.
  • each SRS resource in the set of SRS resources may be indicated with a corresponding delta value from the set of delta values. That is, the delta value may be configured or otherwise indicated per-SRS resource.
  • a common delta value may be configured or indicated with respect to
  • ⁇ offset-common and ⁇ offset-common or separate delta values may be configured or otherwise indicated with respect to ⁇ offset-common and ⁇ offset-common .
  • the UE 505 may receive or otherwise obtain RRC signaling indicating the parameters below:
  • each SRS resource in the set of SRS resources may be indicated with a same delta value from the set of delta values and a corresponding delta value for the corresponding SRS resource may be identified or otherwise determined in accordance with an order or index of the corresponding SRS resource. That is, the delta value may be configured or otherwise indicated per-SRS resource set and applied to each SRS resource depending on the order or index of the SRS resource within the SRS resource set. For example, if the delta value (e.g., either ⁇ ⁇ or ⁇ ⁇ ) is indicated as 5 degree, the UE 505 may apply 0, 5, 10, and 15 degrees for the first, second, third, and fourth, respectively, SRS resources within the SRS resource set.
  • the UE 505 may receive or otherwise obtain RRC signaling indicating the parameters below:
  • the receive beam of the downlink reference signal corresponding to the downlink TRP may change as well as the angular offset information may also change due to the change on location of the UE 505.
  • aspects of the techniques described herein may also provide for the downlink reference signal, the angular offset, or both, being updated via a MAC-CE.
  • a single MAC-CE may be used to updated both the downlink reference signal and the angular offset information or separate MAC-CEs may be used to update the downlink reference signal and angular offset information respectively.
  • the UE 505 may receive or otherwise obtain a MAC-CE that indicates an update to the downlink reference signal, to the angular offset, or to both pieces of information previously configured for the UE 505.
  • the update to the downlink reference signal, to the angular offset, or both may be associated with one or more joint or uplink TCI states.
  • the MAC-CE may update the downlink reference signal, the angular offset, or both, information for one or more joint of uplink TCI states.
  • the update to the downlink reference signal, to the angular offset, or both may be associated with one or more SRS resources.
  • the MAC-CE may update the downlink reference signal, the angular offset, or both, information for one or more SRS resources.
  • the update to the downlink reference signal, to the angular offset, or both may be associated with one or more SRS resource sets.
  • the MAC-CE may update the angular offset information for one or more SRS resource sets. This may include the situation where a common angular offset information is configured or otherwise indicated per-SRS resource set.
  • FIG. 6 shows an example of a wireless communications system 600 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • Wireless communications system 600 may implement aspects of wireless communications system 100, wireless communications system 200, or wireless communications system 500 or aspects of MAC-CE 300 or MAC-CE 400.
  • Wireless communications system 600 may include a UE 605, a network entity 610, and a network entity 615, which may be examples of the corresponding devices described herein.
  • the network entity 610 may be an example of a downlink TRP and the network entity 615 may be an example of an uplink TRP.
  • the UE 605 may receive or otherwise obtain signal (s) that carry or otherwise convey an indication of a beam sweeping range to be applied during SRS transmissions to the uplink TRP.
  • the beam sweeping range may correspond to or otherwise be defined in relation to a downlink receive beam (e.g., the receive beam 625) corresponding to a downlink reference signal (e.g., the transmit beam 620 used for transmission of the downlink reference signal) of the downlink TRP (e.g., the network entity 610, in this example) .
  • the beam sweeping range may further correspond to or otherwise be defined in relation to an angular offset relative to the downlink receive beam.
  • the UE 605 may perform the SRS transmission to the uplink TRP in beam sweeping transmissions according to the beam sweeping range.
  • the downlink TRP (e.g., the downlink transmit point) and the uplink TRP (e.g., the uplink transmit point) may be in a non-collocated deployment scenario as shown in FIG. 6.
  • the receive beam associated with a downlink reference signal corresponding to the downlink TRP may be used as a reference.
  • this may be based on the location of the UE (e.g., x UE , y UE , z UE , ) , the location of the downlink TRP (e.g., x 1 , y 1 , z 1 , ) , and the location of the uplink TRP (e.g., x 2 , y 2 , z 2 , ) .
  • the location information of the UE 605 may be known by the downlink TRP and the location information of the uplink TRP may also be known by the downlink TRP (e.g., via backhaul signaling or other inter-TRP information exchange) .
  • the downlink TRP may derive or otherwise determine the horizontal angular offset ⁇ between the downlink TRP and the uplink TRP.
  • the horizontal angular offset ⁇ may be derived based on the location of the UE 605, of the downlink TRP, and of the uplink TRP.
  • the downlink TRP may derive the vertical angular ⁇ 1 between the downlink TRP and the UE based on the location of the UE 605 and the downlink TRP location.
  • the uplink TRP may derive the vertical angular ⁇ 2 between the uplink TRP and the UE 605 based on the UE location and the uplink TRP location.
  • the uplink TRP may transmit, output, or otherwise provide the vertical angular ⁇ 2 information to the downlink TRP and the downlink TRP may derive the vertical angular offset using ⁇ 1 - ⁇ 2 .
  • the downlink TRP may carry or otherwise convey an indication of a range (e.g., the beam sweeping range) relative to the downlink receive beam for the uplink transmit beam sweep based on the horizontal angular offset and the vertical angular offset.
  • the UE 605 may be indicated with a transmit beam range by or based on the angular offset information relative to a receive beam of a downlink reference signal for uplink transmit beam sweeping.
  • the angular offset information may include the horizontal angular offset denoted as ⁇ offset and the vertical angular offset denoted by ⁇ offset .
  • the horizontal angular offset may be with respect to the horizontal beam direction of the receive beam corresponding to the downlink reference signal.
  • the vertical angular offset may be with respect to the vertical beam direction of the receive beam corresponding to the downlink reference signal.
  • the downlink reference signal may include an SSB or CSI-RS transmission from the downlink TRP using a downlink transmit beam (e.g., the transmit beam 620, which may be associated with a source or pathloss reference signal index or identifier) that corresponds to an uplink receive beam (e.g., receive beam 625) of the UE 605.
  • the uplink receive beam direction may be denoted as ( ⁇ ref , ⁇ ref ) .
  • the UE 605 may perform the SRS transmissions in beam sweeping transmissions according to the beam sweeping range.
  • the UE 605 may perform a first SRS transmission using a transmit beam 630 in a direction according to ( ⁇ offset, 1 , ⁇ offset, 1 ) , perform a second SRS transmission using a transmit beam 635 in a direction according to ( ⁇ offset, 2 , ⁇ offset, 2 ) , perform a third SRS transmission using a transmit beam 640 in a direction according to ( ⁇ offset, 3 , ⁇ offset, 3 ) , and perform a fourth SRS transmission using a transmit beam 645 in a direction according to ( ⁇ offset, 4 , ⁇ offset, 4 ) .
  • the transmit beam directions for the beam sweeping SRS transmissions in this example may correspond to ( ⁇ ref + ⁇ offset, 1 , ⁇ ref + ⁇ offset, 1 ) , ( ⁇ ref + ⁇ offset, 2 , ⁇ ref + ⁇ offset, 2 ) , ( ⁇ ref + ⁇ offset, 3 , ⁇ ref + ⁇ offset, 3 ) , and ( ⁇ ref + ⁇ offset, 4 , ⁇ ref + ⁇ offset, 4 ) for the transmit beam 630, the transmit beam 635, the transmit beam 640, and the transmit beam 645, respectively.
  • the uplink TRP may measure, identify, or otherwise determine that uplink receive beam 650 is the best performing (e.g., channel performance metrics that satisfy a performance threshold) receive beam to be used for uplink transmissions from the UE 605.
  • the uplink receive beam 650 may correspond to transmit beam 635 of the UE 605, in this example.
  • FIG. 7 shows a block diagram 700 of a device 705 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the device 705 may be an example of aspects of a UE 115 as described herein.
  • the device 705 may include a receiver 710, a transmitter 715, and a communications manager 720.
  • the device 705, or one or more components of the device 705 may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 710 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to SRS enhancement for uplink beam management) . Information may be passed on to other components of the device 705.
  • the receiver 710 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 715 may provide a means for transmitting signals generated by other components of the device 705.
  • the transmitter 715 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to SRS enhancement for uplink beam management) .
  • the transmitter 715 may be co-located with a receiver 710 in a transceiver module.
  • the transmitter 715 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be examples of means for performing various aspects of SRS enhancement for uplink beam management as described herein.
  • the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
  • the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • DSP digital signal processor
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • microcontroller discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • At least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
  • the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
  • a general-purpose processor e.g., a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions
  • the communications manager 720 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 710, the transmitter 715, or both.
  • the communications manager 720 may receive information from the receiver 710, send information to the transmitter 715, or be integrated in combination with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 720 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 720 is capable of, configured to, or operable to support a means for receiving one or more signals including an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status including either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a set of multiple narrow beam widths, where the set of multiple narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the communications manager 720 is capable of, configured to, or operable to support a means for performing the SRS transmissions according to the beam sweeping status.
  • the communications manager 720 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 720 is capable of, configured to, or operable to support a means for receiving one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the communications manager 720 is capable of, configured to, or operable to support a means for performing the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the device 705 may support techniques for SRS-based uplink beam management when the usage of the SRS resources are set to beam management. This may include the U1-U3 beam refinement procedure being supported based on beam sweeping status signaling. This may include the SRS beam sweeping being based on a beams sweeping range indicated to the UE.
  • FIG. 8 shows a block diagram 800 of a device 805 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the device 805 may be an example of aspects of a device 705 or a UE 115 as described herein.
  • the device 805 may include a receiver 810, a transmitter 815, and a communications manager 820.
  • the device 805, or one of more components of the device 805 (e.g., the receiver 810, the transmitter 815, the communications manager 820) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 810 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to SRS enhancement for uplink beam management) . Information may be passed on to other components of the device 805.
  • the receiver 810 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 815 may provide a means for transmitting signals generated by other components of the device 805.
  • the transmitter 815 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to SRS enhancement for uplink beam management) .
  • the transmitter 815 may be co-located with a receiver 810 in a transceiver module.
  • the transmitter 815 may utilize a single antenna or a set of multiple antennas.
  • the device 805, or various components thereof may be an example of means for performing various aspects of SRS enhancement for uplink beam management as described herein.
  • the communications manager 820 may include a beam sweeping manager 825, an SRS manager 830, a beam sweeping range manager 835, or any combination thereof.
  • the communications manager 820 may be an example of aspects of a communications manager 720 as described herein.
  • the communications manager 820, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 815, or both.
  • the communications manager 820 may receive information from the receiver 810, send information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 820 may support wireless communications in accordance with examples as disclosed herein.
  • the beam sweeping manager 825 is capable of, configured to, or operable to support a means for receiving one or more signals including an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status including either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a set of multiple narrow beam widths, where the set of multiple narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the SRS manager 830 is capable of, configured to, or operable to support a means for performing the SRS transmissions according to the beam sweeping status.
  • the communications manager 820 may support wireless communications in accordance with examples as disclosed herein.
  • the beam sweeping range manager 835 is capable of, configured to, or operable to support a means for receiving one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the SRS manager 830 is capable of, configured to, or operable to support a means for performing the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • FIG. 9 shows a block diagram 900 of a communications manager 920 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the communications manager 920 may be an example of aspects of a communications manager 720, a communications manager 820, or both, as described herein.
  • the communications manager 920, or various components thereof, may be an example of means for performing various aspects of SRS enhancement for uplink beam management as described herein.
  • the communications manager 920 may include a beam sweeping manager 925, an SRS manager 930, a beam sweeping range manager 935, an SRS resource set manager 940, an SRS resource manager 945, a Joint or uplink TCI state manager 950, a UE capability manager 955, a downlink receive beam manager 960, an angular offset manager 965, an update manager 970, a DCI manager 975, or any combination thereof.
  • Each of these components, or components or subcomponents thereof e.g., one or more processors, one or more memories
  • the communications manager 920 may support wireless communications in accordance with examples as disclosed herein.
  • the beam sweeping manager 925 is capable of, configured to, or operable to support a means for receiving one or more signals including an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status including either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a set of multiple narrow beam widths, where the set of multiple narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the SRS manager 930 is capable of, configured to, or operable to support a means for performing the SRS transmissions according to the beam sweeping status.
  • the beam sweeping status is configured on at least one of a per-SRS resource basis, a per-SRS resource set basis, or a per-joint or uplink TCI state basis.
  • the first beam sweeping state is configured on a per-SRS resource set basis, and the SRS resource set manager 940 is capable of, configured to, or operable to support a means for receiving an indication of a joint or uplink TCI state associated with each SRS resource in an SRS resource set.
  • the first beam sweeping state is configured on a per-SRS resource set basis
  • the SRS resource set manager 940 is capable of, configured to, or operable to support a means for applying, for each SRS resource in the SRS resource set, a spatial domain filter to SRS resources in accordance with the joint or uplink TCI state associated with the SRS resource, where the spatial domain filter is associated with a source reference signal in the joint or uplink TCI state.
  • the second beam sweeping state is configured on a per-SRS resource set basis
  • the SRS resource set manager 940 is capable of, configured to, or operable to support a means for receiving, for each SRS resource in an SRS resource set, an indication of a joint or uplink TCI state associated with the SRS resource.
  • the second beam sweeping state is configured on a per-SRS resource set basis
  • the SRS resource set manager 940 is capable of, configured to, or operable to support a means for applying a first spatial domain filter to each SRS resource in the SRS resource set in accordance with the joint or uplink TCI state of the SRS resource, where the first spatial domain filter is different from a second spatial domain filter associated with a source reference signal in the joint or uplink TCI state of the SRS resource.
  • the first beam sweeping state is configured on a per-SRS resource basis, and the SRS resource manager 945 is capable of, configured to, or operable to support a means for receiving an indication of a joint or uplink TCI state associated with an SRS resource.
  • the first beam sweeping state is configured on a per-SRS resource basis, and the SRS resource manager 945 is capable of, configured to, or operable to support a means for applying a spatial domain filter to the SRS resource in accordance with a source reference signal in the joint or uplink TCI state.
  • the second beam sweeping state is configured on a per-SRS resource basis, and the SRS resource manager 945 is capable of, configured to, or operable to support a means for receiving an indication of a joint or uplink TCI state associated with an SRS resource.
  • the second beam sweeping state is configured on a per-SRS resource basis, and the SRS resource manager 945 is capable of, configured to, or operable to support a means for applying different spatial domain filters to the SRS resource during different symbols in accordance with a source reference signal in the joint or uplink TCI state, where application of the different spatial domain filters during the different symbols includes the set of multiple narrow beam widths.
  • the second beam sweeping state is configured on a per-SRS resource basis, and the SRS resource manager 945 is capable of, configured to, or operable to support a means for receiving an indication of a joint or uplink TCI state associated with an SRS resource.
  • the second beam sweeping state is configured on a per-SRS resource basis, and the SRS resource manager 945 is capable of, configured to, or operable to support a means for applying a unique spatial domain filter to the SRS resource during different symbols that is different from a spatial domain filter associated with a source reference signal in the joint or uplink TCI state, where application of the unique spatial domain filter during different symbols includes a narrow beam width.
  • the first beam sweeping state is configured on a per-joint or uplink TCI state basis
  • the Joint or uplink TCI state manager 950 is capable of, configured to, or operable to support a means for receiving an indication of a joint or uplink TCI state associated with an SRS resource set.
  • the first beam sweeping state is configured on a per-joint or uplink TCI state basis
  • the Joint or uplink TCI state manager 950 is capable of, configured to, or operable to support a means for applying a spatial domain filter to SRS resources in the SRS resource set in accordance with a source reference signal in the joint or uplink TCI state.
  • the second beam sweeping state is configured on a per-joint or uplink TCI state basis
  • the Joint or uplink TCI state manager 950 is capable of, configured to, or operable to support a means for receiving an indication of a joint or uplink TCI state associated with an SRS resource set.
  • the second beam sweeping state is configured on a per-joint or uplink TCI state basis
  • the Joint or uplink TCI state manager 950 is capable of, configured to, or operable to support a means for applying multiple spatial domain filters to SRS resources in the SRS resource set that is different from a spatial domain filter associated with a source reference signal in the joint or uplink TCI state, where application of the multiple spatial domain filters to the SRS resources includes the set of multiple narrow beam widths.
  • the beam sweeping status is configured on a per-joint or uplink TCI state basis
  • the Joint or uplink TCI state manager 950 is capable of, configured to, or operable to support a means for receiving an indication of a joint or uplink TCI state associated with a SRS resource.
  • the beam sweeping status is configured on a per-joint or uplink TCI state basis
  • the Joint or uplink TCI state manager 950 is capable of, configured to, or operable to support a means for applying a beam sweeping status to SRS resources within an SRS resource set in accordance with the beam sweeping status in the joint or uplink TCI state associated with a specific SRS resource, where the specific SRS resource includes a lowest resource identifier within the SRS resource set.
  • the indication of the beam sweeping status is received in a MAC-CE.
  • the beam sweeping status is on a per-SRS resource set basis and a bit in the MAC-CE indicates either the first beam sweeping state or the second beam sweeping state for SRS resources in the SRS resource set.
  • the beam sweeping status is on a per-SRS resource basis and a set of bits in the MAC-CE corresponding to SRS resources in the SRS resource set indicates, for each SRS resource, either the first beam sweeping state or the second beam sweeping state.
  • the indication of the beam sweeping status is received in a DCI and a bit in the DCI indicates either the first beam sweeping state or the second beam sweeping state for one or more SRS resource sets.
  • the SRS transmissions include aperiodic SRS transmissions associated with one or more trigger states where each trigger state is associated with a beam sweeping status that are configured for the UE via RRC signaling.
  • the DCI manager 975 is capable of, configured to, or operable to support a means for receiving a DCI that activates the aperiodic SRS transmissions associated with a trigger state, where the beam sweeping status associated with the trigger state is applied for the aperiodic SRS transmissions.
  • the SRS resource set manager 940 is capable of, configured to, or operable to support a means for receiving an indication of a joint or uplink TCI state for an SRS resource set.
  • the UE being configured with the joint or uplink TCI state for the SRS resource set indicates the second beam sweeping state.
  • the joint or uplink TCI state for the SRS resource set omits a corresponding joint or uplink TCI state for SRS resources in the SRS resource set.
  • the indication of the joint or uplink TCI state for the SRS resource set is received in RRC signaling or in a MAC-CE.
  • a set of power control parameters for SRS resources in the SRS resource set are determined in accordance with the joint or uplink TCI state for the SRS resource set.
  • the Joint or uplink TCI state manager 950 is capable of, configured to, or operable to support a means for receiving an indication of a joint or uplink TCI state and a beam sweeping status for an SRS resource set.
  • the beam sweeping status includes the first beam sweeping state
  • the Joint or uplink TCI state manager 950 is capable of, configured to, or operable to support a means for applying, for each SRS resource in the SRS resource set, a spatial domain filter in accordance with the joint or uplink TCI state of the SRS resource set.
  • the beam sweeping status includes the second beam sweeping state
  • the Joint or uplink TCI state manager 950 is capable of, configured to, or operable to support a means for applying spatial domain filters to SRS resources in the SRS resource set that are different from a spatial domain filter associated with the joint or uplink TCI state of the SRS resource set, where application of the spatial domain filters include the set of multiple narrow beam widths.
  • the set of multiple narrow beam widths that are within the range of the wide beamwidth of the transmit beam are in accordance with, for each narrow beam, a threshold power level associated with the wide beamwidth. In some examples, the set of multiple narrow beam widths that are within the range of the wide beamwidth of the transmit beam are in accordance with, for each narrow beam, a threshold beam direction associated with the wide beamwidth.
  • the UE capability manager 955 is capable of, configured to, or operable to support a means for transmitting UE capability signaling indicating support for hierarchical beam management, where the one or more signals indicating the beam sweeping status are in accordance with the UE capability signaling. In some examples, the UE capability signaling further indicates a quantity of transmit beams or SRS resources that are supported for U1 beam sweeping, for U3 beam sweeping, or both.
  • the communications manager 920 may support wireless communications in accordance with examples as disclosed herein.
  • the beam sweeping range manager 935 is capable of, configured to, or operable to support a means for receiving one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the SRS manager 930 is capable of, configured to, or operable to support a means for performing the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the angular offset includes a horizontal angular offset, a vertical angular offset, or both.
  • the downlink receive beam manager 960 is capable of, configured to, or operable to support a means for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state that identifies a source reference signal and the downlink receive beam is identified in accordance with the source reference signal.
  • the downlink receive beam manager 960 is capable of, configured to, or operable to support a means for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state that identifies a pathloss reference signal and the downlink receive beam is identified in accordance with the pathloss reference signal.
  • the downlink receive beam manager 960 is capable of, configured to, or operable to support a means for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state where a specific joint or uplink TCI state is used to identify the downlink reference signal for SRS resources in the set of SRS resources and the downlink receive beam is identified in accordance with the downlink reference signal.
  • the downlink reference signal includes either a source reference signal or a pathloss reference signal in the specific joint or uplink TCI state that is associated with a lowest resource identifier.
  • the downlink receive beam corresponding to the downlink reference signal is configured or indicated on a per-SRS resource basis or on a per-SRS resource set basis.
  • the downlink receive beam corresponding to the downlink reference signal is identified as a source reference signal in a current indicated joint or downlink TCI state associated with the downlink transmit point.
  • the angular offset manager 965 is capable of, configured to, or operable to support a means for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resources in the set of SRS resources are associated with a joint or uplink TCI state that identifies the angular offset. In some examples, to support receiving the one or more signals, the angular offset manager 965 is capable of, configured to, or operable to support a means for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources is associated with the angular offset.
  • the angular offset manager 965 is capable of, configured to, or operable to support a means for receiving a configuration for a set of SRS resources for performing the SRS transmissions, where the set of SRS resources is associated with a common angular offset and a set of delta values that, for each corresponding SRS resource in the set of SRS resources, identify the angular offset for the corresponding SRS resource.
  • each SRS resource in the set of SRS resources is indicated with a corresponding delta value from the set of delta values.
  • each SRS resource in the set of SRS resources is indicated with a same delta value from the set of delta values and a corresponding delta value for the corresponding SRS resource is identified in accordance with an order or index of the corresponding SRS resource in the set of SRS resources.
  • the update manager 970 is capable of, configured to, or operable to support a means for receiving a MAC-CE that indicates an update to the downlink reference signal, to the angular offset, or both.
  • the update to the downlink reference signal, to the angular offset, or both is associated with one or more joint or uplink TCI states.
  • the update to the downlink reference signal, to the angular offset, or both is associated with one or more SRS resources.
  • the update to the downlink reference signal, to the angular offset, or both is associated with one or more SRS resource sets.
  • FIG. 10 shows a diagram of a system 1000 including a device 1005 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the device 1005 may be an example of or include components of a device 705, a device 805, or a UE 115 as described herein.
  • the device 1005 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) .
  • the device 1005 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1020, an input/output (I/O) controller, such as an I/O controller 1010, a transceiver 1015, one or more antennas 1025, at least one memory 1030, code 1035, and at least one processor 1040. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045) .
  • a bus 1045 e.g., a bus 1045
  • the I/O controller 1010 may manage input and output signals for the device 1005.
  • the I/O controller 1010 may also manage peripherals not integrated into the device 1005.
  • the I/O controller 1010 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1010 may utilize an operating system such as or another known operating system.
  • the I/O controller 1010 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1010 may be implemented as part of one or more processors, such as the at least one processor 1040.
  • a user may interact with the device 1005 via the I/O controller 1010 or via hardware components controlled by the I/O controller 1010.
  • the device 1005 may include a single antenna. However, in some other cases, the device 1005 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 1015 may communicate bi-directionally via the one or more antennas 1025 using wired or wireless links as described herein.
  • the transceiver 1015 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1015 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1025 for transmission, and to demodulate packets received from the one or more antennas 1025.
  • the transceiver 1015 may be an example of a transmitter 715, a transmitter 815, a receiver 710, a receiver 810, or any combination thereof or component thereof, as described herein.
  • the at least one memory 1030 may include random access memory (RAM) and read-only memory (ROM) .
  • the at least one memory 1030 may store computer-readable, computer-executable, or processor-executable code, such as the code 1035.
  • the code 1035 may include instructions that, when executed by the at least one processor 1040, cause the device 1005 to perform various functions described herein.
  • the code 1035 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 1035 may not be directly executable by the at least one processor 1040 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the at least one memory 1030 may include, 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 at least one processor 1040 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) .
  • the at least one processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1040.
  • the at least one processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks supporting SRS enhancement for uplink beam management) .
  • a memory e.g., the at least one memory 1030
  • the device 1005 or a component of the device 1005 may include at least one processor 1040 and at least one memory 1030 coupled with or to the at least one processor 1040, the at least one processor 1040 and the at least one memory 1030 configured to perform various functions described herein.
  • the at least one processor 1040 may include multiple processors and the at least one memory 1030 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein.
  • the at least one processor 1040 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1040) and memory circuitry (which may include the at least one memory 1030) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs.
  • the processing system may be configured to perform one or more of the functions described herein.
  • the at least one processor 1040 or a processing system including the at least one processor 1040 may be configured to, configurable to, or operable to cause the device 1005 to perform one or more of the functions described herein.
  • being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1035 (e.g., processor-executable code) stored in the at least one memory 1030 or otherwise, to perform one or more of the functions described herein.
  • code 1035 e.g., processor-executable code
  • the communications manager 1020 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 1020 is capable of, configured to, or operable to support a means for receiving one or more signals including an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status including either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a set of multiple narrow beam widths, where the set of multiple narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the communications manager 1020 is capable of, configured to, or operable to support a means for performing the SRS transmissions according to the beam sweeping status.
  • the communications manager 1020 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 1020 is capable of, configured to, or operable to support a means for receiving one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the communications manager 1020 is capable of, configured to, or operable to support a means for performing the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the device 1005 may support techniques for SRS-based uplink beam management when the usage of the SRS resources are set to beam management. This may include the U1-U3 beam refinement procedure being supported based on beam sweeping status signaling. This may include the SRS beam sweeping being based on a beams sweeping range indicated to the UE.
  • the communications manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1015, the one or more antennas 1025, or any combination thereof.
  • the communications manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1020 may be supported by or performed by the at least one processor 1040, the at least one memory 1030, the code 1035, or any combination thereof.
  • the code 1035 may include instructions executable by the at least one processor 1040 to cause the device 1005 to perform various aspects of SRS enhancement for uplink beam management as described herein, or the at least one processor 1040 and the at least one memory 1030 may be otherwise configured to, individually or collectively, perform or support such operations.
  • FIG. 11 shows a block diagram 1100 of a device 1105 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the device 1105 may be an example of aspects of a network entity 105 as described herein.
  • the device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120.
  • the device 1105, or one or more components of the device 1105 may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1110 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • Information may be passed on to other components of the device 1105.
  • the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1115 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1105.
  • the transmitter 1115 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • the transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be examples of means for performing various aspects of SRS enhancement for uplink beam management as described herein.
  • the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
  • the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure.
  • at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
  • the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
  • the communications manager 1120 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1110, the transmitter 1115, or both.
  • the communications manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 1120 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 1120 is capable of, configured to, or operable to support a means for outputting, to a UE, one or more signals including an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status including either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a set of multiple narrow beam widths, where the set of multiple narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the communications manager 1120 is capable of, configured to, or operable to support a means for obtaining the SRS transmissions according to the beam sweeping status.
  • the communications manager 1120 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 1120 is capable of, configured to, or operable to support a means for outputting, to a UE and via a downlink transmit point, one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the communications manager 1120 is capable of, configured to, or operable to support a means for obtaining the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the device 1105 may support techniques for SRS-based uplink beam management when the usage of the SRS resources are set to beam management. This may include the U1-U3 beam refinement procedure being supported based on beam sweeping status signaling. This may include the SRS beam sweeping being based on a beams sweeping range indicated to the UE.
  • FIG. 12 shows a block diagram 1200 of a device 1205 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the device 1205 may be an example of aspects of a device 1105 or a network entity 105 as described herein.
  • the device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220.
  • the device 1205, or one of more components of the device 1205 may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1210 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • Information may be passed on to other components of the device 1205.
  • the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1215 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1205.
  • the transmitter 1215 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) .
  • the transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the device 1205, or various components thereof may be an example of means for performing various aspects of SRS enhancement for uplink beam management as described herein.
  • the communications manager 1220 may include a beam sweeping manager 1225, an SRS manager 1230, a beam sweeping range manager 1235, or any combination thereof.
  • the communications manager 1220 may be an example of aspects of a communications manager 1120 as described herein.
  • the communications manager 1220, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1210, the transmitter 1215, or both.
  • the communications manager 1220 may receive information from the receiver 1210, send information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 1220 may support wireless communications in accordance with examples as disclosed herein.
  • the beam sweeping manager 1225 is capable of, configured to, or operable to support a means for outputting, to a UE, one or more signals including an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status including either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a set of multiple narrow beam widths, where the set of multiple narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the SRS manager 1230 is capable of, configured to, or operable to support a means for obtaining the SRS transmissions according to the beam sweeping status.
  • the communications manager 1220 may support wireless communications in accordance with examples as disclosed herein.
  • the beam sweeping range manager 1235 is capable of, configured to, or operable to support a means for outputting, to a UE and via a downlink transmit point, one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the SRS manager 1230 is capable of, configured to, or operable to support a means for obtaining the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • FIG. 13 shows a block diagram 1300 of a communications manager 1320 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the communications manager 1320 may be an example of aspects of a communications manager 1120, a communications manager 1220, or both, as described herein.
  • the communications manager 1320, or various components thereof, may be an example of means for performing various aspects of SRS enhancement for uplink beam management as described herein.
  • the communications manager 1320 may include a beam sweeping manager 1325, an SRS manager 1330, a beam sweeping range manager 1335, an SRS resource set manager 1340, an SRS resource manager 1345, a joint or uplink TCI state manager 1350, a UE capability manager 1355, a downlink receive beam manager 1360, an angular offset manager 1365, an update manager 1370, a DCI manager 1375, or any combination thereof.
  • Each of these components, or components or subcomponents thereof e.g., one or more processors, one or more memories
  • the communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.
  • the communications manager 1320 may support wireless communications in accordance with examples as disclosed herein.
  • the beam sweeping manager 1325 is capable of, configured to, or operable to support a means for outputting, to a UE, one or more signals including an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status including either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a set of multiple narrow beam widths, where the set of multiple narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the SRS manager 1330 is capable of, configured to, or operable to support a means for obtaining the SRS transmissions according to the beam sweeping status.
  • the beam sweeping status is configured on at least one of a per-SRS resource basis, a per-SRS resource set basis, or a per-joint or uplink TCI state basis.
  • the first beam sweeping state is configured on a per-SRS resource set basis
  • the SRS resource set manager 1340 is capable of, configured to, or operable to support a means for outputting an indication of a joint or uplink TCI state associated with each SRS resource in an SRS resource set, where the UE applies, for each SRS resource in the SRS resource set, a spatial domain filter to SRS resources in accordance with the joint or uplink TCI state associated with the SRS resource, where the spatial domain filter is associated with a source reference signal in the joint or uplink TCI state.
  • the second beam sweeping state is configured on a per-SRS resource set basis
  • the SRS resource set manager 1340 is capable of, configured to, or operable to support a means for outputting, for each SRS resource in a SRS resource set, an indication of a joint or uplink TCI state associated with the SRS resource, where the UE applies a first spatial domain filter to each SRS resource in the SRS resource set in accordance with the joint or uplink TCI state of the SRS resource, where the first spatial domain filter is different from a second spatial domain filter associated with a source reference signal in the joint or uplink TCI state of the SRS resource.
  • the first beam sweeping state is configured on a per-SRS resource basis
  • the SRS resource manager 1345 is capable of, configured to, or operable to support a means for outputting an indication of a joint or uplink TCI state associated with an SRS resource, where the UE applies a spatial domain filter to the SRS resource in accordance with a source reference signal in the joint or uplink TCI state.
  • the second beam sweeping state is configured on a per-SRS resource basis
  • the SRS resource manager 1345 is capable of, configured to, or operable to support a means for outputting an indication of a joint or uplink TCI state associated with an SRS resource, where the UE applies different spatial domain filters to the SRS resource during different symbols in accordance with a source reference signal in the joint or uplink TCI state, where application of the different spatial domain filters during the different symbols includes the set of multiple narrow beam widths.
  • the second beam sweeping state is configured on a per-SRS resource basis
  • the SRS resource manager 1345 is capable of, configured to, or operable to support a means for outputting an indication of a joint or uplink TCI state associated with an SRS resource, where the UE applies a unique spatial domain filter to the SRS resource during different symbols that is different from a spatial domain filter associated with a source reference signal in the joint or uplink TCI state, where application of the unique spatial domain filter during different symbols includes the set of multiple narrow beam widths.
  • the first beam sweeping state is configured on a per-joint or uplink TCI state basis
  • the joint or uplink TCI state manager 1350 is capable of, configured to, or operable to support a means for outputting an indication of a joint or uplink TCI state associated with an SRS resource set, where the UE applies a spatial domain filter to SRS resources in the SRS resource set in accordance with a source reference signal in the joint or uplink TCI state.
  • the second beam sweeping state is configured on a per-joint or uplink TCI state basis
  • the joint or uplink TCI state manager 1350 is capable of, configured to, or operable to support a means for outputting an indication of a joint or uplink TCI state associated with a SRS resource set, where the UE applies multiple spatial domain filters to SRS resources in the SRS resource set that is different from a spatial domain filter associated with a source reference signal in the joint or uplink TCI state, where application of the multiple spatial domain filters to the SRS resources includes the set of multiple narrow beam widths.
  • the beam sweeping status is configured on a per-joint or uplink TCI state basis
  • the joint or uplink TCI state manager 1350 is capable of, configured to, or operable to support a means for outputting an indication of a joint or uplink TCI state associated with a SRS resource, where the UE applies a beam sweeping status to the SRS resources within an SRS resource set in accordance with the beam sweeping status in the joint or uplink TCI state associated with a specific SRS resource, where the specific SRS resource includes a lowest resource identifier within the SRS resource set.
  • the indication of the beam sweeping status is output in a MAC-CE.
  • the beam sweeping status is on a per-SRS resource set basis and a bit in the MAC-CE indicates either the first beam sweeping state or the second beam sweeping state for SRS resources in the SRS resource set.
  • the beam sweeping status is on a per-SRS resource basis and a set of bits in the MAC-CE corresponding to SRS resources in the SRS resource set indicates, for each SRS resource, either the first beam sweeping state or the second beam sweeping state.
  • the indication of the beam sweeping status is output in a DCI and a bit in the DCI indicates either the first beam sweeping state or the second beam sweeping state for one or more SRS resource sets.
  • the SRS transmissions include aperiodic SRS transmissions associated with one or more trigger states where each trigger state is associated with a beam sweeping status that are configured for the UE via RRC signaling.
  • the DCI manager 1375 is capable of, configured to, or operable to support a means for outputting a DCI that activates the aperiodic SRS transmissions associated with a trigger state, where the beam sweeping status associated with the trigger state is applied for the aperiodic SRS transmissions.
  • the joint or uplink TCI state manager 1350 is capable of, configured to, or operable to support a means for outputting an indication of a joint or uplink TCI state for an SRS resource set.
  • the UE being configured with the joint or uplink TCI state for the SRS resource set indicates the second beam sweeping state.
  • the joint or uplink TCI state for the SRS resource set omits a corresponding joint or uplink TCI state for SRS resources in the SRS resource set.
  • the indication of the joint or uplink TCI state for the SRS resource set is output in RRC signaling or in a MAC-CE.
  • a set of power control parameters for SRS resources in the SRS resource set are determined in accordance with the joint or uplink TCI state for the SRS resource set.
  • the joint or uplink TCI state manager 1350 is capable of, configured to, or operable to support a means for outputting an indication of a joint or uplink TCI state and a beam sweeping status for an SRS resource set.
  • the beam sweeping status includes the first beam sweeping state and the UE applies, for each SRS resource in the SRS resource set, a spatial domain filter in accordance with the joint or uplink TCI state of the SRS resource set.
  • the beam sweeping status includes the second beam sweeping state and the UE applies spatial domain filters to SRS resources in the SRS resource set that are different from a spatial domain filter associated with the joint or uplink TCI state of the SRS resource set.
  • application of the spatial domain filters include the set of multiple narrow beam widths.
  • the set of multiple narrow beam widths that are within the range of the wide beamwidth of the transmit beam are in accordance with, for each narrow beam, a threshold power level associated with the wide beamwidth. In some examples, the set of multiple narrow beam widths that are within the range of the wide beamwidth of the transmit beam are in accordance with, for each narrow beam, a threshold beam direction associated with the wide beamwidth.
  • the UE capability manager 1355 is capable of, configured to, or operable to support a means for obtaining UE capability signaling indicating support for hierarchical beam management, where the one or more signals indicating the beam sweeping status are in accordance with the UE capability signaling.
  • the UE capability signaling further indicates a quantity of transmit beams or SRS resources that are supported for U1 beam sweeping, U3 beam sweeping, or both.
  • the communications manager 1320 may support wireless communications in accordance with examples as disclosed herein.
  • the beam sweeping range manager 1335 is capable of, configured to, or operable to support a means for outputting, to a UE and via a downlink transmit point, one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the SRS manager 1330 is capable of, configured to, or operable to support a means for obtaining the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the angular offset includes a horizontal angular offset, a vertical angular offset, or both.
  • the downlink receive beam manager 1360 is capable of, configured to, or operable to support a means for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state that identifies a source reference signal and the downlink receive beam is identified in accordance with the source reference signal.
  • the downlink receive beam manager 1360 is capable of, configured to, or operable to support a means for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state that identifies a pathloss reference signal and the downlink receive beam is identified in accordance with the pathloss reference signal.
  • the downlink receive beam manager 1360 is capable of, configured to, or operable to support a means for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state where a specific joint or uplink TCI state is used to identify the downlink reference signal for SRS resources in the set of SRS resources and the downlink receive beam is identified in accordance with the downlink reference signal.
  • the downlink reference signal includes either a source reference signal or a pathloss reference signal in the specific joint or uplink TCI state that is associated with a lowest resource identifier.
  • the downlink receive beam corresponding to the downlink reference signal is configured or indicated on a per-SRS resource basis or on a per-SRS resource set basis. In some examples, the downlink receive beam corresponding to the downlink reference signal is identified as a source reference signal in a current indicated joint or downlink TCI state associated with the downlink transmit point.
  • the angular offset manager 1365 is capable of, configured to, or operable to support a means for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resources in the set of SRS resources are associated with a joint or uplink TCI state that identifies the angular offset. In some examples, to support outputting the one or more signals, the angular offset manager 1365 is capable of, configured to, or operable to support a means for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where each SRS resource in the set of SRS resources is associated with the angular offset.
  • the angular offset manager 1365 is capable of, configured to, or operable to support a means for outputting a configuration for a set of SRS resources for performing the SRS transmissions, where the set of SRS resources is associated with a common angular offset and a set of delta values that, for each corresponding SRS resource in the set of SRS resources, identify the angular offset for the corresponding SRS resource.
  • each SRS resource in the set of SRS resources is indicated with a corresponding delta value from the set of delta values.
  • each SRS resource in the set of SRS resources is indicated with a same delta value from the set of delta values and a corresponding delta value for the corresponding SRS resource is identified in accordance with an order or index of the corresponding SRS resource in the set of SRS resources.
  • the update manager 1370 is capable of, configured to, or operable to support a means for outputting a MAC-CE that indicates an update to the downlink reference signal, to the angular offset, or both.
  • the update to the downlink reference signal, to the angular offset, or both is associated with one or more joint or uplink TCI states.
  • the update to the downlink reference signal, to the angular offset, or both is associated with one or more SRS resources.
  • the update to the downlink reference signal, to the angular offset, or both is associated with one or more SRS resource sets.
  • FIG. 14 shows a diagram of a system 1400 including a device 1405 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the device 1405 may be an example of or include components of a device 1105, a device 1205, or a network entity 105 as described herein.
  • the device 1405 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof.
  • the communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof.
  • the device 1405 may include components that support outputting and obtaining communications, such as a communications manager 1420, a transceiver 1410, one or more antennas 1415, at least one memory 1425, code 1430, and at least one processor 1435. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1440) .
  • a communications manager 1420 e.g., operatively, communicatively, functionally, electronically, electrically
  • buses e.g., a bus 1440
  • the transceiver 1410 may support bi-directional communications via wired links, wireless links, or both as described herein.
  • the transceiver 1410 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the device 1405 may include one or more antennas 1415, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) .
  • the transceiver 1410 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1415, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1415, from a wired receiver) , and to demodulate signals.
  • the transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1415 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1415 that are configured to support various transmitting or outputting operations, or a combination thereof.
  • the transceiver 1410 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof.
  • the transceiver 1410, or the transceiver 1410 and the one or more antennas 1415, or the transceiver 1410 and the one or more antennas 1415 and one or more processors or one or more memory components may be included in a chip or chip assembly that is installed in the device 1405.
  • the transceiver 1410 may be operable to support communications via one or more communications links (e.g., communication link (s) 125, backhaul communication link (s) 120, a midhaul communication link 162, a fronthaul communication link 168) .
  • communications links e.g., communication link (s) 125, backhaul communication link (s) 120, a midhaul communication link 162, a fronthaul communication link 168) .
  • the at least one memory 1425 may include RAM, ROM, or any combination thereof.
  • the at least one memory 1425 may store computer-readable, computer-executable, or processor-executable code, such as the code 1430.
  • the code 1430 may include instructions that, when executed by one or more of the at least one processor 1435, cause the device 1405 to perform various functions described herein.
  • the code 1430 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1430 may not be directly executable by a processor of the at least one processor 1435 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the at least one memory 1425 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the at least one processor 1435 may include multiple processors and the at least one memory 1425 may include multiple memories.
  • One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system) .
  • the at least one processor 1435 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) .
  • the at least one processor 1435 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into one or more of the at least one processor 1435.
  • the at least one processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1425) to cause the device 1405 to perform various functions (e.g., functions or tasks supporting SRS enhancement for uplink beam management) .
  • the device 1405 or a component of the device 1405 may include at least one processor 1435 and at least one memory 1425 coupled with one or more of the at least one processor 1435, the at least one processor 1435 and the at least one memory 1425 configured to perform various functions described herein.
  • the at least one processor 1435 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1430) to perform the functions of the device 1405.
  • the at least one processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1405 (such as within one or more of the at least one memory 1425) .
  • the at least one processor 1435 may include multiple processors and the at least one memory 1425 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
  • the at least one processor 1435 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1435) and memory circuitry (which may include the at least one memory 1425) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs.
  • the processing system may be configured to perform one or more of the functions described herein.
  • the at least one processor 1435 or a processing system including the at least one processor 1435 may be configured to, configurable to, or operable to cause the device 1405 to perform one or more of the functions described herein.
  • being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1425 or otherwise, to perform one or more of the functions described herein.
  • a bus 1440 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1440 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1405, or between different components of the device 1405 that may be co-located or located in different locations (e.g., where the device 1405 may refer to a system in which one or more of the communications manager 1420, the transceiver 1410, the at least one memory 1425, the code 1430, and the at least one processor 1435 may be located in one of the different components or divided between different components) .
  • a logical channel of a protocol stack e.g., between protocol layers of a protocol stack
  • the device 1405 may refer to a system in which one or more of the communications manager 1420, the transceiver 1410, the at least one memory 1425, the code 1430, and the at least one
  • the communications manager 1420 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) .
  • the communications manager 1420 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the communications manager 1420 may manage communications with one or more other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices) .
  • the communications manager 1420 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
  • the communications manager 1420 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 1420 is capable of, configured to, or operable to support a means for outputting, to a UE, one or more signals including an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status including either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a set of multiple narrow beam widths, where the set of multiple narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the communications manager 1420 is capable of, configured to, or operable to support a means for obtaining the SRS transmissions according to the beam sweeping status.
  • the communications manager 1420 may support wireless communications in accordance with examples as disclosed herein.
  • the communications manager 1420 is capable of, configured to, or operable to support a means for outputting, to a UE and via a downlink transmit point, one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the communications manager 1420 is capable of, configured to, or operable to support a means for obtaining the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the device 1405 may support techniques SRS-based uplink beam management when the usage of the SRS resources are set to beam management. This may include the U1-U3 beam refinement procedure being supported based on beam sweeping status signaling. This may include the SRS beam sweeping being based on a beams sweeping range indicated to the UE.
  • the communications manager 1420 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1410, the one or more antennas 1415 (e.g., where applicable) , or any combination thereof.
  • the communications manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1420 may be supported by or performed by the transceiver 1410, one or more of the at least one processor 1435, one or more of the at least one memory 1425, the code 1430, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1435, the at least one memory 1425, the code 1430, or any combination thereof) .
  • the code 1430 may include instructions executable by one or more of the at least one processor 1435 to cause the device 1405 to perform various aspects of SRS enhancement for uplink beam management as described herein, or the at least one processor 1435 and the at least one memory 1425 may be otherwise configured to, individually or collectively, perform or support such operations.
  • FIG. 15 shows a flowchart illustrating a method 1500 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1500 may be implemented by a UE or its components as described herein.
  • the operations of the method 1500 may be performed by a UE 115 as described with reference to FIGs. 1 through 10.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving one or more signals including an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status including either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a set of multiple narrow beam widths, where the set of multiple narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a beam sweeping manager 925 as described with reference to FIG. 9.
  • the method may include performing the SRS transmissions according to the beam sweeping status.
  • the operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by an SRS manager 930 as described with reference to FIG. 9.
  • FIG. 16 shows a flowchart illustrating a method 1600 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1600 may be implemented by a network entity or its components as described herein.
  • the operations of the method 1600 may be performed by a network entity as described with reference to FIGs. 1 through 6 and 11 through 14.
  • a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.
  • the method may include outputting, to a UE, one or more signals including an indication of a transmit beam and a beam sweeping status to be applied during SRS transmissions, the beam sweeping status including either a first beam sweeping state where the SRS transmissions are performed using a wide beamwidth corresponding to the transmit beam or a second beam sweeping state where the SRS transmissions are performed using a set of multiple narrow beam widths, where the set of multiple narrow beam widths are within a range of the wide beamwidth of the transmit beam.
  • the operations of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a beam sweeping manager 1325 as described with reference to FIG. 13.
  • the method may include obtaining the SRS transmissions according to the beam sweeping status.
  • the operations of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by an SRS manager 1330 as described with reference to FIG. 13.
  • FIG. 17 shows a flowchart illustrating a method 1700 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1700 may be implemented by a UE or its components as described herein.
  • the operations of the method 1700 may be performed by a UE 115 as described with reference to FIGs. 1 through 10.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a beam sweeping range manager 935 as described with reference to FIG. 9.
  • the method may include performing the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by an SRS manager 930 as described with reference to FIG. 9.
  • FIG. 18 shows a flowchart illustrating a method 1800 that supports SRS enhancement for uplink beam management in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1800 may be implemented by a network entity or its components as described herein.
  • the operations of the method 1800 may be performed by a network entity as described with reference to FIGs. 1 through 6 and 11 through 14.
  • a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.
  • the method may include outputting, to a UE and via a downlink transmit point, one or more signals including an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, where the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam.
  • the operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a beam sweeping range manager 1335 as described with reference to FIG. 13.
  • the method may include obtaining the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • the operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by an SRS manager 1330 as described with reference to FIG. 13.
  • a method for wireless communications at a UE comprising: receiving one or more signals comprising an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, wherein the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam; and performing the SRS transmissions to the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • Aspect 2 The method of aspect 1, wherein the angular offset comprises a horizontal angular offset, a vertical angular offset, or both.
  • Aspect 3 The method of any of aspects 1 through 2, wherein receiving the one or more signals comprises: receiving a configuration for a set of SRS resources for performing the SRS transmissions, wherein each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state that identifies a source reference signal and the downlink receive beam is identified in accordance with the source reference signal.
  • Aspect 4 The method of any of aspects 1 through 3, wherein receiving the one or more signals comprises: receiving a configuration for a set of SRS resources for performing the SRS transmissions, wherein each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state that identifies a pathloss reference signal and the downlink receive beam is identified in accordance with the pathloss reference signal.
  • Aspect 5 The method of any of aspects 1 through 4, wherein receiving the one or more signals comprises: receiving a configuration for a set of SRS resources for performing the SRS transmissions, wherein each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state where a specific joint or uplink TCI state is used to identify the downlink reference signal for SRS resources in the set of SRS resources and the downlink receive beam is identified in accordance with the downlink reference signal.
  • Aspect 6 The method of aspect 5, wherein the downlink reference signal comprises either a source reference signal or a pathloss reference signal in the specific joint or uplink TCI state that is associated with a lowest resource identifier.
  • Aspect 7 The method of any of aspects 1 through 6, wherein the downlink receive beam corresponding to the downlink reference signal is configured or indicated on a per-SRS resource basis or on a per-SRS resource set basis.
  • Aspect 8 The method of any of aspects 1 through 7, wherein the downlink receive beam corresponding to the downlink reference signal is identified as a source reference signal in a current indicated joint or downlink TCI state associated with the downlink transmit point.
  • receiving the one or more signals comprises: receiving a configuration for a set of SRS resources for performing the SRS transmissions, wherein each SRS resources in the set of SRS resources are associated with a joint or uplink TCI state that identifies the angular offset.
  • Aspect 10 The method of any of aspects 1 through 9, wherein receiving the one or more signals comprises: receiving a configuration for a set of SRS resources for performing the SRS transmissions, wherein each SRS resource in the set of SRS resources is associated with the angular offset.
  • Aspect 11 The method of any of aspects 1 through 10, wherein receiving the one or more signals comprises: receiving a configuration for a set of SRS resources for performing the SRS transmissions, wherein the set of SRS resources is associated with a common angular offset and a set of delta values that, for each corresponding SRS resource in the set of SRS resources, identify the angular offset for the corresponding SRS resource.
  • Aspect 12 The method of claim 11, wherein each SRS resource in the set of SRS resources is indicated with a corresponding delta value from the set of delta values.
  • Aspect 13 The method of claim 11, wherein each SRS resource in the set of SRS resources is indicated with a same delta value from the set of delta values and a corresponding delta value for the corresponding SRS resource is identified in accordance with an order or index of the corresponding SRS resource in the set of SRS resources.
  • Aspect 14 The method of any of aspects 1 through 13, further comprising: receiving a MAC-CE that indicates an update to the downlink reference signal, to the angular offset, or both.
  • Aspect 15 The method of aspect 14, wherein the update to the downlink reference signal, to the angular offset, or both, is associated with one or more joint or uplink TCI states.
  • Aspect 16 The method of any of aspects 14 through 15, wherein the update to the downlink reference signal, to the angular offset, or both, is associated with one or more SRS resources.
  • Aspect 17 The method of any of aspects 14 through 16, wherein the update to the downlink reference signal, to the angular offset, or both, is associated with one or more SRS resource sets.
  • a method for wireless communications at a network entity comprising: outputting, to a UE and via a downlink transmit point, one or more signals comprising an indication of a beam sweeping range to be applied during SRS transmissions to an uplink receive point, wherein the beam sweeping range is defined in accordance with a downlink receive beam corresponding to a downlink reference signal of a downlink transmit point and an angular offset relative to the downlink receive beam; and obtaining the SRS transmissions at the uplink receive point in beam sweeping transmissions according to the beam sweeping range.
  • Aspect 19 The method of aspect 18, wherein the angular offset comprises a horizontal angular offset, a vertical angular offset, or both.
  • Aspect 20 The method of any of aspects 18 through 19, wherein outputting the one or more signals comprises: outputting a configuration for a set of SRS resources for performing the SRS transmissions, wherein each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state that identifies a source reference signal and the downlink receive beam is identified in accordance with the source reference signal.
  • Aspect 21 The method of any of aspects 18 through 20, wherein outputting the one or more signals comprises: outputting a configuration for a set of SRS resources for performing the SRS transmissions, wherein each SRS resource in the set of SRS resources is associated with a joint or uplink TCI state that identifies a pathloss reference signal and the downlink receive beam is identified in accordance with the pathloss reference signal.
  • Aspect 22 The method of any of aspects 18 through 21, wherein outputting the one or more signals comprises: outputting a configuration for a set of SRS resources for performing the SRS transmissions, wherein each SRS resource in the set of is associated with a joint or uplink TCI state where a specific joint or uplink TCI state is used to identify the downlink reference signal for SRS resources in the set of SRS resources and the downlink receive beam is identified in accordance with the downlink reference signal.
  • Aspect 23 The method of aspect 22, wherein the downlink reference signal comprises either a source reference signal or a pathloss reference signal in the specific joint or uplink TCI state that is associated with a lowest resource identifier.
  • Aspect 24 The method of any of aspects 18 through 23, wherein the downlink receive beam corresponding to the downlink reference signal is configured or indicated on a per-SRS resource basis or on a per-SRS resource set basis.
  • Aspect 25 The method of any of aspects 18 through 24, wherein the downlink receive beam corresponding to the downlink reference signal is identified as a source reference signal in a current indicated joint or downlink TCI state associated with the downlink transmit point.
  • Aspect 26 The method of any of aspects 18 through 25, wherein outputting the one or more signals comprises: outputting a configuration for a set of SRS resources for performing the SRS transmissions, wherein each SRS resources in the set of SRS resources are associated with a joint or uplink TCI state that identifies the angular offset.
  • Aspect 27 The method of any of aspects 18 through 26, wherein outputting the one or more signals comprises: outputting a configuration for a set of SRS resources for performing the SRS transmissions, wherein each SRS resource in the set of SRS resources is associated with the angular offset.
  • Aspect 28 The method of any of aspects 18 through 27, wherein outputting the one or more signals comprises: outputting a configuration for a set of SRS resources for performing the SRS transmissions, wherein the set of SRS resources is associated with a common angular offset and a set of delta values that, for each corresponding SRS resource in the set of SRS resources, identify the angular offset for the corresponding SRS resource.
  • Aspect 29 The method of claim 28, wherein each SRS resource in the set of SRS resources is indicated with a corresponding delta value from the set of delta values.
  • Aspect 30 The method of claim 28, wherein each SRS resource in the set of SRS resources is indicated with a same delta value from the set of delta values and a corresponding delta value for the corresponding SRS resource is identified in accordance with an order or index of the corresponding SRS resource in the set of SRS resources.
  • Aspect 31 The method of any of aspects 18 through 30, further comprising: outputting a MAC-CE that indicates an update to the downlink reference signal, to the angular offset, or both.
  • Aspect 32 The method of aspect 31, wherein the update to the downlink reference signal, to the angular offset, or both, is associated with one or more joint or uplink TCI states.
  • Aspect 33 The method of any of aspects 31 through 32, wherein the update to the downlink reference signal, to the angular offset, or both, is associated with one or more SRS resources.
  • Aspect 34 The method of any of aspects 31 through 33, wherein the update to the downlink reference signal, to the angular offset, or both, is associated with one or more SRS resource sets.
  • a UE for wireless communications comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 17.
  • a UE for wireless communications comprising at least one means for performing a method of any of aspects 1 through 17.
  • Aspect 37 A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 17.
  • a network entity for wireless communications comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 18 through 34.
  • a network entity for wireless communications comprising at least one means for performing a method of any of aspects 18 through 34.
  • Aspect 40 A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 18 through 34.
  • 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 Institute of Electrical and Electronics Engineers
  • 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) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.
  • the functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of 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 location 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.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.
  • the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components.
  • the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function.
  • a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components.
  • a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.
  • subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components.
  • referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”
  • determining encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

Landscapes

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

Abstract

L'invention concerne des procédés, des systèmes, et des dispositifs destinés aux communications sans fil. Un équipement utilisateur (UE) peut recevoir un ou plusieurs signaux comprenant une indication d'une plage de balayage de faisceau à appliquer pendant des transmissions de signal de référence de sondage (SRS) à un point de réception de liaison montante, la plage de balayage de faisceau étant définie conformément à un faisceau de réception de liaison descendante correspondant à un signal de référence de liaison descendante d'un point de transmission de liaison descendante et à un décalage angulaire par rapport au faisceau de réception de liaison descendante. L'UE peut réaliser les transmissions de SRS vers le point de réception de liaison montante dans des transmissions de balayage de faisceau selon la plage de balayage de faisceau.
PCT/CN2024/106899 2024-07-23 2024-07-23 Amélioration de signal de référence de sondage pour la gestion de faisceau de liaison montante Pending WO2026020301A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/106899 WO2026020301A1 (fr) 2024-07-23 2024-07-23 Amélioration de signal de référence de sondage pour la gestion de faisceau de liaison montante

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/106899 WO2026020301A1 (fr) 2024-07-23 2024-07-23 Amélioration de signal de référence de sondage pour la gestion de faisceau de liaison montante

Publications (1)

Publication Number Publication Date
WO2026020301A1 true WO2026020301A1 (fr) 2026-01-29

Family

ID=98564786

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/106899 Pending WO2026020301A1 (fr) 2024-07-23 2024-07-23 Amélioration de signal de référence de sondage pour la gestion de faisceau de liaison montante

Country Status (1)

Country Link
WO (1) WO2026020301A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109964436A (zh) * 2016-04-20 2019-07-02 康维达无线有限责任公司 可配置的参考信号
CN115104356A (zh) * 2020-02-13 2022-09-23 上海诺基亚贝尔股份有限公司 用于ul定位的参考信号传输上的波束扫描
US20230033910A1 (en) * 2020-02-25 2023-02-02 Qualcomm Incorporated Beam switching techniques for uplink transmission
WO2024033829A1 (fr) * 2022-08-10 2024-02-15 Lenovo (Singapore) Pte. Ltd. Gestion des interférences de liaison croisée entre stations de base à l'aide d'indications transmises par voie hertzienne

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109964436A (zh) * 2016-04-20 2019-07-02 康维达无线有限责任公司 可配置的参考信号
CN115104356A (zh) * 2020-02-13 2022-09-23 上海诺基亚贝尔股份有限公司 用于ul定位的参考信号传输上的波束扫描
US20230033910A1 (en) * 2020-02-25 2023-02-02 Qualcomm Incorporated Beam switching techniques for uplink transmission
WO2024033829A1 (fr) * 2022-08-10 2024-02-15 Lenovo (Singapore) Pte. Ltd. Gestion des interférences de liaison croisée entre stations de base à l'aide d'indications transmises par voie hertzienne

Similar Documents

Publication Publication Date Title
US20250088887A1 (en) Channel state information resource configurations for beam prediction
US12363568B2 (en) Beam measurement reporting for spatially offset beams
US12356393B2 (en) Sounding reference signal resource configuration for transmission antenna ports
US12191964B2 (en) User receive beam measurement prioritization
WO2025118233A1 (fr) Valeurs multiples d'avance temporelle pour déploiements denses de liaison montante
WO2024197782A1 (fr) États d'indicateur de configuration de transmission pour prédiction de faisceau spatial
US12532324B2 (en) Techniques for dynamic transmission parameter adaptation
US12500655B2 (en) Techniques for beam refinement and beam selection enhancement
US12156066B2 (en) Transmission and reception beam management for cross link interference measurement
WO2026020301A1 (fr) Amélioration de signal de référence de sondage pour la gestion de faisceau de liaison montante
WO2026020300A1 (fr) Amélioration de signal de référence de sondage pour la gestion de faisceau de liaison montante
WO2025199854A1 (fr) Améliorations de signal de référence de sondage pour découverte de liaison montante ou gestion de faisceau
US20250233627A1 (en) Enhancement of user equipment (ue) selection for uplink aggregation
WO2025208403A1 (fr) Mappage de signaux de référence à des indicateurs de configuration de transmission pour une gestion et un rapport de faisceau
US20260095794A1 (en) User equipment capabilities for layer 1 cross link interference measurement and reporting
WO2025179416A1 (fr) Configurations d'états de réglage de commande de puissance distincts pour signaux de référence de sondage
US20260059457A1 (en) Synchronization signal block (ssb) pattern switching
US20250240141A1 (en) Reference signal configurations for sidelink beam maintenance
US20250317258A1 (en) User equipment behavior for sub-band full duplex operations
WO2025145314A1 (fr) Rapport d'informations d'état de canal (csi) pour des cellules candidates à mobilité déclenchée par une couche inférieure
US20240097758A1 (en) Techniques for switching between adaptive beam weights-based analog beamforming and hybrid beamforming
US20240098759A1 (en) Common time resources for multicasting
WO2025152102A1 (fr) Signalisation de capacité agrégée pour une agrégation de porteuses et des modes de connectivité double
US20250261109A1 (en) On-demand synchronization signaling for network energy savings systems
US20250260531A1 (en) Sounding reference signal antenna switch with three transmit chains

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

Country of ref document: EP

Kind code of ref document: A1