User Equipment Beam Management Capability Reporting

Abstract

Certain aspects of the present disclosure provide techniques for a method of wireless communication in a wireless device. The method generally includes obtaining a configuration for reporting beam management (BM)-related information and outputting a BM report for transmission in accordance with the configuration, the BM report including an indication of BM-related capabilities.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 334,618, filed on April 25, 2022, both of which are assigned to the assignee of the present application and are expressly incorporated by reference in their entireties as if fully set forth below and for all applicable purposes. [Background technology]

[0002] Field of Disclosure Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for reporting beam management (BM) related capabilities of user equipment (UE).

[0003] 2. Description of Related Art Wireless communication systems have been widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, or other similar types of services. These wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing the available wireless communication system resources with those users.

[0004] Although wireless communication systems have made great technological advances over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Thus, there is a continuing desire to improve the technical performance of wireless communication systems, including, for example, improving the speed and data carrying capacity of communication, improving the efficiency of use of the shared communication medium, reducing the power used by the transmitter and receiver while performing communication, improving the reliability of wireless communication, avoiding redundant transmissions and / or receptions and associated processing, improving the coverage area of ​​wireless communication, increasing the number and types of devices that can access the wireless communication system, improving the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, and the like. Thus, further improvements in wireless communication systems are needed to overcome the aforementioned technical challenges and others. Summary of the Invention

[0005] One aspect provides a method of wireless communication in a wireless device, the method including obtaining a configuration for reporting beam management (BM) related information, and outputting a BM report for transmission in accordance with the configuration, the BM report including an indication of BM-related capabilities of the wireless device.

[0006] Another aspect provides a method of wireless communication in a wireless device, the method including: outputting a configuration for reporting BM-related information for transmission; and obtaining a BM report according to the configuration, the BM report including an indication of BM-related capabilities.

[0007] Other aspects provide an apparatus operable, configured, or otherwise adapted to perform any one or more of the methods described above and / or elsewhere herein, a non-transitory computer readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the methods described above and elsewhere herein, a computer program product embodied on a computer readable storage medium comprising code for performing the methods described above and elsewhere herein, and / or an apparatus comprising means for performing the methods described above and elsewhere herein. By way of example, the apparatus may comprise a processing system, a device having a processing system, or processing systems cooperating over one or more networks.

[0008] The following description and the annexed drawings set forth certain features by way of example only.

[0009] The accompanying drawings illustrate certain features of the various aspects described herein and are not to be construed as limiting the scope of the disclosure. [Brief description of the drawings]

[0010] [Figure 1] 1 illustrates an exemplary wireless communication network. [Diagram 2] 1 illustrates an exemplary split base station architecture. [Diagram 3] 1 illustrates aspects of an exemplary base station and exemplary user equipment. [Figure 4A] 1 illustrates various example aspects of a data structure for a wireless communication network. [Figure 4B] 1 illustrates various example aspects of a data structure for a wireless communication network. [Figure 4C] 1 illustrates various example aspects of a data structure for a wireless communication network. [Figure 4D] 1 illustrates various example aspects of a data structure for a wireless communication network. [Diagram 5]FIG. 1 is a call flow diagram illustrating an example of a codebook-based UL transmission in accordance with certain aspects of the present disclosure. [Figure 6] FIG. 1 is a call flow diagram illustrating an example of a non-codebook based UL transmission in accordance with certain aspects of the present disclosure. [Figure 7] 1 illustrates a call flow diagram for reporting beam management (BM) related capabilities of a UE in accordance with certain aspects of the present disclosure. [Figure 8] A method of wireless communication is shown. [Figure 9] A method of wireless communication is shown. [Figure 10] 1 illustrates aspects of an exemplary communications device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Aspects of the present disclosure provide an apparatus, method, processing system, and computer-readable medium for reporting beam management (BM)-related capabilities of a wireless device. As used herein, the term wireless device (or wireless node) generally refers to any type of device capable of wireless communication, such as a UE or a network entity such as a base station (e.g., gNB).

[0012] Various extensions to beam management (e.g., for communications between UEs and network entities) have been proposed and possibly implemented. Such extensions can be supported, for example, by reporting various BM measurements to support multiple transmitter and receiver point (mTRP) scenarios using UE panel information reporting.

[0013] One potential challenge is how the UE can indicate its ability to support such extensions. Aspects of the present disclosure provide various mechanisms that can enable the UE to indicate BM-related capabilities. For example, the techniques presented herein can enable the UE to send panel-related capability updates in physical layer (PHY or L1) beam reporting opportunities.

[0014] One potential benefit to such an approach is that it can use existing BM reporting mechanisms to provide capability information efficiently (e.g., rather than relying on potentially time-consuming RRC signaling). This approach also allows for flexible provision of updates, for example, to adapt to changing conditions (e.g., to improve throughput and / or save power).

[0015] Introduction to Wireless Communication Networks The techniques and methods described herein can be used for a variety of wireless communication networks. Although aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, aspects of the present disclosure may be equally applicable to other communication systems and standards not explicitly mentioned herein.

[0016] FIG. 1 illustrates an example of a wireless communication network 100 in which aspects described herein can be implemented.

[0017] Generally, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communication device and / or a communication function performed by a communication device (e.g., a user equipment (UE), a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network and various devices associated with and interacting with the network can be considered network entities. Furthermore, the wireless communication network 100 includes terrestrial aspects, such as a ground-based network entity (e.g., BS 102), and non-terrestrial aspects, such as a satellite 140 and an aircraft 145, which can include on-board network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and user equipment.

[0018] In the illustrated example, the wireless communication network 100 includes a BS 102, a UE 104, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and a 5G Core (5GC) 190 network, which interoperate to provide communication services over various communication links, including wired and wireless links.

[0019] 1 illustrates various exemplary UEs 104, which may more generally include a mobile phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an internet of things (IoT) device, an always on (AON) device, an edge processing device, or other similar devices. The UEs 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, or the like.

[0020] The BS 102 wirelessly communicates with the UE 104 (e.g., transmits signals to the UE 104, or receives signals from the UE 104) over a communication link 120. The communication link 120 between the BS 102 and the UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the BS 102, and / or downlink (DL) (also referred to as forward link) transmissions from the BS 102 to the UE 104. The communication link 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.

[0021] The BSs 102 may generally include a NodeB, an enhanced NodeB (eNB), a next generation enhanced NodeB (ng-eNB), a next generation NodeB (gNB or gNodeB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a transmit / receive point, and / or others. Each of the BSs 102 may provide communication coverage for a respective geographic coverage area 110, which may be referred to as a cell and may overlap in some cases (e.g., a small cell 102′ may have a coverage area 110′ that overlaps with a coverage area 110 of a macro cell). The BSs may provide communication coverage for, for example, a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively smaller geographic area, such as a sports stadium), a femto cell (covering a relatively smaller geographic area (e.g., a home)), and / or other types of cells.

[0022] Although the BS 102 is shown in various aspects as a single communications device, the BS 102 may be implemented in various configurations. For example, one or more components of a base station may be separated and include a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC, to name a few. In another example, various aspects of a base station may be virtualized. More generally, a base station (e.g., the BS 102) may include components located in a single physical location, or components located in various physical locations. In examples where a base station includes components located in various physical locations, the various components may each perform functions such that the various components collectively achieve similar functionality as a base station located in a single physical location. In some aspects, a base station that includes components located at different physical locations may be referred to as a split radio access network architecture, such as an Open RAN (O-RAN) or Virtualized RAN (VRAN) architecture. Figure 2 illustrates and describes an example split base station architecture.

[0023] Different BSs 102 in the wireless communication network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) via a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0024] The wireless communication network 100 may subdivide the electromagnetic spectrum into various classes, bands, channels, or other characteristics. In some aspects, the subdivision is effected based on wavelength and frequency, where the frequencies may also be referred to as carriers, subcarriers, frequency channels, tones, or subbands. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 410 MHz to 7125 MHz, which is often referred to (interchangeably) as "sub-6 GHz." Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 24,250 MHz to 52,600 MHz, which is sometimes referred to (interchangeably) as "millimeter wave" ("mmW" or "mm-wave"). A base station (e.g., an mm-wave base station such as BS180) configured to communicate using mm-wave / near-mm-wave radio frequency bands can utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0025] The communication link 120 between the BS 102 and, for example, the UE 104, may be via one or more carriers that may have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. The allocation of carriers may also be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than UL).

