WO2025097817A1

WO2025097817A1 - Csi process for ue initiated beam report

Info

Publication number: WO2025097817A1
Application number: PCT/CN2024/103873
Authority: WO
Inventors: Bingchao LIU; Yi Zhang; Wei Ling
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2024-07-05
Filing date: 2024-07-05
Publication date: 2025-05-15
Anticipated expiration: 2027-01-05

Abstract

Various aspects of the present disclosure relate to methods, apparatuses, and systems that are related to channel state information (CSI) process for UE initiated (UEI) beam report. Some implementations of the method and apparatuses described herein may include a user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: report a capability on time requirement for UEI beam report, if the UE supports mode#A, the capability on the time requirement includes: a first minimal time requirement between the last symbol of reception of downlink control information (DCI) scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.

Description

CSI PROCESS FOR UE INITIATED BEAM REPORT

TECHNICAL FIELD

The present disclosure relates to wireless communications, and more specifically to channel state information (CSI) process for UE initiated (UEI) beam report.

BACKGROUND

A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .

This disclosure targets CSI process for UE initiated beam report.

SUMMARY

An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

The present disclosure relates to methods, apparatuses, and systems that support UE initiated beam report.

Some implementations of the method and apparatuses described herein may further include a user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: report a capability on time requirement for UEI beam report, if the UE supports mode#A, the capability on the time requirement includes: a first minimal time requirement between the last symbol of reception of DCI scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.

Some implementations of the method and apparatuses described herein may include a processor in a UE for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: report a capability on time requirement for UEI beam report, if the UE supports mode#A, the capability on the time requirement includes: a first minimal time requirement between the last symbol of reception of DCI scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.

Some implementations of the method and apparatuses described herein may include a method performed by a UE, the method comprising: reporting a capability on time requirement for UEI beam report, if the UE supports mode#A, the capability on the time requirement includes: a first minimal time requirement between the last symbol of reception of DCI scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.

In some embodiment, if the UE supports mode#B, the capability on the time requirement further includes: a third minimal time requirement between transmission of a UEI beam report notification and the first symbol of transmission of the uplink channel carrying the UEI beam report.

The value of each of the first and second minimal time requirements is selected from existing values specified in the network initiated beam report, or existing values involved in physical uplink shared channel (PUSCH) scheduling, or values reported by UE; while the value of the third minimal time requirement is selected from existing values specified in the network initiated beam report, or values reported by UE.

One CSI process unit is occupied for a CSI report configuration configured for the UEI beam report; and one CSI process unit is occupied for any event or any combination of events configured for the UE initiated beam report.

When event-1 that quality of the current beam is worse than a configured threshold is configured, CSI process unit is occupied from the first symbol of the reference signal (RS) transmission for the current beam until Z’ symbols after the reception of the RS for the current beam, where Z’ symbols are used for the UE to compute the quality of the current beam and compare the same with the configured threshold.

When event-2 that quality of at least one new beam becomes a threshold value better than the current beam is configured, CSI process unit is occupied from the first symbol of each transmission occasion of an RS resource group including the RS resources for new beam identification and the RS associated with the current beam until Z’ symbols after the last symbol of the RS resource group, where Z’ symbols are used for the UE to compute and compare the quality of each of the beams.

When event-3 that quality of at least one new beam becomes a threshold value better than the RS derived from the activated transmission configuration indication (TCI) state with the worst quality or event-4 that quality of at least one new beam becomes a threshold value better than the RS derived from the activated TCI state with the best quality is configured, CSI process unit is occupied from the first symbol of each transmission occasion of an RS resource group including the RS resources for new beam identification and the RSs derived from all the activated joint or downlink (DL) TCI states for the bandwidth part (BWP) of a serving cell until Z’ symbols after the last symbol of the RS resource group, where Z’ symbols are used for the UE to compute and compare the quality of each of the beams.

Z’ is a value selected from existing values specified in the network initiated beam report.

In mode#A, when the UEI beam report is triggered, CSI process unit is occupied from the last symbol of the UEI beam report scheduling request until the last symbol of the uplink channel carrying the UEI beam report. In mode#B, when the UEI beam report is triggered, CSI process unit is occupied from the last symbol of the UEI beam report notification until the last symbol of the uplink channel carrying the UEI beam report.

Some implementations of the method and apparatuses described herein may include at least one memory; and at least one processor coupled with the at least one memory and configured to cause the base station to: receive a capability on time requirement for UEI beam report, if the UE supports mode#A, the capability on the time requirement includes: a first minimal time requirement between the last symbol of reception of DCI scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report

