CN117882302A

CN117882302A - Method and apparatus for beam measurement and reporting

Info

Publication number: CN117882302A
Application number: CN202280058082.8A
Authority: CN
Inventors: M·S·拉曼; E·昂戈萨努西; E·N·法拉格
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2021-08-27
Filing date: 2022-08-26
Publication date: 2024-04-12

Abstract

The present disclosure relates to 5G or 6G communication systems for supporting higher data transmission rates. Methods and apparatus for beam measurement and reporting. A method performed by a User Equipment (UE), the method comprising: transmitting UE capability information including a supported set of capability values to a base station; receiving configuration information on Channel State Information (CSI) reports from a base station; identifying a capability value corresponding to a maximum sounding reference signal (SR S) antenna port number of the UE; determining that the report includes a CS I report indicating an indicator of the capability value; and transmitting the identified CSI report to the base station.

Description

Method and apparatus for beam measurement and reporting

Technical Field

The present disclosure relates generally to wireless communication systems, and more particularly, to methods and apparatus for beam measurement and reporting.

Background

The 5G mobile communication technology defines a wide frequency band, enables high transmission rates and new services, and can be implemented not only in a "below 6 GHz" frequency band such as 3.5GHz, but also in a "above 6 GHz" frequency band called millimeter waves including 28GHz and 39 GHz. In addition, in order to achieve a transmission rate 50 times faster than that of the 5G mobile communication technology and an ultra-low latency of one tenth of that of the 5G mobile communication technology, it has been considered to implement the 6G mobile communication technology (referred to as a super 5G system) in a terahertz (THz) band (e.g., 95GHz to 3THz band).

In the early stages of the development of 5G Mobile communication technology, in order to support services and meet performance requirements related to enhanced Mobile BroadBand (eMBB), ultra-reliable low latency communication (Ultra Reliable Low Latency Communications, URLLC), and large-scale Machine-type communication (emtc), standardization has been proceeding with respect to: beamforming and massive MIMO for alleviating radio wave path loss and increasing radio wave transmission distance in millimeter waves; supporting a basic set of parameters (e.g., operating multiple subcarrier spacings) for dynamic operation that efficiently utilizes millimeter wave resources and slot formats; an initial access technology for supporting multi-beam transmission and broadband; definition and operation of BWP (BandWidth Part); new channel coding methods such as LDPC (Low Density Parity Check ) codes for large data transmission and polarization codes for highly reliable transmission of control information; l2 pretreatment; and a network slice for providing a private network dedicated to a particular service.

Currently, in view of services that the 5G mobile communication technology will support, discussions are being made about improvement and performance enhancement of the initial 5G mobile communication technology, and there has been physical layer standardization with respect to technologies such as: V2X (Vehicle-to-everything) for assisting driving determination of the autonomous Vehicle based on information about the position and state of the Vehicle transmitted by the Vehicle, and for enhancing user convenience; NR-U (New Radio Unlicensed, new radio license exempt), system operation for compliance with various regulatory-related requirements in the license exempt band; NR UE saves energy; a Non-terrestrial network (Non-Terrestrial Network, NTN) that is a UE-satellite direct communication for providing coverage in areas where communication with the terrestrial network is unavailable; and positioning.

Furthermore, standardization has been underway in terms of air interface architecture/protocols with respect to technologies such as: industrial internet of things (Industrial Internet of Things, IIoT) for supporting new services through interworking and fusion with other industries; an IAB (Integrated Access and Backhaul ) for providing a node for network service area extension by supporting a wireless backhaul link and an access link in an integrated manner; mobility enhancements, including conditional handoffs and DAPS (Dual Active Protocol Stack ) handoffs; and two-step random access for simplifying a random access procedure (2-step RACH for NR). Standardization has also been underway in terms of system architecture/services with respect to: a 5G baseline architecture (e.g., a service-based architecture or a service-based interface) for combining network function virtualization (Network Functions Virtualization, NFV) and Software-defined networking (SDN) technologies; and a mobile edge calculation (Mobile Edge Computing, MEC) for receiving services based on the UE location.

With commercialization of the 5G mobile communication system, the connection device, which has been exponentially increased, will be connected to the communication network, and accordingly, it is expected that enhanced functions and performance of the 5G mobile communication system and integrated operation of the connection device will be necessary. For this purpose, new studies related to the following are planned: augmented Reality (XR) for effectively supporting AR (Augmented Reality ), VR (Virtual Reality), MR (Mixed Reality), and the like; improving 5G performance and reducing complexity by utilizing artificial intelligence (Artificial Intelligence, AI) and Machine Learning (ML); AI service support; meta-universe service support; and unmanned aerial vehicle communication.

Further, such development of the 5G mobile communication system will be fundamental not only as a new waveform for developing coverage of the terahertz band for the 6G mobile communication technology, multi-antenna transmission technology such as Full dimension MIMO (FD-MIMO), array antennas and massive antennas, metamaterial-based lenses and antennas for improving coverage of the terahertz band signals, high Dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum ) and RIS (Reconfigurable Intelligent Surface, reconfigurable intelligent surface), but also as a basis for developing Full duplex technology for improving frequency efficiency of the 6G mobile communication technology and improving a system network, AI-based communication technology for implementing system optimization by utilizing satellites and AI (artificial intelligence) and internalizing end-to-end AI support functions from a design stage, and next generation distributed computing technology for implementing a degree of complexity of services exceeding the UE operation capability limit by utilizing ultra-high performance communication and computing resources.

Understanding and properly estimating the channel between a User Equipment (UE) and a Base Station (BS), such as a gNode B (gNB), is important for efficient and effective wireless communication. To properly estimate DL channel conditions, the gNB may send reference signals (e.g., CSI-RS) for DL channel measurements to the UE, and the UE may report (e.g., feedback) information (e.g., CSI) about the channel measurements to the gNB. With this DL channel measurement, the gNB can select appropriate communication parameters to efficiently and effectively perform wireless data communication with the UE. For millimeter wave communication systems, the reference signals may correspond to spatial beams and the CSI may correspond to beam reports indicating preferred spatial beams for communication. In such beamforming systems, beam measurement and reporting from the UE and beam indication mechanisms from the gNB are required in order to align the spatial beams at both the gNB and the UE.

Disclosure of Invention

Technical problem

Embodiments of the present disclosure provide methods and apparatus for beam measurement and reporting.

Solution to the problem

In one embodiment, a UE for beam measurement reporting in a wireless communication system is provided. The UE includes a transceiver configured to receive information about a report including at least one capability value for an Uplink (UL) transmission. The UE also includes a processor operatively connected to the transceiver, the processor configured to: determining at least one capability value, and determining a report comprising an indicator indicating the at least one capability value; wherein the transceiver is further configured to transmit a report.

In another embodiment, a BS in a wireless communication system is provided. The BS includes a processor configured to generate information about a report including at least one capability value for UL transmissions. The BS includes a transceiver operably coupled to the processor, the transceiver configured to transmit information and receive a report, wherein the report includes an indicator indicating at least one capability value.

In yet another embodiment, a method for operating a UE is provided. The method comprises the following steps: receiving information about a report, the report including at least one capability value for UL transmissions; determining at least one capability value; determining a report comprising an indicator indicating at least one capability value; and sending a report.

Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

Before proceeding with the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," and derivatives thereof, encompass both direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation. The term "or" is inclusive, meaning and/or. The phrase "associated with … …" and its derivatives are intended to include, be included within … …, interconnect with … …, contain, be included within … …, connect to … … or connect to … …, couple to … … or couple to … …, be communicable with … …, cooperate with … …, interleave, juxtapose, be proximate to … …, bind to … … or bind to … …, have attributes of … …, have relationships with … …, and the like. The term "controller" means any device, system, or portion thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and/or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase "at least one of … …," when used with a list of items, means that different combinations of one or more of the listed items can be used, and that only one item in the list may be required. For example, "at least one of A, B and C" includes any combination of the following: A. b, C, A and B, A and C, B and C, and a and B and C.

Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or portions thereof adapted for implementation in a suitable computer readable program code. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer readable medium" includes any type of medium capable of being accessed by a computer, such as Read Only Memory (ROM), random access memory (random access memory, RAM), a hard disk drive, a Compact Disc (CD), a digital video disc (digital video disc, DVD), or any other type of memory. "non-transitory" computer-readable media do not include wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer readable media include media that can permanently store data and media that can store data and be later rewritten (such as rewritable optical disks or erasable storage devices).

Definitions for other specific words and phrases are also provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior as well as future uses of such defined words and phrases.

Advantageous effects of the invention

Aspects of the present disclosure provide an efficient communication method in a wireless communication system.

Drawings

For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

fig. 1 illustrates an example wireless network according to an embodiment of the disclosure;

FIG. 2 illustrates an example gNB, according to an embodiment of the present disclosure;

fig. 3 illustrates an example UE in accordance with an embodiment of the present disclosure;

fig. 4A illustrates a high-level diagram of an orthogonal frequency division multiple access transmit path according to an embodiment of the present disclosure;

fig. 4B illustrates a high-level diagram of an orthogonal frequency division multiple access receive path according to an embodiment of the present disclosure;

fig. 5 shows a transmitter block diagram for PDSCH in a subframe according to an embodiment of the disclosure;

fig. 6 shows a receiver block diagram for PDSCH in a subframe according to an embodiment of the disclosure;

fig. 7 shows a transmitter block diagram for PUSCH in a subframe according to an embodiment of the disclosure;

Fig. 8 shows a receiver block diagram for PUSCH in a subframe according to an embodiment of the disclosure;

fig. 9 illustrates an example antenna block or array forming a beam in accordance with an embodiment of the present disclosure;

fig. 10 illustrates uplink multi-beam operation according to an embodiment of the present disclosure;

fig. 11 illustrates uplink multi-beam operation according to an embodiment of the present disclosure;

fig. 12 illustrates downlink multi-beam operation according to an embodiment of the present disclosure;

fig. 13 illustrates an example antenna panel according to an embodiment of the disclosure;

fig. 14 illustrates other example antenna panels according to embodiments of the present disclosure;

fig. 15 illustrates a UE configured to measure DL measurement RS resources and determine a report including a capability index in accordance with an embodiment of the present disclosure;

fig. 16 shows a flowchart of a UE configured to measure DL measurement RS resources and report beam reports in accordance with an embodiment of the present disclosure;

fig. 17 shows a flowchart of a UE configured to measure DL measurement RS resources and report beam reports in accordance with an embodiment of the present disclosure;

figure 18 shows an example of a single mesh MAC CE for multiple MPE reports in accordance with an embodiment of the present disclosure;

figure 19 illustrates another example of a single mesh MAC CE for multiple MPE reports according to an embodiment of the disclosure;

Figure 20 illustrates yet another example of a single mesh MAC CE for multiple MPE reports in accordance with an embodiment of the present disclosure;

fig. 21 shows a flowchart of a method for operating a UE in accordance with an embodiment of the present disclosure;

fig. 22 shows a flowchart of a method for operating a BS according to an embodiment of the present disclosure;

fig. 23 shows a block diagram illustrating a structure of a UE according to an embodiment of the present disclosure; and

fig. 24 shows a block diagram illustrating a structure of a base station according to an embodiment of the present disclosure.

Detailed Description

Figures 1 through 247, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will appreciate that the principles of the present disclosure may be implemented in any suitably arranged system or device.

The following documents and standard descriptions are incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 36.211v17.0.0, "EUTRA, physical channel and modulation" (herein "REF 1"); 3GPP TS 36.212v17.0.0, "EUTRA, multiplexing and channel coding" (herein "REF 2"); 3GPP TS 36.213v17.0.0, "EUTRA, physical layer procedure" (herein "REF 3"); 3GPP TS 36.321v17.0.0, "E-UTRA, medium Access Control (MAC) protocol Specification" (herein "REF 4"); 3GPP TS 36.331v17.0.0, "EUTRA, radio Resource Control (RRC) protocol specification" (herein "REF 5"); 3GPP TS 38.211v17.0.0, "NR, physical channel and modulation" (herein "REF 6"); 3GPP TS 38.212v17.0.0, "E-UTRA, NR, multiplexing and channel coding" (herein "REF 7"); 3GPP TS 38.213v17.0.0, "NR, physical layer control procedure" (herein "REF 8"); 3GPP TS 38.214v 17.0.0, "NR, physical layer data program" (herein "REF 9"); 3GPP TS 38.215v17.0.0, "NR, physical layer measurement" (herein "REF 10"); 3GPP TS 38.321v17.0.0, "NR, medium Access Control (MAC) protocol specification" (herein "REF 11"); and 3GPP TS 38.331v17.0.0, "NR, radio Resource Control (RRC) protocol specification" (herein "REF 12").

Aspects, features and advantages of the present disclosure will become apparent from the following detailed description simply by illustrating a number of specific embodiments and implementations, including the best mode contemplated for carrying out the present disclosure. The disclosure is capable of other different embodiments and its several details are capable of modifications in various obvious respects, all without departing from the spirit and scope of the present disclosure. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive. The present disclosure is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.

Hereinafter, for brevity, both FDD and TDD are considered as duplex methods for DL signaling and UL signaling.

Although the following exemplary description and embodiments assume orthogonal frequency division multiplexing (orthogonal frequency division multiplexing, OFDM) or orthogonal frequency division multiple access (orthogonal frequency division multiple access, OFDMA), the present disclosure may be extended to other OFDM-based transmission waveforms or multiple access schemes, such as filtered OFDM (F-OFDM).

In order to meet the increasing demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or front 5G communication systems. Therefore, the 5G or front 5G communication system is also referred to as a "super 4G network" or a "LTE-after-system".

A 5G communication system is considered to be implemented in a higher frequency (millimeter wave) band (e.g., 60GHz band) in order to achieve higher data rates, or in a lower frequency band (e.g., below 6 GHz) in order to achieve robust coverage and mobility support. In order to reduce propagation loss of radio waves and increase transmission coverage, beamforming, massive Multiple Input Multiple Output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, massive antenna techniques, and the like are discussed in 5G communication systems.

Further, in the 5G communication system, development of system network improvement based on advanced small cells, cloud radio access networks (radio access network, RAN), ultra dense networks, device-to-device (D2D) communication, wireless backhaul communication, mobile networks, cooperative communication, coordinated multipoint (coordinated multi-points, coMP) transmission and reception, interference mitigation and cancellation, and the like is underway.

The discussion of the 5G system and the frequency bands associated therewith is for reference as certain embodiments of the present disclosure may be implemented in a 5G system. However, the present disclosure is not limited to 5G systems or frequency bands associated therewith, and embodiments of the present disclosure may be used in conjunction with any frequency band. For example, aspects of the present disclosure may also be applied to 5G communication systems, 6G or even higher versions of deployments that may use terahertz (THz) frequency bands.

Fig. 1-4B below describe various embodiments implemented in a wireless communication system utilizing Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. The description of fig. 1-3 is not meant to imply physical or architectural limitations with respect to the manner in which different embodiments may be implemented. The various embodiments of the present disclosure may be implemented in any suitably arranged communication system. The present disclosure encompasses several components that may be used in combination or combination with one another or that may operate as stand-alone schemes.

Fig. 1 illustrates an example wireless network according to an embodiment of this disclosure. The embodiment of the wireless network shown in fig. 1 is for illustration only. Other embodiments of wireless network 100 may be used without departing from the scope of this disclosure.

As shown in fig. 1, the wireless network includes a gNB 101, a gNB 102, and a gNB 103. The gNB 101 communicates with the gNB 102 and the gNB 103. The gNB 101 is also in communication with at least one network 130, such as the Internet, a proprietary Internet protocol (Internet Protocol, IP) network, or other data network.

The gNB 102 provides wireless broadband access to the network 130 for a first plurality of User Equipment (UEs) within the coverage area 120 of the gNB 102. The first plurality of UEs includes: UE 111, which may be located in a small business; UE 112, which may be located in enterprise (E); UE 113, which may be located in a WiFi Hotspot (HS); UE 114, which may be located in a first home (R); a UE 115, which may be located in a second home (R); and UE 116, which may be a mobile device (M), such as a cellular telephone, wireless laptop, wireless PDA, or the like. The gNB 103 provides wireless broadband access to the network 130 for a second plurality of UEs within the coverage area 125 of the gNB 103. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of the gNBs 101-103 may communicate with each other and with the UEs 111-116 using 5G, LTE, LTE-A, wiMAX, wiFi or other wireless communication techniques.

Depending on the network type, the term "base station" or "BS" may refer to any component (or set of components) configured to provide wireless access to a network, such as a Transmit Point (TP), a transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macrocell, a femtocell, a WiFi Access Point (AP), or other wireless-enabled device. The base station may provide wireless access according to one or more wireless communication protocols, e.g., 5g 3gpp new radio interface/access (NR), long term evolution (long term evolution, LTE), LTE-advanced (LTE-a), high speed packet access (high speed packet access, HSPA), wi-Fi 802.11a/b/g/n/ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to the network infrastructure components that provide wireless access to remote terminals. Furthermore, the term "user equipment" or "UE" may refer to any component, such as a "mobile station", "subscriber station", "remote terminal", "wireless terminal", "reception point" or "user equipment", depending on the type of network. For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to a remote wireless device that wirelessly accesses the BS, whether the UE is a mobile device (such as a mobile phone or smart phone) or is generally considered to be a stationary device (such as a desktop computer or vending machine).

The dashed lines illustrate the general extent of coverage areas 120 and 125, which are shown as being generally circular for purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with the gnbs, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gnbs and the variations in the radio environment associated with the natural and man-made obstructions.

As described in more detail below, one or more of UEs 111-116 include circuitry, programs, or a combination thereof for: receiving information about a report, the report including at least one capability value for an Uplink (UL) transmission; determining at least one capability value; determining a report comprising an indicator indicating at least one capability value; and sending a report. One or more of the gnbs 101-103 include circuitry, programs, or a combination thereof for: generating information about a report, the report including at least one capability value for an Uplink (UL) transmission; and receiving a report, wherein the report includes an indicator indicating at least one capability value.

Although fig. 1 shows one example of a wireless network, various changes may be made to fig. 1. For example, the wireless network may include any number of gnbs and any number of UEs in any suitable arrangement. Further, the gNB 101 may communicate directly with any number of UEs and provide these UEs with wireless broadband access to the network 130. Similarly, each of the gnbs 102-103 may communicate directly with the network 130 and provide the UE with direct wireless broadband access to the network 130. Furthermore, the gnbs 101, 102, and/or 103 may provide access to other or additional external networks (such as external telephone networks or other types of data networks).

Fig. 2 illustrates an example gNB 102 in accordance with an embodiment of the disclosure. The embodiment of the gNB 102 shown in fig. 2 is for illustration only, and the gnbs 101 and 103 of fig. 1 may have the same or similar configuration. However, there are a variety of configurations of the gnbs, and fig. 2 does not limit the scope of the disclosure to any particular implementation of the gnbs.

As shown in fig. 2, the gNB 102 includes a plurality of antennas 205a-205n, a plurality of RF transceivers 210a-210n, transmit (TX) processing circuitry 215, and Receive (RX) processing circuitry 220. The gNB 102 also includes a controller/processor 225, memory 230, and a backhaul or network interface 235.

RF transceivers 210a-210n receive incoming RF signals, such as signals transmitted by UEs in network 100, from antennas 205a-205 n. The RF transceivers 210a-210n down-convert incoming RF signals to generate IF or baseband signals. The IF or baseband signal is sent to RX processing circuit 220, and RX processing circuit 220 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuit 220 sends the processed baseband signals to a controller/processor 225 for further processing.

TX processing circuitry 215 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from controller/processor 225. TX processing circuitry 215 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 210a-210n receive outgoing processed baseband or IF signals from TX processing circuitry 215 and upconvert the baseband or IF signals to RF signals transmitted via antennas 205a-205 n.

The controller/processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, controller/processor 225 may control the reception of UL channel signals and the transmission of DL channel signals via RF transceivers 210a-210n, RX processing circuitry 220, and TX processing circuitry 215, in accordance with well-known principles. The controller/processor 225 may also support additional functions, such as higher-level wireless communication functions.

For example, the controller/processor 225 may support beamforming or directional routing operations in which outgoing signals from the plurality of antennas 205a-205n are weighted differently to effectively direct the outgoing signals in a desired direction. The controller/processor 225 may support any of a wide variety of other functions in the gNB 102.

The controller/processor 225 is also capable of executing programs and other processes residing in memory 230, such as an OS. Controller/processor 225 may move data into and out of memory 230 as needed to perform the process.

The controller/processor 225 is also coupled to a backhaul or network interface 235. Backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems through a backhaul connection or through a network. The interface 235 may support communication over any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G, LTE or LTE-a), the interface 235 may allow the gNB 102 to communicate with other gnbs over a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 may allow the gNB 102 to communicate with a larger network (such as the internet) through a wired or wireless local area network or through a wired or wireless connection. Interface 235 includes any suitable structure that supports communication over a wired or wireless connection, such as an ethernet transceiver or an RF transceiver.

Memory 230 is coupled to controller/processor 225. A portion of memory 230 may include RAM and another portion of memory 230 may include flash memory or other ROM.

Although fig. 2 shows one example of the gNB 102, various changes may be made to fig. 2. For example, the gNB 102 may include any number of each of the components shown in FIG. 2. As a particular example, an access point may include multiple interfaces 235 and the controller/processor 225 may support routing functions to route data between different network addresses. As another particular example, while shown as including a single instance of TX processing circuitry 215 and a single instance of RX processing circuitry 220, the gNB 102 may include multiple instances of each (such as one instance per RF transceiver). Furthermore, the various components in fig. 2 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs.

Fig. 3 illustrates an example UE 116 according to an embodiment of this disclosure. The embodiment of UE 116 shown in fig. 3 is for illustration only and UEs 111-115 of fig. 1 may have the same or similar configuration. However, there are a variety of configurations for the UE, and fig. 3 does not limit the scope of the present disclosure to any particular implementation of the UE.

As shown in fig. 3, UE 116 includes an antenna 305, a Radio Frequency (RF) transceiver 310, TX processing circuitry 315, a microphone 320, and Receive (RX) processing circuitry 325.UE 116 also includes speaker 330, processor 340, input/output (I/O) interface 345, touch screen 350, display 355, and memory 360. The memory 360 includes an Operating System (OS) 361 and one or more applications 362.

RF transceiver 310 receives incoming RF signals from antenna 305 that are transmitted by the gNB of network 100. The RF transceiver 310 down-converts the incoming RF signal to generate an intermediate frequency (intermediate frequency, IF) or baseband signal. The IF or baseband signal is sent to RX processing circuit 325, and RX processing circuit 325 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. RX processing circuit 325 sends the processed baseband signal to speaker 330 (such as for voice data) or processor 340 for further processing (such as for web browsing data).

TX processing circuitry 315 receives analog or digital voice data from microphone 320 or other outgoing baseband data (such as web data, email, or interactive video game data) from processor 340. TX processing circuitry 315 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 310 receives outgoing processed baseband or IF signals from TX processing circuitry 315 and up-converts the baseband or IF signals to RF signals that are transmitted via antenna 305.

Processor 340 may include one or more processors or other processing devices and execute OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor 340 may control reception of DL channel signals and transmission of UL channel signals through RF transceiver 310, RX processing circuit 325, and TX processing circuit 315 in accordance with well-known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.

Processor 340 is also capable of executing other processes and programs resident in memory 360, such as processes for: receiving information about a report, the report including at least one capability value for an Uplink (UL) transmission; determining at least one capability value; determining a report comprising an indicator indicating at least one capability value; and sending a report. Processor 340 may move data into and out of memory 360 as needed to perform the process. In some embodiments, the processor 340 is configured to execute the application 362 based on the OS 361 or in response to a signal received from the gNB or operator. Processor 340 is also coupled to I/O interface 345, I/O interface 345 providing UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I/O interface 345 is the communication path between these accessories and processor 340.

Processor 340 is also coupled to touch screen 350 and display 355. An operator of UE 116 may input data to UE 116 using touch screen 350. Display 355 may be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and/or at least limited graphics, such as limited graphics from a website.

A memory 360 is coupled to the processor 340. A portion of memory 360 may include Random Access Memory (RAM) and another portion of memory 360 may include flash memory or other Read Only Memory (ROM).

Although fig. 3 shows one example of UE 116, various changes may be made to fig. 3. For example, the various components in FIG. 3 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs. As a particular example, the processor 340 may be divided into multiple processors, such as one or more central processing units (central processing unit, CPUs) and one or more graphics processing units (graphics processing unit, GPUs). Further, while fig. 3 shows the UE 116 configured as a mobile phone or smart phone, the UE may be configured to operate as other types of mobile or stationary devices.

Fig. 4A is a high-level diagram of a transmit path circuit. For example, the transmit path circuitry may be used for Orthogonal Frequency Division Multiple Access (OFDMA) communications. Fig. 4B is a high-level diagram of a receive path circuit. For example, the receive path circuitry may be used for Orthogonal Frequency Division Multiple Access (OFDMA) communications. In fig. 4A and 4B, for downlink communications, the transmit path circuitry may be implemented in the base station (gNB) 102 or the relay station, and the receive path circuitry may be implemented in a user equipment (e.g., user equipment 116 of fig. 1). In other examples, for uplink communications, the receive path circuitry 450 may be implemented in a base station (e.g., the gNB 102 of fig. 1) or a relay station, and the transmit path circuitry may be implemented in a user equipment (e.g., the user equipment 116 of fig. 1).

The transmit path circuitry includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, an N-point inverse fast fourier transform (Inverse Fast Fourier Transform, IFFT) block 415, a parallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425, and an up-converter (UC) 430. The receive path circuitry 450 includes a down-converter (DC) 455, a remove cyclic prefix block 460, a serial-to-parallel (S-to-P) block 465, an N-point fast fourier transform (Fast Fourier Transform, FFT) block 470, a parallel-to-serial (P-to-S) block 475, and a channel decoding and demodulation block 480.

At least some of the components in fig. 4a 400 and 4b 450 may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. In particular, note that the FFT blocks and IFFT blocks described in this disclosure may be implemented as configurable software algorithms, where the value of size N may be modified depending on the implementation.

Furthermore, while the present disclosure is directed to embodiments implementing a fast fourier transform and an inverse fast fourier transform, this is merely illustrative and should not be construed as limiting the scope of the present disclosure. It will be appreciated that in alternative embodiments of the present disclosure, the inverse fast fourier transform function and the inverse fast fourier transform function may be readily replaced by a discrete fourier transform (discrete Fourier transform, DFT) function and an inverse discrete fourier transform (inverse discrete Fourier transform, IDFT) function, respectively. It is understood that for DFT and IDFT functions, the value of the N variable may be any integer (i.e., 1, 4, 3, 4, etc.), while for FFT and IFFT functions, the value of the N variable may be any integer that is a power of 2 (i.e., 1, 2, 4, 8, 16, etc.).

In transmit path circuitry 400, a channel coding and modulation block 405 receives a set of information bits, applies a coding (e.g., LDPC coding) and modulates (e.g., quadrature phase shift keying (quadrature phase shift keying, QPSK) or quadrature amplitude modulation (quadrature amplitude modulation, QAM)) input bits to produce a sequence of frequency domain modulation symbols. Serial-to-parallel block 410 converts (i.e., demultiplexes) the serial modulation symbols into parallel data to produce N parallel symbol streams, where N is the IFFT/FFT size used in BS102 and UE 116. The N-point IFFT block 415 then performs an IFFT operation on the N parallel symbol streams to produce a time-domain output signal. Parallel-to-serial conversion block 420 converts (i.e., multiplexes) the parallel time-domain output symbols from N-point IFFT block 415 to produce a serial time-domain signal. The cyclic prefix block 425 is added and then the cyclic prefix is inserted into the time domain signal. Finally, up-converter 430 modulates (i.e., up-converts) the output of the add cyclic prefix block 425 to an RF frequency for transmission over a wireless channel. The signal may also be filtered at baseband before being converted to RF frequency.

The transmitted RF signals arrive at the UE 116 after passing through the wireless channel and perform the inverse operation of the operation at the gNB 102. Down converter 455 down converts the received signal to baseband frequency and remove cyclic prefix block 460 removes the cyclic prefix to produce a serial time domain baseband signal. Serial to parallel conversion module 465 converts the time domain baseband signal into a parallel time domain signal. The N-point FFT block 470 then performs an FFT algorithm to produce N parallel frequency domain signals. Parallel to serial conversion block 475 converts the parallel frequency domain signals into a sequence of modulated data symbols. The channel decoding and demodulation block 480 demodulates and then decodes the modulation symbols to recover the original input data stream.

Each of the gnbs 101-103 may implement a transmit path similar to transmitting to the user devices 111-116 in the downlink and may implement a receive path similar to receiving from the user devices 111-116 in the uplink. Similarly, each of user devices 111-116 may implement a transmit path corresponding to an architecture for transmitting in the uplink to gNBs 101-103 and may implement a receive path corresponding to an architecture for receiving in the downlink from gNBs 101-103.

