[go: up one dir, main page]

WO2024239709A1 - Rapport de faisceau - Google Patents

Rapport de faisceau Download PDF

Info

Publication number
WO2024239709A1
WO2024239709A1 PCT/CN2024/075053 CN2024075053W WO2024239709A1 WO 2024239709 A1 WO2024239709 A1 WO 2024239709A1 CN 2024075053 W CN2024075053 W CN 2024075053W WO 2024239709 A1 WO2024239709 A1 WO 2024239709A1
Authority
WO
WIPO (PCT)
Prior art keywords
csi
threshold
report
event triggered
dci
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/075053
Other languages
English (en)
Inventor
Bingchao LIU
Chenxi Zhu
Lingling Xiao
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2024/075053 priority Critical patent/WO2024239709A1/fr
Publication of WO2024239709A1 publication Critical patent/WO2024239709A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication

Definitions

  • the present disclosure relates to wireless communications, and more specifically to beam reporting.
  • a wireless communications system may include one or multiple network communication devices, such as base stations (BSs) , which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • BSs base stations
  • eNB eNodeB
  • gNB next-generation NodeB
  • 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) .
  • time resources e.g., symbols, slots, subframes, frames, or the like
  • frequency resources e.g., subcarriers, carriers
  • 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) ) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • beam management may be crucial for efficient communication. Beams may be formed dynamically based on the channel conditions, user location, network requirements, or other factors. In general, beam management includes procedures for beamforming, beam tracking, and beam reporting. However, these procedures related to beam management in various communication systems may need to be further improved, so as to provide better communication performance.
  • the present disclosure relates to methods, apparatuses, and systems that support beam reporting.
  • Some implementations of the method and devices described herein include, receiving, from a base station, a downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) for an uplink control information (UCI) transmission for event triggered beam reporting, wherein the DCI is based on a first scheduling request (SR) for requesting the UCI transmission and includes an indication associated with at least one channel state information (CSI) report configuration for the event triggered beam reporting; and transmitting, via the transceiver and to the base station, the UCI transmission including a beam report.
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • UCI uplink control information
  • CSI channel state information
  • Some implementations of the method and devices described herein may include, receiving, from the base station, a downlink signaling for updating a channel measurement resource (CMR) or at least one resource in the CMR associated with a CSI report configuration among the one or more CSI report configurations.
  • CMR channel measurement resource
  • the CMR may comprise at least one channel state information reference signal (CSI-RS) resource or at least one synchronization signal block (SSB) resource.
  • CSI-RS channel state information reference signal
  • SSB synchronization signal block
  • the indication may comprise at least one CSI request field indicating at least one CSI request codepoint associated with at least one identity (ID) of the at least one CSI report configuration.
  • the at least one CSI request field may be included in the DCI with a first DCI format or a second DCI format, and the DCI with the first format or the second DCI format may be scrambled by one of the following: a cell-radio network temporary identifier (C-RNTI) ; a semi-persistent CSI-RNTI (SP-CSI-RNTI) ; or a dedicated RNTI configured for the UCI transmission for the event triggered beam reporting.
  • C-RNTI cell-radio network temporary identifier
  • SP-CSI-RNTI semi-persistent CSI-RNTI
  • dedicated RNTI configured for the UCI transmission for the event triggered beam reporting.
  • the first SR may be transmitted from the UE to the base station, and may have a higher priority than a second SR for regular uplink transmissions and a lower priority than a third SR for a beam failure recovery (BFR) .
  • BFR beam failure recovery
  • a CMR associated with the at least one CSI report configuration may be associated with a serving cell for the UE, and wherein the event triggered beam reporting may be triggered based on at least one of the following events: qualities of a first number of resources in the CMR are equal to or larger than a first threshold; qualities of a second number of resources in the CMR are larger than a first quality with a first offset, wherein the first quality is a quality of a resource associated with an indicated transmission configuration indication (TCI) state among a plurality of activated TCI states, and the first offset is equal to or larger than a second threshold; or qualities of resources associated with the plurality of activated TCI states are less than a third threshold, and qualities of a third number of resources in the CMR are larger than a fourth threshold.
  • TCI transmission configuration indication
  • a quality of a resource in the CMR may be one of a layer 1 (L1) -reference signal received power (RSRP) , a L1-singal to interference noise ratio (SINR) , or an average value of the L1-RSRP or the L1-SINR in a measurement window.
  • L1 layer 1
  • SINR L1-singal to interference noise ratio
  • the first threshold or the third threshold may be a block error rate (BLER) based on a plurality of specific hypothetical physical downlink control channel (PDCCH) transmission parameters; and/or the fourth threshold is a L1-RSRP.
  • BLER block error rate
  • PDCCH physical downlink control channel
  • the event triggered beam reporting may be triggered in the case that the at least one event is identified for a plurality of continuous times in at least one time window.
  • the beam report may comprise one of the following: resource indicators for a plurality of reported resources among resources in a CMR associated with the at least one CSI report configuration; and qualities of the plurality of reported resources, wherein qualities of the reported resources comprise one of the following qualities corresponding to each of the plurality of reported resources: a L1-RSRP, a L1-SINR, or an average value of the L1-RSRP or the L1-SINR.
  • a CMR associated with the at least one CSI report configuration may be associated with one or more candidate cells, and wherein each of the one or more candidate cells may have a physical cell identity (PCI) different from that of a serving cell for the UE, and wherein the event triggered beam reporting may be triggered based on at least one of the following events: qualities of a fourth number of candidate cells are equal to or larger than a fifth threshold; or a quality of the serving cell is less than a sixth threshold, and qualities of a fifth number of candidate cells are larger than a seventh threshold.
  • PCI physical cell identity
  • a CMR associated with the at least one CSI report configuration may be associated with one or more candidate cells, and wherein each of the one or more candidate cells may have a physical cell identity (PCI) different from that of a serving cell for the UE, and wherein the event triggered beam reporting may be triggered based on the following event: qualities of a sixth number of candidate cells are larger than a second quality with a second offset, wherein the second quality is a quality of the serving cell, and the second offset is equal to or larger than an eighth threshold.
  • PCI physical cell identity
  • a quality of a candidate cell is an average value of a seventh number of maximum RSRPs of resources in the CMR associated with the candidate cell; and/or a quality of the serving cell is an average value of an eighth number of maximum RSRPs of resources associated with the serving cell.
  • the method and devices described herein may include at least one of the following: in the case that each of a ninth number of maximum RSRPs of resources associated with the candidate cell is equal to or larger than the fifth threshold, the quality of the candidate cell is equal to or larger than the fifth threshold; in the case that each of a tenth number of maximum RSRPs of resources associated with the serving cell is less than the sixth threshold, the quality of the serving cell is less than the sixth threshold; or in the case that each of an eleventh number of maximum RSRPs of resources associated a candidate cell is equal to or larger than the seventh threshold, the quality of the candidate cell is equal to or larger than the seventh threshold.
  • the beam report may be an event triggered beam report among a plurality of CSI reports
  • some implementations may include one of the following: in the case that the plurality of CSI reports are overlapped in a time domain, a priority of the event triggered beam report is higher than a priority of an aperiodic CSI report and a semi-persistent CSI report on the PUSCH among the plurality of CSI reports; or a priority of the event triggered beam report carried on the PUSCH with a first identity is higher than that of a further event triggered beam report carried on the PUSCH with a second identity, wherein the first identity is smaller than the second identity.
  • Some implementations of the method and devices described herein include, transmitting, to a user equipment (UE) , a downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) for an uplink control information (UCI) transmission for event triggered beam reporting, wherein the DCI is based on a first scheduling request (SR) for requesting the UCI transmission and includes an indication associated with at least one channel state information (CSI) report configuration for the event triggered beam reporting; and receiving, from the UE, the UCI transmission including a beam report.
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • UCI uplink control information
  • CSI channel state information
  • Some implementations of the method and devices described herein may include, transmitting, to the UE, a downlink signaling for updating a channel measurement resource (CMR) or at least one resource in the CMR associated with a CSI report configuration among the one or more CSI report configurations.
  • CMR channel measurement resource
  • the CMR may comprise at least one channel state information reference signal (CSI-RS) resource or at least one synchronization signal block (SSB) resource.
  • CSI-RS channel state information reference signal
  • SSB synchronization signal block
  • the indication may comprise at least one CSI request field indicating at least one CSI request codepoint associated with at least one identity (ID) of the at least one CSI report configuration.
  • the at least one CSI request field may be included in the DCI with a first DCI format or a second DCI format, and the DCI with the first format or the second DCI format may be scrambled by one of the following: a cell-radio network temporary identifier (C-RNTI) ; a semi-persistent CSI-RNTI (SP-CSI-RNTI) ; or a dedicated RNTI configured for the UCI transmission for the event triggered beam reporting.
  • C-RNTI cell-radio network temporary identifier
  • SP-CSI-RNTI semi-persistent CSI-RNTI
  • dedicated RNTI configured for the UCI transmission for the event triggered beam reporting.
  • Some implementations of the method and devices described herein may include, receiving, from the UE, the first SR, and wherein the first SR may have a higher priority than a second SR for regular uplink transmissions and a lower priority than a third SR for a beam failure recovery (BFR) .
  • BFR beam failure recovery
  • a CMR associated with the at least one CSI report configuration may be associated with a serving cell for the UE, and some implementations may include receiving, from the UE, the first SR based on at least one of the following events: qualities of a first number of resources in the CMR are equal to or larger than a first threshold; qualities of a second number of resources in the CMR are larger than a first quality with a first offset, wherein the first quality is a quality of a resource associated with an indicated transmission configuration indication (TCI) state among a plurality of activated TCI states, and the first offset is equal to or larger than a second threshold; or qualities of resources associated with the plurality of activated TCI states are less than a third threshold, and qualities of a third number of resources in the CMR are larger than a fourth threshold.
  • TCI transmission configuration indication
  • a quality of a resource in the CMR may be one of a layer 1 (L1) -reference signal received power (RSRP) , a L1-singal to interference noise ratio (SINR) , or an average value of the L1-RSRP or the L1-SINR in a measurement window.
  • L1 layer 1
  • SINR L1-singal to interference noise ratio
  • the first threshold or the third threshold is a block error rate (BLER) based on a plurality of specific hypothetical physical downlink control channel (PDCCH) transmission parameters; or the fourth threshold is a L1-RSRP.
  • BLER block error rate
  • PDCCH physical downlink control channel
  • Some implementations of the method and devices described herein may include, receiving, from the UE, the first SR in the case that the at least one event may be identified for a plurality of continuous times in at least one time window.
  • the beam report may comprise one of the following: resource indicators for a plurality of reported resources among resources in a CMR associated with the at least one CSI report configuration; and qualities of the plurality of reported resources, wherein qualities of the reported resources comprise one of the following qualities corresponding to each of the plurality of reported resources: a L1-RSRP, a L1-SINR, or an average value of the L1-RSRP or the L1-SINR.
  • a CMR associated with the at least one CSI report configuration may be associated with one or more candidate cells, and wherein each of the one or more candidate cells may have a physical cell identity (PCI) different from that of a serving cell for the UE, and some implementations may include receiving, from the UE, the first SR based on at least one of the following events: qualities of a fourth number of candidate cells are equal to or larger than a fifth threshold; or a quality of the serving cell is less than a sixth threshold, and qualities of a fifth number of candidate cells are larger than a seventh threshold.
  • PCI physical cell identity
  • a CMR associated with the at least one CSI report configuration may be associated with one or more candidate cells, and wherein each of the one or more candidate cells has a physical cell identity (PCI) different from that of a serving cell for the UE, and some implementations may include receiving, from the UE, the first SR based on the following event: qualities of a sixth number of candidate cells are larger than a second quality with a second offset, wherein the second quality is a quality of the serving cell, and the second offset is equal to or larger than an eighth threshold.
  • PCI physical cell identity
  • a quality of a candidate cell is an average value of a seventh number of maximum RSRPs of resources in the CMR associated with the candidate cell; or a quality of the serving cell is an average value of an eighth number of maximum RSRPs of resources associated with the serving cell.
  • Some implementations of the method and devices described herein may include at least one of the following: in the case that each of a ninth number of maximum RSRPs of resources associated with the candidate cell is equal to or larger than the fifth threshold, the quality of the candidate cell is equal to or larger than the fifth threshold; in the case that each of a tenth number of maximum RSRPs of resources associated with the serving cell is less than the sixth threshold, the quality of the serving cell is less than the sixth threshold; or in the case that each of an eleventh number of maximum RSRPs of resources associated a candidate cell is equal to or larger than the seventh threshold, the quality of the candidate cell is equal to or larger than the seventh threshold.
  • the beam report is an event triggered beam report among a plurality of CSI reports, wherein one of the following: in the case that the plurality of CSI reports are overlapped in a time domain, a priority of the event triggered beam report is higher than a priority of an aperiodic CSI report and a semi-persistent CSI report on the PUSCH among the plurality of CSI reports; or a priority of the event triggered beam report carried on the PUSCH with a first identity is higher than that of a further event triggered beam report carried on the PUSCH with a second identity, wherein the first identity is smaller than the second identity.
  • FIG. 1 illustrates an example of a wireless communications system that supports beam reporting in accordance with aspects of the present disclosure.
  • FIG. 2 illustrates an example signaling diagram illustrating an example process that supports beam reporting in accordance with aspects of the present disclosure.
  • FIG. 3 illustrates an example of a device that support beam reporting in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example of a processor that support beam reporting in accordance with aspects of the present disclosure.
  • FIG. 5 illustrates a flowchart of a method that supports beam reporting in accordance with aspects of the present disclosure.
  • FIG. 6 illustrates a flowchart of a method that supports beam reporting in accordance with aspects of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.
  • the term “communication network” refers to a network following any suitable communication standards, such as, 5G new radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) , and so on.
  • NR 5G new radio
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a user equipment and a network device in the communication network may be performed according to any suitable generation communication protocols, including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • any suitable generation communication protocols including but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will also be future type communication technologies and systems in which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned systems.
  • the term “network device” generally refers to a node in a communication network via which a user equipment can access the communication network and receive services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , a radio access network (RAN) node, an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , an infrastructure device for a V2X (vehicle-to-everything) communication, a transmission and reception point (TRP) , a reception point (RP) , a remote radio head (RRH) , a relay, an integrated access and backhaul (IAB) node, a low power node such as a femto a base station (BS) , a pico BS,
  • UE user equipment
  • a user equipment generally refers to any end device that may be capable of wireless communications.
  • a user equipment may also be referred to as a communication device, a terminal device, an end user device, a subscriber station (SS) , an unmanned aerial vehicle (UAV) , a portable subscriber station, a mobile station (MS) , or an access terminal (AT) .
  • SS subscriber station
  • UAV unmanned aerial vehicle
  • MS mobile station
  • AT access terminal
  • the user equipment may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable user equipment, a personal digital assistant (PDA) , a portable computer, a desktop computer, an image capture user equipment such as a digital camera, a gaming user equipment, a music storage and playback appliance, a vehicle-mounted wireless user equipment, a wireless endpoint, a mobile station, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , a USB dongle, a smart device, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device (for example, a remote surgery device) , an industrial device (for example, a robot and/or other wireless devices operating in an industrial and/or an automated processing chain
  • FIG. 1 illustrates an example of a wireless communications system (or referred to as communication network) 100 that supports beam reporting in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment) , one or more UEs 104, a core network 106, and a packet data network 108.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network.
  • LTE-A LTE-Advanced
  • the wireless communications system 100 may be a 5G network, such as an NR network.
  • 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.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G. 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.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • a network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a communication interface.
  • a network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112.
  • a network entity 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.
  • a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs 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 mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT Internet-of-Things
  • IoE Internet-of-Everything
  • MTC machine-type communication
  • a UE 104 may be stationary in the wireless communications system 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1.
  • a UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1.
  • a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a communication interface.
  • a network entity 102 may support communications with the core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another 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) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • one or more network entities 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) .
  • TRPs transmission-reception points
  • a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open Radio Access Network (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • IAB integrated access backhaul
  • OF-RAN open Radio Access Network
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.
  • CU central unit
  • DU distributed unit
  • RU radio unit
  • RIC RAN Intelligent Controller
  • RIC e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC)
  • SMO Service Management and Orchestration
  • An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack.
  • the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signalling (e.g., RRC, service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, MAC layer) functionality and signalling, and may each be at least partially controlled by the CU.
  • L1 e.g., physical (PHY) layer
  • L2 radio link control
  • RLC radio link control
  • a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack.
  • the DU may support one or multiple different cells (e.g., via one or more RUs) .
  • a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
  • a CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • a CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u)
  • a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface)
  • FH open fronthaul
  • a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 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) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • 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 network entities 102 associated with the core network 106.
  • NAS non-access stratum
  • the core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • 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 core network 106 via a network entity 102.
  • the core network 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 core network 106 (e.g., one or more network functions of the core network 106) .
  • the network entities 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) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the network entities 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 subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first numerology associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.
  • a time interval of a 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.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • 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.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • 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) .
  • 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
  • FR5 114.25 GHz
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities 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) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • NW Network (NW) controlled beam measurement and beam reporting for beam management was specified in the first version of new radio (NR) and has been enhanced from Rel-16 to Rel-18 for performance improvement or for signaling overhead reduction.
  • NR new radio
  • the network needs to configure/activate frequent periodic or semi-persistent beam reporting (e.g., N best beams and corresponding layer 1 reference signal received powers (L1-RSRPs) ) or triggers frequent aperiodic beam reporting.
  • UL uplink
  • the NW may first configure up to 128 joint/downlink (DL) TCI state for a BWP of a serving cell by a radio resource control (RRC) signaling. Based on the beam report corresponding to periodic/semi-persistent/aperiodic beam measurement and beam reporting, the NW may activate up to 8 joint or DL TCI states for one or two transmission reception points (TRP) sand any one of them may be indicated for DL channel/reference signal (RS) reception. To ensure the system performance with the indicated TCI state, which is selected among the activated TCI states, the NW should carefully select the TCI states for activation.
  • RRC radio resource control
  • Some embodiments in the present disclosure involve a UE initiated beam reporting procedure to help the NW select proper TCI states for activation for a BWP of a serving cell.
  • FIG. 2 illustrates an example signaling diagram illustrating an example process that supports beam reporting in accordance with aspects of the present disclosure.
  • the process 200 may involve a UE 201 and a base station 202.
  • the UE 201 may be an example of the UE 104.
  • the base station 202 may be an example of the network entity 102. It would be appreciated that although the process 200 is applied in the communication environment 100 of FIG. 1, this process may be likewise applied to other communication scenarios with similar issues.
  • the base station 202 may transmit (210) , for example via its transceiver, to the UE 201, a downlink control information (DCI) 205 for scheduling a physical uplink shared channel (PUSCH) for an uplink control information (UCI) transmission for event triggered beam reporting.
  • the DCI 205 may be based on a first scheduling request (SR) for requesting the UCI transmission 215 and may include an indication associated with at least one channel state information (CSI) report configuration for the event triggered beam reporting.
  • SR scheduling request
  • CSI channel state information
  • the UE 201 may receive (212) , for example via its transceiver, from the base station 202, the DCI 205 above.
  • the UE 201 may transmit (214) , for example via its transceiver, to the base station 202, the UCI transmission 215 including a beam report.
  • the base station 202 may receive (216) , for example via its transceiver, from the UE 201, the UCI transmission 215 above.
  • the UE 201 may be configured with one or more CSI report configurations, for example, higher layer information element CSI-ReportConfig, which can be used for the CSI report for intra-cell measurement, or LTM-CSI-ReportConfig, which can be used for CSI report for L1/L2 triggered mobility, dedicated for UE initiated beam reporting.
  • one or more CSI report configurations may be configured for the event triggered beam reporting.
  • the CSI-ReportConfig or the LTM-CSI-ReportConfig may be configured with a higher layer parameter reportType set to ‘eventTriggered’ .
  • UE initiated beam report is triggered be specified event, so UE initiated beam report is also called event driven or event triggered beam report.
  • resources for measurement may be configured for the UE 201 and may be updated by a downlink (DL) signaling.
  • the UE 201 may monitor a quality of the periodic QCL-TypeD RS, which can be a CSI-RS for beam management or a CSI-RS for tracking (TRS) , configured in all the activated joint/DL TCI states to monitor the radio link quality.
  • a UE can be configured with multiple TCI states for a BWP of a serving cell and one or more of the configured TCI states can be activated for a BWP of serving cell.
  • a UE can be configured with a joint TCI state in a BWP of a serving cell for the UE to determine the spatial receive (Rx) filter, i.e., Rx beam, for the DL reception as well as the spatial transmit (Tx) filter, i.e., Tx beam, for the UL transmission in joint TCI mode; or be indicated with a DL TCI state which is used for the UE to determine the Rx beam and a UL TCI state which is used for the UE to determine the Tx beam in a BWP of a serving cell.
  • a beam is represented by a reference signal, e.g., a CSI-RS resource or an SSB.
  • a NZP CSI-RS resource set containing K periodic or semi-persistent NZP CSI-RS resources are configured as the channel measurement resource (CMR) of the CSI-ReportConfig or LTM-CSI-ReportConfig for the UE 201 to identify new candidate beams for TCI state activation.
  • the configured NZP CSI-RS resource set is called as the candidate beam identification set hereinafter. Since all the K NZP CSI-RS resources in the CMR will be measured by the UE 201, the number K should be configured according to capability of the UE 201.
  • the measurement resources associated with the CSI-ReportConfig or the LTM-CSI-ReportConfig may be semi-statically updated. For example, if the activated TCI states are updated by the unified TCI state activation/deactivation MAC CE, the candidate beam identification set may need to be updated as well, e.g., by a MAC CE.
  • the base station 202 may transmit, and the UE 201 may receive, a downlink signaling for updating a channel measurement resource (CMR) or at least one resource in the CMR associated with a CSI report configuration among the one or more CSI report configurations.
  • the downlink signaling may be a DCI, a MAC CE or a RRC signaling.
  • An example of the CSI report configuration may be CSI-ReportConfig or the LTM-CSI-ReportConfig.
  • the CMR may comprise at least one channel state information reference signal (CSI-RS) resource or at least one synchronization signal block (SSB) resource.
  • CSI-RS channel state information reference signal
  • SSB synchronization signal block
  • the base station 202 may transmit the downlink signaling to the UE 201 via the transceiver of the base station 202, and the UE 201 may receive the downlink signaling from the base station 202 via the transceiver of the UE 201.
  • the transceivers of the UE 201 and the base station 202 may be used for other receiving or transmitting operations as mentioned below between the UE 201 and the base station 202.
  • multiple CSI-ReportConfigs or LTM-CSI-ReportConfigs may be configured for the event triggered beam reporting, the network (NW, e.g. the base station 202) may dynamically activate any one of them when the activated joint/DL TCI state is updated.
  • the network e.g. the base station 202
  • the network may dynamically activate any one of them when the activated joint/DL TCI state is updated.
  • any one of the CSI-ReportConfig or LTM-CSI-ReportConfig configured for the event triggered beam reporting may be activated by the DL signaling, such as a DCI, a MAC CE or a RRC signaling.
  • the CSI-ReportConfig or the LTM-CSI-ReportConfig may be activated by the Unified TCI States Activation/Deactivation MAC CE, which is used for the TCI state activation for a BWP of a serving cell for the UE 201.
  • one CSI-ReportConfig or LTM-CSI-ReportConfig is configured for the event triggered beam reporting, while the CMR associated with the CSI-ReportConfig or LTM-CSI-ReportConfig, or the NZP CSI-RS resources or SSB resources within the CSI resource set for the CMR may be updated by a MAC CE.
  • the UE 201 may directly report the beam report (including beam measurement results) in layer 1 (L1) as an uplink control information (UCI) to reduce the latency. For example, as shown in FIG. 2, the UE 201 may transmit the UCI transmission 215 including the beam report to the base station 202.
  • a dedicated scheduling request (SR) is configured for the UE 201 to request a physical uplink shared channel (PUSCH) transmission for the beam report corresponding a CSI-ReportConfig for the event triggered beam reporting.
  • the dedicated SR may be an example of the first SR transmitted from the UE 201 to the base station 202.
  • the first SR may have a higher priority than a SR (referred to as a second SR) for regular uplink transmissions and a lower priority than a SR (referred to as a third SR) for a beam failure recovery (BFR) request, that is the dedicated SR above should have a higher priority than a regular SR and have a lower priority than the SR for beam failure recovery (BFR) request.
  • the NW e.g. the base station 202
  • DCI downlink control information
  • the indication included in the DCI 205 may comprise at least one CSI request field indicating at least one CSI request codepoint associated with at least one identity (ID) of the at least one CSI report configuration.
  • the DCI 205 can use the CSI request field to indicate the CSI request codepoint associated with a CSI-ReportConfigId or a LTM-CSI-ReportConfigId.
  • the CSI-ReportConfigId or the LTM-CSI-ReportConfigId may be an example of the ID of the at least one CSI report configuration.
  • the at least one CSI request field may be included in the DCI 205 with a first DCI format or a second DCI format.
  • An example of the first DCI format may be DCI format 0_1.
  • An example of the second DCI format may be DCI format 0_2.
  • the DCI 205 with the first format or the second DCI format may be scrambled by a cell-radio network temporary identifier (C-RNTI) , or a semi-persistent CSI-RNTI (SP-CSI-RNTI) , or a dedicated RNTI configured for the UCI transmission for the event triggered beam reporting.
  • C-RNTI cell-radio network temporary identifier
  • SP-CSI-RNTI semi-persistent CSI-RNTI
  • a dedicated RNTI configured for the UCI transmission for the event triggered beam reporting.
  • the CSI request for aperiodic CSI triggering or CSI request for semi-persistent CSI triggering may be used for the following examples 1-3.
  • one of the CSI-AssociatedTriggerState that is mapped with a non-zero CSI request field codepoint is associated with a CSI-ReportConfigId or LTM-CSI-ReportConfigId for the event triggered beam reporting, or to configure a CSI-AssociatedTriggerStateId for the CSI-ReportConfigId or the LTM-CSI-ReportConfigId for the event triggered beam reporting.
  • the PUSCH for the beam reporting may be scheduled by the DCI 205 with the DCI format 0_1 or the DCI format 0_2 scrambled by the C-RNTI containing a non-zero CSI request field which is associated with the CSI-ReportConfigId or the LTM-CSI-ReportConfigId for the event triggered beam reporting.
  • one of the CSI-SemiPersistentOnPUSCH-TriggerState that is mapped with a CSI request field codepoint is associated with the CSI-ReportConfigId or the LTM-CSI-ReportConfigId for the event triggered beam reporting, or to configure a CSI-SemiPersistentOnPUSCH-TriggerStateId for the CSI-ReportConfigId or the LTM-CSI-ReportConfigId for the event triggered beam reporting.
  • the PUSCH for the beam reporting is scheduled by the DCI 205 with the DCI format 0_1 or the DCI format 0_2 scrambled by the SP-CSI-RNTI containing a CSI request field which is associated with the CSI-ReportConfigId for the event triggered beam reporting.
  • some of the DCI field shall be set as special values.
  • the HARQ process number field and the redundancy version field may be set to all ‘0’s. Different from the semi-persistent CSI triggering, this CSI and the corresponding PUSCH only transmitted in one time.
  • a dedicated RNTI is configured for the PUSCH scheduling for the UCI reporting for the event trigger beam reporting.
  • the DCI 205 with the DCI format 0_1 or the DCI format 0_2 scrambled by EVENT-CSI-RNTI is used for the PUSCH scheduling for the CSI report for the CSI-ReportConfigId or the LTM-CSI-ReportConfigId for the event triggered beam reporting.
  • one or more CSI-Event-TriggerState may be configured by RRC, where each CSI-Event-TriggerState may be associated with one or more CSI-ReportConfigIds or LTM-CSI-ReportConfigIds for the event triggered beam reporting.
  • Each CSI-Event-TriggerState is mapped to a CSI request field codepoint value for the UE 201 to identify that the scheduled PUSCH is dedicated for the UCI reporting for the CSI-ReportConfigId or the LTM-CSI-ReportConfigId for the event triggered beam reporting.
  • the DCI 205 with a DCI format 0_0 scrambled with a dedicated RNTI may also be used to schedule the PUSCH resource for the beam reporting. This method of the process 200 may be at least applied to the case that a dedicated CSI report configuration is configured for the event triggered beam reporting.
  • the UE 201 may directly report the beam report in an UCI transmission.
  • the CSI report carrying the triggered beam report should be carried by a PUSCH to save the UL signal resources.
  • the beam measurement results corresponding to a specified event are carried by MAC CE.
  • the UE 201 needs to transmit a SR to request UL resources for the MAC CE transmission when the beam reporting is triggered.
  • the MAC CE format for the measurement results reporting corresponding to different event should be specified.
  • the UE 201 may transmit the beam report with a configured grant PUSCH by associating a CG-PUSCH with the CSI-ReportConfig for the event triggered beam reporting.
  • the beam report is carried by the earliest CG PUSCH transmission corresponding to the associated CG PUSCH configuration satisfying the timing requirement.
  • each CSI-ReportConfig for the event triggered beam reporting may be configured with one or more events to trigger the beam report.
  • the CMR associated with the at least one CSI report configuration is associated with a serving cell for the UE 201.
  • the event triggered beam reporting is triggered based on one or more of the following events: event (i) qualities of a first number of resources in the CMR are equal to or larger than a first threshold. Additionally, or alternatively, event (ii) qualities of a second number of resources in the CMR are larger than a first quality with a first offset, in which the first quality is a quality of a resource associated with an indicated transmission configuration indication (TCI) state among a plurality of activated TCI states, and the first offset is equal to or larger than a second threshold. Additionally, or alternatively, event (iii) qualities of resources associated with the plurality of activated TCI states are less than a third threshold, and qualities of a third number of resources in the CMR are larger than a fourth threshold.
  • TCI transmission configuration indication
  • a quality of a resource in the CMR is one of a layer 1 (L1) -reference signal received power (RSRP) , a L1-singal to interference noise ratio (SINR) , or an average value of the L1-RSRP or the L1-SINR in a measurement window.
  • the first threshold above e.g. Q 1 below
  • the third threshold above may be a block error rate (BLER) based on a plurality of specific hypothetical physical downlink control channel (PDCCH) transmission parameters.
  • the fourth threshold (e.g. below) may be a L1-RSRP.
  • the event triggered beam reporting may be triggered in the case that the at least one event is identified for a plurality of continuous times in at least one time window. The details will be further described below.
  • L ⁇ 1 beams, i.e., resources, in the candidate beam identification set become better than (e.g. larger than or equal to) a threshold (Q 1 )
  • Q 1 is an example of the first threshold L ⁇ 1 beams in the candidate beam identification set become better than the threshold (Q 1 ) , that is, qualities of L resources in the CMR are equal to or larger than the threshold (Q 1 ) .
  • the UE 201 only needs to monitor the qualities of the beams configured in the CMR of the dedicated CSI-ReportConfig.
  • the quality may be a L1-RSRP or a L1-SINR
  • the Q 1 may be a block error rate (BLER) which is derived based on the specific hypothetical PDCCH transmission parameters.
  • BLER block error rate
  • the UE when the UE finds L beams of the CMR with its average L1-RSRP over the slide window equals to or larger than Q 1 , it will send a SR (afirst SR) on the dedicated SR resource to request UL resource for the beam reporting.
  • the L1-RSRP for the event triggering may be a measured RSRP corresponding to a measurement instance.
  • the event triggered beam reporting may be triggered in the case that the at least one event is identified for a plurality of continuous times in at least one time window.
  • the UE 201 may send the MAC CE when the UE 201 has detected that the quality equals to or be larger than Q 1 for N 1 continuous times (which may be controlled by a counter in MAC) within a time window W 1 (which can be controlled by a timer in the MAC) , then the UE 201 may send a SR to trigger the beam reporting procedure.
  • L ⁇ 1 beams in the candidate beam identification set become offset ( ⁇ Q 2 ) better than the indicated beam, then the beam reporting is triggered.
  • the qualities of L resources in the CMR are larger than the first quality with the first offset.
  • L is an example of the second number
  • L is an integer
  • Q 2 may be an example of the second threshold.
  • Qualities of L ⁇ 1 beams in the candidate beam identification set refer to the qualities of the second number of resources in the CMR.
  • the quality of the indicated beam refers to the first quality, i.e. the quality of a resource associated with an indicated TCI state among a plurality of activated TCI states for a BWP of a serving cell.
  • the UE 201 needs to monitor the qualities of the beams configured in CMR and the beam associated with the indicated joint and/or DL transmission configuration indication (TCI) states.
  • TCI transmission configuration indication
  • L1-RSRP as the quality is preferred.
  • the UE may compare the qualities of the beams in CMR (i.e. the qualities of the resources in the CMR) against Q 0 to find L ⁇ 1 beams satisfy the condition whose quality is better than Q 0 with an offset (an example of the first offset) .
  • Q 0 is the quality of the indicated joint/DL TCI state, i.e., the first quality.
  • the UE 201 if the UE 201 detects that L beams in the CMR with qualities are better than Q 0 , and the quality offset (i.e. the first offset) equals to or larger than Q 2 , then the UE will send a SR (i.e. the first SR) to trigger the beam report procedure.
  • the quality offset i.e. the first offset
  • the event triggered beam reporting may be triggered in the case that the at least one event is identified for a plurality of continuous times in at least one time window.
  • the quality offset i.e. the first offset
  • the UE will send a SR (i.e. the first SR) to trigger the beam report procedure.
  • the beam reporting is triggered.
  • All the activated TCI states become worse than a threshold in other words, the qualities of resources associated with the plurality of activated TCI states of a BWP of a serving cell are less than a third threshold.
  • the threshold is an example of the third threshold.
  • L ⁇ 1 beams become better than a threshold in other words, the qualities of a third number of resources in the CMR are larger than a fourth threshold.
  • L is an example of the third number, an L is an integer.
  • the threshold is an example of the fourth threshold.
  • BLER block error rate
  • the UE 201 may firstly monitor the quality of all the activated TCI states, when the qualities of all the activated TCI state is below then the UE may further monitor the qualities of the beams in the CMR against when L out of all the beams in CMR are identified with qualities better than the UE may trigger the beam reporting.
  • the event triggered beam reporting may be triggered in the case that the at least one event is identified for a plurality of continuous times in at least one time window.
  • the UE 201 has detected that qualities of all the activated TCI states are less than for N 1 continuous times (which can be controlled by a counter in MAC layer) within a time window W 1 (which can be controlled by a timer in MAC layer) , and identify L beams in CMR with the radio link quality better than the threshold within another time window, the UE will send a SR (i.e. the first SR) to trigger the beam report procedure.
  • a SR i.e. the first SR
  • the base station 202 may receive the first SR in the case that the at least one event is identified for the plurality of continuous times in the at least one time window.
  • the UE may send the SR when the event is detected for a measurement time instance.
  • the beam report may comprise resource indicators for a plurality of reported resources among resources in the CMR associated with the at least one CSI report configuration.
  • the plurality of reported resource may be one of the first number of resources, the second number of resources or third number of resources above.
  • the beam report may comprise L CSI-RS resource indicators (CRIs) for the identified NZP CSI-RS resources with the quality better than Q 1 above.
  • the beam report may further comprise qualities of the plurality of reported resources.
  • the qualities of the reported resources may comprise qualities corresponding to each of the plurality of reported resources, for example, the L1-RSRP, the L1-SINR, or the average value of the L1-RSRP or the L1-SINR.
  • the beam report may comprise the L1-RSRP or the L1-SINR correspond to each of the reported NZP CSI-RS resources.
  • the CMR associated with the at least one CSI report configuration may be associated with a serving cell for the UE 201.
  • the CMR associated with the at least one CSI report configuration may be associated with one or more candidate cells.
  • Each of the one or more candidate cells may have a physical cell identity (PCI) different from that of the serving cell for the UE 201.
  • PCI physical cell identity
  • the CSI-ReportConfig or the LTM-CSI-ReportConfig is configured for event triggered beam measurement/report for inter-cell operation, e.g., by setting reportType as ‘eventTriggered’ .
  • reportType as ‘eventTriggered’
  • a CMR including CSI-RS or SSB associated with serving cell PCI, and/or one of an additional PCI, which is different from the serving cell PCI or candidate cell PCI may be configured for beam measurement.
  • CSI Resource Set including multiple SSBs is configured for the CSI-ReportConfig or the LTM-CSI-ReportConfig for channel measurement as that in NR release 18.
  • Each of the SSBs may be associated with a PCI. This can be used for the case that the UE 201 only need to monitor the performance for one or more candidate cells and the serving cells are monitored by another set of CSI report configuration, e.g., for inter-cell beam management scenario without L1/L2 triggered mobility.
  • the UE 201 may be configured with a set of PCIs or candidate cell indices and the SSB indices associated with each PCI or candidate cell.
  • the CMR is configured by a list of PCI/candidate cell index and each PCI/candidate cell index is associated with a set of SSBs for measurement.
  • explicit CSI resource set is not needed. This can be used for the case that the UE 201 is required to compare the quality of serving cell and the candidate cells for potential cell switch in L1 and/or L2, e.g., for L1/L2 triggered mobility scenario.
  • the event triggered beam reporting may be triggered based on events (a) , (b) and (c) below.
  • Event (a) qualities of a fourth number of candidate cells equal to or be larger than a fifth threshold.
  • Event (b) a quality of the serving cell is less than a sixth threshold, and qualities of a fifth number of candidate cells are larger than a seventh threshold.
  • Event (c) qualities of a sixth number of candidate cells are larger than a second quality with a second offset, in which the second quality is a quality of the serving cell, and the second offset is equal to or larger than an eighth threshold.
  • CSI-RSs and/or SSBs associated with a serving PCI i.e.
  • the UE 201 only needs to measure the beams configured for candidate cell. For the event (b) and the event (c) above, if CSI-RSs/SSBs associated with serving PCI are configured in the CMR, then the UE may measure the beams configured for the serving cell as well as the beams configured for multiple candidate cells.
  • an example of the event (a) may be defined as ‘E (a) : L ⁇ 1 candidate cells become better than a threshold’ .
  • the threshold is the fifth threshold
  • L is an integer representing the fourth number.
  • an example of the event (b) may be defined as ‘E (b) : The serving cell is worse than a threshold and L ⁇ 1 candidate cells become better than a further threshold’ .
  • L is an integer representing the fifth number
  • the threshold may be the sixth threshold
  • the further threshold may be the seventh threshold.
  • an example of the event (c) may be defined as ‘E (c) : L ⁇ 1 candidate cells become offset (equal to or larger than a threshold) better than the serving cell’ .
  • L is an integer representing the sixth number
  • offset may be the second offset
  • the threshold may be the eighth threshold.
  • a quality of a candidate cell may be an average value of a seventh number of maximum RSRPs of resources in the CMR associated with the candidate cell.
  • a quality of the serving cell may be an average value of an eighth number of maximum RSRPs of resources associated with the serving cell.
  • the quality of a cell (acandidate cell or a serving cell) may be referred to as performance of the cell.
  • L1-RSRP is basically used as a metric for cell quality evaluation.
  • layer 3 (L3) -RSRP which is filtered over measured L1-RSRP of adjacent occasions can be used (as the metric) based on UE capability when the candidate cell is one of the neighbor cells configured for L3 mobility.
  • the cell level quality may be the average L1/L3-RSRP of the top-K beams of the cell, in which K is an integer representing the seventh number for the candidate cell or the eighth number for the serving cell.
  • a candidate cell is identified when the average L1-RSRP/L3-RSRP of the top-K beams equals to or larger than a configured threshold.
  • the configured threshold is the fifth threshold and represented as Q 1 .
  • the average L1/L3-RSRP of the top-K beams of each candidate cell and the serving cell is used for the cell quality monitoring.
  • a candidate cell or a serving cell may be identified when the average L1-RSRP/L3-RSRP of the top-K beams equals to or larger than a configured threshold.
  • the sixth threshold is represented as and the seventh threshold is represented as
  • RSRP k, l is the L1-RSRP or the L3-RSRP of resource k in a candidate cell l.
  • RSRP k, serving is the L1-RSRP or the L3-RSRP of resource k in the serving cell.
  • the average L1-RSRP/L3-RSRP of the top-K beams of each candidate cell and the serving cell is used for the cell quality monitoring. As shown in the following formula, represents a quality of the candidate cell l, and represents a quality of the serving cell. If the offset (i.e. the second offset between the quality of the candidate cell and the quality of the serving cell is equal to or larger than a threshold (i.e. the eighth threshold, represented as Q 2a as shown in the following formula) , then the candidate cell is identified.
  • a threshold i.e. the eighth threshold, represented as Q 2a as shown in the following formula
  • the cell level quality may be associated with each of a number of maximum RSRPs of resources associated with the cell.
  • the cell level quality is associated with the L1-RSRP or L3-RSRP of the top-K beams of a same cell.
  • the quality of the candidate cell is equal to or larger than the fifth threshold.
  • the quality of the serving cell is less than the sixth threshold.
  • the quality of the candidate cell is equal to or larger than the seventh threshold.
  • the UE 201 may trigger the beam report procedure when the condition is satisfied for one beam measurement instance. In some other examples, if L1-RSRP is used for quality monitoring, the UE 201 may trigger the beam report procedure when event has been detected for N 1 continuous times (which can be controlled by a counter in MAC layer) within a time window W 1 (which can be controlled by a timer in MAC layer) .
  • the CMR associated with the at least one CSI report configuration is associated with one or more candidate cells
  • the beam report may comprise the identified candidate cell and the beams in the candidate cell.
  • the NW e.g. the base station 202
  • the NW may indicate the UE 201 to always report the top-K beams and the corresponding L1-RSRPs of the identified candidate cells in the beam report.
  • the beam report for a certain event is reported by a MAC CE, it’s carried by a PUSCH as a data transmission and no collision handling principle is needed.
  • the event is report as a type of UCI in L1, when two PUSCHs carrying UCI are overlapped in a time domain and only one of them can be transmitted, priority may be needed for the UE 201 when only one UCI can be transmitted by one PUSCH. Prioritization is also needed when UCI carrying PUSCH collides with PUCCH. Because the event triggered beam report is carried by PUSCH, it should have higher priority than the CSI carried by PUCCH.
  • the beam report is an event triggered beam report among a plurality of CSI reports.
  • a priority of the event triggered beam report is higher than a priority of an aperiodic CSI report and a semi- persistent CSI report on the PUSCH among the plurality of CSI reports. For example, considering that the beam report corresponding to an event may be more important than the regular beam report because the regular beam report may be the same as the last report, it should have higher priority than the aperiodic beam report and the semi-persistent beam report on PUSCH.
  • a priority of the event triggered beam report carried on the PUSCH with a first identity may be higher than that of a further event triggered beam report carried on the PUSCH with a second identity, in which the first identity is smaller than the second identity.
  • the CSI-ReportConfigId associated with the beam report will be used to determine its priority.
  • the CSI-ReportConfigId smaller, the corresponding priority higher. The example below may be used for describe the priority.
  • PriiCSI (y, k, c, s) 2 ⁇ Ncells ⁇ Ms ⁇ y + Ncells ⁇ Ms ⁇ k + Ms ⁇ c + s
  • c is the serving cell index and Ncells is the value of the higher layer parameter maxNrofServingCells
  • s is the reportConfigID and Ms is the value of the higher layer parameter maxNrofCSI-ReportConfigurations.
  • a first CSI report is said to have priority over second CSI report if the associated PriiCSI (y, k, c, s) value is lower
  • a UE initiated beam report mechanism is proposed.
  • One or two activated TCI states may be indicated as a common beam for all the DL reception and/or UL transmission.
  • Dedicated CSI-ReportConfig is configured for event triggered beam report and several events are proposed. Different from event beam reporting by the MAC CE, e.g., beam report for BFR (Beam Failure Recovery) , UCI based event triggered beam report in L1 is proposed: a dedicated SR is configured for event triggered beam report and DCI format 0_1/0_2 with CSI request field is used to schedule the PUSCH resources for the UCI reporting.
  • BFR Beam Failure Recovery
  • an event triggered beam report for LTM (lower layer triggered mobility) is proposed, where the UE only need to send the beam report when one or more good cells are identified based on the proposed events.
  • LTM lower layer triggered mobility
  • more timely beam reporting may be implemented, and beam reporting overhead may be reduced, in addition, it is helpful for the network to select proper TCI states to be activated for a BWP of a serving cell for the UE.
  • FIG. 3 illustrates an example of a device 300 that supports beam reporting in accordance with aspects of the present disclosure.
  • the device 300 may be an example of a UE 104 as described herein.
  • the device 300 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 300 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 302, a memory 304, a transceiver 306, and, optionally, an I/O controller 308. 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) .
  • interfaces e.g., buses
  • the processor 302, the memory 304, the transceiver 306, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 302, the memory 304, the transceiver 306, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 302, the memory 304, the transceiver 306, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 302 and the memory 304 coupled with the processor 302 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 302, instructions stored in the memory 304) .
  • the processor 302 may support wireless communication at the device 300 in accordance with examples as disclosed herein.
  • the processor 302 may be configured to operable to support a means for receiving, from a base station, a downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) for an uplink control information (UCI) transmission for event triggered beam reporting, wherein the DCI is based on a first scheduling request (SR) for requesting the UCI transmission and includes an indication associated with at least one channel state information (CSI) report configuration for the event triggered beam reporting; and a means for, transmitting, to the base station, the UCI transmission including a beam report.
  • the processor 302 may be configured to operable to support other means for other implementations of method 500.
  • the processor 302 may be configured to operable to support a means for transmitting, to a user equipment (UE) , a downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) for an uplink control information (UCI) transmission for event triggered beam reporting, wherein the DCI is based on a first scheduling request (SR) for requesting the UCI transmission and includes an indication associated with at least one channel state information (CSI) report configuration for the event triggered beam reporting; and a means for receiving, from the UE, the UCI transmission including a beam report.
  • the processor 302 may be configured to operable to support other means for other implementations of method 600.
  • the processor 302 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 302 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 302.
  • the processor 302 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 304) to cause the device 300 to perform various functions of the present disclosure.
  • the memory 304 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 302 cause the device 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 code may not be directly executable by the processor 302 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 304 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 308 may manage input and output signals for the device 300.
  • the I/O controller 308 may also manage peripherals not integrated into the device M02.
  • the I/O controller 308 may represent a physical connection or port to an external peripheral.
  • the I/O controller 308 may utilize an operating system such as or another known operating system.
  • the I/O controller 308 may be implemented as part of a processor, such as the processor 302.
  • a user may interact with the device 300 via the I/O controller 308 or via hardware components controlled by the I/O controller 308.
  • the device 300 may include a single antenna 310. However, in some other implementations, the device 300 may have more than one antenna 310 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 306 may communicate bi-directionally, via the one or more antennas 310, wired, or wireless links as described herein.
  • the transceiver 306 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 306 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 310 for transmission, and to demodulate packets received from the one or more antennas 310.
  • the transceiver 306 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain 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 transmit chain 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 transmit chain may also include one or more antennas 310 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 310 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain 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 receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • FIG. 4 illustrates an example of a processor 400 that supports beam reporting in accordance with aspects of the present disclosure.
  • the processor 400 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 400 may include a controller 402 configured to perform various operations in accordance with examples as described herein.
  • the processor 400 may optionally include at least one memory 404. Additionally, or alternatively, the processor 400 may optionally include one or more arithmetic-logic units (ALUs) 406.
  • ALUs arithmetic-logic units
  • 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 400 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.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • 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 400) 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) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 402 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 400 to cause the processor 400 to support various operations in accordance with examples as described herein.
  • the controller 402 may operate as a control unit of the processor 400, generating control signals that manage the operation of various components of the processor 400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 402 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 404 and determine subsequent instruction (s) to be executed to cause the processor 400 to support various operations in accordance with examples as described herein.
  • the controller 402 may be configured to track memory address of instructions associated with the memory 404.
  • the controller 402 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 402 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 400 to cause the processor 400 to support various operations in accordance with examples as described herein.
  • the controller 402 may be configured to manage flow of data within the processor 400.
  • the controller 402 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 400.
  • ALUs arithmetic logic units
  • the memory 404 may include one or more caches (e.g., memory local to or included in the processor 400 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 404 may reside within or on a processor chipset (e.g., local to the processor 400) .
  • the memory 404 may reside external to the processor chipset (e.g., remote to the processor 400) .
  • the memory 404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 400, cause the processor 400 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 402 and/or the processor 400 may be configured to execute computer-readable instructions stored in the memory 404 to cause the processor 400 to perform various functions (e.g., functions or tasks supporting transmit power prioritization) .
  • the processor 400 and/or the controller 402 may be coupled with or to the memory 404, the processor 400, the controller 402, and the memory 404 may be configured to perform various functions described herein.
  • the processor 400 may include multiple processors and the memory 404 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 406 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 406 may reside within or on a processor chipset (e.g., the processor 400) .
  • the one or more ALUs 406 may reside external to the processor chipset (e.g., the processor 400) .
  • One or more ALUs 406 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 406 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 406 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 406 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 406 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 406 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 400 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 402 may be configured to or operable to support a means for receiving, from a base station, a downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) for an uplink control information (UCI) transmission for event triggered beam reporting, wherein the DCI is based on a first scheduling request (SR) for requesting the UCI transmission and includes an indication associated with at least one channel state information (CSI) report configuration for the event triggered beam reporting; and a means for, transmitting, to the base station, the UCI transmission including a beam report.
  • the processor 400 may be configured to or operable to support other means for other implementations of method 500.
  • the processor 402 may be configured to or operable to support a means for transmitting, to a user equipment (UE) , a downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) for an uplink control information (UCI) transmission for event triggered beam reporting, wherein the DCI is based on a first scheduling request (SR) for requesting the UCI transmission and includes an indication associated with at least one channel state information (CSI) report configuration for the event triggered beam reporting; and a means for receiving, from the UE, the UCI transmission including a beam report.
  • the processor 400 may be configured to or operable to support other means for other implementations of method 600.
  • FIG. 5 illustrates a flowchart of a method 500 that supports beam reporting in accordance with aspects of the present disclosure.
  • the operations of the method 500 may be implemented by a device or its components as described herein.
  • the operations of the method 500 may be performed by the UE 201 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method includes receiving, from a base station, a downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) for an uplink control information (UCI) transmission for event triggered beam reporting, wherein the DCI is based on a first scheduling request (SR) for requesting the UCI transmission and includes an indication associated with at least one channel state information (CSI) report configuration for the event triggered beam reporting.
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • UCI uplink control information
  • SR scheduling request
  • CSI channel state information
  • the method may include transmitting, to the base station, the UCI transmission including a beam report.
  • the operations of 510 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 510 may be performed by a device as described with reference to FIG. 1.
  • FIG. 6 illustrates a flowchart of a method 600 that supports beam reporting in accordance with aspects of the present disclosure.
  • the operations of the method 600 may be implemented by a device or its components as described herein.
  • the operations of the method 600 may be performed by the base station 202 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method includes transmitting, to a user equipment (UE) , a downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) for an uplink control information (UCI) transmission for event triggered beam reporting, wherein the DCI is based on a first scheduling request (SR) for requesting the UCI transmission and includes an indication associated with at least one channel state information (CSI) report configuration for the event triggered beam reporting.
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • UCI uplink control information
  • SR scheduling request
  • CSI channel state information
  • the method may include receiving, from the UE, the UCI transmission including a beam report.
  • the operations of 610 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 610 may be performed by a device as described with reference to FIG. 1.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • 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.
  • a list of items 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) .
  • 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.
  • a “set” may include one or more elements.