Some implementations of the method and apparatuses described herein may include a processor in a base station for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive a capability on time requirement for UEI beam report, if the UE supports mode#A, the capability on the time requirement includes: a first minimal time requirement between the last symbol of reception of DCI scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report

Some implementations of the method and apparatuses described herein may include a method performed by a base station, the method comprising: receiving a capability on time requirement for UEI beam report, if the UE supports mode#A, the capability on the time requirement includes: a first minimal time requirement between the last symbol of reception of DCI scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.

The value of each of the first and second minimal time requirements is selected from existing values specified in the network initiated beam report, or existing values involved in PUSCH scheduling, or values reported by UE, while the value of the third minimal time requirement is selected from existing values specified in the network initiated beam report, or values reported by UE.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

Figure 2 illustrates an example of a user equipment (UE) 200 in accordance with aspects of the present disclosure.

Figure 3 illustrates an example of a processor 300 in accordance with aspects of the present disclosure.

Figure 4 illustrates an example of a network equipment (NE) 400 in accordance with aspects of the present disclosure.

Figure 5 illustrates a first embodiment.

Figure 6 illustrates a second embodiment.

Figure 7 (a) illustrates an example of CSI processing unit (CPU) occupation for event-1 with mode#A. Figure 7 (b) illustrates an example of CPU occupation for event-1 with mode#B.

Figure 8 (a) illustrates an example of CPU occupation for event-2 with mode#A. Figure 8 (b) illustrates an example of CPU occupation for event-2 with mode#B.

Figure 9 (a) illustrates an example of CPU occupation for event-3 or event-4 with mode#A. Figure 9 (b) illustrates an example of CPU occupation for event-3 or event-4 with mode#B.

Figure 10 illustrates a flowchart of method performed by a UE in accordance with aspects of the present disclosure.

Figure 11 illustrates a flowchart of method performed by a NE in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Aspects of the present disclosure are described in the context of a wireless communications system.

Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE (Long Term Evoluation) network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a New Radio (NR) network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.

The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN) , a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN) . In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (C) device, among other examples.

A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links 116 (e.g., S1, N2, N2, or network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .

The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

The CN 106 may communicate with a packet data network 108 over one or more backhaul links (e.g., via an S1, N2, N2, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106) .

In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.

Figure 2 illustrates an example of a UE 200 in accordance with aspects of the present disclosure. The UE 200 may include a processor 202, a memory 204, a controller 206, and a transceiver 208. The processor 202, the memory 204, the controller 206, or the transceiver 208, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

The processor 202, the memory 204, the controller 206, or the transceiver 208, or various combinations or components thereof may be implemented in hardware (e.g., circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

The processor 202 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a central process unit, an ASIC, a Field Programmable Gate Array (FPGA) , or any combination thereof) . In some implementations, the processor 202 may be configured to operate the memory 204. In some other implementations, the memory 204 may be integrated into the processor 202. The processor 202 may be configured to execute computer-readable instructions stored in the memory 204 to cause the UE 200 to perform various functions of the present disclosure.

The memory 204 may include volatile or non-volatile memory. The memory 204 may store computer-readable, computer-executable code including instructions when executed by the processor 202 cause the UE 200 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 204 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

In some implementations, the processor 202 and the memory 204 coupled with the processor 202 may be configured to cause the UE 200 to perform one or more of the functions described herein (e.g., executing, by the processor 202, instructions stored in the memory 204) . For example, the processor 202 may support wireless communication at the UE 200 in accordance with examples as disclosed herein. The UE 200 may be configured to support a means for determining that a Physical Uplink Shared Channel (PUSCH) transmission is associated with a plurality of Phase-Tracking Reference Signal (PTRS) ports; and transmitting the PUSCH transmission together with the plurality of PTRS ports.

The controller 206 may manage input and output signals for the UE 200. The controller 206 may also manage peripherals not integrated into the UE 200. In some implementations, the controller 206 may utilize an operating system such as or other operating systems. In some implementations, the controller 206 may be implemented as part of the processor 202.

In some implementations, the UE 200 may include at least one transceiver 208. In some other implementations, the UE 200 may have more than one transceiver 208. The transceiver 208 may represent a wireless transceiver. The transceiver 208 may include one or more receiver chains 210, one or more transmitter chains 212, or a combination thereof.

A receiver chain 210 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 210 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 210 may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receiver chain 210 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 210 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

A transmitter chain 212 may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmitter chain 212 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmitter chain 212 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 212 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

Figure 3 illustrates an example of a processor 300 in accordance with aspects of the present disclosure. The processor 300 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 300 may include a controller 302 configured to perform various operations in accordance with examples as described herein. The processor 300 may optionally include at least one memory 304, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 300 may optionally include one or more arithmetic-logic units (ALUs) 306. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 300 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 300) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .

The controller 302 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 300 to cause the processor 300 to support various operations in accordance with examples as described herein. For example, the controller 302 may operate as a control unit of the processor 300, generating control signals that manage the operation of various components of the processor 300. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

The controller 302 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 304 and determine subsequent instruction (s) to be executed to cause the processor 300 to support various operations in accordance with examples as described herein. The controller 302 may be configured to track memory address of instructions associated with the memory 304. The controller 302 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 302 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 300 to cause the processor 300 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 302 may be configured to manage flow of data within the processor 300. The controller 302 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 300.

The memory 304 may include one or more caches (e.g., memory local to or included in the processor 300 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 304 may reside within or on a processor chipset (e.g., local to the processor 300) . In some other implementations, the memory 304 may reside external to the processor chipset (e.g., remote to the processor 300) .

The memory 304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 300, cause the processor 300 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 302 and/or the processor 300 may be configured to execute computer-readable instructions stored in the memory 304 to cause the processor 300 to perform various functions. For example, the processor 300 and/or the controller 302 may be coupled with or to the memory 304, the processor 300, the controller 302, and the memory 304 may be configured to perform various functions described herein. In some examples, the processor 300 may include multiple processors and the memory 304 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

The one or more ALUs 306 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 306 may reside within or on a processor chipset (e.g., the processor 300) . In some other implementations, the one or more ALUs 306 may reside external to the processor chipset (e.g., the processor 300) . One or more ALUs 306 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 306 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 306 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 306 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 306 to handle conditional operations, comparisons, and bitwise operations.

The processor 300 may support wireless communication in accordance with examples as disclosed herein. The processor 300 may be configured to or operable to support a means for determining that a PUSCH transmission is associated with a plurality of Phase-Tracking Reference Signal (PTRS) ports; and transmitting the PUSCH transmission together with the plurality of PTRS ports.

Figure 4 illustrates an example of a NE 400 in accordance with aspects of the present disclosure. The NE 400 may include a processor 402, a memory 404, a controller 406, and a transceiver 408. The processor 402, the memory 404, the controller 406, or the transceiver 408, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

The processor 402, the memory 404, the controller 406, or the transceiver 408, or various combinations or components thereof may be implemented in hardware (e.g., circuitry) . The hardware may include a processor, a DSP, an ASIC, or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

The processor 402 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a central process unit, an ASIC, an FPGA, or any combination thereof) . In some implementations, the processor 402 may be configured to operate the memory 404. In some other implementations, the memory 404 may be integrated into the processor 402. The processor 402 may be configured to execute computer-readable instructions stored in the memory 404 to cause the NE 400 to perform various functions of the present disclosure.

The memory 404 may include volatile or non-volatile memory. The memory 404 may store computer-readable, computer-executable code including instructions when executed by the processor 402 cause the NE 400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 404 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

In some implementations, the processor 402 and the memory 404 coupled with the processor 402 may be configured to cause the NE 400 to perform one or more of the functions described herein (e.g., executing, by the processor 402, instructions stored in the memory 404) . For example, the processor 402 may support wireless communication at the NE 400 in accordance with examples as disclosed herein.

The controller 406 may manage input and output signals for the NE 400. The controller 406 may also manage peripherals not integrated into the NE 400. In some implementations, the controller 406 may utilize an operating system such as or other operating systems. In some implementations, the controller 406 may be implemented as part of the processor 402.

In some implementations, the NE 400 may include at least one transceiver 408. In some other implementations, the NE 400 may have more than one transceiver 408. The transceiver 408 may represent a wireless transceiver. The transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof.

A receiver chain 410 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 410 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 410 may include at least one amplifier (e.g., an LNA) configured to amplify the received signal. The receiver chain 410 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 410 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

A transmitter chain 412 may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmitter chain 412 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as AM, FM, or digital modulation schemes like PSK or QAM. The transmitter chain 412 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 412 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

This disclosure relates to UE initiated (UEI) beam report.

Traditionally, beam report (e.g., CSI report with L1-RSRP reporting) was initiated at network side, e.g., by gNB. UEI beam report (BR) is being specified in NR Release 19 for UL resource overhead reduction. For example, the UE shall only trigger beam report when the condition for some specified event (s) is satisfied to avoid frequent periodic or semi-persistent beam reporting.

The examples of specified events are as follows:

Event-1: Quality, such as layer 1 reference signal received power (L1-RSRP) , of the current beam is worse than a certain threshold.

Event-2: Quality, such as L1-RSRP, of at least one new beam becomes a threshold value better than the current beam.