[0026] Communications using higher frequency bands may have higher path loss and shorter range compared to lower frequency communications. Thus, some base stations (e.g., 180 in FIG. 1) may utilize beamforming 182 with the UE 104 to improve path loss and range. For example, the BS 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182′. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182″. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182″. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182′. The BS 180 and the UE 104 may then perform beam training to determine the best receive and transmit directions for each of the BS 180 and the UE 104. In particular, the transmit and receive directions for the BS 180 may or may not be the same. Similarly, the transmit and receive directions for the UE 104 may or may not be the same.

[0027] The wireless communication network 100 further includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, for example, in the 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.

[0028] Several UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0029] The EPC 160 may include various functional components including, for example, in the illustrated example, a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and / or a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management.

[0030] Generally, user Internet Protocol (IP) packets are forwarded through a Serving Gateway 166, which itself is connected to a PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to IP Services 176, which may include, for example, the Internet, an Intranet, an IP Multimedia Subsystem (IMS), Packet Switched (PS) streaming services, and / or other IP services.

[0031] The BM-SC 170 may provide the functionality of MBMS user service provisioning and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions and may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN) and / or may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to deliver MBMS traffic to BSs 102 that belong to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and / or may be responsible for session management (start / stop) and collecting eMBMS related charging information.

[0032] The 5GC 190 may include various functional components, including an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196.

[0033] The AMF 192 is a control node that handles signaling between the UE 104 and the 5GC 190. The AMF 192 provides, for example, quality of service (QoS), flow and session management.

[0034] Internet Protocol (IP) packets are forwarded through UPF 195, which connects to IP services 197 and provides UE IP address allocation and other functions for 5GC 190. IP services 197 may include, for example, Internet, Intranet, IMS, PS streaming services, and / or other IP services.

[0035] In various aspects, the network entity or network node may be implemented as an aggregated base station, as a separate base station, as a component of a base station, as an integrated access and backhaul (IAB) node, as a relay node, as a sidelink node, to name a few.

[0036] 2 illustrates an exemplary split base station 200 architecture. The split base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with the core network 220 via a backhaul link or indirectly with the core network 220 via one or more split base station units (such as a near real-time (near RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both). The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served by multiple RUs 240 simultaneously.

[0037] Each of the units, e.g., CU 210, DU 230, RU 240, and quasi-RT RIC 225, non-RT RIC 215, and SMO framework 205, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more of the other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally or alternatively, a unit may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., a radio frequency (RF) transceiver) configured to receive or transmit or transmit signals over a wireless transmission medium to one or more of the other units.

[0038] In some aspects, the CU 210 can host one or more upper layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can implement an interface configured to communicate signals with other control functions hosted by the CU 210. The CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 210 can be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit over an interface such as an E1 interface when implemented in an O-RAN configuration. The CU 210 may be implemented to communicate with the DU 230, as necessary, for network control and signaling.

[0039] The DU 230 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 may correspond to a 3G Partnership Project (3GPP)-compliant 3GPP ... rdDepending at least in part on a functional division such as that defined by the Third Generation Partnership Project (3GPP), the DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, the DU 230 may further host one or more lower PHY layers. Each layer (or module) may implement an interface configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0040] The lower layer functions may be implemented by one or more RUs 240. In some deployments, the RUs 240 controlled by the DU 230 may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional division such as a lower layer functional division. In such an architecture, the RU(s) 240 may be implemented to handle over the air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communications with the RU(s) 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the DU(s) 230 and the CU 210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0041] The SMO framework 205 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support deployment of dedicated physical resources for RAN coverage requirements that can be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 290) to perform network element life cycle management (e.g., instantiate virtualized network elements) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network elements may include, but are not limited to, the CU 210, the DU 230, the RU 240, and the quasi-RT RIC 225. In some implementations, the SMO framework 205 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 211, via an O1 interface. Additionally, in some implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via an O1 interface. The SMO framework 205 can also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0042] The non-RT RIC 215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the quasi-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the quasi-RT RIC 225 (e.g., via an A1 interface). The quasi-RT RIC 225 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources via data collection and action via one or more CUs 210, one or more DUs 230, or both, and interfaces connecting the O-eNB to the quasi-RT RIC 225 (e.g., via an E2 interface).

[0043] In some implementations, the non-RT RIC 215 may receive parameters or external enrichment information from an external server to generate the AI / ML models deployed to the quasi-RT RIC 225. Such information may be utilized by the quasi-RT RIC 225 or may be received at the SMO framework 205 or the non-RT RIC 215 from non-network data sources or from network functions. In some examples, the non-RT RIC 215 or the quasi-RT RIC 225 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 215 may employ the AI / ML models to monitor long-term trends and patterns regarding performance and take corrective action via the SMO framework 205 (e.g., reconfiguration via O1) or via creation of RAN management policies (e.g., A1 policies).

[0044] FIG. 3 illustrates an example aspect of the BS 102 and UE 104.

[0045] Generally, the BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-t (collectively 334), transceivers 332a-t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, the BS 102 may transmit and receive data between the BS 102 and the UE 104. The BS 102 includes a controller / processor 340 that may be configured to implement various functions described herein related to wireless communication.

[0046] Generally, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-r (collectively 352), transceivers 354a-r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., received from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communication.

[0047] For an example downlink transmission, the BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data may be for a physical downlink shared channel (PDSCH).

[0048] The transmit processor 320 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS).

[0049] A transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) in transceivers 332a-t. Each modulator in transceivers 332a-t may process a respective output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in transceivers 332a-t may be transmitted via antennas 334a-t, respectively.

[0050] To receive downlink transmissions, the UE 104 includes antennas 352a-352r, which can receive downlink signals from the BS 102 and provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in the transceivers 354a-354r may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.

[0051] A MIMO detector 356 may obtain received symbols from all demodulators in the transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols and provide decoded data for the UE 104 to a data sink 360 and provide decoded control information to the controller / processor 380.

[0052] For an example uplink transmission, the UE 104 further includes a transmit processor 364 that can receive and process data (e.g., for a PUSCH) from a data source 362 and control information (e.g., for a physical uplink control channel (PUCCH)) from a controller / processor 380. The transmit processor 364 can also generate reference symbols for a reference signal (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be precoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM, etc.), and transmitted to the BS 102.