Landscapes

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

Abstract

Divers aspects de la présente divulgation concernent le rapport de faisceau. Selon un aspect, un équipement utilisateur (UE) reçoit, en provenance d'une station de base, des informations de commande de liaison descendante (DCI) pour planifier un canal partagé de liaison montante physique (PUSCH) pour une transmission d'informations de commande de liaison montante (UCI) pour un rapport de faisceau déclenché par un événement. Les DCI sont basées sur une première demande de planification (SR) pour demander la transmission d'UCI et comprennent une indication associée à au moins une configuration de rapport d'informations d'état de canal (CSI) pour le rapport de faisceau déclenché par un événement. L'UE transmet, à la station de base, la transmission d'UCI comprenant un rapport de faisceau.
PCT/CN2024/075053 2024-01-31 2024-01-31 Rapport de faisceau Pending WO2024239709A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/075053 WO2024239709A1 (fr) 2024-01-31 2024-01-31 Rapport de faisceau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/075053 WO2024239709A1 (fr) 2024-01-31 2024-01-31 Rapport de faisceau

Publications (1)

Publication Number Publication Date
WO2024239709A1 true WO2024239709A1 (fr) 2024-11-28

Family

ID=93588858

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/075053 Pending WO2024239709A1 (fr) 2024-01-31 2024-01-31 Rapport de faisceau