Event-3: Quality, such as L1-RSRP, of at least one new beam becomes a threshold value better than the reference signal (RS) derived from the activated transmission configuration indication (TCI) state with the worst quality.

Event-4: Quality, such as L1-RSRP, of at least one new beam becomes a threshold value better than the RS derived from the activated TCI state with the best quality.

If the condition of an event (e.g., any of Event-1, Event-2, Event-3, Event-4) or any combination of the events is satisfied (step 0) , UE may initiate (or trigger) a beam report (i.e., UEI beam report) . Two different modes are specified to support UEI BR.

Mode#A: dynamically scheduling uplink control information (UCI) by gNB. Three steps A1, A2 and A3 are included in UEI BR for mode#Ain addition to step 0 (which are illustrated in Figure 5) .

Step A1: UE transmits, to gNB, a first Physical Uplink Control Channel (PUCCH) to request a resource for a second UL channel to carry UL beam report. A scheduling request (SR) for UEI beam report (referred as UEI beam report SR hereinafter) is carried on the first PUCCH.

Step A2: gNB sends, to UE, a UL grant (e.g., a resource for a second UL channel) for UEI beam report where the UL grant is contained in a downlink control information (DCI) , in response to receiving the UEI beam report SR. UE detects the DCI.

Step A3: UE transmits, to gNB, the UEI beam report in the second UL channel (e.g., PUSCH or PUCCH) . Note that although either PUSCH or PUCCH can be the second UL channel, Figure 5 only shows PUSCH as the example of the second UL channel in step A3.

Mode#B: UCI in pre-configured resource (s) for the second UL channel. Two steps B1 and B2 are included in UEI BR for mode#B in addition to step 0 (which are illustrated in Figure 6) .

Step B1: UE transmits, to gNB, a first PUCCH (with one or multiple bits) carrying a UEI beam report notification that notifies gNB of UEI beam report to be carried on a second UL channel.

Step B2: UE transmits, to gNB, the UEI beam report in the second UL channel (e.g., PUSCH or PUCCH) . Note that although either PUSCH or PUCCH can be the second UL channel, Figure 6 only shows PUSCH as the example of the second UL channel in step B2.

Note that the notification in step B1 is in a separate reporting instance from the UEI beam report in step B2. It means that step B1 and step B2 are performed at different time instances with different resources.

This disclosure targets two issues to be considered in UEI BR. The first issue is to specify CSI preparation time; and the second issue is the CSI process unit (CPU) occupation behavior for UEI beam report.

The CSI preparation time includes at least CSI computation time, in which CSI is computed, and PUSCH/PUCCH assembly time, in which CSI report is assembled into PUSCH (or PUCCH) . For mode#A, the CSI preparation time also includes Physical Downlink Control Channel (PDCCH) decoding time for decoding PDCCH carrying DCI containing UL grant in step A2.

A first embodiment relates to CSI preparation for UEI beam report with mode#A.

Figure 5 illustrates the first embodiment. In mode#A, there are three phases, i.e., phases AP1, AP2 and AP3, within steps 0, A1, A2 and A3.

Phase AP1: After step 0, that is, after the condition of the UEI BR for a certain event being satisfied.

Phase AP2: After step A1, that is, after the UE sending, to gNB, UEI beam report SR that would be carried on a first UL channel (e.g., first PUCCH) . The UEI beam report SR is the request for the scheduling of the second UL channel.

Phase AP3: After step A2, that is, after receiving PDCCH carrying the DCI scheduling the second UL channel (PUSCH or PUCCH) resource for the UEI beam report transmission.

As described above, three different phases AP1, AP2 and AP3 correspond to three different timing requirements, and lead to different scheduling or configuration restrictions.

Three different UE capabilities (or behaviors) AC1, AC2 and AC3 are proposed for different scheduling or configuration restrictions.

UE capability (behavior) AC1: The CSI report preparation (e.g., CSI computation) starts in phase AP1, that is, after step 0 (i.e., after the condition of the UEI BR for a certain event is satisfied) .

The start of the CSI report preparation is before sending the UEI beam report SR in step A1. So, only PDCCH decoding time and PUSCH/PUCCH preparation time should be specified between the last symbol of the reception of the PDCCH carrying DCI containing UL grant in step A2 and the first symbol of the transmission of the PUSCH or PUCCH carrying the UEI beam report in step A3, which is named as T_UEI CSI, 1

To ensure the UE has enough CSI computation time, the network (e.g., gNB) should ensure the time between the last symbol of the reception of the latest RS resource, for which the condition for UEI BR is satisfied, and the first symbol of the first PUCCH carrying the UEI beam report SR in step A1 is enough. For example, the latest RS resource for UEI beam report associated with a PUCCH for UEI BR SR is determined based on the CSI computation time.