[0053] At the BS 102, the uplink signals from the UE 104 may be received by antennas 334a-t, processed by demodulators in transceivers 332a-t, detected by a MIMO detector 336 if applicable, and further processed by a receive processor 338 to obtain decoded data and control information transmitted by the UE 104. The receive processor 338 may provide the decoded data to a data sink 339 and the decoded control information to a controller / processor 340.

[0054] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0055] A scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0056] In various aspects, the BS 102 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as outputting data from the data source 312, the scheduler 344, the memory 342, the transmit processor 320, the controller / processor 340, the TX MIMO processor 330, the transceivers 332a-t, the antennas 334a-t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from the antennas 334a-t, the transceivers 332a-t, the RX MIMO detector 336, the controller / processor 340, the receive processor 338, the scheduler 344, the memory 342, and / or other aspects described herein.

[0057] In various aspects, the UE 104 may similarly be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as outputting data from the data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a-t, antennas 352a-t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from the antennas 352a-t, transceivers 354a-t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0058] In some aspects, the processor may be configured to perform various operations, such as those associated with the methods described herein, to transmit (output) data to or receive (obtain) data from another interface configured to transmit or receive data, respectively.

[0059] 4A, 4B, 4C, and 4D illustrate aspects of data structures for a wireless communication network, such as wireless communication network 100 of FIG.

[0060] In particular, FIG. 4A is a diagram 400 illustrating an example of a first subframe in a 5G (e.g., 5G NR) frame structure, FIG. 4B is a diagram 430 illustrating an example of a DL channel in a 5G subframe, FIG. 4C is a diagram 450 illustrating an example of a second subframe in a 5G frame structure, and FIG. 4D is a diagram 480 illustrating an example of a UL channel in a 5G subframe.

[0061] Wireless communication systems may utilize orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) on the uplink and downlink. Such systems may also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the system bandwidth into multiple orthogonal subcarriers (e.g., as shown in FIGS. 4B and 4D). Each subcarrier may be modulated with data. Modulation symbols may be transmitted in the frequency domain with OFDM and / or in the time domain with SC-FDM.

[0062] The wireless communication frame structure may be frequency division duplex (FDD) where, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD) where, for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0063] In Figures 4A and 4C, the wireless communication frame structure is TDD, D is DL, U is UL, and X is flexible for use between DL / UL. The UE can be configured with the slot format via a received slot format indicator (SFI) (dynamically via DL control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling). In the illustrated example, a 10 ms frame is divided into ten equally sized 1 ms subframes. Each subframe may include one or more time slots. In some examples, each slot may include 7 or 14 symbols depending on the slot format. A subframe may also include a minislot, which generally has fewer symbols than an entire slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0064] In some aspects, the number of slots in a subframe is based on the slot configuration and numerology. For example, for slot configuration 0, different numerologies (μ) 0-5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different numerologies 0-2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and numerology μ, 14 symbols / slot and 2 μ There are slots / subframes. Subcarrier spacing and symbol length / duration are functions of numerology. Subcarrier spacing is 2 μ×15 kHz, where μ is a numerology from 0 to 5. Thus, numerology μ=0 has a subcarrier spacing of 15 kHz and numerology μ=5 has a subcarrier spacing of 480 kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 4A, 4B, 4C, and 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0065] A resource grid can be used to represent the frame structure, as shown in Figures 4A, 4B, 4C, and 4D. Each time slot includes resource blocks (RBs) (also called physical RBs (PRBs)), e.g., spanning 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0066] As shown in Figure 4A, some of the REs carry reference (pilot) signals (RS) for the UE (e.g., UE 104 in Figures 1 and 3). The RS may include demodulation RS (DMRS) and / or channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS).

[0067] 4B shows an example of various DL channels within a subframe of a frame. A physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs), each CCE including, for example, 9 RE groups (REGs), each REG including, for example, 4 consecutive REs within an OFDM symbol.

[0068] A primary synchronization signal (PSS) may be present in symbol 2 of a particular subframe of a frame. The PSS is used by the UE (e.g., 104 in Figures 1 and 3) to determine subframe / symbol timing and physical layer identification information.

[0069] A secondary synchronization signal (SSS) may be present in symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the group number of the physical layer cell identity and the timing of the radio frame.

[0070] Based on the physical layer identity and the group number of the physical layer cell identity, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the above-mentioned DMRS. A physical broadcast channel (PBCH) carrying a master information block (MIB) may be logically grouped with a PSS and an SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and a system frame number (SFN). A physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted over the PBCH, such as system information blocks (SIBs), and / or paging messages.

[0071] As shown in FIG. 4C, some of the REs carry DMRS (denoted as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE can transmit DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS can be transmitted, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used. The UE 104 can transmit a sounding reference signal (SRS). The SRS can be transmitted, for example, in the last symbol of a subframe. The SRS can have comb configurations, and the UE can transmit the SRS in one of those combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0072] 4D shows an example of various UL channels within a subframe of a frame. The PUCCH, in one configuration, may be arranged as shown. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0073] QCL port and TCI status In many cases, it is important for a UE to know which assumptions it can make on the channel corresponding to different transmissions. For example, the UE may need to know which reference signals it can use to estimate the channel in order to decode the transmitted signal (e.g., PDCCH or PDSCH). It may also be important for the UE to be able to report relevant channel state information (CSI) to the BS (gNB) for scheduling, link adaptation, and / or beam management purposes. In NR, the concepts of quasi-co-location (QCL) and transmission configuration indicator (TCI) states are used to convey information about these assumptions.

[0074] QCL assumptions are generally defined with respect to channel characteristics. According to 3GPP TS 38.214, "two antenna ports are said to be quasi co-located if the characteristics of the channel through which symbols on one antenna port are conveyed can be inferred from the channel through which symbols on the other antenna port are conveyed." Different reference signals may be considered to be quasi co-located ("QCL") if a receiver (e.g., a UE) can apply channel characteristics determined by detecting a first reference signal to help detect a second reference signal. TCI conditions generally include configurations such as, for example, QCL relationships between DL RSs and PDSCH DMRS ports in one CSI-RS set.

[0075] In some cases, a UE may be configured with up to M TCI states. The configuration of the M TCI states may be done via higher layer signaling, and the UE may be signaled to decode the PDSCH according to a detected PDCCH having a DCI indicating one of the TCI states. Each configured TCI state may include one RS set TCI-RS-SetConfig, indicating a different QCL assumption between a source signal and a target signal.

[0076] For example, TCI-RS-SetConfig may indicate that a source reference signal (RS) is shown in the top block and is associated with a target signal shown in the bottom block. In this context, a target signal generally refers to a signal whose channel characteristics can be inferred by measuring the channel characteristics of the associated source signal. As mentioned above, the UE may use the source RS to determine various channel parameters depending on the associated QCL type, and use those various channel characteristics (determined based on the source RS) to process the target signal. The target RS does not necessarily have to be the DMRS of the PDSCH, but rather can be any other RS, PUSCH DMRS, CSIRS, TRS, and SRS.