The 5G communication system use case has been identified and described. These use cases can be roughly divided into three different groups. In one example, an enhanced mobile broadband (eMBB) is determined to meet high bit/second requirements and less stringent latency and reliability requirements. In another example, ultra-reliable low latency (URLL) is determined with less stringent bit/second requirements. In yet another example, determining the number of devices for large-scale machine type communication (mctc) may be per km ² Up to 100000 to 1 million, but reliability/throughput/latency requirements may be less stringent. Such a scenario may also involve power requirements, as battery consumption may be minimized as much as possible.

The communication system includes a Downlink (DL) that conveys signals from a transmission point, such as a Base Station (BS) or a NodeB, to a User Equipment (UE), and an Uplink (UL) that conveys signals from the UE to a reception point, such as a NodeB. The UE, also commonly referred to as a terminal or mobile station, may be fixed or mobile and may be a cellular telephone, a personal computer device or an automated device. An eNodeB, which is typically a fixed station, may also be referred to as an access point or other equivalent terminology. For LTE systems, the NodeB is commonly referred to as an eNodeB.

In a communication system such as an LTE system, DL signals may include data signals conveying information content, control signals conveying DL control information (DL control information, DCI), and Reference Signals (RSs), also referred to as pilot signals. The eNodeB transmits data information over a physical DL shared channel (physical DL shared channel, PDSCH). The eNodeB transmits DCI over a physical DL control channel (physical DL control channel, PDCCH) or Enhanced PDCCH (EPDCCH).

The eNodeB transmits acknowledgement information in a physical hybrid ARQ indicator channel (physical hybrid ARQ indicator channel, PHICH) in response to a data Transport Block (TB) transmission from the UE. The eNodeB transmits one or more of several types of RSs, including UE-Common RSs (CRS), channel state information RSs (channel state information RS, CSI-RS), or demodulation RSs (DMRS). The CRS is transmitted over the DL system Bandwidth (BW) and may be used by UEs to obtain channel estimates to demodulate data or control information or perform measurements. To reduce CRS overhead, the eNodeB may transmit CSI-RS in the time and/or frequency domain with less density than CRS. The DMRS may be transmitted only in BW of the corresponding PDSCH or EPDCCH, and the UE may use the DMRS to demodulate data or control information in the PDSCH or EPDCCH, respectively. The transmission time interval for the DL channel is referred to as a subframe and may have a duration of, for example, 1 millisecond.

The DL signal also includes the transmission of logical channels carrying system control information. Either the BCCH is mapped to a transport channel called broadcast channel (broadcast channel, BCH) when DL signaling a master information block (master information block, MIB) or to a DL shared channel (DL shared channel, DL-SCH) when DL signaling a system information block (System Information Block, SIB). Most of the system information is included in different SIBs transmitted using the DL-SCH. The presence of system information on the DL-SCH in a subframe may be indicated by transmission of a corresponding PDCCH transmitting a codeword with a cyclic redundancy check (cyclic redundancy check, CRC) scrambled with a system information RNTI (system information RNTI, SI-RNTI). Alternatively, the scheduling information for SIB transmission may be provided in an earlier SIB, and the scheduling information for the first SIB (SIB-1) may be provided by the MIB.

DL resource allocation is performed in units of subframes and physical resource block (physical resource block, PRB) groups. The transmission BW includes frequency resource units called Resource Blocks (RBs). Each RB includesA subcarrier or Resource Element (RE), such as 12 REs. A unit of one RB on one subframe is called a PRB. For PDSCH transmission BW, UEs may be allocated M _PDSCH RB, total->And RE.

The UL signals may include data signals conveying data information, control signals conveying UL control information (UL control information, UCI), and UL RSs. UL RS includes DMRS and Sounding RS (SRS). The UE transmits the DMRS only in BW of the corresponding PUSCH or PUCCH. The eNodeB may use the DMRS to demodulate the data signal or UCI signal. The UE transmits SRS to provide UL CSI to the eNodeB. The UE transmits data information or UCI through a corresponding physical UL shared channel (physical UL shared channel, PUSCH) or physical UL control channel (Physical UL control channel, PUCCH). If the UE needs to transmit data information and UCI in the same UL subframe, the UE may multiplex both in PUSCH. UCI includes hybrid automatic repeat request acknowledgement (Hybrid Automatic Repeat request acknowledgement, HARQ-ACK) information indicating correct (ACK) or incorrect (NACK) detection or absence of PDCCH Detection (DTX) for a data TB in PDSCH, scheduling request (scheduling request, SR) indicating whether the UE has data in a buffer of the UE, rank Indicator (RI), and channel state information (channel state information, CSI) enabling the eNodeB to perform link adaptation for PDSCH transmission to the UE. HARQ-ACK information is also sent by the UE in response to detecting PDCCH/EPDCCH indicating release of semi-persistently scheduled PDSCH

The UL subframe includes two slots. Each time slot includes a transmitter for transmittingData information, UCI, DMRS or SRSAnd a symbol. The frequency resource element of the UL system BW is an RB. For transmitting BW, the UE is assigned N _RB RB, total->And RE. For PUCCH, N _RB =1. The last subframe symbol may be used to multiplex SRS transmissions from one or more UEs. The number of subframe symbols available for data/UCI/DMRS transmission is +.>Wherein if the last subframe symbol is used for transmitting SRS, N _SRS =1, otherwise N _SRS ＝0。

Fig. 5 shows a transmitter block diagram 500 for PDSCH in a subframe according to an embodiment of the disclosure. The embodiment of the transmitter block diagram 500 shown in fig. 5 is for illustration only. One or more of the components shown in fig. 5 may be implemented in dedicated circuitry configured to perform the functions, or one or more of the components may be implemented by one or more processors that execute instructions to perform the functions. Fig. 5 does not limit the scope of the present disclosure to any particular implementation of transmitter block diagram 500.

As shown in fig. 5, information bits 510 are encoded by an encoder 520, such as a turbo encoder, and modulated by a modulator 530, e.g., using Quadrature Phase Shift Keying (QPSK) modulation. A serial-to-parallel (S/P) converter 540 generates M modulation symbols that are then provided to a mapper 550 to be mapped to REs selected by a transmit BW selection unit 555 for an assigned PDSCH transmit BW, unit 560 applies an Inverse Fast Fourier Transform (IFFT), and a parallel-to-serial (P/S) converter 570 serializes the output to create a time domain signal, filters 580, and transmits the signal at 590. Other functions such as data scrambling, cyclic prefix insertion, time windowing, interleaving, etc. are well known in the art and are not shown for the sake of brevity.

Fig. 6 shows a receiver block diagram 600 for PDSCH in a subframe according to an embodiment of the disclosure. The embodiment of diagram 600 shown in fig. 6 is for illustration only. One or more of the components shown in fig. 6 may be implemented in dedicated circuitry configured to perform the functions, or one or more of the components may be implemented by one or more processors that execute instructions to perform the functions. Fig. 6 does not limit the scope of the present disclosure to any particular embodiment of diagram 600.

As shown in fig. 6, filter 620 filters received signal 610, BW selector 635 selects REs 630 for assigned received BW, unit 640 applies a Fast Fourier Transform (FFT), and parallel-to-serial converter 650 serializes the output. Subsequently, demodulator 660 coherently demodulates the data symbols by applying channel estimates obtained from the DMRS or CRS (not shown), and decoder 670 (such as a turbo decoder) decodes the demodulated data to provide estimates of information data bits 680. For simplicity, additional functions such as time window, cyclic prefix removal, descrambling, channel estimation and deinterleaving are not shown.

Fig. 7 shows a transmitter block diagram 700 for PUSCH in a subframe, according to an embodiment of the disclosure. The embodiment of block diagram 700 shown in fig. 7 is for illustration only. One or more of the components shown in fig. 5 may be implemented in dedicated circuitry configured to perform the functions, or one or more of the components may be implemented by one or more processors that execute instructions to perform the functions. Fig. 7 does not limit the scope of the present disclosure to any particular implementation of block diagram 700.

As shown in fig. 7, information data bits 710 are encoded by an encoder 720 (such as a turbo encoder) and modulated by a modulator 730. A Discrete Fourier Transform (DFT) unit 740 applies DFT to the modulated data bits, a transmission BW selection unit 755 selects REs 750 corresponding to the assigned PUSCH transmission BW, a unit 760 applies IFFT, and after cyclic prefix insertion (not shown), a filter 770 applies filtering and transmits a signal at 780.

Fig. 8 shows a receiver block diagram 800 for PUSCH in a subframe according to an embodiment of the disclosure. The embodiment of block diagram 800 shown in fig. 8 is for illustration only. One or more of the components shown in fig. 8 may be implemented in dedicated circuitry configured to perform the functions, or one or more of the components may be implemented by one or more processors that execute instructions to perform the functions. Fig. 8 does not limit the scope of the present disclosure to any particular embodiment of block diagram 800.

As shown in fig. 8, a filter 820 filters the received signal 810. Subsequently, after removing the cyclic prefix (not shown), element 830 applies an FFT, the received BW selector 845 selects REs 840 corresponding to the assigned PUSCH received BW, element 850 applies an Inverse DFT (IDFT), demodulator 860 coherently demodulates the data symbols by applying channel estimates obtained from the DMRS (not shown), and decoder 870 (such as a turbo decoder) decodes the demodulated data to provide estimates of the information data bits 880.

In the next generation cellular system, various use cases beyond the capabilities of the LTE system are envisaged. Known as 5G or fifth generation cellular systems, systems capable of operating below 6GHz and above 6GHz (e.g., millimeter wave range) are one of the requirements. In 3GPP TR 22.891, 74 5G use cases have been identified and described; these use cases can be roughly divided into three different groups. The first group is called "enhanced mobile broadband (eMBB)", targeting high data rate services with less stringent latency and reliability requirements. The second group is called "ultra-reliable low latency (URLL)", targeting applications where data rate requirements are less stringent but time delay is less tolerant. The third group is called "large-scale MTC (mctc)", targeting a large number of low power device connections (such as per km) with less stringent reliability, data rate and latency requirements ² 100 ten thousand).

The 3GPP NR specifications support up to 32 CSI-RS antenna ports, which enables the gNB to be equipped with a large number of antenna elements (such as 64 or 128). In this case, multiple antenna elements are mapped onto one CSI-RS port. For next generation cellular systems such as 5G, the maximum CSI-RS port number may either remain unchanged or increase.

Fig. 9 illustrates an example antenna block or array 900 according to an embodiment of this disclosure. The embodiment of the antenna block or array 900 shown in fig. 9 is for illustration only. Fig. 9 is not intended to limit the scope of the present disclosure to any particular implementation of an antenna block or array 900.

For the millimeter wave band, while the number of antenna elements may be greater for a given form factor, the CSI-RS port number (corresponding to the number of digitally precoded ports) tends to be limited due to hardware constraints, such as the feasibility of installing a large number of ADCs/DACs at millimeter wave frequencies, as shown in fig. 9. In this case, one CSI-RS port is mapped onto a large number of antenna elements that can be controlled by a set of analog phase shifters 901. One CSI-RS port may correspond to one sub-array that produces a narrow analog beam by analog beamforming 905. The analog beam may be configured to sweep a wider angular range (920) by changing the phase shifter sets between symbols or subframes. Number of subarrays (equal to number of RF chains) and number of CSI-RS ports N _CSI-PORT The same applies. Digital beamforming unit 910 is at N _CSI-PORT Linear combining is performed on the analog beams to further increase the precoding gain. Although the analog beams are wideband (and thus not frequency selective), the digital precoding may vary between frequency subbands or resource blocks.

Since the above-described system utilizes multiple analog beams for transmission and reception (where one or a small number of analog beams are selected from a large number of analog beams, e.g., performed after a training duration-from time to time), the term "multi-beam operation" is used to refer to the overall system aspect. For illustration purposes, this includes: indicating an assigned DL or UL Transmit (TX) beam (also referred to as a "beam indication"), measuring at least one reference signal for calculating and performing beam reporting (also referred to as "beam measurement" and "beam reporting", respectively), and receiving DL or UL transmissions via selection of a corresponding Receive (RX) beam.

The above system is also applicable to higher frequency bands, such as > 52.6GHz (also known as FR 4). In this case, the system can only employ analog beams. Due to the O2 absorption loss around 60GHz frequency (about 10dB of additional loss at 100m distance), more and sharper analog beams (and hence more radiators in the array) will be required to compensate for the additional path loss.

In rel.15nr, multi-beam operation is designed mainly for single Transmit Receive Points (TRP) and single antenna panels. Thus, the specification supports beam indication for one TX beam, where the TX beam is associated with a reference RS. For DL beam indication and measurement, the reference RS may be NZP (non-zero power) CSI-RS and/or SSB (synchronization signal block including primary synchronization signal, secondary synchronization signal and PBCH). Here, DL beam indication is done via a transmission configuration indicator (transmission configuration indicator, TCI) field in DL-related DCI including an index to one (and only one) assigned reference RS. The set of hypothesized or so-called TCI states is configured via higher layer (RRC) signaling and a subset of these TCI states is selected/activated for the TCI field code points via the MAC CE when applicable. For UL beam indication and measurement, the reference RS may be NZP CSI-RS, SSB, and/or SRS. Here, UL beam indication is done via SRS resource indicator (SRS resource indicator, SRI) field in UL related DCI linked to one (and only one) reference RS. This association is configured via higher layer signaling using SpatialRelationInfo RRC parameters. Essentially, only one TX beam is indicated to the UE.

In one example related to rel.15/16NR, beam management is designed to share the same framework as CSI acquisition. However, this compromises the performance of beam management, especially for FR 2. This is because beam management operates mainly with analog beams (characteristics of FR 2), which are essentially different from CSI acquisition (designed in consideration of FR 1). Therefore, rel.15/16 beam management becomes cumbersome and is less likely to keep up with more aggressive examples (e.g., higher frequency bands, high mobility, and/or more narrower analog beams) that require a large number of beams and fast beam switching. Furthermore, rel.15/16 is designed to accommodate many unknown or preliminary capabilities (e.g., UEs that do not support beam correspondence). For flexibility, a number of options are available. This becomes burdensome for L1 control signaling, and thus multiple reconfigurations are performed via RRC signaling (higher layer configuration). While this avoids L1 control overhead, it either results in high latency (if reconfiguration is performed sparsely) or results in high PDSCH usage (because RRC signaling consumes PDSCH resources).

In one example related to rel.15/16NR, UL beam selection may be performed via measurement of DL RSs (CSI-RSs and/or SSBs) and CRI reports accompanied by corresponding beam metrics (e.g., RSRP, SINR) when utilizing beam correspondences. That is, based on CRI/RSRP or CRI/SINR reports from the UE, the Network (NW) may assume that the UE performs UL transmission on PUSCH using UL TX beams associated with one of the most recent CRI reports (especially the report with the highest RSRP or SINR). Also, the UE may assume that the NW knows this UE selection. Thus, no separate UL beam indication is required (e.g., via the SRI field or UL-TCI field in the corresponding UL grant).

In rel.15/16NR, UL beam selection may be performed by the NW selecting and indicating UL TX beams to the UE via UL grants (signaled via SRI field or UL-TCI field—essentially indicating UL TCI status associated with UL TX beams) when beam correspondence is not utilized. This selection is achieved by measuring SRS transmitted from the UE (configured by NW).

In either case, when an event occurs that causes the UE to have to select a different (alternative) UL TX beam than the NW expects, some additional mechanism is needed to ensure that (a) the UE has an alternative UL TX beam available and the next UL TX beam indication can only be in a later time slot when the UE detects such an event, and (b) the NW knows the UE decision. Several examples of such events are as follows.

● In one example, such an event may occur due to a so-called maximum allowed exposure (Maximum Permissible Exposure, MPE) specification (especially in north america) that limits the UE transmit power in certain directions. That is, to prevent any excessive electromagnetic wave exposure on delicate soft tissues (e.g., brain tissue), the UE will avoid sending high energy signals in some directions (e.g., toward the head). Unfortunately, such a direction may correspond to the "best" UL TX beam (e.g., associated with the CRI with the highest reported RSRP/SINR or associated with the SRS resource that produces the best measured SINR at NW). Some loss of UL throughput (especially coverage) will occur when the "best" UL TX beam is not used for UL transmission.

● In another example, such an event may occur due to Hardware (HW) limitations at a UE equipped with multiple antenna panels, and in response to the event, the UE needs to select/switch the antenna panels for UL transmission.

● In yet another example, such an event may occur due to a potential beam failure, and to avoid the beam failure, the UE needs to select/switch the antenna panel for UL transmission.

● In yet another example, such an event may occur due to a sudden change in channel conditions (e.g., due to high speed, antenna/panel blocking, etc.) that may cause a beam failure, and the UE needs to switch/change the TX beam in order to continue UL transmission without interruption/failure or having to wait for the next UL TX beam update/indication.

Therefore, there is a need for an efficient design to achieve UL TX beam selection in order to avoid power outages (or beam failures), UL throughput loss, UL coverage loss, and HW related problems that may occur due to the events described above. In this disclosure, several example embodiments are presented for such a design.

The present disclosure encompasses several components that may be used in combination or combination with one another or that may operate as a stand-alone solution.

In this disclosure, the term "activate" describes an operation in which a UE receives and decodes a signal from a network (or gNB) indicating a time start point. The starting point may be the exact position of the current or future slot/subframe or symbol, either implicitly or explicitly indicated, or of a fixed or higher layer configuration. After successfully decoding the signal, the UE responds accordingly. The term "deactivation" describes an operation in which the UE receives a signal from the network (or gNB) indicating a time stop point and decodes it. The stopping point may be the exact position of the current or future slot/subframe or symbol, either implicitly or explicitly indicated, or of a fixed or higher layer configuration. After successfully decoding the signal, the UE responds accordingly.

Terms such as TCI, TCI status, spatialreactioninfo, target RS, reference RS, etc. are used for illustration purposes and are therefore not normative. Other terms referring to the same function may also be used.

The "reference RS" corresponds to a set of characteristics (such as direction, precoding/beamforming, number of ports, etc.) of the DL or UL TX beams. For example, when the UE receives the reference RS index/ID in the assigned DL represented by the TCI state, the UE applies the known characteristics of the reference RS to the assigned DL transmission. The UE may receive and measure a reference RS (in this case, the reference RS is a downlink signal such as NZP CSI-RS and/or SSB), where the result of the measurement is used to calculate a beam report (in rel.15nr, at least one L1-RSRP is accompanied by at least one CRI). When the NW/gNB receives the beam report, the NW may be better equipped with information to assign a specific DL TX beam to the UE. Alternatively, the reference RS may be transmitted by the UE (in this case, the reference RS is an uplink signal such as SRS). When the NW/gNB receives the reference RS, the NW/gNB may measure and calculate information required to assign a specific DL TX beam to the UE. This option applies when the DL-UL beam pair (beam pair) correspondence is established.

The reference RS may be dynamically triggered by the NW/gNB (e.g., via DCI in the case of aperiodic RS), preconfigured with a specific time domain behavior (such as period and offset in the case of periodic RS) or a combination of such preconfiguration and activation/deactivation (in the case of semi-persistent RS).

Two types of Frequency Ranges (FR) are defined in the 3GPP NR specifications. The range below 6GHz is referred to as frequency range 1 (FR 1), and the millimeter wave range is referred to as frequency range 2 (FR 2). Examples of the frequency ranges of FR1 and FR2 are shown below.

Frequency range name	Corresponding frequency range
		FR1	450MHz–6000MHz
FR2	24250MHz–52600MHz

The following embodiments are examples of DL multi-beam operation with DL beam indication after the Network (NW) receives some transmissions from the UE. In a first example embodiment, aperiodic CSI-RS are transmitted by NW and measured by UE. Although aperiodic RSs are used in both examples, periodic or semi-persistent RSs may also be used.

For millimeter wave (or FR 2) or higher frequency bands where multi-beam operation is particularly relevant (such as > 52.6GHz or FR 4), the transmit-receive process includes the receiver selecting a Receive (RX) beam for a given TX beam. For UL multi-beam operation, the gNB selects a UL RX beam for each UL TX beam (corresponding to the reference RS). Thus, when UL RS (such as SRS and/or DMRS) is used as a reference RS, NW/gNB triggers or configures the UE to transmit UL RS (associated with selection of UL TX beam). The gNB selects an UL RX beam after receiving and measuring the UL RS. As a result, the TX-RX beam pair is derived. The NW/gNB may perform this operation on all configured reference RSs (either each reference RS performs the operation or performs a "beam sweep") and determine all TX-RX beam pairs associated with all reference RSs configured to the UE. On the other hand, when DL RS (such as CSI-RS and/or SSB) is used as reference RS (related to when DL-UL beam correspondence or reciprocity holds), NW/gNB transmits the RS to UE (for UL and in terms of reciprocity, this corresponds to UL RX beam). In response, the UE measures the reference RS (and selects the UL TX beam in the process) and reports the beam metric associated with the quality of the reference RS. In this case, the UE determines a TX-RX beam pair for each configured (DL) reference RS. Thus, although NW/gNB cannot obtain this knowledge, the UE, upon receiving the reference RS (and thus UL RX beam) indication from NW/gNB, may select the UL TX beam from the knowledge about all TX-RX beam pairs.

In the present disclosure, the term "resource indicator" (also abbreviated REI) is used to refer to an indicator of RS resources for signal/channel and/or interference measurements. This term is used for illustration purposes and may be replaced with any other term referring to the same function. Examples of REIs include the aforementioned CSI-RS resource indicators (CSI-RS resource indicator, CRI) and SSB resource indicators (SSB resource indicator, SSB-RI). Any other RS may also be used for signal/channel and/or interference measurements, such as DMRS.

Fig. 10 illustrates an uplink multi-beam operation 1000 according to an embodiment of the disclosure. The embodiment of the uplink multi-beam operation 1000 shown in fig. 10 is for illustration only. Fig. 10 does not limit the scope of the present disclosure to any particular embodiment of uplink multi-beam operation 1000.

As shown in fig. 10, UL multi-beam operation 1000 begins with the gNB/NW signaling an aperiodic CSI-RS (AP-CSI-RS) trigger or indication to the UE (step 1001). The trigger or indication may be included in the DCI (either UL related or DL related; either signaled separately or signaled jointly with aperiodic CSI request/trigger) and indicates transmission of the AP-CSI-RS in the same time slot/subframe (zero time offset) or in a later time slot/subframe (> 0 time offset). After receiving the AP-CSI-RS sent by the gNB/NW (step 1002), the UE measures the AP-CSI-RS and in turn calculates and reports a "beam metric" (indicating the quality of the particular TX beam hypothesis) (step 1003). Examples of such beam reports are CSI-RS resource indicators (CRI) or SSB resource indicators (SSB-RI) and their associated L1-RSRP/L1-RSRQ/L1-SINR/CQI. Upon receiving the beam report from the UE, the NW may use the beam report to select an UL TX beam for the UE and use the SRI field in the UL related DCI (carrying a UL grant, such as DCI format 0_1 in NR) to indicate UL TX beam selection (step 1004). The SRI corresponds to a "target" SRS resource linked to a reference RS (in this case, an AP-CSI-RS) via a SpatialReconstate info configuration. After successfully decoding the UL-related DCI with the SRI, the UE performs UL transmission (such as data transmission on PUSCH) using the UL TX beam associated with the SRI (step 1005).

Fig. 11 illustrates uplink multi-beam operation 1100 according to an embodiment of the disclosure. The embodiment of uplink multi-beam operation 1100 shown in fig. 11 is for illustration only. Fig. 11 does not limit the scope of the present disclosure to any particular embodiment of uplink multi-beam operation 1100.

As shown in fig. 11, UL multi-beam operation 1100 begins with the gNB/NW signaling an aperiodic SRS (AP-SRS) trigger or request to the UE (step 1101). The trigger may be included in the DCI (either UL related or DL related). After receiving and decoding the AP-SRS trigger (step 1102), the UE transmits the AP-SRS to the gNB/NW (step 1103) so that the NW (or gNB) can measure the UL propagation channel and select the UL TX beam for the UE. The gNB/NW may then indicate UL TX beam selection using an SRI field in the UL related DCI (carrying a UL grant, such as DCI format 0_1 in NR) (step 1104). The SRI corresponds to a "target" SRS resource linked to a reference RS (in this case, an AP-SRS) via a SpatialReconstate info configuration. After successfully decoding the UL-related DCI with the SRI, the UE performs UL transmission (such as data transmission on PUSCH) using the UL TX beam associated with the SRI (step 1105).

Fig. 12 illustrates a downlink multi-beam operation 1200 according to an embodiment of the disclosure. The embodiment of the downlink multi-beam operation 1200 shown in fig. 12 is for illustration only. Fig. 12 does not limit the scope of the present disclosure to any particular implementation of the downlink multi-beam operation 1200.

As shown in fig. 12, where the UE is configured to measure/receive aperiodic CSI-RS (AP-CSI-RS) and report aperiodic CSI (AP-CSI), DL multi-beam operation 1200 begins with the gNB/NW signaling an aperiodic CSI-RS (AP-CSI-RS) trigger or indication to the UE (step 1201). The trigger or indication may be included in the DCI (either UL related or DL related; either signaled separately or signaled jointly with aperiodic CSI request/trigger) and indicates transmission of the AP-CSI-RS in the same time slot/subframe (zero time offset) or in a later time slot/subframe (> 0 time offset). After receiving the AP-CSI-RS transmitted by the gNB/NW (step 1202), the UE measures the AP-CSI-RS and in turn calculates and reports a "beam metric" (included in the CSI, indicating the quality of the particular TX beam hypothesis) (step 1203). Examples of such beam reports (supported in rel.15/16 NR) are CSI-RS resource indicator (CRI) or SSB resource indicator (SSB-RI) and their associated L1-RSRP and/or L1-SINR. Upon receiving the beam report from the UE, the NW/gNB may use the beam report to select a DL TX beam for the UE and use the TCI field in the DL-related DCI (carrying a DL assignment, such as DCI format 1_1 in NR) to indicate DL TX beam selection (step 1204). The TCI state corresponds to a reference RS (in this case an AP-CSI-RS) defined/configured via a TCI state definition (higher layer/RRC configured, with a subset of them activated via MAC CEs for DCI-based selection). After successfully decoding the DL-related DCI with the TCI field, the UE performs DL reception (e.g., data transmission on PDSCH) using the DL TX beam associated with the TCI field (step 1205). In this example embodiment, only one DL TX beam is indicated to the UE.

The SRI used in the embodiments shown in fig. 10 and 11 may also be replaced with UL-TCI, wherein UL-TCI fields may be introduced in the relevant UL-related DCI(s), either replacing the SRI field in rel.15/16 or supplementing the SRI field in rel.15/16.

The aperiodic CSI-RS (and associated aperiodic reports) in the embodiment shown in fig. 10 and the aperiodic SRS in the embodiment shown in fig. 11 can be replaced with another time domain behavior, such as semi-persistent (SP) or periodic (P).

In any embodiment or sub-embodiment or example below, the flow diagrams are for illustration purposes. Any possible variations of the flow diagrams are covered by the present disclosure as long as at least some of the components therein are included. Such components include UL TX beam indications indicating a plurality of UL TX beams and event-related UL TX beam switching starting from the indicated plurality of UL TX beams.

In the remainder of this disclosure, the term "beam" may be associated with spatial transmission/reception of Resource Signals (RSs) from "ports", "antenna ports" or "virtual antennas/ports". Also, the term "Transmit (TX) beam" may be associated with a spatial transmission of a Resource Signal (RS) or channel from a "port", "antenna port", or "virtual antenna/port"; and the term "Receive (RX) beam" may be associated with spatial reception of a Resource Signal (RS) or channel from a "port", "antenna port", or "virtual antenna/port". Spatial transmission/reception of beams may be performed in three-dimensional (3D) space. In a beamformed wireless system, transmission and reception of wireless signals may occur via multiple TX beams and multiple RX beams.

In NR, UL transmission is configured to be codebook-based or non-codebook-based via higher layer parameter txConfig set to "codebook" or "non-codebook" in PUSCH-Config.

According to REF9 section 6.1.1.1, for codebook-based UL transmissions, the following is supported.

For codebook-based transmissions, the UE is TPMI-based and determines its codebook subset after receiving the higher layer parameters ul codebook subset or codebook subset in PUSCH-Config, which may be configured as "fullan partialanon component" or "noccomponent" depending on the UE capability. The maximum transmission rank may be configured by the higher parameter ULmaxRank or maxRank in PUSCH-Config.

A UE reporting the UE capability of its "partialanandnetwork" transmission will not expect to be configured by a ulccodebook subset with "fullnendendnetwork".

A UE that reports the UE capability of its "Non-Coherent" transmission will not be expected to be configured by a ul codebook subset with "fullnendeparatiandnoncoherent" or "partialanadnoncoherent".

When two antenna ports are configured, the UE will not expect to be configured with a higher layer parameter ulcodebook subset set to "partialanddnoncoupler".

In this disclosure, "fullnendendin coherence", "partialhenconncoherence" and "Non-coherence" are referred to as three examples of coherence types/capabilities, where the term "coherence" means a subset of antenna ports at a UE that can be used to coherently transmit a layer or include an antenna panel.