Country Status (1)

Country Link
WO (1) WO2024239709A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN120111541A (zh) * 2025-05-09 2025-06-06 荣耀终端股份有限公司 上报波束报告的方法和通信装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023280043A1 (fr) * 2021-07-05 2023-01-12 维沃移动通信有限公司 Procédé de notification de faisceaux et terminal
WO2023077401A1 (fr) * 2021-11-05 2023-05-11 Qualcomm Incorporated Techniques de transmission d'informations de commande de liaison montante en deux parties pour un rapport de faisceau basé sur un groupe
US20230344490A1 (en) * 2020-09-15 2023-10-26 Lg Electronics Inc. Method and device for beam reporting in wireless communication system
WO2023240601A1 (fr) * 2022-06-17 2023-12-21 Lenovo (Beijing) Limited Mesure de faisceau et rapport de faisceau initiés par un ue

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230344490A1 (en) * 2020-09-15 2023-10-26 Lg Electronics Inc. Method and device for beam reporting in wireless communication system
WO2023280043A1 (fr) * 2021-07-05 2023-01-12 维沃移动通信有限公司 Procédé de notification de faisceaux et terminal
WO2023077401A1 (fr) * 2021-11-05 2023-05-11 Qualcomm Incorporated Techniques de transmission d'informations de commande de liaison montante en deux parties pour un rapport de faisceau basé sur un groupe
WO2023240601A1 (fr) * 2022-06-17 2023-12-21 Lenovo (Beijing) Limited Mesure de faisceau et rapport de faisceau initiés par un ue

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN120111541A (zh) * 2025-05-09 2025-06-06 荣耀终端股份有限公司 上报波束报告的方法和通信装置