[0077] Each TCI-RS-SetConfig may contain various parameters that may, for example, configure the quasi-co-location relationship(s) between reference signals in the RS Set and the DM-RS port group of the PDSCH. An RS Set contains a reference to one or two DL RSs and the associated quasi-co-location type (QCL-Type) of each DL RS configured by the higher layer parameter QCL-Type.

[0078] For two DL RSs, the QCL types can take various configurations. For example, the QCL types may not be the same whether the reference is to the same DL RS or to different DL RSs. In the illustrated example, the SSB is associated with a Type C QCL in the P-TRS, and the CSI-RS for beam management (CSIRS BM) is associated with a Type D QCL.

[0079] The QCL information and / or type may in some scenarios depend on or be a function of other information. For example, the quasi-co-location (QCL) type indicated to the UE may be based on the higher layer parameter QCL-Type and may take one or a combination of the following types: QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread} QCL-TypeB: {Doppler shift, Doppler spread} QCL-TypeC: {average delay, Doppler shift}, and QCL-TypeD:{Spatial Rx parameters} The spatial QCL hypotheses (QCL-TypeD) may be used to help the UE select an analog Rx beam (e.g., during a beam management procedure). For example, the SSB resource indicator may indicate that the same beam as the previous reference signal should be used for the subsequent transmission.