Fig. 13 illustrates an example antenna panel 1300 according to an embodiment of this disclosure. The embodiment of antenna panel 1300 shown in fig. 13 is for illustration only. Fig. 13 is not intended to limit the scope of the present disclosure to any particular embodiment of antenna panel 1300.

Fig. 14 illustrates other example antenna panels 1400 according to embodiments of the disclosure. The embodiment of the antenna panel 1400 shown in fig. 14 is for illustration only. Fig. 14 is not intended to limit the scope of the present disclosure to any particular embodiment of an antenna panel 1400.

The term "antenna panel" refers to a set of antenna ports or a set of antenna elements or a subset of antenna ports associated with a resource (e.g., SRS resource, CSI-RS resource, SSB block). In fig. 13 two examples are shown, the first example (left side) having a single panel comprising dual polarized (i.e. two) antennas/ports, the second example having four panels each comprising a single antenna/port (pointing in four different directions). Another example is shown in fig. 14, where there are four antenna panels (on opposite sides) each comprising four dual polarized antennas/ports.

In one embodiment, the UE reports the UE capability value(s) including information based on the coherence type of its antenna port (e.g., SRS antenna port or PUSCH antenna port) via its capability to report a list of UE capability value(s). In one example, the coherence type is one of "fullnendentdnoneagent" (FC), "partialdnoneagent" (PC), and "nonpixel" (NC) (see 6.1.1.1 of TS 38.214).

As shown in fig. 14, the UE is configured to measure (receive) P ₁ DL measurement RS resources (such as CSI-RS or SSB), where P ₁ And is more than or equal to 1. The configuration may be sent by the NW/gNB via higher layer (RRC) signaling (received by the UE). Alternatively, the NW/gNB may dynamically signal/update the DL measurement RS resource set (subset) via L1 or L2 DL control (PDCCH or MAC CE). These resources are used by the UE and/or NW/gNB to follow different beam or spatial directions (represented by beam forming/precoding operations) and possibly use different antenna facets at the UEThe board performs beam measurements. The time domain behavior of DL measurement RS resources may be configured as Aperiodic (AP), semi-persistent (SP), or periodic (P). In one example, P ₁ Each of the DL measurement RS resources is a port resource. In one example, P ₁ Each of the DL measurement RS resources is one or two port resources. In one example, the DL measurement RS resources include path-loss (PL) RS resources. In one example, the DL measurement RS resources include (NZP) CSI-RS resources. In one example, DL measurement RS resources include both PL RS resources and (NZP) CSI-RS resources. In one example, the DL measurement RS resources include SSB resources.

The UE is also configured to determine a beam report using the measurements (based on the received DL measurement RS resources) and report the beam report via an UL channel (e.g., PUCCH or PUSCH), as configured by the higher layer parameters CSI-ReportConfig. Wherein PUSCH may be one of dynamic grant PUSCH, type 1 configuration grant PUSCH, type 2 configuration grant PUSCH, msgA PUSCH associated with a type 2 random access procedure, or Msg3 PUSCH associated with a type 1 random access procedure.

The beam report includes N.gtoreq.1 pairs (R, I), where R is a resource indicator and I is an index corresponding to the reported R. In one example, R is SSBRI indicating an SSB index, or CRI indicating a CSI-RS resource index. In one example, the beam report further includes a beam metric corresponding to (or associated with) each reported resource indicator R. In one example, each beam metric is L1-RSRP (as in Rel.15). In one example, each beam metric is an L1-SINR (as in Rel.16). In one example, each beam metric is L1-RSRP or L1-SINR based on a configuration that may be subject to UE capabilities reported by the UE. When N >1, the beam metrics are reported in a differential manner (as in rel.15/16), with 7 bits for the first (absolute) beam metric and 4 bits for each of the remaining N-1 (differential) beam metrics relative to the first beam metric, the details of such differential reporting are as described in the rel.15/16NR specifications.

In one example, index I indicates a correspondence between CSI-RS and/or SSB resource indexes (indicated via R) and UE capability values from a list of UE capability values (or set of values) reported by the UE (via UE capability signaling). In one example, index I is an index of UE capability values from a list of UE capability values (or set of values). Details of the list of UE capability values (or set of values) will be described later in this disclosure. The UE will not update or expect to maintain the correspondence between (two consecutive) beam reporting instances (in time).

In one example, beam reporting is configured via reportquality in CSI-ReportConfig set to an existing (rel.15/16) value (i.e., "cri-RSRP" or "ssb-Index-RSRP" or "cri-SINR" or "ssb-Index-SINR").

In one example, beam reporting is configured via reportquality in CSI-ReportConfig set to a new value (i.e., "cri-RSRP-r17" or "ssb-Index-RSRP-r17" or "cri-SINR-r17" or "ssb-Index-SINR-r 17"), where the term "cri" or "ssb-Index" corresponds to a resource indicator, the term "RSRP" or "SINR" corresponds to a beam metric, and the term "r17" corresponds to Index I. In one example of this, in one implementation,

● In one example, the term "r17" is replaced with "CapabilityIndex", i.e., the new value is "cri-RSRP-CapabilityIndex", "ssb-Index-RSRP-CapabilityIndex", "cri-SINR-CapabilityIndex", or "ssb-Index-SINR-CapabilityIndex".

● In one example, the term "r17" is replaced with "SetIndex", i.e., the new value is "cri-RSRP-SetIndex", "ssb-Index-RSRP-SetIndex", "cri-SINR-SetIndex", or "ssb-Index-SINR-SetIndex".

● In one example, the term "r17" is replaced with "ValueIndex", i.e., the new values are "cri-RSRP-ValueIndex", "ssb-Index-RSRP-ValueIndex", "cri-SINR-ValueIndex", "ssb-Index-SINR-ValueIndex".

● In one example, the term "r17" is replaced with "ValueSetIndex", i.e., the new value is "cri-RSRP-ValueSetIndex", "ssb-Index-RSRP-ValueSetIndex", "cri-SINR-ValueSetIndex", "ssb-Index-SINR-ValueSetIndex".

● In one example, the term "r17" is replaced with "capabilyvaluesetindex", i.e., the new value is "cri-RSRP-capabilyvaluesetindex", "ssb-Index-RSRP-capabilyvaluesetindex", "cri-SINR-capabilyvaluesetindex", "ssb-Index-SINR-capabilyvaluesetindex".

● In one example, the term "r17" is replaced with "capabilyvalueindex", i.e., the new value is "cri-RSRP-capabilyvalueindex", "ssb-Index-RSRP-capabilyvalueindex", "cri-SINR-capabilyvalueindex", "ssb-Index-SINR-capabilyvalueindex".

● In one example, the term "r17" is replaced with "capabiltysetindex", i.e., the new value is "cri-RSRP-capabiltysetindex", "ssb-Index-RSRP-CapabilitySet Index", "cri-SINR-capabiltysetindex", "ssb-Index-SINR-Capability SetIndex".

The index I (or correspondence) is determined/configured according to at least one of the following examples.

In one example, index I indicates information about the coherence type. For example, index I indicates one of:

● Full Coherence (FC) indicates all SRS ports. In one example, this corresponds to the case where 1 antenna panel includes all SRS ports. In one example, this corresponds to the case where all SRS ports are selected (or turned on).

● Partial Coherence (PC) indicates a pair of SRS ports or a subset of 2 SRS ports. In one example, this corresponds to the case where 1 antenna panel is selected (from a plurality of panels each including a subset of SRS ports). In one example, this corresponds to the case where a subset of ports (e.g., 2 SRS ports) is selected (or turned on) from > 2 (e.g., 4) SRS antenna ports.

● Incoherence (NC) indicates 1 SRS port. In one example, this corresponds to the case where 1 antenna panel is selected (from among a plurality of panels each including 1 SRS port). In one example, this corresponds to the case where 1 SRS port is selected (or turned on) from > 1 (e.g., 2 or 4) SRS antenna ports.

In one example, for SRS resources with 4 SRS ports, index I indicates one of the following.

● X1: FC (for 1 panel with 4 ports, or select 4 SRS ports)

● X2: PC (for 2 panels each with 2 ports, or select 2 SRS ports)

● X3: NC (for 4 panels each with 1 port, or select 1 SRS port)

In one example, the index I depends on the type of coherence reported by the UE.

● For UEs supporting NC and 4 ports, I is fixed to X3 and therefore may not be reported.

● For a UE supporting PC and 4 ports, I may be X2 or X3 and thus may be reported (e.g., via a 1-bit report).

● For UEs supporting FC and 4 ports, I may be X1 or X2 or X3 and thus may be reported (e.g., via a 2-bit report).

In one example, the index I is not dependent on the type of coherence reported by the UE.

● For a UE supporting 4 ports, I may be X1 or X2 or X3 and thus may be reported (e.g., via a 2-bit report).

● X1: FC (for 1 panel with 4 ports, or select 4 SRS ports)

● X2: PC (for 2 panels each with 2 ports, or select 2 SRS ports)

● X3: NC (for 4 panels each with 1 port, or select 1 SRS port)

● X4: PC+NC (for 3 panels, 1 panel with 2 ports or 2 SRS ports selected, 2 panels with 1 port or 1 SRS port each)

● For a UE supporting PC and 4 ports, I may be X2 or X3 and thus may be reported (e.g., via a 1-bit report). Or for a UE supporting PC and 4 ports, I may be X2 or X3 or X4 and thus may be reported (e.g., via a 2-bit report).

● For UEs supporting FC and 4 ports, I may be X1 or X2 or X3 or X4 and thus may be reported (e.g., via a 2-bit report).

● For a UE supporting 4 ports, I may be X1 or X2 or X3 or X4 and thus may be reported (e.g., via a 2-bit report).

In one example, for SRS resources with 2 SRS ports, index I indicates one of the following.

● Y1: FC (for 1 panel with 2 ports, or select 2 SRS ports)

● Y3: NC (for 2 panels each with 1 port, or select 1 SRS port)

● For UEs supporting NC and 2 ports, I is fixed to Y3 and therefore may not be reported.

● For UEs supporting FC and 2 ports, I may be Y1 or Y3 and thus may be reported (e.g., via a 1-bit report).

● For a UE supporting 2 ports, I may be Y1 or Y3 and thus may be reported (e.g., via a 1-bit report).

In one example, NW configures a set of allowed values for index I, or NW configures an association between index I and a coherence type or SRS antenna port selection. The configuration may be subject to UE capabilities reported by the UE, which may be, for example, a list of supported UE capability values (or set of values), including a coherence type and/or SRS antenna port selection for reporting index I. The UE determines the index I based on the NW configuration and if the number of supported coherence types or SRS antenna port selections for reporting the index I is 1, 2, 3 or 4, respectively, the bit width of the index I report is 0, 1, 2 or 2 bits.

In one example, index I indicates information about the coherence type. The details are the same as in one or more of the examples described above, except that index I is allowed to take a value indicating the selection of 3 SRS ports for 4 SRS ports.

For SRS resources with 4 SRS ports, index I indicates one of the following.

● X1: FC (for 1 panel with 4 ports, or select 4 SRS ports)

● X2: PC (for 2 panels each with 2 ports, or select 2 SRS ports)

● X3: NC (for 4 panels each with 1 port, or select 1 SRS port)

● X4: PC_3ports (for 1 panel each with 3 ports, or select 3 SRS ports)

● For a UE supporting pc_3port and 4 ports, I may be X2 or X3 or X4 and thus may be reported (e.g., via a 2-bit report).

For SRS resources with 4 SRS ports, index I indicates one of the following.

● X1: FC (for 1 panel with 4 ports, or select 4 SRS ports)

● X2: PC (for 2 panels each with 2 ports, or select 2 SRS ports)

● X3: NC (for 4 panels each with 1 port, or select 1 SRS port)

● X4: PC_3ports (for 1 panel each with 3 ports, or select 3 SRS ports)

● X5: PC+NC (for 3 panels, 1 panel with 2 ports or 2 SRS ports selected, 2 panels with 1 port or 1 SRS port each)

● X6: PC_3port+NC (for 2 panels, 1 panel with 3 ports or 3 SRS ports selected, 1 panel with 1 port or 1 SRS port selected)

● For a UE supporting PC and 4 ports, I may be X2 or X3 or X5 and thus may be reported (e.g., via a 2-bit report).

● For UEs supporting FC and 4 ports, I may be X1 or X2 or X3 or X4 or X5 or X6 and thus may be reported (e.g., via a 3-bit report).

● For a UE supporting pc_3port and 4 ports, I may be X2 or X3 or X4 or X5 or X6 and thus may be reported (e.g., via a 3-bit report).

● For a UE supporting 4 ports, I may be X1 or X2 or X3 or X4 or X5 or X6 and thus may be reported (e.g., via a 3-bit report).

In one example, index I indicates information about the coherence type and SRS antenna port(s). For example, index I indicates one of:

● Partial Coherence (PC) indicates a pair of SRS ports or a subset of 2 SRS ports. In one example, this corresponds to the case where 1 antenna panel is selected (from a plurality of panels each including a subset of SRS ports). In one example, this corresponds to the case where a subset of SRS ports (e.g., 2 SRS ports) is selected (or turned on) from > 2 (e.g., 4) SRS antenna ports. For 4 SRS antenna ports, since there are two SRS antenna port pairs, the index also indicates one of these two pairs

PC_PortPair1 indicates the first SRS port pair (a, b)

PC_PortPair2 indicates the second SRS port pair (c, d)

● Incoherence (NC) indicates 1 SRS port. In one example, this corresponds to the case where 1 antenna panel is selected (from among a plurality of panels each including 1 SRS port). In one example, this corresponds to the case where 1 SRS port is selected (or turned on) from > 1 (e.g., 2 or 4) SRS antenna ports. For 2 SRS antenna ports, the index also indicates one of the two ports

The O NC_Port1 indicates the first SRS Port a

The O NC_Port2 indicates a second SRS Port b

Also, for the 4 SRS antenna ports, the index also indicates one of the four ports

The O NC_Port1 indicates the first SRS Port a

The O NC_Port2 indicates the first SRS Port b

The o nc_port3 indicates the first SRS Port c

The O NC_Port4 indicates the first SRS Port d

● X1: FC (for 1 panel with 4 ports, or select 4 SRS ports)

● X2: PC_PortPair1 (first of two panels each with 2 ports, or select 2 SRS ports)

● X3: PC_PortPair2 (the second of two panels each having 2 ports, or 2 SRS ports selected)

● X4: NC_Port1 (first of 4 panels each with 1 Port, or select 1 SRS Port)

● X5: NC_Port2 (second of 4 panels each with 1 Port, or select 1 SRS Port)

● X6: NC_Port3 (the third of 4 panels each with 1 Port, or 1 SRS Port selected)

● X7: NC_Port4 (the fourth of 4 panels each with 1 Port, or 1 SRS Port selected)

● For UEs supporting NC and 4 ports, I may be one of X4, … …, X7 and thus may be reported (e.g., via a 2-bit report).

● For a UE supporting a PC and 4 ports,

o I may be one of X2, … …, X7 and thus may be reported (e.g., via a 3-bit report).

Alternatively, I may be one of X2 and X3 and thus may be reported (e.g., via a 1-bit report).

● For a UE supporting FC and 4 ports,

o I may be one of X1, … …, X7 and thus may be reported (e.g., via a 3-bit report).

Alternatively, I may be one of X1, … …, X3 and thus may be reported (e.g., via a 2-bit report).

● For a UE supporting 4 ports, I may be one of X1, … …, X7 and thus may be reported (e.g., via a 3-bit report).

● X1 to X7 in one or more examples as described above

● X8: pc+nc_portpair 1=pc_portpair 1 (first of 3 panels, 1 panel with 2 ports or 2 SRS ports selected, 2 panels each with 1 port or 1 SRS port selected)

● X9: pc+nc_port3=nc_port3 (second of 3 panels, 1 panel with 2 ports or 2 SRS ports selected, 2 panels with 1 Port or 1 SRS Port each)

● X10: pc+nc_port4=nc_port4 (the third of 3 panels, 1 panel with 2 ports or 2 SRS ports selected, 2 panels with 1 Port or 1 SRS Port each)

● For a UE supporting a PC and 4 ports,

Alternatively, I may be one of X2 and X3, and thus may be reported (e.g., via a 1-bit report)

Alternatively, I may be one of X2, … …, X10 and thus may be reported (e.g., via a 4-bit report)

● For a UE supporting FC and 4 ports,

Alternatively, I may be one of X1, … …, X10 and thus may be reported (e.g., via a 4-bit report).

● For a UE supporting 4 ports, I may be one of X1, … …, X10 and thus may be reported (e.g., via a 4-bit report).

● Y1: FC (for 1 panel with 2 ports, or select 2 SRS ports)

● Y3: NC_Port1 (first of 2 panels each with 1 Port, or select 1 SRS Port)

● Y4: NC_Port2 (second of 2 panels each with 1 Port, or select 1 SRS Port)

● For UEs supporting NC and 2 ports, I is one of Y3 and Y4 and thus can be reported (e.g., via a 1-bit report).

● For UEs supporting FC and 2 ports, I may be Y1 or Y3 or Y4 and thus may be reported (e.g., via a 2-bit report).

● For a UE supporting 2 ports, I may be Y1 or Y3 or Y4 and thus may be reported (e.g., via a 2-bit report).

In one example, NW configures a set of allowed values for index I, or NW configures an association between index I and a coherence type or SRS antenna port selection. The configuration may be subject to UE capabilities reported by the UE, which may be, for example, a list of supported UE capability values (or set of values), including a coherence type and/or SRS antenna port selection for reporting index I. The UE determines the index I based on the NW configuration and the bit width of the index I report is 0, 1, 2 or 3 bits if the number of supported coherence types or SRS antenna port selections for reporting the index I is between 1, 2-3, 4-7 or ≡8, respectively.

In one example, index I indicates information about the coherence type and SRS antenna port(s). The details are the same as in one or more of the examples described above, except that index I is allowed to take a value indicating the selection of 3 SRS ports for 4 SRS ports.

For SRS resources with 4 SRS ports, index I indicates one of the following.

● X1: complete coherence (FC): as in one or more of the examples above

● Partial Coherence (PC):

o X2: pc_portpair1; x3: pc_portpair2, as in one or more of the examples above

● Incoherence (NC): for 2 SRS antenna ports, the index also indicates one of the two ports

Nc_port1, nc_port2, as in one or more of the examples above, for 4 SRS antenna ports, the index also indicates one of the four ports

O X4: NC_Port1; x5: NC_Port2; x6: NC_Port3; x7: NC_Port4, as in one or more of the examples described above

● Pc+nc (for 2 panels, one with 3 ports or 3 SRS ports selected, the other with 1 port): for 4 SRS antenna ports, the index indicates one of the following two ports

O X8: pc_port123 indicates three SRS ports (a, b, c)

O X9: nc_port4 indicates a fourth SRS Port d

● For a UE supporting a PC and 4 ports,

● For a UE supporting FC and 4 ports,

Alternatively, I may be one of X1, … …, X9 and thus may be reported (e.g., via a 3-bit report).

● For a UE supporting PC + NC and 4 ports,

o I may be X8 or X9 and thus may be reported (e.g., via a 1-bit report).

Alternatively, I may be one of X2, … …, X9 and thus may be reported (e.g., via a 3-bit report).

Alternatively, I may be one of X2, X3, X8, and X9, and thus may be reported (e.g., via a 2-bit report).

● For a UE supporting 4 ports, I may be one of X1, … …, X9 and thus may be reported (e.g., via a 4-bit report).

For SRS resources with 4 SRS ports, index I indicates one of the following.

● X1-X7, as in one or more of the examples above

● X8-X10, as in one or more of the examples above

O X11: pc_port123 indicates three SRS ports (a, b, c)

O X12: nc_port4 indicates a fourth SRS Port d

● For a UE supporting a PC and 4 ports,

Alternatively, I may be one of X2, … …, X12 and thus may be reported (e.g., via a 4-bit report).

● For a UE supporting FC and 4 ports,

Alternatively, I may be one of X1, … …, X12 and thus may be reported (e.g., via a 4-bit report).

● For a UE supporting PC + NC and 4 ports,

o I may be one of X8, … …, X10 and thus may be reported (e.g., via a 2-bit report).

Alternatively, I may be X11 or X12 and thus may be reported (e.g., via a 1-bit report).

Alternatively, I may be one of X8, … …, X12 and thus may be reported (e.g., via a 3-bit report).

Alternatively, I may be one of X2, … …, X10 and thus may be reported (e.g., via a 4-bit report).

Alternatively, I may be one of X2, X3, X8, … X12 and thus may be reported (e.g., via a 3-bit report).

● For a UE supporting 4 ports, I may be one of X1, … …, X12 and thus may be reported (e.g., via a 4-bit report).

In one example, index I indicates information about one TPMI or multiple TPMI (i.e., TPMI group), where each TPMI indicates a precoding matrix W (e.g., PUSCH triggered by DCI or configured via RRC (e.g., via higher layer PUSCH-Config)) for UL transmission. According to section 6.3.1.5 of REF7, the precoding matrix W is equal to the identity matrix for non-codebook based UL transmissions. For codebook-based UL transmissions, the precoding matrix W is given by w=1 for single layer transmissions on a single antenna port, otherwise given by tables 1 to 6 (replicated below). Three coherent types of TPMI index subsets are summarized in tables 7 and 8, where rank = r corresponds to (corresponds to) r layers.

The rank (or number of layers) and the corresponding precoding matrix W are indicated to the UE using TRI and TPMI, respectively. In one example, the indication is done jointly via the field "precoding information and number of layers" in the DCI (e.g., using DCI format 0_1). In another example, the indication is via higher layer RRC signaling. In one example, the mapping between the fields "precoding information and number of layers" and TRI/TPMI is according to [ REF10] section 7.3.1.1.2.

Table 1: precoding matrix W for single layer transmission using two antenna ports

Table 2: precoding matrix W for single layer transmission using four antenna ports with transform precoding disabled

Table 3: precoding matrix W for two-layer transmission using two antenna ports with transform precoding disabled

Table 4: precoding matrix W for two-layer transmission using four antenna ports with transform precoding disabled

Table 5: precoding matrix W for three-layer transmission using four antenna ports with transform precoding disabled

Table 6: precoding matrix W for four-layer transmission using four antenna ports with transform precoding disabled

Table 7: TPMI index for two antenna ports

Rank of	Non-Coherent	fullAndPartialAndNonCoherent
			1	0-1	0-5
2	0	0-2

Table 8: TPMI index for 4 antenna ports

Rank of	Non-Coherent	partialAndNonCoherent	fullAndPartialAndNonCoherent
				1	0-3	0-11	0-27
2	0-5	0-13	0-21
				3	0	0-2	0-6
4	0	0-2	0-4

For 2Tx or 2 SRS ports, index I indicates rank 1TPMI for 2 antenna ports (see table 1). Two examples are shown in table 9:

● In one example: i=0 indicates that 1 SRS port (including antenna panel) is selected, i=1 indicates that 2 SRS ports (including antenna panel) is selected

● In one example: i=0 indicates that 1 SRS port is selected (including an antenna panel having a first port), i=1 indicates that 1 SRS port is selected (including an antenna panel having a second port), and i=1 indicates that 2 SRS ports are selected (including an antenna panel having two ports)

In one example, TPMI2 in one or more of the examples described above is replaced with any one of TPMI2-TPMI5 (table 9). In one example, TPMI2 in one or more of the examples described above is replaced with a plurality of TPMI (or TPMI groups) in TPMI2-TPMI5 (table 9).

In one example, TPMI0 in one or more of the examples described above is replaced with TPMI1 (table 9).

In one example, the index I depends on the type of coherence reported by the UE. Thus, I may take values from table 9 depending on the type of coherence.

● For UEs supporting NC and 2 ports, I may take i=0 (and thus need not be reported) for one or more of the examples described above, and I may take one of i=0 and i=1 (and thus may be reported via a 1-bit report) for one or more of the examples described above.

● For a UE supporting FC and 2 ports, I may take any value (e.g., from table 9), and thus may be reported via the 1-bit report of one or more examples described above and the 2-bit report of one or more examples described above

● For a UE supporting 2 ports, I may take any value (e.g., from table 9), and thus may be reported via the 1-bit report of one or more examples described above and the 2-bit report of one or more examples described above.

Table 9: index I-to-TPMI mapping for 2 SRS ports

For 4Tx or 4 SRS ports, index I indicates rank 1TPMI for 4 antenna ports (see table 2). Two examples are shown in table 10:

● In one example: i=0 indicates 1 SRS port (including antenna panel) is selected, i=1 indicates 2 SRS ports (including antenna panel) is selected, and i=2 indicates 4 SRS ports (including antenna panel) is selected

● In one example: i=0 indicates 1 SRS port (including an antenna panel with a first port), i=1 indicates 1 SRS port (including an antenna panel with a second port), i=2 indicates 1 SRS port (including an antenna panel with a third port), i=3 indicates 1 SRS port (including an antenna panel with a fourth port), i=4 indicates 2 SRS ports (including an antenna panel with a first port and a second port), i=5 indicates 2 SRS ports (including an antenna panel with a third port and a fourth port), and i=6 indicates 4 SRS ports (including antenna panels with all ports) are selected.

In one example, TPMI12 in one or more of the examples described above is replaced with any of TPMI12-TPMI27 (table 10). In one example, TPMI12 in one or more of the examples described above is replaced with a plurality of TPMI (or TPMI groups) in TPMI12-TPMI27 (table 10).

In one example, TPMI4 in one or more of the examples described above is replaced with TPMI8 (table 10). In one example, TPMI4 in one or more of the examples described above is replaced with any one of TPMI4-TPMI7 (table 10). In one example, TPMI4 in one or more of the examples described above is replaced with a plurality of TPMI (or TPMI groups) in TPMI4-TPMI7 (table 10). In one example, TPMI4 in one or more of the examples described above is replaced with any one of TPMI4-TPMI11 (table 10). In one example, TPMI4 in one or more of the examples described above is replaced with a plurality of TPMI (or TPMI groups) in TPMI4-TPMI11 (table 10). In one example, TPMI4 in one or more of the examples described above is replaced with any one of TPMI8-TPMI11 (table 10). In one example, TPMI4 in one or more of the examples described above is replaced with a plurality of TPMI (or TPMI groups) in TPMI8-TPMI11 (table 10).

In one example, TPMI4 in one or more of the examples described above is replaced with any one of TPMI4-TPMI7 (table 10). In one example, TPMI4 in one or more of the examples described above is replaced with a plurality of TPMI (or TPMI groups) in TPMI4-TPMI7 (table 10). In one example, TPMI8 in one or more of the examples described above is replaced with any one of TPMI8-TPMI11 (table 10). In one example, TPMI8 in one or more of the examples described above is replaced with a plurality of TPMI (or TPMI groups) in TPMI8-TPMI11 (table 10).

In one example, TPMI0 in one or more of the examples described above is replaced with any one of TPMI1-TPMI3 (table 10).

In one example, the index I depends on the type of coherence reported by the UE. Thus, I may take on values from table 10 depending on the type of coherence.

● For UEs supporting NC and 4 ports, I may take i=0 (and thus need not be reported) for one or more of the examples described above, and I may take one of i=0, … …, 3 (and thus may be reported via a 2-bit report) for one or more of the examples described above.

● For a UE supporting PC and 4 ports, I may take i=0 or 1 (and thus may be reported via a 1-bit report) for one or more of the examples described above, and one of i=0, … …, 5 (and thus may be reported via a 3-bit report) for one or more of the examples described above.

● For UEs supporting FC and 4 ports, I may take any value (e.g., from table 10), and thus may be reported by the 2-bit report of one or more examples described above and the 3-bit report of one or more examples described above.

● For a UE supporting 4 ports, I may take any value (e.g., from table 10), and thus may be reported by the 2-bit report of one or more examples described above and the 3-bit report of one or more examples described above.

Table 10: index I-to-TPMI mapping for 4 SRS ports

In one example, index I indicates information about TPMI or TPMI groups, where TPMI indicates a precoding matrix with a number of columns indicating the number of antenna panels at the UE, and each column indicates one or more antenna port indexes including the antenna panel.

In one example, each column of the precoding matrix is a selection vector comprising one "1" and the remaining "0" entries, and the position (or row index) corresponding to "1" indicates the antenna port comprising the panel. Three examples are shown in tables 11, 12 and 13.

Table 11: index I-to-TPMI mapping for 2 SRS ports

Table 12: index I-to-TPMI mapping for 4 SRS ports

Table 13: index I-to-TPMI mapping for 4 SRS ports

In one example, each column of the precoding matrix is a selection vector selecting 1 port or more than 1 port, including "1" and "0" as entries, and a position (or row index) corresponding to "1" indicates an antenna port including a panel. Examples of two antenna ports are shown in tables 14 and 15.

Table 14: index I-to-TPMI mapping for 2 SRS ports

Table 15: index I-to-TPMI mapping for 2 SRS ports

Three examples are shown in tables 16-18 for 4 antenna ports. In one example, i=5 in table 18 indicates rank 3TPMI0:and rank 1TPMI0: />

Table 16: index I-to-TPMI mapping for 4 SRS ports