UE capability (behavior) AC2: The CSI report preparation (e.g., CSI computation) starts in phase AP2, that is, after step A1 (i.e., after sending the UEI beam report SR in the first PUCCH) .

The UE needs enough time to compute the CSI after sending the UEI beam report SR and before sending the PUSCH or PUCCH carrying the UEI beam report. The following two time requirements may need to be specified:

The first time requirement is T_UEI CSI, 2 defined between the last symbol of the transmission of the first PUCCH carrying UEI beam report SR in step A1 and the first symbol of the transmission of the PUSCH or PUCCH carrying the UEI beam report in step A3.This time requirement includes the CSI computation time, PDCCH decoding time and PUSCH/PUCCH preparation time.

The second time requirement is T′_UEI CSI, 2 defined between the last symbol of the reception of the PDCCH carrying DCI containing UL grant in step A2 and the first symbol of the transmission of the PUSCH or PUCCH carrying the UEI beam report in step A3.This time requirement is the same as T_UEI CSI, 1 if it is assumed that the UE can complete the CSI computation before receiving the DCI in step A2.

UE capability (behavior) AC3: The CSI report preparation (e.g., CSI computation) starts in phase AP3, that is, after step A2 (i.e., after receiving the PDCCH carrying DCI containing UL grant in step A2) . The UE needs enough CSI computation time after receiving the PDCCH carrying DCI containing UL grant and before sending the PUSCH or PUCCH carrying the UEI beam report.

A time requirement T_UEI CSI, 3 is defined between the last symbol of receiving the PDCCH carrying DCI containing UL grant in step A2 and the first symbol of the transmission of the PUSCH or PUCCH carrying the UEI beam report in step A3. This time requirement includes CSI computation time, PDCCH decoding time and PUSCH/PUCCH preparation time, although only CSI computation time is shown in Figure 5 for UE capability AC3. Incidentally, the PDCCH decoding time may be overlapped with the CSI computation time.

It can be seen from the above description of UE capabilities (behaviors) AC1, AC2 and AC3 for mode#Athat T_UEI CSI, 1, T′_UEI CSI, 2 and T_UEI CSI, 3 may have the same time length, while T_UEI CSI, 2 has another time length. In other words, for mode#A, two values, one for T_UEI CSI, 1, T′_UEI CSI, 2 and T_UEI CSI, 3, and the other for T_UEI CSI, 2, are to be specified.

Basically, existing values specified in the network initiated beam report, or existing values involved in PUSCH scheduling, or new values reported by UE can be used to specify the detailed values for T_UEI CSI, 1, T′_UEI CSI, 2 and T_UEI CSI, 3, and for T_UEI cSI, 2. In particular, the following values can be considered as specifying the detailed values for T_UEI CSI, 1, T′_UEI CSI, 2 and T_UEI CSI, 3, and for T_UEI CSI, 2.

Alternative 1: Z₃ which is used to define the time requirement between the first symbol of the PUSCH carrying the beam report and the last symbol of the reception of the PDCCH triggering the CSI report (initiated by gNB) .

Alternative 2: Z′₃ which is used to define the time requirement between the first symbol of the PUSCH carrying the beam report and the last symbol of the aperiodic CSI-RS resources for channel or interference measurement associated with the triggered CSI report (initiated by gNB) .

Alternative 3: T_proc, 2 which is used to define the time requirement between the reception of the PDCCH carrying DCI which schedules PUSCH and the transmission of the scheduled PUSCH.

Alternative 4: other new values, e.g., Z₄ for T_UEI CSI, 1, T′_UEI CSI, 2 and T_UEI CSI, 3, and Z′₄ for T_UEI CSI, 2, reported by UE as part of UE capability reporting. In one example, they can be reported as number of OFDM symbols per sub-carrier spacing.

In particular, Z₃, Z′₃, T_proc, 2 or Z₄ can be the detailed value for T_UEI CSI, 1, T′_UEI CSI, 2 and T_UEI CSI, 3, and Z₃, Z′₃, T_proc, 2 or Z′₄ can be the detailed value for T_UEI CSI, 2.

Z₃ and Z′₃ are listed in Table 1

Table 1