[0080] An initial CORESET in NR (e.g., CORESET ID 0 or simply CORESET#0) may be identified (e.g., via a field in a MIB) during initial access by the UE. A Control Resource Set information element (CORESET IE) sent via Radio Resource Control (RRC) signaling may convey information about the CORESET configured for the UE. The CORESET IE typically includes the CORESET ID, an indication of the frequency domain resources allocated to the CORESET (e.g., number of RBs), the continuous duration of the CORESET in a number of symbols, and the Transmission Configuration Indicator (TCI) state.

[0081] As mentioned above, a subset of TCI states provides a quasi-co-location (QCL) relationship between DL RS(s) and PDCCH demodulation RS (DMRS) ports in an RS set (e.g., TCI-Set). A particular TCI state for a given UE (e.g., for a unicast PDCCH) may be signaled to the UE by a Medium Access Control (MAC) Control Element (MAC-CE). A particular TCI state is typically selected from a set of TCI states signaled by a CORESET IE, and an initial CORESET (CORESET#0) is typically configured via a MIB.

[0082] Search space information may also be provided via RRC signaling. For example, SearchSpace IE is another RRC IE that defines how and where to search for PDCCH candidates for a given CORESET. Each search space is associated with one CORESET. SearchSpace IE identifies the search space configured for a CORESET by a search space ID. In one aspect, the search space ID associated with CORESET#0 is SearchSpace ID#0. Search spaces are generally configured via PBCH (MIB).

[0083] Exemplary SRS-Based Transmission Some deployments (e.g., NR Release 15 and 16 systems) support codebook-based and non-codebook-based transmission schemes for uplink transmission with a wideband precoder. Codebook-based UL transmission can be used when reciprocity is not maintained, depending on the BS configuration.

[0084] 5 is a call flow diagram 500 illustrating an example of a conventional codebook-based UL transmission using a wideband precoder. As shown, the UE transmits an SRS (not precoded) using up to two SRS resources (each resource having one, two, or four ports). The gNB measures the SRS and, based on the measurement, selects one SRS resource and a wideband precoder to be applied to the SRS ports in the selected resource.

[0085] As shown, the gNB configures the UE with the selected SRS resource via an SRS resource indicator (SRI) and the wideband precoder via a transmit precoder matrix indicator (TPMI). In the case of a dynamic grant, the SRI and TPMI may be configured via DCI format 0_1. In the case of a configured grant (e.g., for a semi-persistent uplink), the SRI and TPMI may be configured via RRC or DCI.

[0086] The UE determines the selected SRS resource from the SRI and the precoding from the TPMI, and transmits the PUSCH accordingly.

[0087] FIG. 6 is a call flow diagram 600 illustrating an example of a non-codebook-based UL transmission. As shown, the UE transmits a (precoded) SRS. Although the example shows two SRS resources, the UE may transmit with up to four SRS resources (each resource with one port). The gNB measures the SRS and selects one or more SRS resources based on the measurement. In this case, the UE sent a precoded SRS, so by selecting an SRS resource, the gNB is effectively selecting precoding as well. For non-codebook-based UL transmission, each SRS resource corresponds to a layer. The precoder of the layer is actually the precoder of the SRS emulated by the UE. Selecting N SRS resources means the rank is N. The UE will transmit the PUSCH using the same precoder as the SRS.

[0088] As shown, the gNB configures the UE with the selected SRS resources via an SRS resource indicator (SRI). In the case of a dynamic grant, the SRI may be configured via DCI format 0_1. In the case of a configured grant, the SRI may be configured via RRC or DCI.

[0089] Aspects Related to UE Beam Management Capability Reporting Aspects of the present disclosure provide an apparatus, method, processing system, and computer-readable medium for reporting beam management (BM)-related capabilities of a UE.

[0090] As mentioned above, one potential challenge is how a UE can indicate its ability to support such extensions. Aspects of the present disclosure provide various mechanisms that can enable a UE to indicate BM-related capabilities.

[0091] The techniques proposed herein may be understood with reference to the example call flow diagram 700 of FIG.

[0092] As shown, the UE may be configured by a network entity (e.g., a component of a gNB or separate base station) for beam management (BM) reporting 702. As shown, the UE may transmit a BM report 704 that includes an indication of the UE's BM-related capabilities.

[0093] For example, this approach may enable the UE to send panel-related capability updates at Layer 1 (L1) beam reporting occasions. In some cases, the panel-related capabilities may include a metric representing the maximum number of supported SRS ports for each panel (which may be associated with a TCI). In some cases, the UE may report the SSB ID, CSI RS ID, L1 RSRP, and the maximum number of supported SRS ports.

[0094] In some cases, a new reporting quantity may be added (and configured) to support this feature in RRC (e.g., a new quantity for reporting BM-related capabilities in BM reporting). For example, a new reporting quantity such as "cri-RSRP-SetIndex", "ssb-Index-RSRP-SetIndex", "cri-SINR-SetIndex", or "ssb-Index-SINR-SetIndex" may be introduced as a new reporting quantity for CSI reporting settings.

[0095] In this context, the set index (parameter xxx-SetIndex) generally refers to the capability set index. For example, to indicate the number of ports supported, the SetIndex value can be "0" for {1 port} and "1" for {2 ports}.

[0096] In some cases, the UE capability of the maximum number of supported uplink transmission (UL Tx) layers may be determined based on one of various options. According to a first option, the number of supported UL Tx layers may be determined by the following formula:

[0097] min{Maximum number of SRS ports in the reported set, Maximum number of UL Tx layers reported by UE capabilities}.

[0098] According to another option, the maximum value of the SRS port in any reported capability set may be less than or equal to the reported UL Tx layer reported by the UE.

[0099] In some cases, the UE may report panel-related capability metrics and indicate which type of time-domain behavior the metric applies to. For example, the UE may indicate whether the reported capability supports periodic (P), aperiodic (AP), or semi-persistent (SP) reporting.

[0100] This may be beneficial since a UE may not support all types of time domain behavior, for example, in some cases P reporting may be the baseline option, while AP reporting and SP reporting may be optional.

[0101] However, for an extended beam report that includes an index(es) of a UE capability value set, all types of time domain behaviors may be supported. In such a case, which time domain behaviors the UE supports may be based on (indicated by) the UE capability report (e.g., an indication provided in the BM report). As an example, all UEs may be expected to support P reporting (e.g., as defined in the standard), while SP and / or AP reporting may be left to UE capabilities. In some cases, the candidate periodicity of periodic / SP reporting may depend on UE capabilities. For example, a UE may only have limited power available, and the period between reports may be long to reduce power consumption. In some cases, semi-persistent and / or aperiodic reporting may be triggered only when periodic reporting is configured.

[0102] In some cases, the UE may support the ability to update the BFD-RS set per TRP BFR. For example, in some cases (e.g., in NR Rel 17), the TCI of the UE-dedicated PDCCH / CORESET may be dynamically updated by the DCI. For example, the previous TCI of the CORESET may be updated by the MAC-CE. In some cases, the BFD-RS set may be configured to monitor the beam corresponding to the CORESET. In current systems, the BFD-RS set may be configured only by the RRC, and the update time is much longer than the DCI.

[0103] Aspects of the present disclosure may enable faster update signaling, e.g., via MAC-CE or DCI, to update BFD RS. In some cases, BFR may be supported per TRP. For example, in such cases, a BFD RS set may be configured per TRP and / or CORESET pool.

[0104] Aspects of the present disclosure may introduce a UE capability to indicate whether the UE supports MAC-CE and / or DCI to update the explicit BFD RS set per TRP. If not supported, the explicit BFD RS may be RRC configured only (not updated via MAC-CE and / or DCI) as indicated by the UE. If supported, the MAC-CE and / or DCI signaling may be used to select the BFD RS set per TRP from the RS pool configured in RRC. In some cases, the UE may report its UE capability regarding the maximum number of explicitly configured candidate BFD RSs per set pool or a common pool of both sets for the MAC-CE (or DCI) to down-select.

[0105] In some cases, in a single DCI (S-DCI) scenario for mTRP, in the BFR process per TRP, the UE may make some assumptions after receiving the gNB response. For example, the UE may assume that the QCL assumption of the CORESET associated with the failed BFD-RS set is updated to the latest reported qnew beam (e.g., Qnew may be reported in the BFR MAC-CE). In some cases, to associate the BFD-RS set with the CORESET, the UE may determine the CORESET based on the RS indicated by the active TCI state and the associated BFD-RS set of the explicitly configured BFD-RS. In some cases, to associate the BFD-RS set with the CORESET, there may be an explicit association between the CORESET(s) and the BFD-RS set index(es) explicitly configured by RRC.

[0106] Possibly, for a SCell BFR with an integrated TCI framework, via the UE capability of the BFR, the UE may indicate whether it supports beam reset of all channels and / or RS applicable to the indicated TCI before the BFR is triggered. If not, only the PDCCH and / or PDSCH may have beam reset, and other channels and / or CSI-RS may not be reset. Possibly, if the SpCell BFR is configured in the same band, the UE may indicate the UE capability as the maximum number of component carriers (CCs) configured in the SCell BFR.

[0107] In some cases, the gNB may configure a CC list in the UE, and all CCs on the same list share the same TCI update and / or activation. In some cases, the number of lists that the UE supports per cell group may depend on the UE capabilities. According to some aspects of the present disclosure, for MAC-CE-based and DCI-based beam direction, for common TCI status ID update and activation CC lists, the maximum number of CC lists that may be configured is 4 per cell group. In some cases, the maximum number of CC lists that the UE supports may depend on its UE capabilities.

[0108] In the unified TCI framework, the TCI indicated by DCI format 1_1 or 1_2 may apply to all UE dedicated PDSCH / PDCCH receptions. For other channels / RS, whether they follow the same indicated TCI (as the UE dedicated PDSCH / PDCCH) may be configured by RRC. In some cases, within the unified TCI framework, for periodic and / or semi-persistent (P / SP) CSI-RS, the UE may assume that the indicated (Rel-17) TCI state always applies. In other cases, whether to apply the indicated Rel-17 TCI state may be configured per CSI-RS resource CORESET by RRC, and if not, the legacy MAC-CE signaling mechanism may be used. In other cases, the indicated Rel-17 TCI state may never apply (e.g., the legacy MAC-CE signaling mechanism is always used). In other cases, the indicated Rel-17 TCI state applies only when the gNB has not configured a TCI state for the P / SP CSI-RS.

[0109] Possibly, for DL ​​channels / signals sharing the same indicated (Rel-17) TCI state as UE-dedicated reception on PDSCH / PDCCH, the following options regarding source RS and QCL type may also be supported based on UE capabilities: CSI-RS of CSI may be configured for source RS of QCL-TypeA and QCL-TypeD.

[0110] In some cases, in (Rel-17) DCI based beam direction, in case of carrier aggregation (CA), when common TCI state ID update is not configured / supported, there are several beam application time (BAT) configuration options across CCs. According to one option, BAT is configured per CC. According to a second option, the same scheme as with common TCI state ID update may be used (e.g., common BAT is determined by CC(s) with smallest SCS in band). According to a third option, BAT list may be configured under cell group configuration and applied for each CC in the CG. For CCs not configured with common TCI state ID update, BAT may be determined by subcarrier spacing (SCS) of active BWP of CC. In some cases, in Rel-17 DCI based beam direction, for beam direction application time of non-CA, BAT may be configured / determined per CC.

[0111] In some cases, the scheduling parameter K0 (e.g., representing the offset between the DL slot where the PDCCH (DCI) for downlink scheduling is received and the DL slot where the PDSCH data is scheduled) may be selected from a limited set including 0. According to some aspects, for a DCI indicating a TCI update without scheduling a DL assignment, the UE may always assume that a virtual PDSCH is scheduled in the same slot of the DCI (K0 field=0) to determine a type 1 HARQ ACK codebook for the ACK for the DCI. For DCI formats 1_1 and 1_2 with a PDSCH assignment indicating a TCI status, the positive response to the TCI status update is an ACK of the PDSCH. The UE may receive multiple DCIs, each DCI scheduling a PDSCH and indicating a TCI status update. The DCIs may arrive at different times and the indicated TCI updates may be different. ACKs for all PDSCHs scheduled by those DCIs may be multiplexed and sent in the same PUCCH transmission (e.g., with the same ACK / NAK codebook).

[0112] In some cases, rules may be provided to clarify which TCI state update indicated in multiple DCIs is executed by the UE. For example, the application time of the TCI update may be counted from ACK to DCI, so that all TCI indications from all DCIs above are potentially valid at the same time, but only one can actually be executed. An example of such a rule is that the TCI state(s) indicated in the DCI corresponding to the last position with an ACK value in the HARQ-ACK codebook is counted. In such a case, for the remaining DCIs, the TCI state update indication may be overridden by the DCI corresponding to the last position ACK.

[0113] In some cases, in (Rel-17) beam direction with integrated TCI, for DCI format 1_1 / 1_2 without DL allocation, a "carrier indicator" field may be used in the DCI to indicate the CC ID for which the indicated TCI is updated. As an example, the DCI may be sent in CC1, the carrier indicator field of the DCI may indicate CC2, and the TCI field of the DCI may indicate TCI2. In this case, TCI2 may be updated in CC2 instead of CC1.

[0114] In some cases, for a UE activated in more than one TCI state (one TCI from the serving cell and at least one from one of at least one non-serving cell), the UE may receive both paging / short message / system information (SI) symbols from the serving cell if they do not overlap with DL signal symbols from the non-serving cell, and the UE may receive paging / short message / SI if at least one symbol of the paging / short message / SI from the serving cell overlaps with DL signal symbols from the non-serving cell.

[0115] In some cases, for a CORESET with index 0, the UE may make various QCL assumptions. For example, it may be assumed that the DM-RS antenna port for PDCCH reception in CORESET is quasi-colocated with one or more DL RSs configured by the TCI state indicated by a MAC CE activation command or TCI update DCI in CORESET, if any, or with an SS / PBCH block identified by the UE during a recent random access procedure not initiated by a PDCCH command triggering a contention-free random access procedure, or with an SS / PBCH block identified by the UE during a recently configured grant PUSCH transmission, if no MAC-CE activation / TCI update TCI DCI command is received indicating a TCI state in CORESET after the recent random access procedure. In some cases, the QCL information determined for the DMRS in CORESET 0 also applies to any channels sharing the same QCL as CORESET 0, e.g., any PDSCH, PUSCH, PUCCH, etc. scheduled by DCI from CORESET 0.

[0116] In some cases, for TCI updates when a single DCI schedules multiple PDSCHs, the applied TCI state may be updated using a unified TCI framework within the scope of the multiple PDSCHs, in which case any PDSCHs scheduled after the beam application time of the new TCI will follow the new TCI.

[0117] In some cases, for TCI updates when a single DCI schedules multiple PDSCHs, the applied TCI state cannot be updated using a unified TCI framework within the scope of the multiple PDSCHs, in which case, as long as the first PDSCH among the multiple PDSCHs is before the application time of the new TCI, all PDSCHs should use the same TCI as the first PDSCH (e.g., all use the old TCI).

[0118] For any SRS resource or resource set that possibly does not share the same indicated Rel-17 TCI state(s) as all of the dynamic grant / configured grant based PUSCH and dedicated PUCCH resources, but may be configured as a target signal for the Rel-17 UL or, if applicable, joint TCI (and thus the Rel-17 UL or, if applicable, joint TCI state pool), the MAC-CE signaling of the Rel-17 TCI state indication may include at least the TCI ID of each SRS resource, the cell ID of the SRS resource set, and the BWP ID of the SRS resource set. In such a case, the power control parameters of the SRS resource set may be derived based on the power control parameters associated with the indicated TCI for the first SRS resource.

[0119] For example, the techniques presented herein may enable a UE to send panel-related capability updates at physical layer (PHY or L1) beam reporting opportunities.

[0120] Exemplary Operation of User Equipment FIG. 8 illustrates an example method 800 of wireless communication by a wireless device, an example of which may be a UE, such as UE 104 of FIGS.

[0121] Method 800 begins with obtaining (e.g., from a network entity) a configuration for reporting BM-related information in step 805. In some cases, the operations of this step may refer to or be performed by obtaining circuitry and / or code, such as those described with reference to FIG.

[0122] The method 800 then proceeds to step 810, where the BM report is output for transmission (e.g., to a network entity) in accordance with the configuration, the BM report including an indication of the BM-related capabilities of the wireless device. In some cases, the operations of this step may refer to or be performed by output circuitry and / or output code, such as those described with reference to FIG. 10.

[0123] In some aspects, the configuration indicates at least one reporting quantity indicative of a BM-related capability of the wireless device.

[0124] In some aspects, the UE's BM-related capabilities include the number of SRS ports per antenna panel or TCI supported by the wireless device.

[0125] In some aspects, the at least one reporting quantity comprises a capability set index.

[0126] In some aspects, the UE's BM-related capabilities include a number of supported uplink transmission layers that are supported by the wireless device.

[0127] In some aspects, the BM report also includes an indication of one or more time domain BM reporting behaviors associated with the UE's BM related capabilities.

[0128] In some aspects, the one or more time domain reporting behaviors include at least one of periodic reporting, semi-persistent reporting, or periodic reporting.

[0129] In some aspects, the BM-related capabilities of the wireless device include a UE capability to support updating the BFD RS indication via at least one of MAC-CE or DCI signaling.

[0130] In some aspects, the BM report indicates the number of configured candidate BFD RSs from a pool of candidate BFD RSs that may be down-selected via MAC CE or DCI signaling.

[0131] In some aspects, the BM-related capabilities of the wireless device include the capability of the UE to support beam reset of multiple channels or RSs applicable to the indicated TCI before a BFR is triggered.

[0132] In some aspects, the BM report indicates the number of CCs of a band configured with an SCell BFR if an SpCell BFR is configured in the band.

[0133] In some aspects, the BM-related capabilities of the wireless device include the number of CC lists supported by the UE, where all CCs in the CC lists share the same TCI updates or activations.

[0134] In one aspect, the method 800, or any aspect related thereto, may be performed by an apparatus such as a communications device 1000 of Figure 10 that includes various components operable, configured, or adapted to perform the method 800. Communications device 1000 is described in further detail below.

[0135] It should be noted that FIG. 8 is merely one example of a method and that other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

[0136] Exemplary Operation of a Network Entity FIG. 9 illustrates an example method 900 of wireless communication by a wireless device, an example of which may include a network entity such as BS 102 of FIGS. 1 and 3, or a separate base station as described with respect to FIG.

[0137] Method 900 begins with outputting a configuration reporting BM-related information for transmission (e.g., to a UE) in step 905. In some cases, operations in this step may refer to or be performed by output circuitry and / or output code, such as those described with reference to FIG.

[0138] The method 900 then proceeds to step 910, where in accordance with the configuration, the BM report is obtained (e.g., from the UE), the BM report including an indication of the BM-related capabilities (e.g., of the UE). In some cases, the operations of this step may refer to or be performed by obtaining circuitry and / or code, such as those described with reference to FIG. 10.

[0139] In some aspects, the composition exhibits at least one reportable quantity indicative of a BM-associated capacity.

[0140] In some aspects, the UE's BM-related capabilities include the number of supported antenna panels or SRS ports per TCI.

[0141] In some aspects, the at least one reporting quantity comprises a capability set index.

[0142] In some aspects, the UE's BM-related capabilities include the number of supported uplink transmission layers that are supported.

[0143] In some aspects, the BM report also includes an indication of one or more time domain BM reporting behaviors associated with the BM-related capabilities.

[0144] In some aspects, the one or more time domain reporting behaviors include at least one of periodic reporting, semi-persistent reporting, or periodic reporting.

[0145] In some aspects, the UE's BM-related capabilities include a capability to support updating the BFD RS indication via at least one of MAC-CE or DCI signaling.

[0146] In some aspects, the BM report indicates the number of configured candidate BFD RSs from a pool of candidate BFD RSs that may be down-selected via MAC CE or DCI signaling.

[0147] In some aspects, the BM-related capabilities include the capability to support beam reset of multiple channels or RSs applicable to an indicated TCI before a BFR is triggered.

[0148] In some aspects, the BM report indicates the number of CCs of a band configured with an SCell BFR if an SpCell BFR is configured in the band.

[0149] In some aspects, the BM-related capabilities include the number of supported CC lists, where all CCs in a CC list share the same TCI update or activation.

[0150] In one aspect, the method 900, or any aspect related thereto, may be performed by an apparatus such as a communications device 1000 of Figure 10 that includes various components operable, configured, or adapted to perform the method 900. Communications device 1000 is described in further detail below.

[0151] It should be noted that FIG. 9 is merely one example of a method and that other methods including fewer, additional, or alternative steps are possible consistent with this disclosure.

[0152] In some cases, a device may have an interface (means for outputting) for outputting frames for transmission, rather than actually transmitting the frames. For example, a processor may output frames to a radio frequency (RF) front end for transmission via a bus interface. Similarly, a device may have an interface (means for acquiring) for acquiring frames received from another device, rather than actually receiving the frames. For example, a processor may acquire (or receive) frames from an RF front end for reception via a bus interface. In some cases, the interface for outputting frames for transmission and the interface for acquiring frames (sometimes referred to herein as the first and second interfaces) may be the same interface.

[0153] The means for establishing, means for measuring, and means for calculating may include any of the various processors and / or transceivers shown in FIG. 3 or FIG.

[0154] Exemplary Communication Devices Figure 10 illustrates aspects of an exemplary communications device 1000. In some aspects, the communications device 1000 is user equipment, such as the UE 104 described above with respect to Figures 1 and 3. In some aspects, the communications device 1000 is a network entity, such as the BS 102 of Figures 1 and 3, or a separate base station as described with respect to Figure 2.

[0155] The communication device 1000 includes a processing system 1005 coupled to a transceiver 1045 (e.g., a transmitter and / or a receiver). In some aspects (e.g., when the communication device 1000 is a network entity), the processing system 1005 may be coupled to a network interface 1055 configured to obtain and transmit signals for the communication device 1000 via a communication link(s), such as a backhaul link, a midhaul link, and / or a fronthaul link described herein, such as with respect to FIG. 2. The transceiver 1045 is configured to transmit and receive signals for the communication device 1000 via an antenna 1050, such as various signals as described herein. The processing system 1005 can be configured to perform processing functions for the communication device 1000, including processing signals to be received and / or transmitted by the communication device 1000.

[0156] The processing system 1005 includes one or more processors 1010. In various aspects, the one or more processors 1010 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380 as described with respect to FIG. 3. In various aspects, the one or more processors 1010 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340 as described with respect to FIG. 3. The one or more processors 1010 are coupled to a computer-readable medium / memory 1025 via a bus 1040. In some aspects, the computer-readable medium / memory 1025 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1010, cause the one or more processors 1010 to perform the method 800 described with respect to FIG. 8, or any aspects related thereto. In some aspects, the computer-readable medium / memory 1025 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1010, cause the one or more processors 1010 to perform the method 900 described with respect to Figure 9, or any aspects related thereto. It should be noted that reference to a processor performing a function of the communications device 1000 may include one or more processors 1010 performing that function of the communications device 1000.

[0157] In the illustrated example, computer readable medium / memory 1025 stores code (e.g., executable instructions), such as acquisition code 1030 and output code 1035. Processing of acquisition code 1030 and output code 1035 may cause communications device 1000 to perform method 800 described with respect to Figure 8, or any aspect related thereto. Processing of acquisition code 1030 and output code 1035 may cause communications device 1000 to perform method 900 described with respect to Figure 9, or any aspect related thereto.

[0158] The one or more processors 1010 include circuitry configured to implement (e.g., execute) code stored on a computer-readable medium / memory 1025, including circuitry such as an acquisition circuit 1015 and an output circuit 1020. Processing by the acquisition circuit 1015 and the output circuit 1020 may cause the communications device 1000 to perform the method 800 described with respect to Figure 8, or any aspect related thereto. Processing by the acquisition circuit 1015 and the output circuit 1020 may cause the communications device 1000 to perform the method 900 described with respect to Figure 9, or any aspect related thereto.

[0159] Various components of the communications device 1000 may provide means for performing the method 800 described with respect to Figure 8, or any aspect related thereto, as well as means for performing the method 900 described with respect to Figure 9, or any aspect related thereto. For example, the means for transmitting, sending, or outputting for transmission may include the transceiver 354 and / or antenna(s) 352 of the UE 104 shown in Figure 3, the transceiver 332 and / or antenna(s) 334 of the BS 102 shown in Figure 3, and / or the transceiver 1045 and antenna 1050 of the communications device 1000 of Figure 10. The means for receiving or acquiring may include the transceiver 354 and / or antenna(s) 352 of the UE 104 shown in Figure 3, the transceiver 332 and / or antenna(s) 334 of the BS 102 shown in Figure 3, and / or the transceiver 1045 and antenna 1050 of the communications device 1000 of Figure 10.

[0160] Example clauses The following numbered clauses describe example implementations.

[0161] Clause 1: A method of wireless communication in a wireless device, the method comprising: obtaining a configuration for reporting BM-related information; and outputting a BM report in accordance with the configuration for transmission, the BM report including an indication of BM-related capabilities.

[0162] Clause 2: The method of clause 1, wherein the configuration indicates at least one reporting quantity indicative of a BM-related capability.

[0163] Clause 3: The method of clause 2, wherein the at least one reporting quantity indicates a number of SRS ports per supported antenna panel or TCI.

[0164] Clause 4: The method of clause 2, wherein at least one reporting quantity includes a capability set index.

[0165] Clause 5: The method according to any one of clauses 1 to 4, wherein the BM-related capabilities include a number of supported uplink transmission layers.

[0166] Clause 6: The method of any one of clauses 1 to 5, wherein the BM report also includes an indication of one or more time-domain BM reporting behaviors associated with BM-related capabilities.

[0167] Clause 7: The method of clause 6, wherein the one or more time domain reporting behaviors include at least one of periodic reporting, semi-persistent reporting, or periodic reporting.

[0168] Clause 8: The method according to any one of clauses 1 to 7, wherein the BM-related capabilities of the UE include a capability of the UE to support updating the BFD RS indication via at least one of MAC-CE or DCI signaling.

[0169] Clause 9: The method according to clause 8, wherein the BM report indicates the number of configured candidate BFD RSs from a pool of candidate BFD RSs that may be down-selected via MAC CE or DCI signaling.

[0170] Clause 10: The method according to any one of clauses 1 to 9, wherein the BM-related capabilities include the UE's capability to support beam reset of multiple channels or RSs applicable to the indicated TCI before BFR is triggered.

[0171] Clause 11: The method according to any one of clauses 1 to 10, wherein the BM report indicates the number of CCs of the band configured with the SCell BFR when an SpCell BFR is configured in the band.

[0172] Clause 12: The method according to any one of clauses 1 to 11, wherein the BM-related capability includes a number of supported CC lists, and all CCs in the CC lists share the same TCI update or activation.

[0173] Clause 13: A method of wireless communication in a wireless device, the method comprising: outputting a configuration for reporting BM-related information for transmission; and obtaining a BM report in accordance with the configuration, the BM report including an indication of BM-related capabilities.

[0174] Clause 14: The method of clause 13, wherein the configuration indicates at least one reporting quantity indicative of a BM-related capability.

[0175] Clause 15: The method of clause 14, wherein the at least one reporting quantity indicates a number of SRS ports per supported antenna panel or TCI.

[0176] Clause 16: The method of clause 14, wherein at least one reporting quantity includes a capability set index.

[0177] Clause 17: The method according to any one of clauses 13 to 16, wherein the BM-related capabilities of the UE include a number of supported uplink transmission layers.

[0178] Clause 18: The method of any one of clauses 13 to 17, wherein the BM report also includes an indication of one or more time-domain BM reporting behaviors associated with BM-related capabilities.

[0179] Clause 19: The method of clause 18, wherein the one or more time domain reporting behaviors include at least one of periodic reporting, semi-persistent reporting, or periodic reporting.

[0180] Clause 20: The method according to any one of clauses 13 to 19, wherein the BM-related capabilities include a UE capability to support updating the BFD RS indication via at least one of MAC-CE or DCI signaling.

[0181] Clause 21: The method according to clause 20, wherein the BM report indicates the number of configured candidate BFD RSs from a pool of candidate BFD RSs that may be down-selected via MAC CE or DCI signaling.

[0182] Clause 22: A method according to any one of clauses 13 to 21, wherein the BM-related capabilities of the UE include the capability of the UE to support beam reset of multiple channels or RSs applicable to the indicated TCI before BFR is triggered.

[0183] Clause 23: The method according to any one of clauses 13 to 22, wherein the BM report indicates the number of CCs of the band configured with the SCell BFR when the SpCell BFR is configured in the band.

[0184] Clause 24: The method according to any one of clauses 13 to 23, wherein the BM-related capability includes a number of supported CC lists, and all CCs in the CC list share the same TCI update or activation.

[0185] Clause 25: An apparatus comprising: a memory comprising executable instructions; and a processor configured to execute the executable instructions to cause the apparatus to perform a method according to any one of clauses 1 to 24.

[0186] Clause 26: An apparatus comprising means for carrying out the method according to any one of clauses 1 to 24.

[0187] Clause 27: A non-transitory computer-readable medium comprising executable instructions that, when executed by a processor of a device, cause the device to perform a method according to any one of clauses 1 to 24.

[0188] Clause 28: A computer program product embodied on a computer-readable storage medium comprising code for performing the method according to any one of clauses 1 to 24.

[0189] Clause 29: A user equipment (UE) comprising at least one transceiver, a memory containing instructions, and one or more processors configured to execute the instructions and cause the UE to perform a method according to any one of clauses 1 to 12, wherein the at least one transceiver is configured to at least one of receive a configuration or transmit a BM report.

[0190] Clause 30: A network entity comprising at least one transceiver, a memory containing instructions, and one or more processors configured to execute the instructions and cause the network entity to perform a method according to any one of clauses 13 to 24, wherein the at least one transceiver is configured to at least one of transmit a configuration or receive a BM report.

[0191] Additional Considerations The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples described herein are not intended to limit the scope, applicability, or aspects described in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may also be applied to other aspects. For example, changes may be made in the function and arrangement of the elements described without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the methods described may be performed in an order different from that described, and various actions may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects described herein. Additionally, the scope of the disclosure is intended to encompass such apparatus or methods practiced using other structures, functions, or structures and functions in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0192] The various example logic blocks, modules, and circuits described in connection with this disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0193] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. By way of example, "at least one of a, b, or c" is intended to encompass a, b, c, ab, ac, bc, and abc, as well as any combination having multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other permutation of a, b, and c).