Table 17: index I-to-TPMI mapping for 4 SRS ports

Table 18: index I-to-TPMI mapping for 4 SRS ports

Two additional examples are shown in tables 19 and 20 for 4 antenna ports. In one example, i=14 in table 19 indicates rank 3TPMI0:and rank 1TPMI0: />

Table 19: index I-to-TPMI mapping for 4 SRS ports

/>

Table 20: index I-to-TPMI mapping for 4 SRS ports

In one embodiment, the UE reports the UE capability value (or set of values) including information about the supported rank value (or UL rank or number of UL transmission layers) via its capability to report a list of UE capability values (or set of values), and the UE is configured with a report of rank value or maximum rank value (or UL rank or UL MIMO layer number or PUSCH port number or SRS port number or maximum supported SRS port number) in the beam report based on its reported capability. Note that the rank value corresponds to the number of transmission layers for UL transmission (e.g., PUSCH).

As shown in fig. 14, the UE is configured to measure (receive) P ₁ DL measurement RS resources (such as CSI-RS or SSB), where P ₁ ≥1。

The UE is also configured to use the measurements (based on received DL measurement RS resources) to determine a beam report and report the beam report via an UL channel (e.g., PUCCH or PUSCH), as configured by the higher layer parameters CSI-ReportConfig.

The beam report includes N.gtoreq.1 pairs (R, I), where R is a resource indicator and I is an index corresponding to the reported R. In one example, R is SSBRI indicating an SSB index, or CRI indicating a CSI-RS resource index. In one example, the beam report further includes a beam metric corresponding (associated) with each reported resource indicator R. In one example, each beam metric is L1-RSRP (as in Rel.15). In one example, each beam metric is an L1-SINR (as in Rel.16). In one example, each beam metric is L1-RSRP or L1-SINR based on a configuration that may be subject to UE capabilities reported by the UE. When N >1, the beam metrics are reported in a differential manner (as in rel.15/16), with 7 bits for the first (absolute) beam metric and 4 bits for each of the remaining N-1 (differential) beam metrics relative to the first beam metric, the details of such differential reporting are as described in the rel.15/16NR specifications.

In one example, index I indicates a correspondence between CSI-RS and/or SSB resource indexes (indicated via R) and UE capability values from a list of UE capability values (or set of values) reported by the UE (via UE capability signaling). In one example, index I is an index of UE capability values from a list of UE capability values (or set of values). Details of the list of UE capability values (or set of values) will be described later in this disclosure. The UE will not update or expect to maintain the correspondence between beam reporting instances.

In one example, beam reporting is configured via reportquality set to a new value in CSI-ReportConfig (i.e., "cri-RSRP-r17" or "ssb-Index-RSRP-r17" or "cri-SINR-r17" or "ssb-Index-SINR-r 17"), where the term "cri" or "ssb-Index" corresponds to a resource indicator, the term "RSRP" or "SINR" corresponds to a beam metric, and the term "r17" corresponds to Index I. In one example of this, in one implementation,

● In one example, the term "r17" is replaced with "ValueIndex", i.e., the new value is "cri-RSRP-ValueIndex", "ssb-Index-RSRP-ValueIndex", "cri-SINR-ValueIndex", "ssb-Index-SINR-ValueIndex"

● In one example, the term "r17" is replaced with "ValueSetIndex", i.e., the new value is "cri-RSRP-ValueSetIndex", "ssb-Index-RSRP-ValueSetIndex", "cri-SINR-ValueSetIndex", "ssb-Index-SINR-ValueSetIndex"

In one example, the term "r17" is replaced with "capabilysetindex", i.e., the new value is "cri-RSRP-capabilysetindex", "ssb-Index-RSRP-capabilysetindex", "cri-SINR-capabilysetindex", "ssb-Index-SINR-capabilysetindex".

In one example, index I indicates a rank value or maximum rank (or UL rank) value corresponding to the SSBRI/CRI reported in the beam reporting instance.

● X1: rank 4 or maximum rank=4 (for 1 panel with 4 ports, or select 4 SRS ports)

● X2: rank 2 or maximum rank=2 (for 2 panels each with 2 ports, or select 2 SRS ports)

● X3: rank 1 or maximum rank=1 (for 4 panels each with 1 port, or select 1 SRS port)

● X4: rank 4 or maximum rank=4 (for 3 panels, 1 panel with 2 ports or 2 SRS ports selected, 2 panels each with 1 port or 1 SRS port selected)

● For a UE supporting PC and 4 ports, I may be X2 or X3 or X4 and thus may be reported (e.g., via a 2-bit report).

● Y1: rank 2 or maximum rank=2 (for 1 panel with 2 ports, or select 2 SRS ports)

● Y3: rank 1 or maximum rank=1 (for 2 panels each with 1 port, or select 1 SRS port)

In one example, NW configures an allowed rank value set for index I, or NW configures an association between index I and rank value (for selecting SRS antenna ports or for selecting panels). The configuration may be subject to UE capabilities reported by the UE, which may be, for example, a list of supported UE capability values (or set of values) including rank values. The UE determines the index I based on the NW configuration, and if the number of supported rank values for reporting the index I is 1, 2, 3, or 4, respectively, the bit width of the index I report is 0, 1, 2, or 2 bits.

In one example, index I indicates a rank value corresponding to SSBRI/CRI reported in the beam reporting instance. The details are the same as one or more examples described above, except that index I is allowed to take a value indicating rank 3 for 4 SRS ports (either 3 SRS ports or a panel with 3 ports is selected).

For SRS resources with 4 SRS ports, index I indicates one of the following.

● X4: rank 3 or maximum rank=3 (for 1 panel each with 3 ports, or select 3 SRS ports)

For SRS resources with 4 SRS ports, index I indicates one of the following.

● X5: rank 2+1 or maximum rank = 2+1 (for 3 panels, 1 panel with 2 ports or 2 SRS ports selected, 2 panels each with 1 port or 1 SRS port selected)

● X6: rank 3+1 or maximum rank = 3+1 (for 2 panels, 1 panel with 3 ports or 3 SRS ports selected, 1 panel with 1 port or 1 SRS port selected)

In one example, NW configures an allowed rank value set for index I, or NW configures an association between index I and rank value (for selecting SRS antenna ports or for selecting panels). The configuration may be subject to UE capabilities reported by the UE, which may be, for example, a list of supported UE capability values (or set of values) including rank values. The UE determines the index I based on the NW configuration and if the number of supported coherence types or SRS antenna port selections for reporting the index I is 1, 2, 3, or 4, respectively, the bit width of the index I report is 0, 1, 2, or 2 bits.

In one embodiment, the UE reports the UE capability value (or set of values) including information about the number of supported SRS antenna ports via its capability to report a list of UE capability values (or set of values), and the UE is configured with a report of the number of SRS antenna ports or the maximum number of SRS antenna ports in the beam report based on its reported capability.

The beam report includes N.gtoreq.1 pairs (R, I), where R is a resource indicator and I is an index corresponding to the reported R. In one example, R is SSBRI indicating an SSB index, or CRI indicating a CSI-RS resource index. In one example, the beam report further includes a beam metric corresponding (associated) with each reported resource indicator R. In one example, each beam metric is L1-RSRP (as in Rel.15). In one example, each beam metric is an L1-SINR (as in Rel.16). In one example, each beam metric is L1-RSRP or L1-SINR based on a configuration that may be subject to UE capabilities reported by the UE. When the beam metrics are reported in a differential manner (as in rel.15/16) when N >1, where 7 bits are for the first (absolute) beam metric and 4 bits are for each of the remaining N-1 (differential) beam metrics relative to the first beam metric, the details of such differential reporting are as described in the rel.15/16NR specification.

Index I is determined/configured according to at least one of the following examples.

In one example, index I indicates a number of SRS antenna ports or a maximum number of SRS antenna ports corresponding to SSBRI/CRI reported in the beam reporting instance.

● X1: SRS antenna port number=4 or maximum SRS antenna port number=4 (for 1 panel with 4 ports, or select 4 SRS ports)

● X2: SRS antenna port number=2 or maximum SRS antenna port number=2 (for 2 panels each with 2 ports, or 2 SRS ports are selected)

● X3: SRS antenna port number=1 or maximum SRS antenna port number=1 (for 4 panels each with 1 port, or 1 SRS port is selected)

● X4: SRS antenna port number=4 or maximum SRS antenna port number=4 (for 3 panels, 1 panel with 2 ports or 2 SRS ports selected, 2 panels with 1 port or 1 SRS port each)

● Y1: SRS antenna port number=2 or maximum SRS antenna port number=2 (for 1 panel with 2 ports, or 2 SRS ports are selected)

● Y3: SRS antenna port number=1 or maximum SRS antenna port number=1 (for 2 panels each with 1 port, or 1 SRS port is selected)

In one example, NW configures a set of allowed SRS antenna port numbers for index I, or NW configures an association between index I and SRS antenna port numbers. The configuration may be subject to UE capabilities reported by the UE, which may be, for example, a list of supported UE capability values (or set of values) including the number of SRS antenna ports. The UE determines the index I based on the NW configuration, and if the number of SRS antenna ports for reporting the index I is 1, 2, 3, or 4, respectively, the bit width of the index I report is 0, 1, 2, or 2 bits.

In one example, index I indicates a number of SRS antenna ports or a maximum number of SRS antenna ports corresponding to SSBRI/CRI reported in the beam reporting instance. The details are the same as one or more examples described above, except that for 4 SRS ports the allowed index I takes a value indicating SRS antenna port number 3 or maximum SRS antenna port number = 3 (either 3 SRS ports or a panel with 3 ports is selected).

For SRS resources with 4 SRS ports, index I indicates one of the following.

● X4: SRS antenna port number=3 or maximum SRS antenna port number=3 (for 1 panel each with 3 ports, or 3 SRS ports are selected)

For SRS resources with 4 SRS ports, index I indicates one of the following.

● X5: SRS antenna port number = 2+1 or maximum SRS antenna port number = 2+1 (for 3 panels, 1 panel with 2 ports or 2 SRS ports selected, 2 panels with 1 port or 1 SRS port each)

● X6: SRS antenna port number = 3+1 or maximum SRS antenna port number = 3+1 (for 2 panels, 1 panel with 3 ports or 3 SRS ports selected, 1 panel with 1 port or 1 SRS port selected)

In one embodiment, the UE reports the UE capability value (or set of values) including information about the number of supported SRS resources via its capability to report a list of UE capability values (or set of values), and the UE is configured with a report of the number of SRS resources or the maximum number of SRS resources in a beam report based on its capability to report. In one example, each SRS resource is a 1-port resource. The remainder of the embodiment is the same as described above, except that the number of SRS antenna ports is replaced with the number of SRS resources.

In one embodiment, the indication of the coherence type, rank value, or SRS antenna port number may be extended from one reporting amount to multiple reporting amounts, where the reporting amount is the coherence type, rank value, or SRS antenna port number.

In one example, the beam report includes (R, I), where R is a resource indicator (SSBRI/CRI), and index I is a joint index indicating N >1 reporting amounts.

In one example, the beam report includes (R, I), where R is a resource indicator (SSBRI/CRI), index i= [ I ₁ ,…I _N ]Comprises N indexes, I-th index I _i Corresponding to the i-th reporting amount.

In one example, the beam report includes (R, I), where R is a joint indicator indicating N >1 resource indicators (each resource indicator is either SSBRI or CRI), and index I is a joint index indicating N >1 reporting amounts.

In one example, the beam report includes (R, I), where R is an indication N>1 joint indicator of resource indicators (each resource indicator is either SSBRI or CRI), index i= [ I ₁ ,…I _N ]Comprises N indexes, I-th index I _i Corresponding to the i-th reporting amount.

In one example, the beam report includes (R, I), where r= [ R ₁ ,…R _N ]Includes N resource indicators, the ith indicator R _i Is a resource indicator (SSBRI or CRI), and index I is an indication N>Joint index of 1 reporting amount.

In one example, the beam report includes (R, I), where r= [ R ₁ ,…R _N ]Includes, the ith indicator R _i Is a resource indicator (SSBRI or CRI), index i= [ I ₁ ,…I _N ]Comprises N indexes, I-th index I _i Corresponding to the i-th reporting amount.

At least one of the following is used/configured with respect to N.

● In one example, N is fixed (e.g., n=2).

● In one example, N depends on the maximum number of SRS ports supported by the UE.

● In one example, N is configured, for example, from {1,2} or {1,2,4} or {1,2,3,4 }.

● In one example, if the UE supports up to 4 SRS ports, N is configured from {1,2} or {1,2,4} or {1,2,3,4} and if the UE supports up to 2 SRS ports, N is configured from {1,2} where the maximum number of SRS ports supported is reported by the UE as part of the UE capability.

● In one example, N is reported by the UE as part of a beam report or as part of a UE capability report. When N is reported as part of a beam report, a two-part UCI may be used, wherein UCI part 1 includes a beam report for a fixed number (e.g., 1) of report amounts, UCI part 2 includes the remaining (e.g., N-1) report amounts, and information about the remaining report amounts may be included in UCI part 1.

In one embodiment, a UE may be configured with multiple SRS resource sets having different numbers of SRS antenna ports, where SRS resources in an SRS resource set have the same number of SRS antenna ports. In one example, multiple SRS resource sets may be used to distinguish multiple antenna panels at a UE.

Alternatively, the UE may be configured with multiple SRS resource sets having different numbers of SRS antenna ports, where SRS resources in the SRS resource sets have different numbers of SRS antenna ports. In one example, multiple SRS resource sets may be used to distinguish multiple antenna panels at a UE.

Alternatively, the UE may be configured with multiple SRS resource sets having different numbers of SRS antenna ports, where SRS resources in the SRS resource sets have the same or different numbers of SRS antenna ports. In one example, multiple SRS resource sets may be used to distinguish multiple antenna panels at a UE.

Alternatively, the UE may be configured with multiple SRS resources having different numbers of SRS antenna ports, where the multiple SRS resources are in the same SRS resource set. In one example, multiple SRS resources may be used to distinguish between multiple antenna panels at a UE.

In one example, this may be configured only when the UE is configured with codebook-based UL transmissions (e.g., via a higher layer parameter txConfig set to "codebook").

In one example, this may be configured only when the UE is configured with non-codebook based UL transmissions (e.g., via a higher layer parameter txConfig set to "non codebook").

In one example, this may be configured for both cases when the UE is configured with codebook-based UL transmissions (e.g., via higher layer parameter txConfig set to "codebook") or when the UE is configured with non-codebook-based UL transmissions (e.g., via higher layer parameter txConfig set to "non codebook").

The SRS resource set or the number of SRS resources (M) may be equal to the panel entity number (M), where the panel entity is functionally equivalent to any one of the following.

● A transmit-receive (Tx-Rx) entity such as an antenna panel, a transmit-receive point (TRP), an antenna port, an antenna group, an antenna port group, a remote radio head (remote radio head, RRH).

● Resource sets (SRS resource sets, CSI resource sets) comprising one or more resources

● One or more resources (SRS, CSI-RS, SSB).

● And (3) a transmission process.

The value of M is according to at least one of the following examples.

● In one example, it is fixed, e.g., 2,3, or 4. The fixed value may depend on the number of antenna ports at the UE.

● In one example, it is based on UE capabilities from {1,2}, {1,2,3,4}, {2,3,4}, or {2,4 }.

● In one example, it is based on UE capability, which is a different maximum SRS port number in number.

For 2 SRS ports, {1_2} or {1_2,2_2}, where x_y indicates that the UE may be configured with two SRS resources or a set of resources with x and y SRS ports.

For 4 SRS ports, {1_2,1_4,2_4,1_2_4} or {1_2,1_3,1_4,2_3,3_4,2_4,1_2_4,1_2_3,1_3_4,2_3_4,1_2_3_4}, x_y_z indicates that the UE may be configured with three SRS resources or a set of resources with x, y, and z SRS ports.

In one example, the number or maximum number (M) of SRS resource sets with different numbers of SRS antenna ports depends on the number of antenna ports (Tx-Rx or RF chains or power amplifiers) at the UE. For example, for a UE with 2 antenna ports, m=2, and for a UE with 4 antenna ports, m=2 or 3.

● For 2 sets, the different SRS antenna port numbers may be (N1, N2) = (2, 1), (4, 1) or (4, 2)

● For 3 sets, the different SRS antenna port numbers may be (N1, N2, N3) = (4, 2, 1)

● For a UE with 2 antenna ports, (N1, N2) = (2, 1).

● For a UE with 4 antenna ports, (N1, N2) = (2, 1), (4, 2) and (N1, N2, N3) = (4, 2, 1).

Number of SRS resources (N _SRS ) May be according to at least one of the following examples.

● In one example, N _SRS Is fixed, e.g. 2.

● In one example, N _SRS E {1, …, m }, where m is the maximum value that can be determined based on UE capability reporting. In one example, m is fixed to 2. In one example, m may be reported from {2,3}, {2,4}, {3,4}, etc.

● In one example, the maximum value m is the same for all resource sets. In one example, the maximum value m is separate for each set.

● In one example, the total number of SRS resources across all SRS resource sets may be a maximum value n, which may be fixed (e.g., 4) or may be determined based on the UE capability report. The number of SRS resources in each resource set may be any value {1,2, … }, as long as the total number of SRS resources across all resource sets is less than or equal to n.

In one embodiment, the UE is also indicated (e.g., via UL-related DCI) with an SRS Resource Indicator (SRI) based on SRS resources corresponding to one SRS resource set (S) among a plurality of SRS resource sets (S1, S2, … …), wherein the SRS resource set (S) may be aligned with the UE-reported information corresponding to index I. In one example, information regarding SRS resource sets aligned with UE reported information is provided according to at least one of the following examples.

● In one example, an SRS resource set indicator indicating information (e.g., index) about an SRS resource set (S) is provided/indicated via UL-DCI (e.g., DCI format 0_1 or 0_2 in NR).

● In one example, information (e.g., index) about the SRS resource set (S) is provided/indicated in conjunction with the SRI. For example, the SRI may indicate an index pair (a, b), where a = an index of the SRS resource set and b = an index of SRS resources within the SRS resource set with index a. An example is shown in fig. 21. The payload of the SRI indication isBit, where t is the number of SRS resource sets, N _i Is the number of SRS resources in the i-th SRS resource set.

● In one example, information (e.g., index) about SRS resource set (S) is provided/indicated via UL BWP handover. For example, the UE may be configured with multiple UL BWPs, each UL BWP having a different number of SRS ports, and provide/indicate information (e.g., index) about the SRS resource set (S) by updating/indicating an index of one of the configured UL BWPs (e.g., whose number of SRS ports is aligned with information reported by the UE). Such UL BWP switching/updating may be indicated via UL-DCI (e.g., DCI format 0_1 or 0_2 in NR).

Table 21

In one example, when there are two SRS resource sets (S1, S2) each having a different (maximum supported) number of SRS ports (N1, N2), the alignment between the set (S) and the reported index I is according to at least one of the following examples.

In one example, when (N1, N2) = (2, 1), the alignment is determined as follows.

(case 1. A) if the index I indicates a coherence type and/or TPMI corresponding to FC (or indicates rank=2 or maximum rank=2 or SRS port number=2 or maximum SRS port number=2), the SRS resource set for SRI indication is s=s1 (i.e. SRS resource with 2 SRS ports). The codebook subset (UL codebook) for PUSCH is given by the following.

● In one example, codebook subset is not dependent on the coherence capability reported by the UE, and codebook subset= 'fullan and dnoncoupler' (abbreviated fc+pc+nc).

● In one example, codebook subset depends on the coherence capability reported by the UE. In particular, the method comprises the steps of,

if the UE supports fc+pc+nc transmission, codebook subset=fc+pc+nc

If UE supports NC transmission, codebook subset=nc

If the UE supports "partialanddnoncoupler" (abbreviated as pc+nc) transmission and is equipped with 4 antenna ports, one of the following is used with respect to codebook subset.

■ codebook subset = fc+pc+nc for 2 antenna ports

■ Or codebook subset = NC for 2 antenna ports

■ Or codebook subset = fc+pc+nc or NC for 2 antenna ports, depending on individual UE capabilities and/or RRC configuration

(case 1. B) if the index I indicates a coherence type and/or TPMI corresponding to the PC, the SRS resource set for SRI indication is according to at least one of the following.

● S=s1 (i.e., SRS resource with 2 SRS ports). The codebook subset is as described in case 1. A.

● S=s2 (i.e., SRS resource with 1 SRS port). No codebook subset is required (due to 1-port SRS resource)

● S=s1 or S2, based on UE capability and/or RRC configuration.

(case 1. C) if the index I indicates a coherence type and/or TPMI corresponding to NC (or indicates rank=1 or maximum rank=1 or SRS port number=1 or maximum SRS port number=1), the SRS resource set for SRI indication is s=s2.

In one example, when (N1, N2) = (2, 1), there is a constraint on the UE reporting. For example, the UE reporting of index I is limited to (FC, NC) or (FC, PC) or (PC, NC).

In one example, when (N1, N2) = (2, 1), there is no constraint on UE reporting. For example, the UE report of index I may come from (FC, PC, NC).

In one example, when (N1, N2) = (4, 1), the alignment is determined as follows.

(case 2. A) if the index I indicates a coherence type and/or TPMI corresponding to FC (or indicates rank=4 or maximum rank=4 or SRS port number=4 or maximum SRS port number=4), the SRS resource set for SRI indication is s=s1 (i.e. SRS resource with 4 SRS ports). The codebook subset (UL codebook) for PUSCH is given by the following.

if the UE supports fc+pc+nc transmission, codebook subset=fc+pc+nc

If the UE supports pc+nc transmission, codebooksubset=pc+nc

If UE supports NC transmission, codebook subset=nc

(case 2. B) if the index I indicates a coherence type and/or TPMI corresponding to PC (or indicates rank=2 or maximum rank=2 or SRS port number=2 or maximum SRS port number=2), the SRS resource set for SRI indication is according to at least one of the following.

● S=s1 (i.e., SRS resource with 4 SRS ports). codebook subset is as described in case 2. A.

● S=s1 or S2, based on UE capability and/or RRC configuration.

(case 2. C) if the index I indicates a coherence type and/or TPMI corresponding to NC (or indicates rank=1 or maximum rank=1 or SRS port number=1 or maximum SRS port number=1), the SRS resource set for SRI indication is s=s2.

In one example, when (N1, N2) = (4, 1), there is a constraint on the UE reporting. For example, the UE reporting of index I is limited to (FC, NC) or (FC, PC) or (PC, NC). In one example, when (N1, N2) = (4, 1), there is no constraint on UE reporting. For example, the UE report of index I may come from (FC, PC, NC).

In one example, when (N1, N2) = (4, 2), the alignment is determined as follows.

(case 3. A) if the index I indicates a coherence type and/or TPMI corresponding to FC (or indicates rank=4 or maximum rank=4 or SRS port number=4 or maximum SRS port number=4), the SRS resource set for SRI indication is s=s1 (i.e. SRS resource with 4 SRS ports). The codebook subset (UL codebook) for PUSCH is given by the following.

if the UE supports fc+pc+nc transmission, codebook subset=fc+pc+nc

If the UE supports pc+nc transmission, codebooksubset=pc+nc

If UE supports NC transmission, codebook subset=nc

(case 3.b) if the index I indicates a coherence type and/or TPMI corresponding to PC (or indicates rank=2 or maximum rank=2 or SRS port number=2 or maximum SRS port number=2), the SRS resource set for SRI indication is according to at least one of the following.

● S=s1 (i.e., SRS resource with 4 SRS ports). codebook subset is as described in case 3. A.

● S=s2 (i.e., SRS resource with 2 SRS ports). The codebook subset is as described in case 1. A.

● S=s1 or S2, based on UE capability and/or RRC configuration.

(case 3.c) if the index I indicates a coherence type and/or TPMI corresponding to NC (or indicates rank=1 or maximum rank=1 or SRS port number=1 or maximum SRS port number=1), the SRS resource set for SRI indication is s=s2. The codebook subset is as described in case 1. A.

In one example, when (N1, N2) = (4, 2), there is a constraint on the UE reporting. For example, the UE reporting of index I is limited to (FC, NC) or (FC, PC) or (PC, NC).

In one example, when (N1, N2) = (4, 2), there is no constraint on UE reporting. For example, the UE report of index I may come from (FC, PC, NC).

In one example, when there are three SRS resource sets (S1, S2, S3) with different (maximally supported) numbers of SRS ports (N1, N2, N3), respectively, the alignment between the set (S) and the reported index I is according to at least one of the following examples.

In one example, when (N1, N2, N3) = (4, 2, 1), the alignment is determined as follows. If the index I indicates a coherence type and/or TPMI corresponding to FC (or indicates rank=4 or maximum rank=4 or SRS port number=4 or maximum SRS port number=4), the SRS resource set for SRI indication is s=s1 (i.e., SRS resource with 4 SRS ports). The codebook subset (UL codebook) for PUSCH is given by the following.

If the UE supports fc+pc+nc transmission, codebook subset=fc+pc+nc

If the UE supports pc+nc transmission, codebooksubset=pc+nc

If UE supports NC transmission, codebook subset=nc

If the index I indicates a coherence type and/or TPMI corresponding to PC (or indicates rank=2 or maximum rank=2 or SRS port number=2 or maximum SRS port number=2), the SRS resource set for SRI indication is s=s2 (i.e. SRS resource with 2 SRS ports). The codebook subset is as described in case 1. A.

If the index I indicates a coherence type and/or TPMI corresponding to NC (or indicates rank=1 or maximum rank=1 or SRS port number=1 or maximum SRS port number=1), the SRS resource set for SRI indication is s=s3 (i.e. SRS resource with 1 SRS port).

In one embodiment, the same as one or more embodiments described above, except that a different SRS antenna port number is replaced with one of the following:

● Different maximum SRS antenna port numbers

● Different ranks (or UL ranks)

● Different maximum ranks (or UL ranks)

● Different UL MIMO layers

● Different maximum UL MIMO layers

● Different maximum number of antenna ports

● Different maximum number of RF chains

● Different maximum PUSCH port numbers

● Different maximum PUCCH port numbers

In one embodiment, the panel entity corresponds to a CSI-RS and/or SSB resource index reported in the beam reporting instance. The correspondence between the panel entity and the reported CSI-RS and/or SSB resource indexes is informed to the NW. Note that the correspondence between CSI-RS and/or SSB resource indexes and panel entities is determined by the UE (similar to Rel-15/16). The UE reports the maximum number of SRS ports per panel entity (e.g., as part of the UE capability).

The UE may be configured with multiple SRS resources or a set of resources with different Z, where Z is the maximum UL MIMO layer number or the number of SRS ports (most supported) or the number of resources (e.g., SRS, CSI-RS, SSB) or one of the amounts described in the above embodiments.

The UE is also indicated (e.g., via UL-related DCI) with an SRS Resource Indicator (SRI) that is based on SRS resources corresponding to one of a plurality of SRS resource sets, wherein the SRS resource set may be aligned with UE capabilities for the panel entity.

The UE is further configured to perform measurements and report beam reporting as described in one or more of the embodiments above.

In one embodiment, the UE reports a list of K.gtoreq.1 UE capability value set(s). In one example, each set of UE capability values corresponds to (or is associated with) an antenna panel at the UE. In one example, each set of UE capability values corresponds to (or is associated with) a set of antenna ports at the UE. In one example, each set of UE capability values corresponds to (or is associated with) a Tx-Rx entity at the UE.

Each set of UE capability values includes at least one of the following components:

● C1: number of SRS ports (maximally supported). In one example, the candidate value for the number of (maximally supported) SRS ports includes {2,4} or {1,2} or {1,4} or {1,2,4}. The remainder of the details are in accordance with one or more embodiments described above.

● C2: UL transport layer number. In one example, the candidate value of the UL transport layer includes {1,2} for a UE having 2 antenna ports, and the candidate value of the UL transport layer is {1,2,3,4} or {1,2,4} for a UE having 4 antenna ports. The remainder of the details are similar to one or more of the embodiments described above.

● And C3: a coherence type. In one example, for a UE with 2 antenna ports, the candidate value of the coherence type includes { FC, NC }, while for a UE with 4 antenna ports, the candidate value of the coherence type is { FC, PC, NC }. The remainder of the details are similar to one or more of the embodiments described above.

● And C4: TPMI. In one example, candidate values for TPMI are as described in this disclosure. The remainder of the details are similar to one or more of the embodiments described above.

● C5: number of SRS resources within one SRS resource set. In one example, the candidate value for the number of SRS resources includes {1,2} or {1,2,4}. The remainder of the details are similar to one or more of the embodiments described above.

In one example, the UE reports k=1 UE capability value sets.

● In one example, the set of UE capability values is S1 comprising one component, wherein the component is according to one of the following examples.

In one example, the component is C1.

In one example, the constituent is C2.

In one example, the constituent is C3.

In one example, the constituent is C4.

In one example, the constituent is C5.

● In one example, the set of UE capability values is S2 comprising two components, wherein the components are according to one of the following examples.

In one example, the component is { C1, C2}.