Table 1 is intercepted from Table 5.4-2 of Clause 5.4 of 3GPP TS38.214 V18.2.0, which is related to network initiated CSI report. μ of Table 1 corresponds to the min (μ_PDCCH, μ_CSI-RS, μ_UL) where the μ_PDCCH corresponds to the subcarrier spacing of the PDCCH with which the DCI was transmitted and μ_UL corresponds to the subcarrier spacing of the PUSCH with which the CSI report is to be transmitted and μ_CSI-RS corresponds to the minimum subcarrier spacing of the aperiodic CSI-RS triggered by the DCI. X₀, X₁, X₂, X₃, X₅, and X₆ are reported as part of UE capability beamReportTiming which indicates the number of OFDM symbols between the last symbol of SSB or CSI-RS and the first symbol of the transmission channel containing beam report for each supported sub-carrier spacing μ. KB₁, KB₂, KB₃ and KB₄ are also reported by UE.

A second embodiment relates to CSI preparation for UEI beam report with mode#B.

Figure 6 illustrates the second embodiment. In mode#B, there are two phases, i.e., phases BP1 and BP2, within steps 0, B1 and B2.

Phase BP1: After step 0, that is, after the condition of the UEI BR for a certain event being satisfied.

Phase BP2: After step B1, that is, after the UE sending, to gNB, the first PUCCH carrying a UEI beam report notification.

As described above, two different phases BP1 and BP2 correspond to two different timing requirements and lead to different scheduling or configuration restrictions.

Two different UE capabilities (behaviors) BC1 and BC2 are proposed for different scheduling or configuration restrictions.

UE capability (behavior) BC1: The CSI report preparation (e.g., CSI computation) starts in phase BP1, that is, after step 0 (i.e., after the condition of the UEI BR for a certain event is satisfied) .

The start of the CSI report preparation is before sending the UEI beam report notification in step B1. To ensure the UE has enough CSI computation time, the network (e.g., gNB) should ensure the time between the last symbol of the reception of the latest RS resource, for which the condition for UEI BR is satisfied, and the first symbol of the first PUCCH carrying the UEI beam report notification in step B1 is enough for the CSI computation time. For example, the latest RS resource for UEI beam report associated with a PUCCH for UEI BR notification is determined based on the CSI computation time.

The UEI beam report notification notifies gNB of UEI beam report to be carried on a second UL channel (e.g., PUSCH or PUCCH) . It means that the time of transmitting the UEI beam report associated with a UEI beam report notification is determined by the time of transmitting the UEI beam report notification. So, there is no need to specify any time restriction between the transmission of the UEI beam report notification and the transmission of the UEI beam report. For example, the UEI beam report notification and the associated PUSCH or PUCCH carrying the UEI beam report can be pre-configured, e.g., transmitted in a same slot.

UE capability (behavior) BC2: The CSI report preparation (e.g., CSI computation) starts in phase BP2, that is, after step B1 (i.e., after sending the UEI beam report notification in the first PUCCH) .

The UE needs enough time to compute the CSI after sending the UEI beam report notification and before sending the PUSCH or PUCCH carrying the UEI beam report.

A time requirement T_UEI CSI, 4 is defined between the last symbol of transmitting the UEI beam report notification in step B1 and the first symbol of the transmission of the PUSCH or PUCCH carrying the UEI beam report in step B2.

Basically, existing values specified in the network initiated beam report (e.g., Z′₃ in Table 1) , or new values reported by UE (e.g., Z₄) can be used to specify the detailed value for T_UEI CSI, 4.

A third embodiment relates to CPU occupation principle for UEI beam report.

To support efficient CSI report with variable report types including periodic, semi-persistent and aperiodic report for network initiated CSI report, how to occupy the CSI process unit (CPU) for variable CSI reports including L1-RSRP report, Precoding Matrix Indicator (PMI) , Rank Indicator (RI) and Channel Quality Indicator (CQI) reporting were specified in NR Release 18 specification. CPU occupation principle for UEI beam report should be specified as well.

A first issue relates to how many CPUs are occupied.

When a CSI report configuration (e.g., by an RRC information element CSI-ReportConfig) is configured for UEI beam report, O_CPU=1 CPU is occupied for each CSI-ReportConfig.

When different events are configured for a BWP (bandwidth part) of a serving cell, O_CPU=1 CPU is occupied for each event. Alternatively, if more than one event is configured for a UE in a BWP of a serving cell, O_CPU=1 CPU is occupied for all the events which can be any combination of event-1, event-2, event-3 and event-4.

A second issue relates to the time duration (e.g., number of OFDM symbols) of the CPU occupation, that is, when the CPU is occupied.

For event#1 (Quality of the current beam is worse than a configured threshold) , the CPU is occupied from the first symbol of the RS transmission for the current beam until Z’symbols after the reception of the RS for the current beam, where Z’ symbols are used for the UE to compute the quality, e.g., L1-RSRP, of the current beam and compare it with the configured threshold.