[0194] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, electing, establishing, and the like.

[0195] The methods disclosed herein include one or more actions that achieve the method. The actions of those methods may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. Furthermore, various operations of the methods described above may be performed by any suitable means capable of performing the corresponding functions. Those means may include various hardware and / or software component(s) including, but not limited to, circuits, application specific integrated circuits (ASICs), or processors, and / or various hardware and / or software module(s).

[0196] The following claims are not intended to be limited to the embodiments set forth herein, but are to be accorded the full scope consistent with the language of the claims. Within the claims, reference to an element by the singular is not intended to mean "one and only one" unless expressly stated as such, but rather "one or more." The term "several" refers to one or more, unless expressly stated otherwise. Claim elements are not to be construed under the provisions of 35 U.S.C. 112(f) unless the element is expressly recited using the phrase "means for." All structural and functional equivalents of the elements of the various embodiments described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be made public, regardless of whether such disclosure is expressly recited in the claims.

Claims

1. A method for wireless communication using user equipment (UE), To obtain the configuration for reporting beam management (BM) related information, Transmitting a BM report in accordance with the above configuration, wherein the BM report includes instructions for the BM-related capabilities of the UE, and the BM-related capabilities include antenna panel-related capability updates. The instruction for the aforementioned BM-related information is transmitted during the Layer 1 (L1) beam reporting opportunity. Methods that include...