Similar Documents

Publication Publication Date Title
WO2024239709A1 (fr) Rapport de faisceau
WO2024160063A1 (fr) Rapport de faisceau entraîné par événement pour tci unifiées
WO2024156192A1 (fr) Rapport sur l'état des retards
WO2024156187A1 (fr) Établissement de rapports de csi
WO2025123703A1 (fr) Communication associée à un résultat de mesure
WO2025107605A1 (fr) Rapport de faisceaux
WO2025107615A1 (fr) Indication de saut relative à des intervalles de mesure
WO2025232292A1 (fr) Modèle de rapport de csi
WO2024213187A1 (fr) Indication de condition supplémentaire côté réseau
WO2024250718A1 (fr) Détermination de nœud intermédiaire
WO2025086738A1 (fr) Surveillance de liaison radio ou reprise après défaillance de faisceau
WO2024109163A1 (fr) Surveillance de performance basée sur une rsrp différentielle pour un modèle ou une fonctionnalité d'ia/am
WO2025060443A1 (fr) Améliorations apportées à un rapport de faisceau initié par un ue
WO2025167196A1 (fr) Indication de l'importance de données sur la liaison montante
WO2024109145A1 (fr) Transmission dans une fenêtre de mesure
WO2025246435A1 (fr) Rapport de faisceau basé sur un groupe
WO2025035816A1 (fr) Transmission de prach
WO2024183344A1 (fr) Configuration pour signal de référence d'informations d'état de canal
WO2024250732A1 (fr) Commande pour système iot ambiant
WO2025030919A1 (fr) Gestion de collision dans un intervalle de mesure
WO2024169259A1 (fr) Prédiction d'informations d'état de canal
WO2025123697A1 (fr) Procédure de lp-wus pour équipement utilisateur
WO2025156689A1 (fr) Rapport de surveillance
WO2025035788A1 (fr) Commande pour système d'ido-a
WO2025152403A1 (fr) Configuration pour rapport de faisceau initié par un ue

Legal Events

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

Ref document number: 24809959

Country of ref document: EP

Kind code of ref document: A1