Figure 7 (a) illustrates an example of CPU occupation for event-1 with mode#A. Figure 7 (b) illustrates an example of CPU occupation for event-1 with mode#B. The CPU occupation (e.g., of 1 CPU) starts from the first symbol of each RS transmission for the current beam until Z’ symbols after the reception of the RS for the current beam. If the condition of an event (e.g., event-1) is met, UEI beam report is triggered. For mode#A, the CPU occupation (e.g., of 1 CPU) starts from the last symbol of the UEI beam report SR (step A1) until the last symbol of the PUSCH or PUCCH carrying the UEI beam report (step A3) (see Figure 7 (a) ) ; while for mode#B, the CPU occupation (e.g., of 1 CPU) starts from the last symbol of the UEI beam report notification (step B1) until the last symbol of the PUSCH or PUCCH carrying the UEI beam report (step B2) (see Figure 7 (b) ) .

For event 2, a RS resource group including the RS resources for new beam identification and the RS associated with the current beam is defined. The CPU occupation (e.g., of 1 CPU) starts from the first symbol of each transmission occasion of the RS resource group until Z’ symbols after the last symbol of the RS resource group, where Z’ symbols are used for the UE to compute and compare the quality, e.g., L1-RSRP, of each of the beams.

Figure 8 (a) illustrates an example of CPU occupation for event-2 with mode#A. Figure 8 (b) illustrates an example of CPU occupation for event-2 with mode#B. The CPU occupation (e.g., of 1 CPU) starts from the first symbol of each RS transmission for the current beam until Z’ symbols after the reception of the RS for the current beam. If the condition of an event (e.g., event-2) is met, UEI beam report is triggered. For mode#A, the CPU occupation (e.g., of 1 CPU) starts from the last symbol of the UEI beam report SR (step A1) until the last symbol of the PUSCH or PUCCH carrying the UEI beam report (step A3) (see Figure 8 (a) ) ; while for mode#B, the CPU occupation (e.g., of 1 CPU) starts from the last symbol of the UEI beam report notification (step B1) until the last symbol of the PUSCH or PUCCH carrying the UEI beam report (step B2) (see Figure 8 (b) ) .

For event 3 and event 4, a RS resource group including the RS resources for new beam identification and the RSs derived from all the activated joint or DL TCI states for the BWP of a serving cell is defined. The CPU occupation (e.g., of 1 CPU) starts from the first symbol of each transmission occasion of the RS resource group until Z’ symbols after the last symbol of the RS resource group, where Z’ symbols are used for the UE to compute and compare the quality, e.g., L1-RSRP, of each of the beams. When O_CPU=1 CPU is occupied for more than one event, the RS resource group includes the RS resources associated with all the events.

Figure 9 (a) illustrates an example of CPU occupation for event-3 or event-4 with mode#A. Figure 9 (b) illustrates an example of CPU occupation for event-3 or event-4 with mode#B. The CPU occupation (e.g., of 1 CPU) starts from the first symbol of each RS transmission for the RS resource group until Z’ symbols after the reception of the RS resource group. If the condition of an event (e.g., event-3 or event-4) is met, UEI beam report is triggered. For mode#A, the CPU occupation (e.g., of 1 CPU) starts from the last symbol of the UEI beam report SR (step A1) until the last symbol of the PUSCH or PUCCH carrying the UEI beam report (step A3) (see Figure 9 (a) ) ; while for mode#B, the CPU occupation (e.g., of 1 CPU) starts from the last symbol of the UEI beam report notification (step B1) until the last symbol of the PUSCH or PUCCH carrying the UEI beam report (step B2) (see Figure 9 (b) ) .

Figure 10 illustrates a flowchart of a method 1000 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

At 1002, reporting a capability on time requirement for UE initiated (UEI) beam report, if the UE supports mode#A, the capability on the time requirement includes: a first minimal time requirement between the last symbol of reception of downlink control information (DCI) scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.

One channel state information (CSI) process unit is occupied for a CSI report configuration configured for the UEI beam report; and one CSI process unit is occupied for any event or any combination of events configured for the UE initiated beam report.

Figure 11 illustrates a flowchart of a method 1100 in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

At 1102, receiving a capability on time requirement for UE initiated (UEI) beam report, if the UE supports mode#A, the capability on the time requirement includes: a first minimal time requirement between the last symbol of reception of downlink control information (DCI) scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.

The value of each of the first and second minimal time requirements is selected from existing values specified in the network initiated beam report, or existing values involved in physical uplink shared channel (PUSCH) scheduling, or values reported by UE, while the value of the third minimal time requirement is selected from existing values specified in the network initiated beam report, or values reported by UE.

It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A user equipment (UE) for wireless communication, comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the UE to:

report a capability on time requirement for UE initiated (UEI) beam report,