2. The method according to claim 1, wherein the configuration indicates at least one reported quantity representing the BM-related capability of the device.

3. The method according to claim 2, wherein the at least one reported quantity indicates the number of sounding reference signal (SRS) ports per antenna panel or transmit configuration indicator (TCI) supported by the device.

4. The method according to claim 2, wherein the at least one reported quantity includes a capability set index.

5. The method according to claim 1, wherein the BM-related capability of the device includes the number of uplink transmission layers supported by the device.

6. The method according to claim 1, wherein the BM report also includes instructions for one or more time-domain BM reporting behaviors associated with the BM-related capabilities of the device.

7. The method according to claim 6, wherein the one or more time-domain reporting behaviors include at least one of periodic reporting, semi-permanent reporting, or non-periodic reporting.

8. The method according to claim 1, wherein the BM-related capability of the apparatus includes the capability of the apparatus to support updating beam fault detection (BFD) reference signal (RS) indications via at least one of medium access control (MAC) control elements (CE) or downlink control information (DCI) signaling, and the BM report indicates the number of configured candidate BFD RSs from a pool of candidate BFD RSs that can be downselected via the MAC CE or the DCI signaling.

9. The method according to claim 1, wherein the BM-related capability of the apparatus includes the ability of the apparatus to support beam reset of a plurality of channels or reference signals (RSs) applicable to an indicated transmit configuration indicator (TCI) before beam fault recovery (BFR) is triggered.

10. The method according to claim 1, wherein the BM report indicates the number of component carriers (CCs) of the band composed of secondary cell (SCell) BFRs when a special cell (SpCell) BFR is configured within the band.

11. The method according to claim 1, wherein the BM-related capability of the device includes the number of component carrier (CC) lists supported by the device, and all CCs in the CC list share the same transmit configuration indicator (TCI) update or activation.

12. A device for wireless communication, An apparatus comprising means configured to perform the method described in one of claims 1 to 11.

13. A method for wireless communication by a network entity, Transmitting a configuration for reporting beam management (BM) related information, wherein the BM related capability includes antenna panel related capability updates. Obtaining a BM report in accordance with the above configuration, wherein the BM report includes an instruction for BM-related capability, and the instruction for BM-related capability is received at a Layer 1 (L1) beam reporting opportunity. Methods that include...

14. A device for wireless communication, An apparatus comprising means configured to perform the method described in claim 13.

15. A computer program comprising program instructions, wherein the program instructions, when the program is executed by a computer, execute the method according to any one of claims 1 to 11 and 13.

Images