In one example, the component is { C1, C3}.

In one example, the component is { C1, C4}.

In one example, the component is { C1, C5}.

In one example, the component is { C2, C3}.

In one example, the component is { C2, C4}.

In one example, the component is { C2, C5}.

In one example, the component is { C3, C4}.

In one example, the component is { C3, C5}.

In one example, the component is { C4, C5}.

● In one example, the set of UE capability values is S3 comprising three components, wherein the components are according to one of the following examples.

In one example, the constituent is { C1, C2, C3}.

In one example, the component is { C1, C2, C4}.

In one example, the component is { C1, C2, C5}.

In one example, the constituent is { C1, C3, C4}.

In one example, the component is { C1, C3, C5}.

In one example, the component is { C1, C4, C5}.

In one example, the component is { C2, C3, C4}.

In one example, the component is { C2, C3, C5}.

In one example, the component is { C2, C4, C5}.

In one example, the component is { C3, C4, C5}.

● In one example, the set of UE capability values is S4 comprising four components, wherein the components are according to one of the following examples.

In one example, the constituent is { C1, C2, C3, C4}.

In one example, the constituent is { C1, C2, C3, C5}.

In one example, the constituent is { C1, C2, C4, C5}.

In one example, the constituent is { C1, C3, C4, C5}.

In one example, the constituent is { C2, C3, C4, C5}.

● In one example, the set of UE capability values is S5 that includes five components, where the components are { C1, C2, C3, C4, C5}.

In one example, the UE reports k=2 UE capability value sets, i.e., T1 and T2.

● The two sets T1 and T2 have the same number of components, i.e. both have the same UE capability Sx, where x is one of 1, … …, 5.

In one example, sx is the same for both sets.

In one example, sx is different for the two sets.

In one example, sx may be the same or different for the two sets.

● The UE capabilities of the two sets T1 and T2 with different numbers of components, i.e. (T1, T2), are (Sx, sy), where (x, y) is one of (1, 2), (1, 3), (1, 4), (1, 5), (2, 3), (2, 4), (2, 5), (3, 4), (3, 5) and (4, 5).

● The two sets T1 and T2 may be identical or different, i.e. (T1, T2) = (Sx, sy), where (x, y) is one of (1, 1), (2, 2), (3, 3), (4, 4), (5, 5), (1, 2), (1, 3), (1, 4), (1, 5), (2, 3), (2, 4), (2, 5), (3, 4), (3, 5) and (4, 5).

In one example, the UE reports K>2 sets of UE capability values, T1, … …, T _K 。

● Collections T1, … …, T _K Having the same number of components, i.e. both having the same UE capability Sx, where x is one of 1, … …, 5.

In one example, sx is the same for K capability sets.

In one example, sx is different for K capability sets.

In one example, sx may be the same or different for K capability sets.

● Collections T1, … …, T _K With a different number of components.

● Collections T1, … …, T _K May be the same or different.

In one example, the value of K is reported by the UE (e.g., as part of a UE capability report).

In one embodiment, when each UE capability set includes a single capability value (component), the UE reports a list of K.gtoreq.1 UE capability value(s). In one example, each UE capability value corresponds to (or is associated with) an antenna panel at the UE. In one example, each UE capability value corresponds to (or is associated with) a set of antenna ports at the UE. In one example, each UE capability value corresponds to (or is associated with) a Tx-Rx entity at the UE.

Each UE capability value includes (corresponds to) at least one of the following components:

● C1: number of SRS ports (maximally supported). In one example, the candidate value for the number of (maximally supported) SRS ports includes {2,4} or {1,2} or {1,4} or {1,2,4}. The remainder of the details are similar to one or more of the embodiments described above.

● And C4: TPMI. In one example, candidate values for TPMI are as described in this disclosure. The remainder of the details are similar to one or more embodiments described above

In one example, the UE reports k=1 UE capability values.

● In one example, the UE capability value is S1 that includes one component, where the component is according to one of the following examples.

In one example, the component is C1.

In one example, the constituent is C2.

In one example, the constituent is C3.

In one example, the constituent is C4.

In one example, the constituent is C5.

● In one example, the UE capability value is S2 that includes two components, wherein the components are according to one of the following examples.

In one example, the component is { C1, C2}.

In one example, the component is { C1, C3}.

In one example, the component is { C1, C4}.

In one example, the component is { C1, C5}.

In one example, the component is { C2, C3}.

In one example, the component is { C2, C4}.

In one example, the component is { C2, C5}.

In one example, the component is { C3, C4}.

In one example, the component is { C3, C5}.

In one example, the component is { C4, C5}.

● In one example, the UE capability value is S3 that includes three components, wherein the components are according to one of the following examples.

In one example, the constituent is { C1, C2, C3}.

In one example, the component is { C1, C2, C4}.

In one example, the component is { C1, C2, C5}.

In one example, the constituent is { C1, C3, C4}.

In one example, the component is { C1, C3, C5}.

In one example, the component is { C1, C4, C5}.

In one example, the component is { C2, C3, C4}.

In one example, the component is { C2, C3, C5}.

In one example, the component is { C2, C4, C5}.

In one example, the component is { C3, C4, C5}.

● In one example, the UE capability value is S4 that includes four components, wherein the components are according to one of the following examples.

In one example, the constituent is { C1, C2, C3, C4}.

In one example, the constituent is { C1, C2, C3, C5}.

In one example, the constituent is { C1, C2, C4, C5}.

In one example, the constituent is { C1, C3, C4, C5}.

In one example, the constituent is { C2, C3, C4, C5}.

● In one example, the UE capability value is S5 that includes five components, where the components are { C1, C2, C3, C4, C5}.

In one example, the UE reports k=2 UE capability values, i.e., T1 and T2.

● The two capability values T1 and T2 have the same number of components, i.e. both have the same UE capability Sx, where x is one of 1, … …, 5.

In one example, sx is the same for both capability values.

In one example, sx is different for the two capability values.

In one example, sx may be the same or different for the two capability values.

● The two capability values T1 and T2 have different numbers of components, i.e. (T1, T2) the UE capability is (Sx, sy), where (x, y) is one of (1, 2), (1, 3), (1, 4), (1, 5), (2, 3), (2, 4), (2, 5), (3, 4), (3, 5) and (4, 5).

● The two capability values T1 and T2 may be the same or different, i.e. (T1, T2) = (Sx, sy), where (x, y) is one of (1, 1), (2, 2), (3, 3), (4, 4), (5, 5), (1, 2), (1, 3), (1, 4), (1, 5), (2, 3), (2, 4), (2, 5), (3, 4), (3, 5) and (4, 5).

In one example, the UE reports K >2 UE capability values, T1, … …, T _K 。

● Capability values T1, … …, T _K Having the same number of components, i.e. both having the same UE capability Sx, where x is one of 1, … …, 5.

In one example, sx is the same for K capability values.

In one example, sx is different for K capability values.

In one example, sx may be the same or different for K capability values.

● K capability values T1, … …, T _K With a different number of components.

● K capability values T1, … …, T _K May be the same or different.

In one embodiment, the UE reports a list of K+.gtoreq.1 UE capability value(s) (or set (s)), where the list includes capability values from Table 21.

Table 22

/>

In one embodiment, as described in this disclosure, a UE is configured to report a correspondence or index I according to at least one of the following examples.

In one example, the correspondence or index I is multiplexed/reported together with a resource indicator R (e.g., CRI or SSBRI) and/or an associated beam metric (e.g., L1-RSRP or L1-SINR) by Uplink Control Information (UCI) sent via a layer 1 channel such as PUCCH or PUSCH, e.g., as configured by the higher layer parameters CSI-ReportConfig. In one example, the PUSCH carrying this information may be one of the following:

● Dynamic grant of PUSCH

● Type 1 configuration grant PUSCH

● Type 2 configuration grant PUSCH

● MsgA PUSCH associated with type 2 random access procedure

● Msg3 PUSCH associated with type 1 random access procedure

In one example, the correspondence or index I is reported separately from a resource indicator R (e.g., CRI or SSBRI) and/or an associated beam metric (e.g., L1-RSRP or L1-SINR), wherein the resource indicator R (e.g., CRI or SSBRI) and/or the associated beam metric (e.g., L1-RSRP or L1-SINR) is reported by Uplink Control Information (UCI) sent via a first layer 1 (L1) channel (such as PUCCH or PUSCH), e.g., as configured by the higher layer parameter CSI-ReportConfig; and the correspondence is reported by a second UCI (different from the first UCI) transmitted via a second L1 channel. In one example, PUSCH may be one of the examples described above. In one example, two separate UCI corresponds to a two-part UCI (as in rel.15nr specifications).

In one example, the correspondence or index I is reported separately from a resource indicator R (e.g., CRI or SSBRI) and/or an associated beam metric (e.g., L1-RSRP or L1-SINR), where the resource indicator R (e.g., CRI or SSBRI) and/or the associated beam metric (e.g., L1-RSRP or L1-SINR) is reported by Uplink Control Information (UCI) sent via a layer 1 (L1) channel (such as PUCCH or PUSCH), e.g., as configured by the higher layer parameter CSI-ReportConfig; and the correspondence is reported via a layer 2 (L2) channel, e.g., an UL channel carrying a MAC CE (e.g., UL MAC CE). In one example, if PUSCH is used as the L1 channel, PUSCH may be one of the examples described above. In one example, if a MAC CE is used as an L2 channel, it may be according to at least one of the following examples.

● In one example, the L2 channel is an existing L2 channel carrying a MAC CE.

In one example, the existing MAC CE is a single entry PHR MAC CE (code point/index 57 in table 22, from table 6.2.1-2 of TS 38.321), i.e., the single entry MAC CE includes information about the correspondence, either via existing parameters or via new parameters.

In one example, the existing MAC CE is a multi-entry PHR MAC CE (code points/indices 54 or 56 in table 22, from table 6.2.1-2 of TS 38.321), i.e., the multi-entry MAC CE includes information about correspondence, either via existing parameters or via new parameters.

In one example, the existing MAC CE is a MAC CE that includes a UL BWP ID, e.g., one of the following:

■ SP CSI reporting MAC CE for PUCCH activation/deactivation

■ SP SRS activation/deactivation MAC CE

■ PUCCH spatial relationship activation/deactivation MAC CE

■ Enhanced PUCCH spatial relationship activation/deactivation MAC CE

■ Enhanced SP/AP SRS spatial relationship indication MAC CE

■ SRS pathloss reference RS update MAC CE

■ PUSCH pathloss reference RS update MAC CE

■ SRS spatial relationship indication MAC CE based on service cell set

■ SP positioning SRS activation/deactivation MAC CE

In one example, the existing MAC CE is a MAC CE that includes a DL BWP ID, e.g., one of the following:

■ SP CSI-RS/CSI-IM resource set activation/deactivation MAC CE

■ Aperiodic CSI trigger state part selection MAC CE

■ TCI status activation/deactivation of UE-specific PDSCH MAC CEs

■ SP ZP CSI-RS resource set activation/deactivation MAC CE

■ Enhanced TCI status activation/deactivation of UE-specific PDSCH MAC CE

● In one example, the L2 channel is a new (dedicated) L2 channel, such as a new MAC CE (e.g., a new UL MAC CE or a new DL MAC CE) for the correspondence.

In one example, an entry (table 22) corresponding to code point/index 47 of the UL MAC CE is for the new UL MAC CE.

In one example, an entry (table 22) corresponding to the code point/index 44 of the UL MAC CE is for the new UL MAC CE.

In one example, an entry (Table 22) corresponding to one of the code points/indices 35-44 of the UL MAC CE is for the new UL MAC CE.

In one example, an entry (table 22) corresponding to code point/index 63 of the UL MAC CE is for the new UL MAC CE.

Table 23: LCID value for UL-SCH

In one example, the correspondence or index I is reported separately from the resource indicator R (e.g., CRI or SSBRI) and/or associated beam metric (e.g., L1-RSRP or L1-SINR), wherein the resource indicator R (e.g., CRI or SSBRI) and/or associated beam metric (e.g., L1-RSRP or L1-SINR) is reported via a first UL channel (such as PUCCH or PUSCH), e.g., as configured by the higher layer parameters CSI-ReportConfig; and the correspondence is reported via a second UL channel, e.g., a UL channel carrying a MAC CE (e.g., UL MAC CE). The two UL channels may be PUCCH, PUSCH, UL MAC CE, or any other UL channel.

In one embodiment, the UE is configured with multiple SRS resources (see UL-fullflowertransmission=fullflowemode 2 in rel.16nr specification) with the same number of SRS ports (e.g., 1-port SRS resources for non-codebook based UL transmissions) or different numbers of SRS ports (e.g., for codebook based UL transmissions) within the SRS resource set. In one example, this configuration is configured when the UE is equipped with multiple antenna panels, or when the UE reports (e.g., via UE capability reporting) that it is able to support panel selection/activation or is able to support/report different values of the maximum number of supported SRS ports (as described in this disclosure). In one example, the SRS resource set is configured with a higher layer parameter usage set to indicate a "codebook" (see section 6.1.1.1 of REF 9) of a codebook-based UL transmission. In one example, the SRS resource set is configured with higher layer parameters usages set to indicate "codebook" (see section 6.1.1 of REF 9) for codebook-based UL transmissions or "non codebook" (see section 6.1.1.2 of REF 9) for non-codebook-based UL transmissions.

For such UEs, an SRI field in the UL-related DCI (e.g., DCI format 0_1 or 0_2 in the NR specification) may be used to indicate one of a plurality of SRS resources (e.g., for the case of codebook-based UL transmissions). In particular, the SRI may indicate (a) an implicit Acknowledgement (ACK) (correspondence index) of the NW successfully receiving and following the reported capability and (B) SRS resources of the plurality of SRS resources that are aligned (or correspond) to the reported capability index, wherein the reported capability index indicates one of the capability types as described in the present disclosure. For example, one of the capability types may be the maximum supported number of SRS ports reported by the UE with the beam report. For the case of codebook-based UL transmissions, the payload indicated by the SRI field is Bits, where N _SRS Is the number of SRS resources in the configured SRS resource set.

For the case of non-codebook based UL transmissions, the SRI may indicate (a) an implicit Acknowledgement (ACK) and (B) L SRS resources of the plurality of SRS resources that are aligned (or correspond) to a reported capability index, wherein the reported capability index indicates one of the capability types as described in the present disclosure. For example, one of the capability types may be the maximum supported number of SRS ports reported by the UE with the beam report. Here, L is the number of layers (or rank value) for non-codebook based UL transmission. In one example, 1.ltoreq.L.ltoreq.N _SRS,x Wherein N is _SRS,x Is the value of the maximum number of supported SRS ports reported by the UE. Further, for non-codebook based UL transmissions, each SRS resource may be a 1-port SRS resource.

For the case of codebook-based UL transmission, at least one of the following examples is used/configured.

In one example, when the number of SRS resources is 2, one SRS resource has n ₁ The SRS ports, another SRS resource has n ₂ The SRI field value may indicate one SRS resource and an implicit ACK, as described in Table 24. In one example, for a UE with a maximum (or a total) of 2 antenna ports (across all antenna panels), (n ₁ ,n ₂ ) = (1, 2) or (2, 1). In one example, for a UE with a maximum (or a total) of 4 antenna ports (across all antenna panels), (n ₁ ,n ₂ ) = (1, 2) or (2, 1), (1, 4) or (4, 1), (4, 2) or (2, 4).

Table 24

In one example, the SRS resource number is 3. In one example, the SRS resource number may be 3 only when the UE supports a maximum of 4 antenna ports.

● For example, when there are two having n ₁ SRS resource of SRS ports and one with n ₂ The SRI field value may indicate one SRS resource and an implicit ACK when SRS resources of the SRS port are utilized, as described in table 25. In one example, for a cell having the most (or a total of) UE with 2 antenna ports (across all antenna panels), (n ₁ ,n ₂ ) = (1, 2) or (2, 1). In one example, for a UE with a maximum (or a total) of 4 antenna ports (across all antenna panels), (n ₁ ,n ₂ ) = (1, 2) or (2, 1), (1, 4) or (4, 1), (4, 2) or (2, 4).

● For example, when there is a single having n ₁ SRS resource of SRS ports, one with n ₂ SRS resource of SRS ports and one with n ₃ The SRI field value may indicate one SRS resource and an implicit ACK when SRS resources of the SRS port are utilized, as described in table 26. In one example, (n) ₁ ,n ₂ ,n ₃ ) = (1, 2, 4), (1, 4, 2), (2, 1, 4), (2, 4, 1), (4, 1, 2) or (4, 2, 1).

Table 25

Table 26

In one example, the SRS resource number is 4. In one example, the SRS resource number may be 4 only when the UE supports a maximum of 4 antenna ports.

● For example, when there are two having n ₁ SRS resources for a number of SRS ports and two with n ₂ The SRI field value may indicate one SRS resource and an implicit ACK when SRS resources of the SRS port are utilized, as described in table 27. In one example, for a UE with a maximum (or a total) of 2 antenna ports (across all antenna panels), (n ₁ ,n ₂ ) = (1, 2) or (2, 1). In one example, for a UE with a maximum (or a total) of 4 antenna ports (across all antenna panels), (n ₁ ,n ₂ ) = (1, 2) or (2, 1), (1, 4)Or (4, 1), (4, 2) or (2, 4).

● In one example, when there are three having n ₁ SRS resource of SRS ports and one with n ₂ The SRI field value may indicate one SRS resource and an implicit ACK when SRS resources of the SRS port are utilized, as described in table 28. In one example, for a UE with a maximum (or a total) of 2 antenna ports (across all antenna panels), (n ₁ ,n ₂ ) = (1, 2) or (2, 1). In one example, for a UE with a maximum (or a total) of 4 antenna ports (across all antenna panels), (n ₁ ,n ₂ ) = (1, 2) or (2, 1), (1, 4) or (4, 1), (4, 2) or (2, 4).

● In one example, when there are two having n ₁ SRS resource of SRS ports, one with n ₂ SRS resource of SRS ports and one with n ₃ The SRI field value may indicate one SRS resource and an implicit ACK when SRS resources of the SRS port are utilized, as described in table 29. In one example, (n) ₁ ,n ₂ ,n ₃ ) = (1, 2, 4), (1, 4, 2), (2, 1, 4), (2, 4, 1), (4, 1, 2) or (4, 2, 1).

Table 27

Table 28

Table 29

In one embodiment, which is a variation of the above embodiment, the ACK mechanism is explicit via dedicated signaling.

● In one example, higher layer (RRC) parameters (new or existing parameters) are used to indicate an ACK.

● In one example, a MAC CE indication (new or existing MAC CE) is used to indicate an ACK.

● In one example, the DCI-based indication is used to indicate an ACK. For example, a 1-bit DCI field (or code point value) in DCI (e.g., UL-DCI formats 0_1 and 0_2) or dedicated DCI (separate from UL-DCI) is used for this indication.

In this case, the payload of the SRI indication depends on the explicit ACK. Specifically, for the case of codebook-based UL transmission, the SRI payload isBits, where N _SRS,x Is the number of SRS resources with x SRS ports in the configured SRS resource set. The bit field (or index) of the SRI indication is mapped to an index of SRS resources in the SRS resource set for which the number of SRS ports is equal to x.

In one embodiment, the UE is configured with multiple SRS resource sets (e.g., two SRS resource sets), where each SRS resource set includes SRS resource(s) having the same number of SRS ports, but the number of SRS ports varies between SRS resource sets. For example, the UE is configured with two SRS resource sets, S1 and S2, where S1 includes a set of SRS resources having n ₁ SRS resource (S) of SRS ports, S2 includes a plurality of SRS resources having n ₂ SRS resource(s) of SRS ports, and n ₁ ≠n ₂ . In one example, n for a UE having a total of 2 antenna ports ₁ And n ₂ Belonging to {1,2}, n for a total of 4 antenna ports ₁ And n ₂ Belonging to {1,2,4} or {2,4}. Note that the number of SRS ports is the same for all SRS resources within a set of SRS resources, but the number of SRS ports is different between sets of resources (i.e., sets). In one example, each SRS resource set includes only one SRS resource. In one example, each SRS resource set may include only one SRS resource or a plurality of SRS resources. In one example, the SRS resource set corresponds to (or is associated with) an antenna panel at the UE. In one example, when a UE is equipped with multiple antenna panels, or when the UE reports (e.g., via UE capability reporting), it can support panel selection/activation or can support/report maximum support This configuration of multiple SRS resource sets is configured at different values of the number of SRS ports held (as described in this disclosure). In one example, the SRS resource set is configured with a higher layer parameter usage set to indicate a "codebook" (see section 6.1.1.1 of REF 9) of a codebook-based UL transmission.

For such UEs, the SRI field in the UL-related DCI (e.g., DCI format 0_1 or 0_2 in the NR specification) may be used to indicate one of a plurality of SRS resources (e.g., for the case of codebook-based UL transmissions). In particular, the SRI may indicate (a) that the NW successfully receives and follows an implicit Acknowledgement (ACK) of the reported capability (correspondence index), (B) one of the plurality of SRS resource sets, and (C) SRS resource(s) of the SRS resource(s) within the indicated SRS resource set, wherein the indicated SRS resource set and SRS resources (B and C) are aligned (or correspond) to the reported capability index, wherein the reported capability index indicates one of the capability types as described in the present disclosure. For example, one of the capability types may be the maximum supported number of SRS ports reported by the UE with the beam report. For the case of codebook-based UL transmissions, the payload indicated by the SRI field is Bits, where N _SRS,tot Is the total number of SRS resources across all the configured SRS resource sets.

In one example, when the number of SRS resource sets is 2, one SRS resource set has n(s) ₁ The port SRS resources, another SRS resource set has n(s) ₂ The port SRS resources, SRI field value may indicate one SRS resource set, one SRS resource, and an implicit ACK, as described in table 30. In one example, for a UE with a maximum (or a total) of 2 antenna ports (across all antenna panels), (n ₁ ,n ₂ ) = (1, 2) or (2, 1). In one example, for a UE with a maximum (or a total) of 4 antenna ports (across all antenna panels), (n ₁ ,n ₂ ) = (1, 2) or (2, 1), (1, 4) or (4, 1), (4, 2) or (2, 4).

Table 30

In one example, the number of SRS resource sets is 2 and the number of SRS resources in each set is 2. The first group has two SRS resources with SRS ports, and the second group has two SRS resources with SRS ports. The SRI field value may indicate one SRS resource set, one SRS resource, and an implicit ACK, as shown in table 31. In one example, or for a UE with a maximum (or a total) of 2 antenna ports (across all antenna panels). In one example, for a UE with a maximum (or a total) of 4 antenna ports (across all antenna panels), either or. n is n ₁ n ₂ (n ₁ ,n ₂ )＝(1,2)(2,1)(n ₁ ,n ₂ )＝(1,2)(2,1)(1,4)(4,1)(4,2)(2,4)

Table 31

In one embodiment, the UE is configured with multiple SRS resource sets (e.g., two SRS resource sets), where each SRS resource set includes multiple SRS resources (e.g., 1-port SRS resources) having the same number of SRS ports, but the number of SRS resources is different between SRS resource sets. In one example, the SRS resource set is configured with a higher layer parameter usage set to indicate a "non codebook" (see section 6.1.1.2 of REF 9) of non codebook based UL transmissions.

For the case of non-codebook based UL transmissions, SRI may beIndicating (a) an implicit Acknowledgement (ACK), (B) one of the plurality of SRS resource sets, and (C) L of the SRS resources within the indicated SRS resource set, wherein the indicated SRS resource set and the L SRS resources (B and C) are aligned (or correspond) to a reported capability index, wherein the reported capability index indicates one of the capability types as described in the present disclosure. For example, one of the capability types may be the maximum supported number of SRS ports reported by the UE with the beam report. Here, L is the number of layers (or rank value) for non-codebook based UL transmission. In one example, 1.ltoreq.L.ltoreq.N _SRS,x Wherein N is _SRS,x Is the value of the maximum number of supported SRS ports reported by the UE. Further, for non-codebook based UL transmissions, each SRS resource may be a 1-port SRS resource.

In one embodiment, which is a variation of one or more of the embodiments described above, the ACK mechanism is explicit via dedicated signaling.

In this case, the payload of the SRI indication depends on the explicit ACK. Specifically, for the case of codebook-based UL transmission, the SRI payload isBits, where N _SRS,x Is the total number of SRS resources with x SRS ports across all configured SRS resource sets. The bit field (or index) of the SRI indication is mapped to an index of SRS resources with a number of SRS ports equal to x across all SRS resource sets.

In one embodiment, a UE equipped with multiple antenna panels is (NW) configured with N with different numbers of SRS ports within an SRS resource set _SRS >1 SRS resource. This configuration may be via higher layer (RRC) signaling. In one example, such SRS resource sets may be configured when the UE is also configured with at least one of the following examples regarding UL transmissions (e.g., of PUSCH).

● In one example, the UL transmission corresponds to a full power transmission mode (e.g., full power mode2 from the rel.16NR specification). Existing RRC parameters may be used for this purpose. One example of an existing RRC parameter is that fullpower transmission-r16 is set to "fullpower mode2" (as supported in the rel.16nr specification). According to this example, for a multi-plane UE, UL transmission is configured by setting fullpower transmission-r16 to "fullpower mode2".

● In one example, UL transmissions are configured via new RRC parameters. An example of a new RRC parameter is FullPowerTransmit-r 17 or MPUETransmit-r 17.

● In one example, UL transmission is configured via a new RRC parameter, however, when configuring the new parameter, it is desirable to set the rel.16 RRC parameter fullpower transmission-r16 to "fullpower mode2".

In one example, the above configuration example may be used only for codebook-based UL transmissions. In one example, they may be used for codebook-based UL transmissions and non-codebook-based UL transmissions.

SRI indication (indication N) _SRS >One of the 1 SRS resources) may be according to at least one of the following examples.

In one example, the SRI payload remains unchanged, i.eThe bit, regardless of the reported capability, i.e., the value v = the maximum supported number of SRS ports reported by the UE with beam reporting.

In one example, the SRI payload is dependent on and determined based on the reported capability, i.e., v-value = the maximum supported number of SRS ports reported by the UE with beam reporting.

When the number of SRS ports (within the SRS resource set) for which only one SRS resource exists is equal to the reporting value (v), at least one of the following examples is used/configured.

● In one example, SRI payload=0, meaning that the SRI field is not present (not indicated/configured). In this case, there is no signaling/indication/ACK (from NW to UE) as to whether the NW received a beam report with v value or whether it acknowledges the received value.

● In one example, SRI payload=0, meaning that the SRI field is not present (not indicated/configured). The absence of the SRI field (from NW to UE) is indicated/acknowledged via the medium/channel. The medium/channel may be RRC or MAC CE or DCI (dedicated DCI different from UL-DCI, e.g. formats 0_1 and 0_2). Alternatively, the medium/channel is a two-part DCI comprising DCI part 1 and DCI part 2, wherein DCI part 1 comprises information (e.g., a 1-bit field) to indicate whether an SRI field is absent (not indicated) or present (indicated) via DCI part 2, DCI part 2 comprises an SRI field (when indicated as such).

● In one example, the SRI payload is 1 bit to indicate (or acknowledge) that the NW received the value v. In one example, SRI value=0 for the ACK. In one example, SRI value=1 is used for the ACK. In one example, another (not used for ACK) SRI value is used for NACK (indicating that the NW either did not receive the value v, or did not follow the value v, or both).

● In one example, the SRI payload is according to one or more of the examples described above when the value v is less than the total number of antenna ports (across the panel), otherwise the SRI payload is according to one or more of the examples described above when v = the total number of antenna ports (across the panel).

When there are more than one SRS resource (within the SRS resource set) with a number of SRS ports equal to the reporting value (v), the SRI is indicated and its payload (number) is determined based on such number of SRS resources (with v SRS ports). Let N be _SRS,v Is the number of such SRS resources. At least one of the following examples is used/configured.

● In one example, the SRI payload isBit, and it indicates N _SRS,v One of the SRS resources having v SRS ports.

● In one example, the SRI payload isA bit indicating ACK (from NW to UE in response to a report value v) and N _SRS,v One of the SRS resources having v SRS ports. In one example, 1 bit is used for indication of ACK, +.>Bits for indicating N _SRS,v One of the SRS resources having v SRS ports. In one example, the SRI indication includes two separate parts (subfields), one for the ACK and the other for the SRS resource indication.

● In one example, the SRI payload isBits, where N _SRS,v SRI values (e.g., 0,1, …, N _SRS,v -1) for joint indication of ACK and one of SRS resources with v SRS ports, one SRI value (e.g. sri=n _SRS,v ) For indicating a NACK (indicating that the NW either did not receive the value v or did not follow the value v, or both).

● In one example, the indication/configuration of the SRI payload via the medium/channel (from NW to UE) is kept unchanged [Bit) or (according to the reported value v in one or more of the examples described above +.>Bit or +.in one or more examples above>Bits or one or more of the examples described above Bits). The medium/channel may be RRC or MAC CE or DCI (dedicated DCI different from UL-DCI, e.g. formats 0_1 and 0_2). Alternatively, the medium/channel is a two-part DCI comprising a DCI part 1 and a DCI part 2, wherein the DCI part 1 comprises information (e.g., a 1-bit field) to indicate that the SRI payload remains unchanged or changes, and the DCI part 2 comprises an SRI field with the indicated payload.