if the UE supports mode#A, the capability on the time requirement includes:

a first minimal time requirement between the last symbol of reception of downlink control information (DCI) scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and

a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.
The UE of claim 1, wherein, if the UE supports mode#B, the capability on the time requirement further includes: a third minimal time requirement between transmission of a UEI beam report notification and the first symbol of transmission of the uplink channel carrying the UEI beam report.
The UE of claim 1, wherein, the value of each of the first and second minimal time requirements is selected from existing values specified in network initiated beam report, or existing values involved in physical uplink shared channel (PUSCH) scheduling, or values reported by UE.
The UE of claim 2, wherein, the value of the third minimal time requirement is selected from existing values specified in network initiated beam report, or values reported by UE.
The UE of claim 1 or 2, wherein, one channel state information (CSI) process unit is occupied for a CSI report configuration configured for the UEI beam report.
The UE of claim 1 or 2, wherein, one CSI process unit is occupied for any event or any combination of events configured for the UE initiated beam report.
The UE of claim 1 or 2, wherein, when event-1 that quality of the current beam is worse than a configured threshold is configured, CSI process unit is occupied from the first symbol of the reference signal (RS) transmission for the current beam until Z’ symbols after the reception of the RS for the current beam, where Z’ symbols are used for the UE to compute the quality of the current beam and compare the same with the configured threshold.
The UE of claim 1 or 2, wherein, when event-2 that quality of at least one new beam becomes a threshold value better than the current beam is configured, CSI process unit is occupied from the first symbol of each transmission occasion of an RS resource group including the RS resources for new beam identification and the RS associated with the current beam until Z’ symbols after the last symbol of the RS resource group, where Z’ symbols are used for the UE to compute and compare the quality of each of the beams.
The UE of claim 1 or 2, wherein, when event-3 that quality of at least one new beam becomes a threshold value better than the RS derived from the activated transmission configuration indication (TCI) state with the worst quality or event-4 that quality of at least one new beam becomes a threshold value better than the RS derived from the activated TCI state with the best quality is configured, CSI process unit is occupied from the first symbol of each transmission occasion of an RS resource group including the RS resources for new beam identification and the RSs derived from all the activated joint or downlink (DL) TCI states for the bandwidth part (BWP) of a serving cell until Z’ symbols after the last symbol of the RS resource group, where Z’ symbols are used for the UE to compute and compare the quality of each of the beams.
The UE of claim 1, wherein, when the UEI beam report is triggered, CSI process unit is occupied from the last symbol of the UEI beam report scheduling request until the last symbol of the uplink channel carrying the UEI beam report.
The UE of claim 2, wherein, when the UEI beam report is triggered, CSI process unit is occupied from the last symbol of the UEI beam report notification until the last symbol of the uplink channel carrying the UEI beam report.
The UE of claim 7 or 8 or 9, wherein, Z’ is a value selected from existing values specified in the network initiated beam report.
A processor in a UE for wireless communication, comprising:

at least one controller coupled with at least one memory and configured to cause the processor to:

report a capability on time requirement for UE initiated (UEI) beam report,

if the UE supports mode#A, the capability on the time requirement includes:

a first minimal time requirement between the last symbol of reception of downlink control information (DCI) scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and

a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.
A method performed by a user equipment (UE) , the method comprising:

reporting a capability on time requirement for UE initiated (UEI) beam report,

if the UE supports mode#A, the capability on the time requirement includes:

a first minimal time requirement between the last symbol of reception of downlink control information (DCI) scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and

a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.
A base station for wireless communication, comprising:

at least one memory; and

at least one processor coupled with the at least one memory and configured to cause the base station to:

receive a capability on time requirement for UE initiated (UEI) beam report,

if the UE supports mode#A, the capability on the time requirement includes:

a first minimal time requirement between the last symbol of reception of downlink control information (DCI) scheduling an uplink channel and the first symbol of transmission of the uplink channel carrying the UEI beam report; and

a second minimal time requirement between the last symbol of transmission of a UEI beam report scheduling request and the first symbol of transmission of the uplink channel carrying the UEI beam report.
The base station of claim 15, wherein, if the UE supports mode#B, the capability on the time requirement further includes: a third minimal time requirement between transmission of a UEI beam report notification and the first symbol of transmission of the uplink channel carrying the UEI beam report.
The base station of claim 15, wherein, the value of each of the first and second minimal time requirements is selected from existing values specified in the network initiated beam report, or existing values involved in physical uplink shared channel (PUSCH) scheduling, or values reported by UE.
The base station of claim 16, wherein, the value of the third minimal time requirement is selected from existing values specified in the network initiated beam report, or values reported by UE.