In one example, according to the method as one or more examples described above (when N _SRS,v =1) and iii.5.2.B (when N _SRS,v >1) The SRI indication and its payload are determined/configured in which (a, b) is fixed or configured from { (1, 4), (1, 5), (1, 6), (1, 7), (2, 4), (2, 5), (2, 6), (2, 7), (3 or 3a, 4), (3 or 3a, 5), (3 or 3a, 6), (3 or 3a, 7) }.

In one example, the configuration as described above is subject to (depends on) UE capability reporting.

● In one example, the UE capability report includes a Feature Group (FG) that includes an element indicating a multi-panel UE (mpre) or a UE equipped with multiple antenna panels (rel.17). In one example, such a UE must also support (and thus report) support for full power mode2 from the rel.16nr specifications (ul-FullPwrMode 2-MaxSRS-ResInSet-r16 and/or ul-FullPwrMode 2-SRSConfig-diffnumsrsport-r 16, TS 38.306).

● In one example, the UE capability report includes 2 FGs, one FG for supporting the MPUE and another FG for supporting full power mode 2.

● In one example, the UE capability report includes 1 FG with 2 components, one component for supporting the MPUE and another component for supporting full power mode 2.

● Details of FGs on SRS resources from different numbers of SRS ports may also be included

In one example, SRS resource number N _SRS The maximum value of (as in this embodiment) is fixed, e.g., N _SRS =2 or N _SRS =3 or N _SRS =4. In one example, SRS resource number N _SRS May be up to x, where x may be configured or may be subject to UE capability reporting (e.g., ul-FullPwrMode2-MaxSRS-ResInSet-r 16). In one example, x=4. In one example, the UE reports the value of x via UE capability reporting or via dynamic beam or CSI reporting.

In one example, the mapping between the SRIs (bit fields) or indexes and the indexes of the SRS resources within the SRS resource set is done one-to-one in increasing order, i.e. the lowest SRIs (bit fields) or index values (e.g. 0) are mapped to SRS resources with the smallest resource IDs and a smaller number of SRS ports. Three examples are shown in tables 32 to 34, where for i=1, 2, n ₁ <n ₂ And I _i,1 <I _i,2 。

Table 32: n (N) _SRS ＝2

Table 33: n (N) _SRS ＝3

Table 34: n (N) _SRS ＝4

In one embodiment, a UE equipped with multiple antenna panels is (NW) configured with N with different numbers of SRS ports within an SRS resource set _SRS >1 SRS resource.

The payload (number of bits) of the TPMI/TRI indication may be according to at least one of the following examples.

In one example, the TPMI/TRI payload remains unchanged regardless of the reported capability, i.e., the value v = the maximum supported number of SRS ports reported by the UE with beam reporting.

In one example, the TPMI/TRI payload is dependent on the reported capability and is determined based on the reported capability, i.e., the value v = the maximum supported number of SRS ports reported by the UE with the beam report.

The payloads (number of bits) indicated by both SRI and TPMI/TRI may be fixed or may vary depending on the value of v, with details according to one or more examples described in one or more of the embodiments above.

The present disclosure includes the following components for implementing a beam measurement and report selection procedure, where beam measurement and reporting may include additional information regarding the status of each beam report, and the status may be related to MPE events, multiple UE panels, whether beam reporting is for DL only or UL only or both DL and UL, etc.

FIG. 16 illustrates a device configured to measure P in accordance with an embodiment of the present disclosure ₁ Flowchart 1600 for a UE of DL measurement RS resources. Shown in fig. 16 configured to measure P ₁ The embodiment of the flowchart 1600 of a UE for DL measurement RS resources is for illustration only. FIG. 16 does not limit the scope of the present disclosure to being configured to measure P ₁ Any particular embodiment of flowchart 1600 for a UE of DL measurement RS resources.

In one embodiment, as shown in FIG. 16, the UE is configured (NW/gNB) to measure (receive) P ₁ DL measurement RS resources (such as CSI-RS or SSB), where P ₁ And is more than or equal to 1. Such configuration may be performed via higher layer (RRC) signaling. Alternatively, NW/gNB may dynamically signal/update the set (subset) of DL measurement RS resources via L1 or L2 DL control (PDCCH or MAC CE). These resources are used by the UE to follow different beams or spatial directionsBeam measurements are performed towards (indicated by beam forming/precoding operations performed at NW/gNB that are transparent to the UE).

The UE is also configured (NW/gNB) to report a beam report, wherein the beam report includes Q ₁ Resource indicators (I) or Q ₁ Pair (I, J) = (resource indicator, beam metric), where Q ₁ ≤P ₁ . In one example, Q ₁ =1. In one example, Q is configured via RRC and/or MAC CE ₁ . The beam metric may represent a link quality associated with the DL channel (or UL channel because the beam correspondence holds). Examples of beam metrics include L1-RSRP, L1-SINR, CQI, or hypothesized BLER, or virtual PHR, or UL RSRP, or any other beam metrics. The resource indicator indicates that the resource is from P ₁ DL measurement RS resource index of each DL measurement RS resource. Examples of the resource indicator include CRI (when DL measurement RS is CSI-RS) and SSB-RI (when DL measurement RS is SSB)

In one example, when the UE is equipped with X>1 antenna panel, Q ₁ =x, and reports one resource indicator (I) or a pair of (I, J) = (resource indicator, beam metric) for each antenna panel. In one example, when the UE is equipped with X>1 antenna panel, Q ₁ Gtoreq X, and reporting at least one resource indicator (I) or a pair (I, J) = (resource indicator, beam metric) for each antenna panel. P (P) ₁ The set of DL measurement RS resources may be partitioned into X subsets, one subset per antenna panel. Or P ₁ The DL measurement RS resources are a superset covering X sets, one set per antenna panel. In one example, information about the X panels is not provided to the NW/gNB. In one example, information about the X panels is provided to the NW/gNB. For example, information about the panel ID may be implicitly included/reported (e.g., according to the resource indicator (I)). Or may explicitly include/report information about the panel ID(s) (e.g., by including/reporting the panel ID(s) in the beam report).

Except for Q ₁ Resource indicators (I) or Q ₁ The beam report may include, in addition to the pair (I, J) = (resource indicator, beam metric) pair, a signal for (by NW/gN)B) UL TX beam selection/indicated UE recommendation (UE-reception). The time domain behaviour of the beam measurements and/or beam reports may be configured as Aperiodic (AP), semi-persistent (SP) or periodic (P). The time domain behavior of the beam measurement RS may be configured as Aperiodic (AP), semi-persistent (SP), or periodic (P).

The UE recommendation may be reported using the joint parameters (or indicators) along with other components included in the beam report. For example, the UE recommendation may be reported in conjunction with at least one resource indicator. Or may report UE recommendations in conjunction with at least one beam metric. Or may report UE recommendations in conjunction with at least one pair (resource indicator, beam metric).

Or may report the UE recommendation separately (independently) from other components in the beam report using a separate parameter (or indicator). Reporting configurations may be joint (one configuration) or separate (two configurations), one for UE recommendation and the other for other components in the beam report.

Or reports recommended to the UE are separate from other components in the beam report, i.e. one report is used for UE recommendation and another report is used for other components in the beam report. Reporting configurations may be joint (one configuration) or separate (two configurations), one for UE recommendation and the other for other components in the beam report.

Note that UE recommendations may not be limited to any particular event (such as MPE), but rather are generic and thus applicable to any event of interest to the UE, such as MPE mitigation, fast panel selection, fast beam switching, avoiding beam failure (as described above).

In one sub-embodiment, the content recommended by the UE is determined (or configured) according to at least one of the following examples.

In one example, the UE recommendation includes Q ₂ Additional (beam) resource indicators. In one example, Q ₂ Is fixed, e.g. Q ₂ =1. In one example, Q ₂ Is configured. In one example, Q ₂ Reported by the UE, e.g. as part of beam reporting(i.e., UE recommendation). In one example, the UE may report Q ₂ The value is zero, and in another example, the UE may report Q ₂ Is a non-zero (positive) value. In another example, the UE may be configured with Q ₂ Maximum value (v) and the UE can report any Q ₂ Value of Q ₂ E {1,2, …, v } or {0,1,2, …, v }.

In one example, the UE recommendation includes Q ₂ For the appended (O, J) = (resource indicator, beam metric). In one example, Q ₂ Is fixed, e.g. Q ₂ =1. In one example, Q ₂ Is configured. In one example, Q ₂ Reported by the UE, e.g., as part of a beam report (i.e., UE recommendation). In one example, the UE may report Q ₂ With a value of zero, in another example, the UE may report Q ₂ Is a non-zero (positive) value. In another example, the UE may be configured with Q ₂ Maximum value (v) and the UE can report any Q ₂ Value of Q ₂ E {1,2, …, v } or {0,1,2, …, v }.

In one example, the UE recommendation includes an ID, where the ID may be associated with a subset of DL measurement RS resources. In one example, P ₁ The set of DL measurement RS resources may be partitioned into X subsets, and the X-th subset includes M _x DL measurement RS resources such thatAn ID (e.g., subset ID) indicates one of the X subsets. In one example, P ₁ The DL measurement RS resources are supersets covering X sets, and the xth set includes M _x DL measurement RS resources such thatAn ID (e.g., a set ID) indicates one of the X sets. In one example, the ID may be associated with an antenna panel (e.g., panel ID) of a UE equipped with multiple antenna panels.

In one example, the UE recommendation includes an ID and Q ₂ Additional (beam) resource indicators, wherein the ID is according to one or more of the aboveDescription in multiple examples, and Q ₂ The additional (beam) resource indicators are according to the description in one or more of the examples above. In one example, Q ₂ Additional (beam) resource indicators may be associated with the ID (depending on or derived from or based on the ID). In one example, Q ₂ The additional (beam) resource indicators may be independent of the ID.

In one example, the UE recommendation includes an ID and Q ₂ For additional (I, J) = (resource indicator, beam metric), where ID is according to the description in one or more examples above, and Q ₂ For the additional (I, J) = (resource indicator, beam metric) according to the description in one or more of the examples above.

In one sub-embodiment, the recommended report for the UE may be determined (or configured) according to at least one of the following examples.

In one example, the UE recommendation may always be included in the beam report (i.e., reported by the UE).

In one example, a UE recommendation may always be included in a beam report (i.e., reported by a UE) when a condition is met, for example, that the UE is equipped with multiple antenna panels, or that the UE reports it (UE recommendation) as part of its UE capabilities, or that the UE may detect an event of interest.

In one example, the recommended reporting to the UE may be configured (turned on/off), e.g., via RRC and/or MAC CE and/or DCI. When configured (on), the UE recommendation is always included in the beam report.

In one example, the UE decides (can freely decide) whether the UE recommendation is included in the beam report, i.e. the UE may or may not include the UE recommendation in the beam report. Such a decision may be made based on events of interest, for example. In one example, beam reporting (with or without UE recommendation) is reported via a portion of UCI (similar to WB CSI reporting in rel.15nr, the UE may append a fixed number of zeros to ensure that the payload remains unchanged, regardless of whether the UE reports the UE recommendation or not). In one example, beam reporting (with or without UE recommendation) is reported via a two-part UCI, where part 1UCI includes information whether the UE reports the UE recommendation. If the information indicates that the UE recommendation is reported, reporting is via part 2 UCI.

In one example, the reported capability recommended to the UE is reported by the UE (e.g., via UE capability reporting or as part of UL transmission). Depending on the reported UE capabilities, the NW/gNB may configure (or trigger) the recommended reporting of the UE via RRC and/or MAC CE (and/or DCI). The UE reports UE recommendations according to configuration/trigger from NW/gNB.

Upon receiving the beam report, the NW/gNB configures/indicates a UL TX beam indication (which may be the same as the DL TX beam indication because the beam correspondence holds) to the UE for UL transmission, wherein the beam indication indicates (a) a message, or (B) n≡1 UL TX beam, or (C) both a message and n≡1 UL TX beam. The beam indication may be via DL-TCI or UL-TCI or J-TCI (joint TCI) or other functionally equivalent entities such as spatialreactive info or SRI indicated via DCI and/or MAC CE and/or RRC. In one example, n=1. In one example, n=2.

In one sub-embodiment, when the beam report does not include a UE recommendation, the beam indication is determined (or configured) according to at least one of the following examples.

In one example, when Q ₁ When =1 resource indicators are included in the beam report, the beam indication may only indicate (a) a message, where the message corresponds to an ACK message to indicate that n=1 UL TX beams correspond to Q included in the beam report ₁ A resource indicator. Some details of the ACK message may be according to the same as described in the embodiments.

In one example, when Q ₁ When =1 resource indicators are included in the beam report, the beam indication may indicate (a) a message or (B) n+.1 UL TX beams, where for (a) the message corresponds to an ACK message to indicate that n=1 UL TX beams correspond to Q included in the beam report ₁ The resource indicators, while for (B), the N.gtoreq.1 UL TX beams are based on P measured by the UE ₁ DL measurement RS resources. Some details of the ACK message may be according to the same as described in the embodiments.

In one example, the beam indication may only indicate (B) N+.1 UL TX beams, where N+.1 UL TX beams are based on P measured by the UE ₁ DL measurement RS resources.

In one sub-embodiment, when the beam report includes a UE recommendation, the NW/gNB may confirm to the UE whether it follows the UE recommendation, and accordingly, determine (or configure) the beam indication according to at least one of the following examples. Some details of the ACK message may be according to the same as described in the embodiments.

In one example, NW/gNB follows the UE recommendation and the beam indication includes (a) an ACK message to the UE. In this case, NW/gNB may not indicate N+.1 UL TX beams. Alternatively, NW/gNB may indicate (B) that N+.1 UL TX beams. Alternatively, whether NW/gNB indicates (B) n+.1 UL TX beams may depend on the UE recommendation. For example, when the UE recommendation includes Q ₂ When=1 additional (beam) resource indicators, NW/gNB does not indicate (B).

In one example, NW/gNB does not follow UE recommendations, it either does not send ACK messages or sends NACK/NULL messages to the UE. The NW/gNB indication includes beam indications of (B) n+.1 UL TX beams. The beam indication may be based on the Q included in the beam report ₁ A resource indicator. Or the beam indication may be based on Q included in the beam report ₁ The resource indicators, and if included in the UE recommendation, may also be based on Q ₂ A resource indicator.

In one example, the NW/gNB signals an ACK message included in the beam indication only when the UE provides (reports) the UE recommendation.

In one sub-embodiment, an ACK (or NACK/NULL) message is determined (or configured) to signal to the UE according to at least one of the following examples. Some details of the ACK message may be according to the same as described in the embodiments.

In one example, the signaling of the ACK message is via a dedicated (separate) parameter or field. The dedicated parameter or field may be indicated via DCI, which may be UL-DCI (scheduling UL grant), or DL-DCI (scheduling DL transmission), or separate DCI for beam (TCI state) indication (UL-TCI-DCI or DL-TCI-DCI or TCI-DCI). Alternatively, the dedicated parameter or field may be indicated via a channel other than DCI (e.g., PDSCH or MAC CE). In one example, the dedicated field corresponds to a 1-bit indication, wherein a bit value of 0 indicates an ACK message (optionally, 1 indicates a NACK/NULL message), or vice versa, i.e., 1 indicates an ACK message (optionally, 0 indicates a NACK/NULL message). In one example, the dedicated parameter may take a value v0 indicating an ACK message (optionally, a value v1 indicating a NACK/NULL message).

In one example, the signaling of the ACK message is performed in conjunction with parameters or fields that may be indicated via DCI or a channel other than DCI as described above. In one example, this field corresponds to a B-bit indication, where when the B-bit indication is equal to the fixed bit sequence B ₀ b ₁ …b _B-1 When it indicates an ACK message. In one example, the fixed bit sequence is all zeros, b ₀ b ₁ …b _B-1 =00 …. In one example, the fixed bit sequence is all 1's, i.e., b ₀ b ₁ …b _B-1 =11 …. For example, when b=3, i.e., 3-bit indication is used for beam indication, code point 000 (or 111) may be used for indicating an ACK message. The remaining bit sequence values may be used to indicate other DL or UL related parameters (such as an indication of n≡1 UL TX beams when the gNB/NW is not signaling an ACK message).

In one example, signaling of the ACK (or NACK/NULL) message is configured (turned on/off) to the UE via RRC and/or MAC CE. When configured (turned on), the signaling is performed according to at least one of the above examples. Some details of the ACK message may be according to the same as described in the embodiments.

In one example, a field (code point) value or parameter value of an ACK (or NULL/NACK) message is reserved and cannot be used for other purposes, regardless of whether the UE is configured to report an ACK (or NULL/NACK) message.

In one example, when configured (on), a field (code point) value or parameter value of an ACK (or NULL/NACK) message is used to indicate the ACK (or NULL/NACK) message, otherwise (off), it is used to indicate other DL or UL related parameters (such as an indication of n≡1 UL TX beam when the gNB/NW is not signaling an ACK message).

In one sub-embodiment, the UE provides two sets of reports, either with the same report or separated in two different reports, wherein;

the first report (sub-report) is a beam report comprising the resource indicator(s) and possible beam metrics, not reflecting the recommendation of the UE.

The second report (sub-report) is a beam report comprising the resource indicator(s) and possible beam metrics reflecting the recommendation of the UE.

In one example, such behavior may be configured/triggered to the UE via RRC and/or MAC CE and/or DCI. When configured, the UE provides two reports (sub-reports), otherwise it provides one report (first report). In one example, the configuration and/or trigger is UE-specific, in another example the configuration and/or trigger is UE group-specific, and in another example the configuration and/or trigger is cell-specific.

In one sub-embodiment, as described above (and elsewhere in this disclosure), the UE is configured to report UE recommendations, where its reporting is limited. At least one of the following examples, or a combination of a plurality of the following examples, is used (or configured) as a limitation.

In one example, the limit is with respect to the resource type. The resource type may be CSI-RS or SSB (including Q1 resource indicators or Q1 pair resource indicators and beam metrics) for beam reporting. However, for a UE recommendation, it may be according to at least one of the following examples.

● In one example, the resource type may be CSI-RS or SSB (including Q2 resource indicators or Q2 pair resource indicators and beam metrics) for UE recommendation.

● In one example, the resource type may be CSI-RS (including Q2 resource indicators or Q2 pair resource indicators and beam metrics) for UE recommendation.

● In one example, the resource type may be SSB (including Q2 resource indicators or Q2 pair resource indicators and beam metrics) for UE recommendation.

In one example, the limit is based on Q ₁ Is a value of (2). At least one of the following examples may be used.

● In one example, only when Q ₁ =1, i.e. reporting of one resource indicator (e.g. CRI or SSBRI) or a pair of resource indicators and beam metrics (e.g. CRI/SSB-ri+rsrp/SINR) is configured, the UE recommendation may be reported. The UE recommendations may include CRI/SSB-RI (or CRI/ssbri+rsrp/SINR) associated with the UL TX beam (or QCL) that should be used, even though they do not correspond to the beam with the maximum RSRP/SINR.

● In one example, only when Q ₁ =2, i.e. reporting of two resource indicators (e.g. CRI or SSBRI) or two pairs of resource indicators and beam metrics (e.g. CRI/SSB-ri+rsrp/SINR) is configured, the UE recommendation may be reported. The UE recommendations may include CRI/SSB-RI (or CRI/ssbri+rsrp/SINR) associated with the UL TX beam (or QCL) that should be used, even though they do not correspond to the beam with the maximum RSRP/SINR.

● In one example, only when Q ₁ =1 or 2, i.e. one or two resource indicators (e.g. CRI or SSBRI) or one or two pairs of resource indicators and beam metrics (e.g. CRI/SSB-ri+rsrp/SINR) are configured, the UE recommendation may be reported. The UE recommendations may include CRI/SSB-RI (or CRI/ssbri+rsrp/SINR) associated with the UL TX beam (or QCL) that should be used, even though they do not correspond to the beam with the maximum RSRP/SINR.

In one example, includes Q ₁ The beam reporting of the individual beam reports remains unchanged regardless of whether the UE recommendation is reported or not, as it may be for DL and/or UL (e.g., beam indication for DL reception and/or UL transmission). However, the reported UE recommends beam indication for UL only (e.g., for UL transmission).

FIG. 17 illustrates a device configured to measure P in accordance with an embodiment of the present disclosure ₁ Flowchart 1700 for a UE of DL measurement RS resources. Shown in fig. 17 configured to measure P ₁ The embodiment of the flowchart 1700 of a UE for DL measurement of RS resources is for illustration only. FIG. 17 will not beThe scope of the present disclosure is limited to being configured to measure P ₁ Any particular embodiment of flowchart 1700 of a UE of DL measurement RS resources.

In one embodiment, as shown in FIG. 17, the UE is configured (NW/gNB) to measure (receive) P ₁ DL measurement RS resources (such as CSI-RS or SSB), where P ₁ 1, and details about this measurement are as described in the examples.

The UE is also configured (NW/gNB) to report a beam report, wherein the beam report includes Q ₁ Resource indicators (I) or Q ₁ Pair (I, J) = (resource indicator, beam metric), where Q ₁ ≤P ₁ And the resource indicator and beam metric are according to the examples described in the embodiments. For example, the resource indicator may be SSBRI or CRI, and the beam metric may be L1-RSRP or L1-SINR, as defined by the Rel.15/16NR specification.

Except for Q ₁ Resource indicators (I) or Q ₁ For (I, J) = (resource indicator, beam metric), the beam report may also include information about the "status" of the beam report (e.g., status = MPE condition). The time domain behavior of the beam measurements and/or beam reports may be configured as Aperiodic (AP), semi-persistent (SP), or periodic (P). The time domain behavior of the beam measurement RS may be configured as Aperiodic (AP), semi-persistent (SP), or periodic (P). Information about the "state" may be reported via a bit map or bit field or bit sequence. Or information about "status" may be reported via a parameter or Information Element (IE).

The "status" may be reported using the joint parameters (or indicators) along with other components included in the beam report. For example, the "status" may be reported in conjunction with at least one resource indicator. Or may report "status" in conjunction with at least one beam metric. Or may report "status" jointly with at least one pair (resource indicator, beam metric).

Or a separate parameter (or indicator) may be used to report "status" separately (independently) from other components in the beam report. Reporting configurations may be joint (one configuration) or separate (two configurations), one for "status" and the other for other components in the beam report.

Or reports of "status" are separate from other components in the beam report, i.e., one report is for "status" and another report is for other components in the beam report. Reporting configurations may be joint (one configuration) or separate (two configurations), one for "status" and the other for other components in the beam report.

In one example, when the UE is equipped with X>1 antenna panel, Q ₁ =x, reporting one resource indicator (I) or a pair of (I, J) = (resource indicator, beam metric) for each antenna panel. In one example, when the UE is equipped with X>1 antenna panel, Q ₁ Reporting at least one resource indicator (I) or a pair of (I, J) = (resource indicator, beam metric) for each antenna panel. P (P) ₁ The set of DL measurement RS resources may be partitioned into X subsets, one subset per antenna panel. Or P ₁ The DL measurement RS resources are a superset covering X sets, one set per antenna panel. In one example, information about the X panels is not provided to the NW/gNB. In one example, information about the X panels is provided to the NW/gNB. For example, information about the panel ID may be implicitly included/reported (e.g., according to the resource indicator (I)). Alternatively, information about the panel ID may be explicitly included/reported (e.g., by including/reporting the panel ID(s) in the beam report).

For X >1 antenna panels at the UE, the "status" may be reported independently for each panel. Or may report a "status" for one of the X panels (e.g., the panel with the most serious MPE problem) and may optionally also include the corresponding panel ID. Or may report "status" for all panels with MPE problems. If no MPE problem is detected, the UE does not report a "status", otherwise the UE reports a "status" for all the faceplates with MPE problem, and may optionally also report the corresponding faceplate ID.

For X >1 subsets (or sets) of DL measurement RS resources, the "state" may be reported independently for each subset (or set). Or may report "status" for one of the X subsets (or sets) (e.g., the subset or set with the most serious MPE problem) and may optionally also include the corresponding subset (or set) ID. Or the "status" may be reported for all subsets (or sets) of MPE questions. If no MPE problem is detected, the UE does not report a "status", otherwise the UE reports a "status" for all subsets (or sets) having MPE problems, and may optionally also report the corresponding subset (or set) ID.

The "status" may relate to an event of interest (such as MPE), a panel status (or ID), or whether beam reporting is used for one or both of DL reception and UL transmission. At least one of the following examples may be used to report information about the status.

● In one example, the status is with respect to MPE events or MPE mitigation. For example, a 1-bit indication B may be used to indicate one of two states: (i) MPE (or MPE mitigation) is detected, and (ii) MPE (not used for MPE mitigation) is not detected. For example, b=1 indicates (i), b=0 indicates (ii), or vice versa. Alternatively, the parameter p is used to indicate one of the two states (i) and (ii) via a value p=v0 and a value p=v1, respectively.

● In one example, the status is about a panel entity when the UE is equipped with multiple UE panels. For example, the status may correspond to an ID, such as a panel ID or a set ID or a resource ID associated with the panel.

● In one example, the status is with respect to a combination of MPE events and panel entities. For example, the status may indicate a pair (x, y), where x is (i) or (ii) in one or more examples described above, and y is an ID as described in one or more examples described above.

● In one example, the status is a recommended/preferred use for beam reporting for one of DL reception and UL transmission. At least one of the following examples is used/configured.

In one example, the state indicates one of two possible values s= { DL received, none }.

In one example, the status indicates one of two possible values s= { none, UL transmit }.

In one example, the status indicates one of two possible values s= { none, DL received and UL sent }.

In one example, the state indicates one of two possible values s= { DL received, UL sent }.

In one example, the state indicates one of two possible values s= { DL reception, DL reception and UL transmission }.

In one example, the status indicates one of two possible values s= { UL transmission, DL reception and UL transmission }.

In one example, the status indicates one of three possible values s= { DL reception, UL transmission, DL reception and UL transmission }.

In one example, the state indicates one of two possible values s= { none, DL received, UL sent }.

In one example, the status indicates one of two possible values s= { none, DL received and UL transmitted }.

In one example, the status indicates one of two possible values s= { none, UL transmit, DL receive and UL transmit }.

In one example, the status indicates one of three possible values s= { none, DL received, UL transmitted, DL received and UL transmitted.

● In one example, the status is a combination of the MPE event and a recommended use of beam reporting for one of DL reception and UL transmission. For example, the state may indicate a pair (x, y), where x is (i) or (ii) in example a, and y takes on value from S as described in example d.

● In one example, the status is a combination of recommended usage of the beam report for one of DL reception and UL transmission and the panel entity. For example, the status may indicate a pair (x, y), where x is an ID as described in one or more examples above, and y is a value from S as described in one or more examples above.

● In one example, the status is a combination of the MPE event, the panel entity, and the recommended use of the beam report for one of DL reception and UL transmission. For example, the status may indicate a triplet (x, y, z), where x is (i) or (ii) in one or more examples described above, y is an ID as described in one or more examples described above, and z is a value from S as described in one or more examples described above.

Where "none" means that there is no report from the UE for recommended/preferred use. Or "none" means that no additional information about the status is reported in the beam report.

With respect to beam metrics for different "state" values, at least one of the following examples is used/configured.

● In one example, the beam metrics may remain unchanged regardless of the reported value of "state".

● In one example, the beam metrics may be modified depending on the reported value of "status". For example, scaling corresponding to beam metrics L1-RSRP or L1-SINR is modified.

● In one example, the beam metric may be m1 for when the reported value of "state" belongs to set T1, and m2 for when the reported value of "state" belongs to set T2, where m1 and m2 are two different beam metrics, and T1 and T2 are two possible sets of values of "state". The sets T1 and T2 may be disjoint (i.e., have no common elements). (m 1, m 2) according to at least one of the following examples:

o (m 1, m 2) = (L1-RSRP, scaled L1-RSRP)

O (m 1, m 2) = (L1-SINR, scaled SINR)

○(m1,m2)＝(L1-RSRP,L1-SINR)

○(m1,m2)＝(L1-RSRP,UL·RSRP)

O (m 1, m 2) = (L1-RSRP, virtual PHR)

○(m1,m2)＝(L1-SINR,UL·RSRP)

O (m 1, m 2) = (L1-SINR, virtual PHR)

● In one example, the beam metric may be m1 for when the reported value of "state" belongs to set T1, m2 for when the reported value of "state" belongs to set T2, and m3 for when the reported value of "state" belongs to set T3, where m1, m2, and m3 are three different beam metrics, and T1, T2, and T3 are three possible sets of values of "state". The sets T1, T2, and T3 may be disjoint (i.e., have no common elements). (m 1, m2, m 3) according to at least one of the following examples:

O (m 1, m2, m 3) = (L1-RSRP, scaled L1-RSRP, UL RSRP)

O (m 1, m2, m 3) = (L1-RSRP, scaled L1-RSRP, virtual PHR)

O (m 1, m2, m 3) = (L1-SINR, scaled L1-SINR, UL RSRP)

O (m 1, m2, m 3) = (L1-SINR, scaled L1-SINR, virtual PHR)

O (m 1, m2, m 3) = (L1-RSRP, UL RSRP, virtual PHR)

O (m 1, m2, m 3) = (L1-SINR, UL RSRP, virtual PHR)

O (m 1, m2, m 3) = (L1-RSRP, L1-SINR, virtual PHR)

○(m1,m2,m3)＝(L1-RSRP,L1-SINR,UL RSRP)

● In one example, the beam report may include a second metric (in addition to the beam metric) for some report values of "status". That is, when the "state" belongs to the set T1, the beam metric is reported (and the second metric is not reported), and when the "state" belongs to the set T2, both the beam metric and the second metric are reported. Whether the second metric can be reported is determined based on at least one of the following examples.

In one example, this is based on configuration (e.g., via RRC and/or MAC CE and/or DCI).

In one example, this is determined and reported by the UE. In this case, a two-part UCI (similar to the rel.15nr specification) may be used, where UCI part 1 has information on whether the second metric and/or the number of second metrics are reported in UCI part 2.

In one example, this is subject to UE capability reporting.

In one example, Q ₁ =1, indicating that only one beam (resource indicator and metric) is reported in the beam report. In this case, the "status" value may be fixed or reported by the UE, the details being as described above.

In one example, when Q ₁ >1, there are multiple beams (resource indicators and metrics) reported in the beam report. At least one of the following examples is used/configured with respect to "status".

● In one example, all Q ₁ The individual beams correspond to the same "state" value. For example, when "state" is related to MPE, all Q' s ₁ The individual beams are either (i) normal beams for MPE mitigation (taking MPE into account) or (ii) MPE free, i.e. without MPE into account. Common bit fields, IEs, or parameters (e.g. 1-bit field or parameters taking two values) for Q ₁ And a beam.

● In one example, Q ₁ N1 of the individual beams may correspond to one "status" value (e.g., taking MPE into account) while the remaining N2 beams may correspond to another "status" value (e.g., normal beams that do not take MPE into account).

In one example, N1 and N2 are both fixed.

In one example, N1 is fixed and N2 is configured (e.g., RRC and/or MAC CE and/or DCI).

In one example, N1 is fixed or configured (e.g., RRC and/or MAC CE and/or DCI), and N2 is reported by the UE. A 2-part UCI may be used. For example, the value N2 may be from 0 to Q ₁ -N1. When n2=0, UCI part 2 does not exist and is not reported. When N2 > 1, one beam is reported via UCI part 2. Or UCI part 1 includes a report for N1 beams and a part of a report for N2 beams, and UCI part 2 includes the remaining part of the report for N2 beams.

In one example, both N1 and N2 are reported by the UE. A 2-part UCI may be used. For example, reporting is done for a fixed number of beams via UCI part 1 and reporting is done for the remaining beams via UCI part 2. Or UCI portion 1 includes a component for Q ₁ Part of the reporting of the individual beams, UCI part 2 includes for Q ₁ The remainder of the reporting of the individual beams.

In the rest of the disclosure, it is assumed that the "status" indicates one of two values, whether or not the UE detects an MPE problem. However, these embodiments and examples also apply to other examples of the "state" described above.

In one sub-embodiment, the content or information conveyed by the "state" is determined (or configured) according to at least one of the following examples.

In one example, the "status" indicates one of two values, e.g., whether the UE detects an MPE problem. For example, information may be conveyed via a 1-bit field, where a field value of=0 (or 1) indicates that no MPE problem is detected, and a field value of=1 (or 0) indicates that an MPE problem is detected.

● For example, when a field value = 0 (or 1) indicates that no MPE problem is detected, the beam report includes beam indicator(s) (e.g., CRI/SSBRI) and beam metric(s) (e.g., L1-RSRP, L1-SINR, etc.)

● For example, when a MPE problem is detected as indicated by a field value=1 (or 0), the beam report includes a beam indicator(s) (e.g., CRI/SSBRI) and a beam metric(s) that considers an event indicated by the field value, wherein the beam metric that considers the event indicated by the field value may be at least one of:

in one example, o: the field value=0 is the same as the beam metric, e.g. L1-RSRP, L1-SINR, etc.

In one example, o: the modified beam metric, for example, corresponds to a scaling of the beam metric L1-RSRP or L1-SINR.

In one example, o: new beam metrics such as UL RSRP or virtual PHR. In one example, UL RSRP is defined as UL rsrp=l1-RSRP-P _DL +P _UL Wherein L1-RSRP is the measured DL RSRP, P _DL Is DL transmission power, P _UL Is the available UL transmit power (or maximum UL transmit power). In one example, the virtual PHR is defined as the maximum available transmit power (e.g., P _c,max ) And the required transmit power.

In one example, the information indicates whether the UE detects MPE problems. For example, the information may be conveyed via a parameter, wherein a parameter value = v0 indicates that no MPE problem is detected and a parameter value = v1 indicates that MPE problem is detected.

In one example, the information includes a value of MPE. For example, the information may be conveyed via an M-bit field. When m=1, the 1-bit field indicates two values { M } ₀ ,m ₁ One of which either both values map to (maximum or minimum) MPE values or one of which maps to the state "MPE problem not detected" and the other value maps to the state "MPE detected and corresponding (maximum or minimum) MPE value". When m=2, the 2-bit field indicates four values { M } ₀ ,m ₁ ,m ₂ ,m ₃ One of the values where either all values map to (maximum or minimum) MPE values or one of the values maps to the state "no MPE problem detected", and the remaining values map to the state "MPE detected and corresponding (maximum or minimum) MPE values". In general, the M-bit field indicates 2 ^M The value { m } ₀ ,m ₁ ,…,m _M-1 One of the values where either all values map to (maximum or minimum) MPE values or one of the values maps to the state "no MPE problem detected", and the remaining values map to the state "MPE detected and corresponding (maximum or minimum) MPE values". Value set { m ₀ ,m ₁ ,…,m _M-1 The may be fixed or configured, e.g., via RRC and/or MAC CE and/or DCI. Or the maximum value of MPE is configured, e.g. via RRC and/or MAC CE and/or DCI, and the value set { m } ₀ ,m ₁ ,…,m _M-1 The value of the configuration is determined based on the maximum value of the configuration. In one example, the set of MP values corresponds to a (maximum or minimum) Power Headroom (PHR) or a power management maximum power reduction (Power Management Maximum Power Reduction, P-MPR) or UL duty cycle value.

In one example, the information includes a value of MPE. For example, the information may be conveyed via a parameter that takes a value from a set of M values. When m=2, the parameter indicates two values { M } ₀ ,m ₁ One of the values, where either two values map to (maximum or minimum) MPE values, or one value maps to the state "MPE problem not detected", and the other value maps to the state "MPE detected and corresponding (maximum or minimum) MPE value" . When m=4, the parameter indicates four values { M } ₀ ,m ₁ ,m ₂ ,m ₃ One of the values where either all values map to (maximum or minimum) MPE values or one of the values maps to the state "no MPE problem detected", and the remaining values map to the state "MPE detected and corresponding (maximum or minimum) MPE values". In general, the parameter indicates M values { M } ₀ ,m ₁ ,…,m _M-1 One of the values where either all values map to (maximum or minimum) MPE values or one of the values maps to the state "no MPE problem detected", and the remaining values map to the state "MPE detected and corresponding (maximum or minimum) MPE values". Value set { m ₀ ,m ₁ ,…,m _M-1 The may be fixed or configured, e.g., via RRC and/or MAC CE and/or DCI. Or the maximum value of MPE is configured, e.g. via RRC and/or MAC CE and/or DCI, and the value set { m } ₀ ,m ₁ ,…,m _M-1 The value of the configuration is determined based on the maximum value of the configuration. In one example, the set of MP values corresponds to a (maximum or minimum) Power Headroom (PHR) or a power management maximum power reduction (P-MPR) or UL duty cycle value.

In one sub-embodiment, a report of "status" is determined (or configured) according to at least one of the following examples.

In one example, the "status" may always be included in the beam report (i.e., reported by the UE).

In one example, the "status" may always be included in the beam report (i.e., reported by the UE) when a condition is met, wherein the condition is, for example, that the UE is equipped with multiple antenna panels, or that the UE reports it (UE recommendation) as part of its UE capabilities, or that the UE may detect an event of interest.

In one example, reporting of "status" is configured via RRC and/or MAC CE (and/or triggered via DCI). When configured (or triggered), the UE always reports a "status", otherwise the UE does not report it. The UE may also be configured with a maximum value of MPE. In one example, the configuration and/or trigger is UE-specific, in another example the configuration and/or trigger is UE group-specific, and in another example the configuration and/or trigger is cell-specific.

In one example, the reporting of the "status" is reported by the UE without any configuration/trigger from the NW (i.e., the UE may initiate such reporting).

In one example, the reported capability for "status" is reported by the UE (e.g., via UE capability reporting or as part of UL transmission). Depending on the reported UE capabilities, the NW/gNB may configure (or trigger) the reporting of the "status" via RRC and/or MAC CE (and/or DCI). The UE reports the "status" according to the configuration/trigger from NW/gNB.

In one example, the UE decides (can freely decide) whether "status" is included in the beam report, i.e. the UE may or may not include "status" in the beam report. Such a decision may be made based on events of interest, for example. In one example, beam reporting (with or without "status") is reported via a portion of UCI (similar to WB CSI reporting in rel.15nr, the UE may append a fixed number of zeros to ensure that the payload remains unchanged, regardless of whether the UE reports "status"). In one example, beam reporting (with or without "status") is reported via a two-part UCI, where part 1UCI includes information whether the UE reports "status". If the information indicates that a "status" is reported, it is reported via part 2 UCI.

In one sub-embodiment, in addition to Q ₁ Resource indicators (I) or Q ₁ In addition to (I, J) = (resource indicator, beam metric) and "status", the beam report may also include UE recommendations for UL TX beam selection/indication (by NW/gNB), wherein details about UE recommendations are as described in obstacle i.1. Furthermore, the "status" and UE recommendations may be reported either jointly or individually.

Upon receiving the beam report, the NW/gNB configures/indicates a UL TX beam indication (which may be the same as the DL TX beam indication because the beam correspondence holds) to the UE for UL transmission, wherein the beam indication indicates n≡1 UL TX beam. The beam indication may be via DL-TCI or UL-TCI or J-TCI (joint TCI) or other functionally equivalent entities such as spatialreactive info or SRI indicated via DCI and/or MAC CE and/or RRC. In one example, n=1. In one example, n=2. Further, the beam indication may include a message (such as an ACK or NACK/NULL), with details regarding the message as described in one or more of the embodiments above.

the first report (sub-report) is a beam report comprising the resource indicator(s) and possible beam metrics, not reflecting the "status".

The second report (sub-report) is a beam report comprising the resource indicator(s) and possible beam metrics, reflecting the "status". For example, the reported resource indicator(s) take into account MPE effects. The beam metrics include MPE effects.

In one embodiment, which is a variation of one or more of the embodiments described above, this or the beam reporting configuration is communicated (provided) to the UE except that a "status" or indicator (e.g., indicating whether the beam report is for MPE) is not included in the beam report. In one example, this is provided via RRC parameters.

● In one example, the RRC parameter is MPE-Reporting-r17, which allows the UE to include a P-MPR based MPE report (similar to rel.16mpe report) in the PHR report when the threshold is reached, and via a MAC-CE (entity) report (or trigger), similar to the description in section 5.4.6 of TS 38/321.

● In one example, the RRC parameter is done via a CSI request field (similar to the beam/CSI report configuration in rel. 15/16).

● In one example, this RRC parameter is done via the CSI request field (similar to the beam/CSI report configuration in rel.15/16), but its triggering is subject (dependent on) the MPE report (similar to rel.16) included on the PHR report via the MAC CE. That is, the beam reporting is triggered only when the UE reports MPE problems via PHR reporting on the MAC CE.

In response to the configuration, the UE determines and reports a beam report based on the value of the "status" or indicator it received. UL channel(s) or resource(s) configured for beam reporting are according to at least one of:

● The beam report may be reported on PUCCH. If the PUCCH transmission including the beam report overlaps with the PUSCH transmission, uplink Control Information (UCI) is multiplexed with the beam report in the PUSCH.

● The beam report may be included in UCI transmitted on PUSCH, where PUSCH transmission may be one of: PUSCH transmissions scheduled by UL grant, or type 1 or type 2 configuration grant PUSCH transmissions, or Msg3 PUSCH transmissions for random access procedure type 1, or MsgA PUSCH transmissions for random access procedure type 2.

● The beam report may be included in the PHR report and triggered via a MAC-CE report or via a MAC entity (scheduled to report via PUSCH carrying UL MAC).

● The beam report may be included in a combination of PHR report and UCI. That is, a portion of the beam report is reported via MAC-CE (scheduled to report via PUSCH carrying UL MAC), and the remaining portion of the beam report is reported via UCI (e.g., PUCCH or PUSCH scheduled to carry UCI). In one example, P ₁ The pair (P-MPR, SSBRI/CRI or UL. TCI) is reported via PHR report, and the remaining Q ₁ -P ₁ Pairs (P-MPR, SSBRI/CRI or UL-TCI or ID associated with antenna panels (e.g., CSI-RS/SRS resource set ID)) are reported via UCI, where Q ₁ >P ₁ . In one example, P ₁ ＝1。Q ₁ May be fixed at 4.Q (Q) ₁ May be reported by the UE via a UE capability report. Alternatively, whether the UE supports MPE reporting via UCI is subject to (dependent on) UE capabilities. That is, the UE may be configured with such reports only when the UE supports reports on UCI; otherwise (when the UE is not supported), the UE cannot be configured with MPE reporting on UCI, so MPE reporting can only be done via MAC CE.

● In one example, a two-part PHR report via MAC CE (similar to a two-part UCI report) is used. The first part of the PHR report includes fixed P ₁ Personal (e.g. P ₁ =1) beam reporting, and the second part of PHR report includes the remaining Q ₁ -P ₁ And reporting the wave beams. When the value Q ₁ As determined by the UE, regarding the value Q ₁ -P ₁ Is included in the first portion. Alternatively, whether the UE supports two-part PHR reporting via MAC CE is subject to (depending on) UE capabilities. That is, the UE may be configured with two-part PHR reports only if such reports are supported by the UE; otherwise (when the UE is not supported), the UE cannot be configured with two-part PHR reporting, so MPE reporting can only be done via (a part of) PHR reporting and/or UCI.

In a variant, to facilitate MPE mitigation, rel-16 event triggered P-MPR based reporting (included in PHR reporting when a threshold is reached, via MAC-CE reporting) is extended as follows.

● In one example, Q ₁ 1 or more P-MPR values may be reported with M.gtoreq.1 SSBRI/CRI, where M SSBRI/CRI are selected by the UE from a pool of candidate SSB/CSI-RS resources and/or from a pool of configured or activated TCI states (UL TCI or joint TCI).

● In one example, Q ₁ The 1P-MPR values may be reported along with m≡1 panel related indicators (e.g., IDs associated with antenna panels (e.g., SRS/CSI-RS resource set IDs)).

● In one example, Q ₁ The 1P-MPR value may be reported with M > 1 SSBRI/CRI and M > 1 panel-related indicators (e.g., IDs associated with antenna panels (e.g., SRS/CSI-RS resource set IDs)).

In one example, Q ₁ The P-MPR values include the existing P-MPR values in the rel.16phr report on the MAC CE. Thus, Q is included in the report ₁ P-MPR values and M SSBRI/CRI. In another example, Q ₁ The P-MPR values are complementary to the existing P-MPR values in the rel.16phr report on the MAC CE. Thus, Q is included in the report ₁ +1P-MPR values (one from existing Rel.16, the remainder being additional) and M SSBRI/CRI.

In one example, Q ₁ =m. In one example, M>Q ₁ . In one example, Q ₁ =1 and m+.1.

In one example, Q ₁ Representing the number of selected beams (via CRI/SSBRI) and/or the number of panels (via IDs associated with the antenna panels).

Q ₁ The support value of (2) may be fixed (e.g., 4). Or it may be configured from {1,2,3,4 }. Or Q ₁ Is reported by the UE (e.g., via UE capability reporting) and the configuration value is less than or equal to the reporting value.

As described above, the reporting may also be performed via a combination of PHR reporting and UCI reporting, or via two-part PHR reporting. Additional reporting amounts may also be included, UL RSRP, virtual PHR, DL RSRP, etc., details of which are in accordance with at least one example of the present disclosure.

Figure 18 illustrates an example of a single mesh MAC CE 1500 for multiple MPE reports according to an embodiment of the disclosure. The embodiment of a single-entry MAC CE 1800 for multiple MPE reports shown in fig. 18 is for illustration only. Figure 18 does not limit the scope of the present disclosure to any particular implementation of a single mesh MAC CE 1800 for multiple MPE reports.

Figure 19 illustrates an example of a single mesh MAC CE 1900 for multiple MPE reports according to an embodiment of the disclosure. The embodiment of a single-entry MAC CE 1900 for multiple MPE reports shown in fig. 19 is for illustration only. Figure 19 does not limit the scope of the present disclosure to any particular implementation of a single mesh MAC CE 1900 for multiple MPE reports.

For beam reports included in PHR reports via MAC CEs, two examples of a single mesh MAC CE for multiple MPE reports are shown in fig. 18 and 19.

In one example, the content of the beam report is according to one of the examples in the present disclosure. Several similar or other examples of beam report content are as follows.

In one example, the beam report includes Q ₁ Pair (I, J), where i=indicator=ssbri or CRI or TCI (UL TCI or joint TCI) or ID associated with the antenna panel (e.g., SRS/CSI-RS resource set ID), j=metric=m=mpe metric when MPE problem is present (MPE problem is detected). In one example, the metric is P-MPR. In one example, the metric is UL-RSRP. In one example, the metric is a modified virtual PHR. In one example, the metric is a combination of DL-RSRP and P-MPR. In one example, the metric is a combination of DL-RSRP and virtual PHR. Details of these metrics are in accordance with examples in this disclosure.

In one example, the beam report includes Q ₁ Pair (I, J), where i=indicator=ssbri or CRI or TCI (UL TCI or joint TCI) or ID associated with the antenna panel (e.g., SRS/CSI-RS resource set ID), j=metric=m is one of m1 and m 2.

● When "status" or indicator = 0 or v0, m = m1, e.g. when there is no MPE problem (no MPE problem detected), it indicates a normal metric,

● When "status" or indicator = 1 or v1, m = m2, e.g. when there is an MPE problem (MPE problem detected), it indicates an MPE metric.

For (m 1, m 2) at least one of the following examples is used/configured.

● In one example, (m 1, m 2) = (DL RSRP, UL RSRP), where

DL rsrp=l 1-RSRP or modified L1-RSRP in rel.15, wherein the modification corresponds to one of the following.

Scaling the beam metric by ζ times, i.e. DL RSRP x ζ; wherein ζ may depend on path loss

Subtracting (reducing) the factor γ, namely DL RSRP- γ; wherein gamma may depend on path loss

○UL·RSRP=dl RSRP-P-MPR or UL rsrp=l1-RSRP-P _DL +P _UL As defined in one or more of the examples above.

● In one example, (m 1, m 2) = (DL SINR, UL RSRP), where

DL rsrp=l 1-SINR in rel.16 or modified L1-SINR, wherein the modification corresponds to one of the following.

Scaling the beam metric by ζ times, i.e. DL SINR x ζ; wherein ζ may depend on path loss

Subtracting (reducing) the factor γ, i.e., DL SINR- γ; wherein gamma may depend on path loss

UL rsrp=dl RSRP-P-MPR or UL rsrp=l1-RSRP-P _DL +P _UL As defined in one or more of the examples above.

● In one example, (m 1, m 2) = (DL RSRP, vPHR), where

DL RSRP is as in the example above, and

the vPHR is a virtual PHR as defined in the disclosure [ REF8 ].

● In one example, (m 1, m 2) = (DL SINR, vPHR), where DL SINR and vPHR are as described in the above examples.

● In one example, (m 1, m 2) = (DL RSRP, UL RSRP or vPHR), where m2=ul RSRP or vPHR based on configuration (e.g., RRC or new parameters via CSI-apeeriodicdigerstate) or code point (CSI request field in DCI or separate field in DCI) or based on UE capabilities. The UE may support only one of these two metrics or the UE may support both metrics and the NW will configure/trigger one of these metrics based on the UE capability report. Details of the three metrics are explained in the above examples.

● In one example, (m 1, m 2) = (DL SINR, UL RSRP or vPHR), where m2=ul RSRP or vPHR based on configuration (e.g. RRC or new parameters via CSI-apersicdigerstate) or code point (CSI request field in DCI or separate field in DCI) or based on UE capability. The UE may support only one of these two metrics or the UE may support both metrics and the NW will configure/trigger one of these metrics based on the UE capability report. Details of the three metrics are explained in the above examples.

● In one example, (m 1, m 2) =one of the examples in one or more embodiments described above.

In one example, the beam report includes Q ₁ Pair (I, J), where i=indicator=ssbri or CRI or TCI (UL TCI or joint TCI) or ID associated with the antenna panel (e.g., SRS/CSI-RS resource set ID), j=metric=m is one of m1 and a pair (m 2, m 3).

● When "status" or indicator = 1 or v1, m = pair (m 2, m 3), e.g. when there is an MPE problem (MPE problem detected), it indicates an MPE metric.

For (m 1, m2, m 3) at least one of the following examples is used/configured.

● In one example, m1=dl RSRP, and (m 2, m 3) = (DL RSRP, P-MPR), where

DL RSRP as in the example above,

the o P-MPR (power management-maximum power reduction) is the reduction of maximum UL power due to the maximum allowed exposure (MPE) specification.

● In one example, m1=dl RSRP, and (m 2, m 3) = (UL RSRP, P-MPR), where DL RSRP, UL RSRP, and P-MPR are as described in the examples above.

● In one example, m1=dl RSRP, and (m 2, m 3) = (DL RSRP, vPHR), where DL RSRP and vPHR are as described in the above examples.

● In one example, m1=dl RSRP, and (m 2, m 3) = (UL RSRP, vPHR), where DL RSRP, UL RSRP, and vPHR are as described in the examples above.

● In one example, m1=dl RSRP, and (m 2, m 3) = (DL RSRP, UL RSRP), where DL RSRP and UL RSRP are as described in the above examples.

● In one example, m1=dl RSRP, and (m 2, m 3) = (P-MPR, vPHR), where P-MPR and vPHR are as described in the examples above.

● In one example, m1=dl SINR, and (m 2, m 3) is according to one of the above examples. Table 35, table 36 and table 37 define three examples of P-MPR report mappings.

Table 35P-MPR mapping

Reporting values	Measurement value	Unit (B)
			P-MPR_00	3≤PMP-R<6	dB
P-MPR_01	6≤PMP-R<9	dB
			P-MPR_02	9≤PMP-R<12	dB
P-MPR_03	PMP-R≥12	dB

Table 36P-MPR mapping

Reporting values	Measurement value	Unit (B)
			P-MPR_00	1.5≤PMP-R<3	dB
P-MPR_01	3≤PMP-R<4.5	dB
			P-MPR_02	4.5≤PMP-R<6	dB
P-MPR_03	6≤PMP-R<7.5	dB
			P-MPR_04	7.5≤PMP-R<9	dB
P-MPR_05	9≤PMP-R<10.5	dB
			P-MPR_06	10.5≤PMP-R<12	dB
P-MPR_07	PMP-R≥12	dB

Table 37P-MPR mapping

When Q is ₁ >1, the first P-MPR may be reported according to one of tables 35 to 37, the remaining Q ₁ -1P-MPR may be reported according to at least one of the following.

● In one example, the P-MPR values are reported without any ordering. Thus, the same payload (number of bits) is used to report each P-MPR value.

● In one example, the P-MPR values are sorted in descending order and reported differently. That is, the first P-MPR (v ₀ ) Using x ₀ Bits (e.g., x ₀ =2 or 3) and serves as a reference for the second P-MPR. Differential second P-MPR (d ₁ ) Using x ₁ Bits (e.g., x ₁ =1 or 2 bits), the actual second P-MPR is reported by v ₁ ＝d ₁ +v ₀ Given, and the second P-MPR serves as a reference for the third P-MPR, and so on. Alternatively, the first P-MPR (v ₀ ) Serving as a reference for all remaining P-MPR values (second, third, etc.).

● In one example, the P-MPR values are reported in different ways. That is, the first P-MPR (v ₀ ) Using x ₀ Bits (e.g., x ₀ =2 or 3) and serves as a reference for the second P-MPR. Differential second P-MPR (d ₁ ) Using x ₁ Bits (e.g., x ₁ =1 or 2 bits), the actual second P-MPR is reported by v ₁ ＝d ₁ +v ₀ Given, and the second P-MPR serves as a reference for the third P-MPR, and so on. Alternatively, the first P-MPR (v ₀ ) Serving as a reference for all remaining P-MPR values (second, third, etc.).

● When a "status" or indicator=0 or v0, m=m1, e.g. when there is an MPE problem (MPE problem detected), it indicates a first MPE metric,

● When "status" or indicator = 1 or v1, m = m2, e.g. when there is an MPE problem (MPE problem detected), it indicates a second MPE metric.

For (m 1, m 2) at least one of the following examples is used/configured.

● In one example, (m 1, m 2) = (Vphr, UL RSRP), where UL RSRP and Vphr are described above.

In one example, the beam report includes Q ₁ Pair (I, J), where i=indicator=ssbri or CRI or TCI (UL TCI or joint TCI) or ID associated with the antenna panel (e.g., SRS/CSI-RS resource set ID), j=metric=m is one of m1, m2, and m 3.

● When "status" or indicator = 1 or v1, m = m2, e.g. when there is an MPE problem (MPE problem detected), it indicates a first MPE metric,

● When "status" or indicator = 2 or v2, m = m3, e.g. when there is an MPE problem (MPE problem detected), it indicates a second MPE metric.

For (m 1, m2, m 3) at least one of the following examples is used/configured.

● In one example, (m 1, m2, m 3) = (DL RSRP, UL RSRP, vPHR), wherein DL RSRP, UL RSRP and vPHR are described above.

● In one example, (m 1, m2, m 3) = (DL SINR, UL RSRP, vPHR), where DL RSRP, UL RSRP, and vPHR are described above.

In one example, the beam report includes Q ₁ Pair (I, J), where i=indicator=ssbri or CRI or TCI (UL TCI or joint TCI) or ID associated with the antenna panel (e.g., SRS/CSI-RS resource set ID), j=metric=m is one of m1, m2 and a pair (m 3, m 4).

● When "status" or indicator = 1 or v1, m = m2, e.g. when there is an MPE problem (MPE problem detected), it indicates an MPE metric,

● When "status" or indicator = 2 or v2, m = a pair (m 3, m 4), e.g. when there is an MPE problem (MPE problem detected), it indicates an MPE metric pair.

For (m 1, m2, m3, m 4) at least one of the following examples is used/configured.

● In one example, m1=dl RSRP, m2=ul RSRP, and (m 3, m 4) is one of the examples of (m 2, m 3) of the one or more examples described above.

● In one example, m1=dl RSRP, m2=vphr, and (m 3, m 4) is one of the examples of (m 2, m 3) of the one or more examples described above.

● In one example, m1=dl RSRP, m2=p-MPR, and (m 3, m 4) is one of the examples of (m 2, m 3) of the one or more examples described above.

● In one example, m1=dl SINR, m2=ul RSRP, and (m 3, m 4) is one of the examples of (m 2, m 3) of the one or more examples described above.

● In one example, m1=dl SINR, m2=vphr, and (m 3, m 4) is one of the examples of (m 2, m 3) of the one or more examples described above.

● In one example, m1=dl SINR, m2=p-MPR, and (m 3, m 4) is one of the (m 2, m 3) examples of the one or more examples described above.

In one example, the UE reports m=m2 and m= (m 3, m 4) via its ability to report whether it supports one or both MPE metrics.

In one example, a status or indicator (e.g., a 1-bit or 2-bit indicator) is explicitly conveyed to the UE, and the UE determines/reports a beam report based on the received status or indicator.

In one example, the status or indicator is conveyed via DCI. For example, a CSI request field or a separate field in DCI may be used for this purpose.

In one example, the status or indicator is communicated via a MAC CE. For example, an activation command to activate CSI-RS subset selection or a separate activation command may be used for this purpose.

In one example, the status or indicator is communicated via a higher layer (RRC). For example, a trigger state definition (CSI-apiodicttriggerstate) for CSI reporting or a separate RRC parameter may be used for this purpose.

Figure 20 shows an example of a single mesh MAC CE 2000 for multiple MPE reports in accordance with an embodiment of the present disclosure. The embodiment of a single mesh MAC CE 2000 for multiple MPE reports shown in fig. 20 is for illustration only. Figure 20 does not limit the scope of the present disclosure to any particular implementation of a single mesh MAC CE 2000 for multiple MPE reports.

In one example, the beam report is implicitly "triggered" (no CSI configuration/trigger). For example, a UE-initiated or event-triggered mechanism may be used as the trigger. For example, when the MPE report includes p=1 and a corresponding MPE (P-PMR) value for a single-mesh PHR MAC CE (fig. 16), the implicit trigger is based on the MPE report via a single-entry or multiple-entry PHR report on the MAC entity (see TS 38.321 section 5.4.6, 6.1.3.8/9). That is, when the UE reports MPE value and p=1, the UE will either report the beam report in the same slot (as for PHR reporting, in conjunction with or separate from PHR reporting), or will report the beam report possibly after a time delay of at least N slots (OFDM symbols) from the slot (or OFDM symbol) containing MPE reporting, where N may be determined according to at least one of the following examples.

● In one example, N is fixed (predetermined) and not configured, e.g., n=0 or 4.

● In one example, N is the earliest time slot scheduled for UL transmission (via configuration grant type 1 or 2, or via DCI).

● In one example, N is configured via higher layers (RRC, triggerState or separate parameters) or MAC CEs (MAC CEs or separate MAC CEs performing a subset selection of aperiodic CSI-RS resources) or DCIs (CSI request field or separate field).

● In one example, N or the minimum value of N or the maximum value of N is reported by the UE as part of the UE capability.

● In one example, when the subcarrier spacing (subcarrier spacing, SCS) and/or BWP of the DL channel and the UL channel are different, the value of N may depend on the SCS of the active UL BWP and/or the UL channel (e.g., PUSCH/PUCCH/PRACH) and/or the active DL BWP for beam reporting. For example, a slot (or OFDM symbol) for UL transmission may be based on a scaling factor x orOr->To determine, wherein->And mu ₁ Sum mu ₂ SCS indicating DL channel and UL channel, respectively, and/or BWP taking a value from {0,1,2,3,4} indicating {15,30,60,120,240}kHz SCS, respectively.

UL transmissions including beam reports are made via configuration grant PUSCH resources and begin at the earliest configuration grant PUSCH opportunity after N slots from the slot (or OFDM symbol) containing the MPE report. Or UL transmission including beam reporting is made via configured PUCCH resources (configured grant type 1 or type 2) and starts at the earliest configured PUCCH opportunity after N slots from the slot (or OFDM symbol) containing MPE reporting. Or UL transmission including beam reporting is made via PRACH (type 1 or type 2), where the preamble starts at the earliest PRACH opportunity after N slots from the slot (or OFDM symbol) containing MPE reporting.

In one example, beam reporting may be explicitly "triggered" only when the UE reports MPE reporting (after that), e.g., when the UE reports MPE reporting via PHR reporting on the MAC entity. That is, the CSI request field in the DCI may trigger the beam report only when the NW receives the MPE report from the UE via the PHR report on the MAC entity.

In one embodiment, the RS(s) for SSBRI/CRI reporting are according to at least one of the following examples:

● In one example, the RS(s) for SSBRI/CRI reporting are measurement RS resources configured at higher layers as in rel.15/16 beam measurement/reporting. For aperiodic CSI-RS(s), the subset selection based on MAC CE may be used when the number of aperiodic CSI-RS resources configured by higher layers is greater than a threshold (determined based on DCI code point/field triggering aperiodic CSI-RS measurement and reporting, bit width of CSI request).

● In one example, the RS(s) for SSBRI/CRI reporting are QCL source RS(s) included in the active TCI state(s) activated via MAC CE

● In one example, the RS(s) for SSBRI/CRI reporting are QCL source RS(s) for TCI state(s) for higher layer (RRC) configuration

● In one example, the RS(s) for SSBRI/CRI reporting are RS(s) configured as PL-RS(s).

● In one example, the RS(s) for SSBRI/CRI reporting are a combination of two RS sets, where x+noteyand x and y belong to {1,2,3,4}.

In one embodiment, as described in the present disclosure, the UE is configured with a candidate SSB/CSI-RS resource pool for SSBRI/CSI(s) included in the MPE-mitigated beam report, wherein the candidate SSB/CSI-RS resource pool is configured according to at least one of the following examples.

In one example, the candidate SSB/CSI-RS resource pool is configured according to one of the examples in one or more embodiments described above.

In one example, the candidate SSB/CSI-RS resource pool is a CSI-RS resource set that is configured via a CSI reporting framework (see 5.2.1.2 of TS 38.214).

In one example, the set of CSI-RS resources is configured via the higher layer parameters CSI-RS-resourcesist included in the CSI-ResourceConfig set ID for the CSI resources of CSI-resourceconfiid. Details can be copied in table 38 according to ts.38.331. The parameter CSI-RS-ResourceLetList may configure a list of S.gtoreq.1 CSI resource sets, including references (IDs) to one or both of the NZP CSI-RS resource set (S) and the SS/PBCH block set (S), details of which are copied from TS 38.331 in tables 39 and 40. In one example, the number of configured CSI-RS resource sets is limited to s=1. In one example, the number of NZP-CSI-RS-resources configured within the configured CSI resource set is limited to 1. In one example, the number of SS/PBCH block sets configured within the configured CSI resource set is limited to 1.

Table 38

/>

In one example, a set of CSI-RS resources including CSI-RS resources is configured via a higher layer parameter NZP-CSI-RS-ResourceSet with ID NZP-CSI-RS-ResourceSet. Details can be reproduced in table 39 according to ts.38.331. In one example, the number of NZP-CSI-RS-ResourceSets configured is limited to 1. In one example, the number of configured NZP-CSI-RS-resources may be greater than 1, but the maximum value is fixed/determined based on UE capability reporting.

Table 39

/>

In one example, the set of CSI-RS resources comprising SSB blocks is configured via a higher layer parameter CSI-SSB-ResourceSet with ID CSI-SSB-ResourceSetId. Details can be copied in table 40 according to ts.38.331. In one example, the number of SSB-resourcesets configured is limited to 1. In one example, the number of SSB-resources set configured may be greater than 1, but the maximum value is fixed/determined based on UE capability reporting.

Table 40

/>

In one example, a set of CSI-RS resources including both CSI-RS resources (set S1) and SSB blocks (set 2) is configured via higher layer parameters NZP-CSI-RS-ResourceSet for ID of S1 and higher layer parameters CSI-SSB-ResourceSet for ID of S2. Details can be reproduced in tables 39 and 40 according to ts.38.331. In one example, the number of NZP-CSI-RS-ResourceSets configured is limited to 1. In one example, the number of SSB-resourcesets configured is limited to 1. In one example, the number of configured NZP-CSI-RS-resources may be greater than 1, but the maximum value is fixed/determined based on UE capability reporting. In one example, the number of SSB-resources set configured may be greater than 1, but the maximum value is fixed/determined based on UE capability reporting. In one example, the total number of configured NZP-CSI-RS-resource eset and/or SSB-resource eset may be greater than 1, but the maximum value is fixed/determined based on UE capability reporting.

In one example, the candidate SSB/CSI-RS resource pool is a CSI-RS resource set configured via a CSI reporting framework (see 5.2.1.2 of TS 38.214). Specifically, the CSI-RS resource set is configured via CSI-ResourceConfig linked (or associated) with CSI reporting settings (higher layer parameters CSI-ReportConfig). Details can be copied in table 41 according to ts.38.331. Details of the CSI-RS resource set are according to one of examples ii.1.1 to ii.1.4. The time reporting behavior of CSI-ReportConfig is indicated by the higher layer parameter reportConfigType and may be set to "mpeReporting" or "mpereportingonphr_macce" for beam reporting with MPE mitigation via PHR on MACCE (see TS 38.321), as described in this disclosure.

Table 41

/>

Furthermore, for CRI+P-MPR or SSBRI+P-MPR reporting, the higher layer parameter reportquality may be set to "CRI-PMPR" or "ssb-Index-PMPR", respectively.

● If reportquality is set to "cri-PMPR" or "ssb-Index-PMPR", then the CSI report setting is said to have wideband frequency granularity.

● In resource settings for channel measurements of CSI-ReportConfig with higher layer parameters reportquality set to "cri-PMPR" or "ssb-Index-PMPR", it is not desirable that the UE is configured with more than 64 NZP CSI-RS resources and/or SS/PBCH block resources. Thus, up to 6 bits are required per CRI/SSBRI report.

● In one example, when the higher layer parameter reportquality is set to "cri-PMPR" or "ssb-Index-PMPR", the number of resource settings linked to CSI-ReportConfig (via CSI-ResourceConfig) is limited to 1.

If the UE is configured with CSI-ReportConfig with higher layer parameters reportquality set to "cri-PMPR" or "ssb-Index-PMPR",

● If the UE is configured with a higher layer parameter groupBasedBeamReporting set to "", the UE does not need to update measurements for more than 64 CSI-RS and/or SSB resources, and the UE will report a different CRI or SSBRI set for each report in a single report nrofReportedPMPR (higher layer configuration). In one example, nrofReportedPMPR configures Q for CRI/SSBRI and P-MPR reporting ₁ Is a value of (2). The configuration of nrofreportedppr may be via PHR-Config or PHR-Config-r17 (e.g., new parameters in MPE-Config-FR2-r 17) or via nrofReportedRS or nrofReportedRS-r17 included in CSI-reporteconfig.

Calculation for P-MPR

When quasi-collocated in terms of resources with "type C" and "type D" (when applicable), the UE may be configured with CSI-RS resources, SS/PBCH block resources, or both CSI-RS and SS/PBCH block resources.

The UE may be configured with CSI-RS resource settings of up to 16 CSI-RS resource sets, with up to 64 resources within each CSI-RS resource set. The total number of different CSI-RS resources on all resource sets does not exceed 128.

For P-MPR reporting, if the higher layer parameter nrofReportedPMPR in PHR-Config or PHR-Config-r17 or CSI-ReportConfig is configured to be 1, the reported P-MPR value is defined by an x-bit value. In one example, x=2, and the p-MPR report is based on table 10.1.26.1-1 in TS 38.133. If the higher layer parameter nrofReportedPMPR is configured to be greater than 1, or if the higher layer parameter groupBasedBeamReporting is configured to be "enabled", one of the following parameters is used.

● The UE will use the x-bit value for all P-MPR values. In one example, x=2 and the P-MPR report is based on table 10.1.26.1-1 in TS 38.133.

● The UE will use a differential P-MPR based report in which one of the P-MPR values (e.g., the first P-MPR value) is quantized to an x-bit value and the differential P-MPR is quantized to a y-bit value for the remaining values. Reference is made to P-

One of the MPR values (e.g., the first P-MPR value) calculates a differential P-MPR value. The mapping between the reported differential value and the measured value may be determined from table 42.

Table 42 mapping of differential P-MPR

Reporting values	Measurement of the quantity	Unit (B)
			Diff_P-MPR_00	1.5≤PMP-R<3	dB
Diff_P-MPR_01	3≤PMP-R<4.5	dB
			Diff_P-MPR_02	4.5≤PMP-R<6	dB
Diff_P-MPR_03	PMP-R≥6	dB

If the higher layer parameter timeRestriction ForChannelMessaging in CSI-ReportConfig is set to "notConfigured", the UE will derive the channel measurements for calculating the P-MPR value reported in uplink slot n based only on SS/PBCH or NZP CSI-RS no later than the CSI reference resources (defined in TS 38.211) associated with the CSI resource setup.

If the higher layer parameter timeRestriction ForChannelMessagementin CSI-ReportConfig is set to "Configured", the UE will derive the channel measurements for calculating the P-MPR reported in uplink slot n based only on the latest timing of the SS/PBCH or NZP CSI-RS (defined in TS 38.211) associated with the CSI resource setup that is no later than the CSI reference resource.

If the UE is configured with CSI-ReportConfig with reportquality set to "cri-PMPR" or "ssb-Index-PMPR" and if CSI-ResourceConfig (higher layer parameter resource measurement) for channel measurement contains NZP-CSI-RS-ResourceSet configured with higher layer parameter repetition without higher layer parameter tres-Info, the UE can only be configured with the same number (1 or 2) of ports with higher layer parameter nrofPorts for all CSI-RS resources within the set. If the UE is configured with CSI-RS resources in the same OFDM symbol(s) as the SS/PBCH block, the UE may assume that the CSI-RS and the SS/PBCH block are quasi-collocated with "type D" if "type D" applies. Furthermore, the UE will not expect to be configured with CSI-RS in the PRB that overlap with CSI-RS of the SS/PBCH block, and the UE will expect to use the same subcarrier spacing for both CSI-RS and SS/PBCH block.

In one example, the candidate SSB/CSI-RS resource pool is a CSI-RS resource set or SSB resource set configured via PHR-Config (existing PHR configuration, e.g., up to rel.16nr) or PHR-Config-r17 (new PHR configuration, e.g., rel.17).

In one example, parameters are included in PHR-Config or PHR-Config-r17 to configure the CSI-RS or SSB resource set. At least one of the following examples is used with respect to the parameters.

● In one example, the parameter corresponds to an ID CSI-ResourceConfigId indicating CSI-ResourceConfig, the details of which are in accordance with one or more of the examples described above.

● In one example, the parameter corresponds to an ID NZP-CSI-RS-ResourceSetId indicating a set of NZP CSI-RS resources, the details of which are in accordance with one or more of the examples described above.

● In one example, the parameter corresponds to an ID CSI-SSB-ResourceSetId indicating the SSB resource set, the details of which are in accordance with one or more of the examples described above.

● In one example, the parameter corresponds to a pair of IDs (ID 1, ID 2), where id1=nzp-CSI-RS-ResourceSetId, ID2 =csi-SSB-resourcesid indicating the set of NZP CSI-RS resources. The remainder of the details regarding both IDs are in accordance with one or more examples described above.

● In one example, the parameter corresponds to an ID CSI-ResourceConfigId indicating CSI-ResourceConfig linked (or associated) with CSI reporting settings (higher layer parameters CSI-ReportConfig), the details of which are in accordance with one or more of the examples described above.

In one example, parameters are included in MPE-Config-FR2 (existing in rel.16) or MPE-Config-FR2-r17 (new in rel.17, for example), MPE-Config-FR2 or MPE-Config-FR2-r17 are in turn included in the Information Element (IE) PHR-Config or PHR-Config-r 17.

● In one example, the parameter is an ID indicating a set of resources, wherein the ID is in accordance with one or more of the examples described above. This is illustrated in table 43, where resourceSet is the parameter, numberOfN-r17 is the number of SSBRI/CRI reported in MPE report. Alternatively, the parameter indicates the resource set/pool itself (without its ID), wherein the resource set/pool is according to at least one of the following examples. This is illustrated in tables 44-50, where maxme-Resources is the maximum number of SSB and/or CSI-RS Resources for MPE reporting. In one example, maxme-resources=64.

In one example, the set/pool of resources is a set/pool of NZP CSI-RS resources including NZP CSI-RS resource(s).

In one example, the resource set/pool is an SSB resource set/pool that includes SSB resource(s).

In one example, the set/pool of resources may be a mix of NZP CSI-RS resource(s) and/or SSB resource(s) in the set/pool of resources.

In one example, the resource set/pool comprises at least two separate resource sets/pools (or subsets), at least one set/pool (subset) comprising NZP CSI-RS resource(s) and at least one set/pool (subset) comprising SSB resource(s). Note that in this example, CSI-RS and SSB resources are kept in separate pools/sets/subsets.

● In one example, the parameter is configured in conjunction with one of mpe-ProhibiTimer-r 17 and mpe-Threshold-r17, the details of which are in accordance with TS 38.331 and TS 38.321. For example, mpe-ProhibiTimer-r 17 indicates both the ID and value of mpe-ProhibiTimer.

Table 43

/>

Table 44

Table 45

Watch 46

/>

Table 47

Table 48

Table 49

/>

Table 50

In one example, the candidate SSB/CSI-RS resource pool is a CSI-RS resource set configured via an IE MAC-CellGroupConfig. For example, a parameter is included in the IE MAC-CellGroupConfig, wherein the parameter is an ID indicating a set of resources, wherein the ID is in accordance with one or more examples described above. This is illustrated in table 51.

Table 51

/>

In one embodiment, beam reporting for MPE mitigation is subject to (dependent on) triggering via DCI. As described in this disclosure, such triggering triggers (indicates) beam reporting for MPE via PHR on MAC CE. Only when the UE receives a trigger via DCI, the UE may report a beam report for MPE mitigation. In one example, when MPE reporting is configured via higher layers, but no trigger is provided via DCI, the UE may report MPE reporting according to the rel.16 mechanism (i.e., 1P-MPR value and other parameters for PHR reporting on MAC CE). Also, when MPE reporting is configured via higher layers and also triggers are provided via DCI, the UE may report Q according to the new MPE reporting mechanism described in this disclosure (i.e., the UE may report Q in addition to 1P-MPR value ₁ Individual CRI/SSBRI + additional P-MPR values and other parameters for PHR reporting on MAC CE) to report MPE reporting.

In one example, the trigger DCI is DCI arranging PHR reporting on the MAC CE. The DCI includes parameters or code points for the trigger. In one example, such a field in DCI can only be presented/provided to a UE when the UE is configured with MPE reporting via higher layers.

In one example, the trigger DCI is DCI that triggers aperiodic CSI. In one example, the trigger state (e.g., state 0) corresponding to MPE reporting may be included in a CSI-aperiodic trigger state list, as shown in table 52. For example, the trigger state may indicate CSI-ReportConfig corresponding to MPE reporting.

Watch 52

/>

Any of the above-described variant embodiments may be utilized independently or in combination with at least one other variant embodiment.

Fig. 21 shows a flowchart of a method 2100 for operating a User Equipment (UE), in accordance with an embodiment of the present disclosure, the method 2100 may be performed by a UE, such as UE 116. The embodiment of method 2100 shown in fig. 21 is for illustration only. Fig. 21 is not intended to limit the scope of the present disclosure to any particular embodiment.

As shown in fig. 21, method 2100 begins at step 2102. In step 2102, the UE (e.g., 111-116 as shown in fig. 1) receives information regarding a report including at least one capability value regarding Uplink (UL) transmissions.

In step 2104, the UE determines at least one capability value.

In step 2106, the UE determines a report comprising an indicator indicating at least one capability value.

In step 2108, the UE sends the report.

In one embodiment, the capability value corresponds to a maximum number of Sounding Reference Signal (SRS) antenna ports associated with the UL transmission.

In one embodiment, the capability value corresponds to at least one of a maximum number of SRS antenna ports or a maximum number of layers or a coherence type associated with the UL transmission or a Transmit Precoding Matrix Indicator (TPMI).

In one embodiment, the report includes (R _i ,M _i ,I _i ) Where i=0, 1, …, N-1, r _i Is a resource indicator, M _i Is a measure of I _i Is an indicator indicating a capability value, the value of N being provided via this information.

In one embodiment, the resource indicator is a channel state information reference signal resource indicator (CRI) or a Synchronization Signal Block (SSB) resource indicator (SSBRI), and the metric is a layer 1 reference signal received power (L1-RSRP) or a layer 1 signal to interference plus noise ratio (L1-SINR).

In one embodiment, the UE transmits UE capability information including a supported set of capability values (S), and the information about the report is subject to the UE capability information.

In one embodiment, when the capability value corresponds to a maximum SRS port number, the set (S) includes {1,2,4}.

Fig. 22 shows a flowchart of another method 2200 according to an embodiment of the disclosure, which method 2200 may be performed by a Base Station (BS), such as BS 102. The embodiment of the method 2200 shown in fig. 22 is for illustration only. Fig. 22 is not intended to limit the scope of the present disclosure to any particular embodiment.

As shown in fig. 22, method 2200 begins at step 2202. In step 2202, the BS (e.g., 101-103 as shown in fig. 1) generates information about a report including at least one capability value for Uplink (UL) transmission.

In step 2204, the BS transmits the report.

In step 2206, the BS receives the report, wherein the report includes an indicator indicating at least one capability value.

In one embodiment, the report includes (R _i ,M _i ,I _i ) Where i=0, 1, …, n-1, r _i Is a resource indicator, M _i Is a measure of I _i Is an indicator indicating a capability value, via which the value of N is provided.

In one embodiment, the BS receives UE capability information including a supported set of capability values (S), and the information about the report is subject to the UE capability information.

The above-described flow diagrams illustrate example methods that may be implemented according to the principles of the present disclosure, and various changes may be made to the methods illustrated in the flow diagrams herein. For example, while shown as a series of steps, individual steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps may be omitted or replaced with other steps.

Fig. 23 shows a block diagram of a UE structure according to an embodiment of the present disclosure. Fig. 23 corresponds to an example of the UE of fig. 3.

As shown in fig. 23, a UE according to an embodiment may include a transceiver 2310, a memory 2320, and a processor 2330. The transceiver 2310, the memory 2320 and the processor 2330 of the UE may operate according to the communication method of the UE described above. However, components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. In addition, the processor 2330, the transceiver 2310, and the memory 2320 may be implemented as a single chip. Further, the processor 2330 may include at least one processor.

The transceiver 2310 is collectively referred to as a UE receiver and a UE transmitter, and may transmit/receive signals to/from a base station or a network entity. Signals transmitted to or received from a base station or network entity may include control information and data. The transceiver 2310 may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal and an RF receiver for low-noise amplifying and down-converting the frequency of a received signal. However, this is merely an example of transceiver 2310 and the components of transceiver 2310 are not limited to RF transmitters and RF receivers.

In addition, the transceiver 2310 may receive a signal through a wireless channel and output it to the processor 2330, and transmit a signal output from the processor 2330 through a wireless channel.

Memory 2320 may store programs and data required for operation of the UE. Further, the memory 2320 may store control information or data included in signals obtained by the UE. The memory 2320 may be a storage medium such as read-only memory (ROM), random-access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The processor 2330 may control a series of processes such that the UE operates as described above. For example, the transceiver 2310 may receive a data signal including a control signal transmitted by a base station or a network entity, and the processor 2330 may determine the result of receiving the control signal and the data signal transmitted by the base station or the network entity.

Fig. 24 shows a block diagram illustrating a structure of a base station according to an embodiment of the present disclosure. Fig. 24 corresponds to an example of the gNB of fig. 2.

As shown in fig. 24, a base station according to an embodiment may include a transceiver 2410, a memory 2420, and a processor 2430. The transceiver 2410, memory 2420 and processor 2430 of a base station can operate in accordance with the communication methods of the base station described above. However, the components of the base station are not limited thereto. For example, a base station may include more or fewer components than those described above. Further, the processor 2430, the transceiver 2410, and the memory 2420 may be implemented as a single chip. Further, the processor 2430 can include at least one processor.

The transceiver 2410 is collectively referred to as a base station receiver and a base station transmitter, and may transmit/receive signals to/from a terminal or network entity. Signals transmitted or received to or from the terminal or network entity may include control information and data. Transceiver 2410 may include an RF transmitter to upconvert and amplify the frequency of a transmitted signal and an RF receiver to low-noise amplify and downconvert the frequency of a received signal. However, this is merely an example of transceiver 2410 and components of transceiver 2410 are not limited to RF transmitters and RF receivers.

Further, the transceiver 2410 may receive signals through a wireless channel and output them to the processor 2430, and transmit signals output from the processor 2430 through the wireless channel.

The memory 2420 may store programs and data required for the operation of the base station. Further, the memory 2420 may store control information or data included in a signal obtained by the base station. The memory 2420 may be a storage medium such as Read Only Memory (ROM), random Access Memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

Processor 2430 can control a series of processes such that the base station operates as described above. For example, the transceiver 2410 may receive a data signal including a control signal transmitted by the terminal, and the processor 2430 may determine a result of receiving the control signal and the data signal transmitted by the terminal.

According to various embodiments, a User Equipment (UE) includes: at least one transceiver; and at least one processor operably coupled to the at least one transceiver, wherein the at least one processor is configured to: the method includes transmitting UE capability information including a supported set of capability values to a base station, receiving configuration information regarding Channel State Information (CSI) reports from the base station, identifying a capability value corresponding to a maximum Sounding Reference Signal (SRS) antenna port number of the UE, identifying a CSI report including an indicator indicating the capability value, and transmitting the identified CSI report to the base station.

In one embodiment, wherein the indicator further indicates a value of the resource indicator and a value of the metric.

In one embodiment, wherein the configuration information regarding CSI reporting corresponds to UE capability information.

In one embodiment, where the capability value corresponds to a maximum number of SRS ports, the supported set of capability values includes {1,2,4}.

In one embodiment, wherein the capability value corresponds to at least one of a maximum number of layers or a coherence type associated with UL transmissions or a Transmit Precoding Matrix Indicator (TPMI).

According to various embodiments, a Base Station (BS) includes: at least one transceiver; and at least one processor operably coupled to the at least one transceiver, wherein the at least one processor is configured to: the method includes receiving UE capability information including a set of supported capability values from a user equipment, transmitting configuration information regarding Channel State Information (CSI) reports to the UE, and receiving CSI reports from the UE including an indicator indicating the capability values, wherein the capability values correspond to a maximum number of Sounding Reference Signal (SRS) antenna ports of the UE.

According to various embodiments, a method performed by a User Equipment (UE), the method comprising: the method includes transmitting UE capability information including a supported set of capability values to a base station, receiving configuration information regarding Channel State Information (CSI) reports from the base station, identifying a capability value corresponding to a maximum Sounding Reference Signal (SRS) antenna port number of the UE, identifying a CSI report including an indicator indicating the capability value, and transmitting the identified CSI report to the base station.

According to various embodiments, a method performed by a Base Station (BS), the method comprising: the method includes receiving UE capability information including a set of supported capability values from a user equipment, transmitting configuration information regarding Channel State Information (CSI) reports to the UE, and receiving CSI reports from the UE including an indicator indicating the capability values, wherein the capability values correspond to a maximum number of Sounding Reference Signal (SRS) antenna ports of the UE.

Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. The disclosure is intended to embrace such alterations and modifications that fall within the scope of the appended claims. Any description in this application should not be construed as implying that any particular element, step, or function is a essential element which must be included in the claims scope. The scope of patented subject matter is defined by the claims.

Claims

1. A User Equipment (UE), comprising:

at least one transceiver; and

at least one processor operatively coupled to the at least one transceiver,

wherein the at least one processor is configured to:

transmitting UE capability information including the supported set of capability values to the base station,

configuration information regarding Channel State Information (CSI) reports is received from the base station,

a capability value indicating a maximum number of Sounding Reference Signal (SRS) antenna ports for the UE is identified,

determining that the report includes a CSI report indicating an indicator of the capability value, and

and sending the identified CSI report to the base station.

2. The UE of claim 1, wherein the indicator further indicates a value of a resource indicator and a value of a metric.

3. The UE of claim 2, wherein the resource indicator is a channel state information reference signal resource indicator (CRI) or a Synchronization Signal Block (SSB) resource indicator (SSBRI), and the metric is a layer 1 reference signal received power (L1-RSRP) or a layer 1 signal-to-interference-and-noise ratio (L1-SINR).

4. The UE according to claim 1,

wherein the configuration information on CSI reporting corresponds to the UE capability information.

5. The UE of claim 4, wherein the supported set of capability values comprises {1,2,4} if the capability value corresponds to a maximum number of SRS ports.

6. The UE of claim 1, wherein the capability value corresponds to at least one of a maximum number of layers or a coherence type associated with UL transmissions or a Transmit Precoding Matrix Indicator (TPMI).

7. A base station, comprising:

at least one transceiver; and

at least one processor operatively coupled to the at least one transceiver,

wherein the at least one processor is configured to:

UE capability information including a set of supported capability values is received from a User Equipment (UE),

transmitting configuration information regarding Channel State Information (CSI) reporting to the UE, and

A CSI report including an indicator indicating a capability value is received from the UE,

wherein the capability value indicates a maximum number of Sounding Reference Signal (SRS) antenna ports for the UE.

8. The BS of claim 7, wherein the indicator further indicates a value of a resource indicator and a value of a metric.

9. The BS of claim 8, wherein the resource indicator is a channel state information reference signal resource indicator (CRI) or a Synchronization Signal Block (SSB) resource indicator (SSBRI), and the metric is a layer 1 reference signal received power (L1-RSRP) or a layer 1 signal to interference plus noise ratio (L1-SINR).

10. The BS of claim 7, wherein the BS,

11. The BS of claim 10, wherein the supported set of capability values comprises {1,2,4} if the capability value corresponds to a maximum number of SRS ports.

12. The BS of claim 7, wherein the capability value corresponds to at least one of a maximum number of layers or a coherence type associated with UL transmissions or a Transmit Precoding Matrix Indicator (TPMI).

13. A method performed by a User Equipment (UE), the method comprising:

Transmitting UE capability information including a supported set of capability values to a base station;

receiving configuration information about Channel State Information (CSI) reports from the base station;

identifying a capability value indicating a maximum Sounding Reference Signal (SRS) antenna port number for the UE;

determining that the report includes a CSI report indicating an indicator of the capability value; and

and sending the identified CSI report to the base station.

14. A method performed by a Base Station (BS), the method comprising:

receiving User Equipment (UE) capability information comprising a set of supported capability values from a UE;