Traffic-aware beam management for accelerated beam switching

Abstract

This disclosure provides a system, device, apparatus, and method comprising a computer program encoded on a storage medium for beam management for beam switching acceleration. A UE receives multiple beams from a network entity for signal quality measurement (408, 908). The UE communicates with the network entity via a first beam of the multiple beams. Based on the fact that the signal quality of the second beam is higher than that of the first beam and that the signal quality of the first beam exceeds a traffic type threshold, the UE sends a message to the network entity indicating that it will accelerate beam switching from the first beam to the second beam of the multiple beams (424, 524, 624, 724, 824, 924).

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication, and more specifically, to beam management in wireless communication.

Background Art

[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) defines a radio interface called 5th Generation (5G) New Radio (5G NR). The architecture for a 5G NR wireless communication system includes a 5G Core (5GC) network, a 5G Radio Access Network (5G-RAN), user equipment (UE), and so on. The 5G NR architecture aims to improve data rate, reduce latency, and / or increase capacity compared to previous-generation cellular communication systems.

[0003] Wireless communication systems generally provide various telecommunication services (such as telephone, video, data, messaging, broadcast, etc.) based on multiple access technologies such as Orthogonal Frequency Division Multiple Access (OFDMA) technology that supports communication with multiple UEs. With the improvement of mobile broadband, the progress of such wireless communication technologies continues. For example, wireless Extended Reality (XR) communication provides a better degree of freedom of movement because geographical or behavioral restrictions are removed wirelessly and XR users can move freely. However, it is difficult to achieve high data rate, high reliability, and low latency for XR communication in a wireless network.

Summary of the Invention

[0004] The following provides a brief overview of one or more embodiments to offer a basic understanding of such embodiments. This overview is not a comprehensive overview of all embodiments to be considered. This overview does not identify any important or definitive elements of all embodiments, nor does it define the scope of any or all embodiments. Its sole purpose is to present, in a simplified form, some concepts of one or more embodiments as a prelude to the more detailed explanations that will follow.

[0005] XR includes Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). XR traffic includes traffic flows of downlink (DL) VR traffic or uplink (UL) AR traffic, and UL traffic flows that transmit attitude / control information that reflects the user's position and movement to adjust AR / VR content. XR traffic is quasi-periodic traffic with a duration equal to the reciprocal of the XR frame rate. In some scenarios, XR traffic experiences jitter due to variations in the delay for encoding video frames.

[0006] XR traffic requires high data rates, high reliability, and low latency, which can be difficult to achieve in wireless networks susceptible to fading, mobility, and other factors. XR traffic is also susceptible to events that may interfere with the transmission of UL AR video traffic or DL ​​VR video traffic. These events include beam switching, bandwidth portion (BWP) switching, channel status information (CSI) measurement and reporting, and / or radio resource management (RRM) measurement. Some of these events can cause latency and jitter in XR traffic, degrading / interfering with the quality of user experience (QoE).

[0007] For example, a beam switching procedure may include beam instruction from a network (NW) entity, beam fault recovery triggered by user equipment (UE), and / or random access channel (RACH) procedures (excluding physical random access channels (PRACH) ordered by the physical downlink control channel (PDCCH) (dedicated to primary cells (PCell))). To complete the beam switching procedure, the UE identifies a first parameter of the UE beam corresponding to the new NW beam, a second parameter of DL pseudo-collocation (QCL) type A related parameters, and a third parameter of UL power control path loss. The time delay for the UE to identify these three parameters can cause latency and interfere with XR communication.

[0008] This disclosure addresses the above and other deficiencies by speeding up or accelerating the beam switching procedure. In some examples, the UE accelerates beam switching to the new beam when the new beam is of better quality than the old beam and the old beam cannot provide a threshold level of performance to support XR traffic. For example, the UE accelerates the procedure for identifying beam switching parameters to reduce the interruption time of XR communications.

[0009] For example, beam indication signaling, beam fault recovery (BFR) response, and / or random access response (RAR) can trigger aperiodic CSI reference signals (CSI-RS) to accelerate the process of identifying beam switching parameters. The UE can identify beam switching parameters based on the aperiodic CSI-RS. Downlink control information (DCI) and / or RAR can be enabled to trigger aperiodic CSI measurements and reports.

[0010] As another example, a UE may measure and store beam switching parameters during a beam measurement procedure before beam switching. The UE may identify the most likely beam, or the top N beams, and measure and store the corresponding beam switching parameters. The NW may set one or more conditions for the UE to initiate the measurement and storage of parameters (e.g., link degradation, block error rate (BLER), packet error rate (PER), latency, etc.). The UE may send a message to the NW indicating whether the UE has measured and stored the beam switching parameters for a particular beam.

[0011] As yet another example, the UE can use Layer 1 (L1)-reference signal received power (RSRP) for path loss measurement. The UE may use L1-RSRP for path loss measurement only during the transition time (for example, before the UE measures Layer 3 (L3)-RSRP). During this transition time, the NW may set a set of uplink power control parameters, e.g., a higher value P0.

[0012] As yet another example, the UE may measure channel quality information (CQI) or a simplified CQI, such as a synchronization signal block (SSB), for each beam and report it to the NW in beam reports, BFR requests, and messages. The UE may measure and report for the top N beams or all beams. The NW may set the number of beams N, which may be based on a predefined protocol.

[0013] In other examples, the UE may use different or lower BLER thresholds to perform beam fault detection in XR communications. The NW may set different or lower BLER thresholds, for example, by a Radio Resource Control (RRC) signal.

[0014] In some embodiments, the UE receives multiple beams from a network entity for signal quality measurement. The UE communicates with the network entity via a first beam among the multiple beams. Based on the fact that the signal quality of the second beam is higher than that of the first beam and that the signal quality of the first beam exceeds a traffic type threshold, the UE sends a message to the network entity indicating that it will accelerate beam switching from the first beam to the second beam among the multiple beams.

[0015] In some embodiments, a network entity transmits multiple beams to the UE for signal quality measurement. The network entity communicates with the UE via a first beam among the multiple beams. The network entity receives a message from the UE indicating that it will accelerate beam switching from the first beam to the second beam among the multiple beams, based on the fact that the signal quality of the second beam is higher than that of the first beam and that the signal quality of the first beam exceeds a traffic type threshold.

[0016] Advantageously, accelerating beam switching reduces XR communication interruption time, thus mitigating the impact on XR communication and reducing disturbances to the user's QoE. Beam switching procedures can be enhanced by speeding up or accelerating beam switching to enable transitions that mitigate the impact on the user experience. For example, enhancing beam switching may be useful in enabling beam switching with less impact on the quality of XR video. [Brief explanation of the drawing]

[0017] [Figure 1] This diagram shows a wireless communication system including multiple user devices (UEs) and network entities communicating via one or more cells. [Figure 2] This figure shows an XR traffic model for XR communication. [Figure 3]This diagram shows how to accelerate beam switching in XR communication between the UE and network entities. [Figure 4] This signaling diagram illustrates an example of communication between a UE and a network entity to accelerate beam switching by using aperiodic CSI-RS. [Figure 5] This signaling diagram illustrates an example of communication between the UE and network entities to accelerate beam switching by measuring and recording beam switching parameters before beam switching. [Figure 6] This signaling diagram illustrates an example of communication between the UE and network entities to accelerate beam switching by using L1-RSRP for path loss measurement. [Figure 7] This is a signaling diagram illustrating an example of communication between a UE and a network entity to accelerate beam switching based on CQI or a simplified CQI. [Figure 8] This signaling diagram illustrates an example of communication between a UE and a network entity to accelerate beam switching through beam fault detection using different BLER thresholds. [Figure 9] This is a flowchart of wireless communication methods in UE. [Figure 10] This is a flowchart of wireless communication methods in a network entity. [Figure 11] This figure shows an exemplary hardware implementation of a UE device. [Figure 12] This figure shows the hardware implementation of one or more exemplary network entities. [Modes for carrying out the invention]

[0018] FIG. 1 shows a diagram 100 of a wireless communication system associated with a plurality of cells 190. The wireless communication system includes a user equipment (UE) 102 and a base station / network entity 104. Some base stations may include a centralized base station architecture, and other base stations may include a distributed base station architecture. The centralized base station architecture utilizes a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node. The distributed base station architecture utilizes a protocol stack that is physically or logically distributed among two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 may be implemented within a RAN node, and one or more DUs 108 may be co-located with CU 110, or may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RUs 106. Any of RUs 106, DUs 108, and CUs 110 may be implemented as virtual units such as a virtual radio unit (VRU), virtual distributed unit (VDU), or virtual central unit (VCU). The base station / network entity 104 (e.g., a centralized base station, or a distributed unit of a base station such as RU 106 or DU 108) may be referred to as a transmission and reception point (TRP).

[0019] The operation and / or network design of base station 104 may be based on the aggregation characteristics of the base station functions. For example, a decentralized base station architecture is used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN) network, or a virtual radio access network (vRAN), which may also be called a cloud radio access network (C-RAN). Decentralization may include distributing functions across two or more units at various physical locations, or virtually distributing the functions of at least one unit, thereby enabling flexibility in network design. Various units of a decentralized base station architecture or decentralized RAN architecture may be configured for wired or wireless communication with at least one other unit. For example, base stations 104d / 104e and / or RU106a-106d may communicate with UE102a-102d and 102s via one or more radio frequency (RF) access links based on a Uu interface. In this example, multiple RU106 and / or base stations 104 can simultaneously provide services to UE102 via intracell and / or intercell access links between UE102 and RU106 / base stations 104.

[0020] RU106, DU108, and CU110 may include (or be coupled to) one or more interfaces configured to transmit or receive information / signals via a wired or wireless transmission medium. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission medium such as a front haul link 160 between RU106d and a baseband unit (BBU) 112 of a base station 104d associated with cell 190d. BBU112 includes DU108 and CU110, which may also have a wired interface (e.g., a mid haul link) configured between DU108 and CU110 to transmit or receive information / signals between DU108d and CU110d. In a further example, a wireless interface may include a transceiver such as a receiver, transmitter, or RF transceiver, which are configured to transmit and / or receive information / signals via a wireless transmission medium, such as information communicated via cross-cell communication beams 136 - 138 between RU106a of cell 190a and a base station 104e of cell 190e.

[0021] RU106 may be configured to implement lower layer functions. For example, RU106 may correspond to a logical node controlled by DU108 and hosting lower layer PHY functions such as RF processing functions, or fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, extraction and filtering of a physical random access channel (PRACH). The functions of RU106 may be based on a functional split such as a lower layer functional split.

[0022] RU106 can transmit or receive over-the-air (OTA) communications with one or more UE102s. For example, RU106b in cell 190b communicates with UE102b in cell 190b via a first set of communication beams 132 of RU106b and a second set of communication beams 134b of UE102b, these communication beams may correspond to intra-cell communication beams, or in some examples, cross-cell communication beams. For example, UE102b in cell 190b can communicate with RU106a in cell 190a via a third set of communication beams 134a of UE102b and a fourth set of communication beams 136 of RU106a. DU108 can control both real-time and non-real-time features of RU106's control plane communications and user plane communications.

[0023] Any combination of RU106, DU108, and CU110, or any individual reference to them, may correspond to base station 104. Thus, base station 104 may include at least one of RU106, DU108, or CU110. Base station 104 provides UE102 with access to the core network. Base station 104 can relay communications between UE102 and the core network (not shown). Base station 104 may be associated with a macrocell for high-power cellular base stations and / or a small cell for low-power cellular base stations. For example, cell 190e may correspond to a macrocell, while cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macrocell and at least one small cell may be called a “heterogeneous network”.

[0024] Transmission from UE102 to base station 104 / RU106 is called uplink (UL) transmission, and transmission from base station 104 / RU106 to UE102 is called downlink (DL) transmission. Uplink transmission is also called reverselink transmission, and downlink transmission is also called forwardlink transmission. For example, RU106d uses the antenna of base station 104d in cell 190d to transmit downlink / forwardlink communication to UE102d, or to receive uplink / reverselink communication from UE102d, based on the Uu interface associated with the access link between UE102d and base station 104d / RU106d.

[0025] The communication link between UE102 and base station 104 / RU106 may be based on multi-input / multi-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be associated with one or more carriers. UE102 and base station 104 / RU106 may utilize a spectral bandwidth of Y MHz per carrier allocated in carrier aggregation up to a total of Yx MHz (e.g., 5, 10, 15, 20, 100, 400, 800, 1600, 2000 MHz, etc.), with x component carriers (CCs) used for communication in the uplink and downlink directions, respectively. The carriers may or may not be adjacent to each other along the frequency spectrum. In the example, the uplink and downlink carriers may be allocated asymmetrically so that more or fewer carriers are allocated to either the uplink or the downlink. The component carriers may include a primary component carrier, as well as one or more secondary component carriers. A primary component carrier may be associated with a primary cell (PCell), and a secondary component carrier may be associated with a secondary cell (SCell).

[0026] Some UE102s, such as the UE102a and UE102s, can perform device-to-device (D2D) communication via sidelinks. For example, sidelink communication / D2D links utilize the spectrum of a wireless wide area network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed via various wireless communication systems, such as Wireless Fidelity (Wi-Fi) systems, Bluetooth® systems, Long-Term Evolution (LTE) systems, and New Radio (NR) systems.

[0027] The electromagnetic spectrum is often subdivided into different classes, bands, channels, etc., based on the different frequencies / wavelengths associated with the electromagnetic spectrum. Fifth-generation (5G) NR is generally associated with two operating frequency ranges (FRs), referred to as Frequency Range 1 (FR1) and Frequency Range 2 (FR2). The FR1 range is 410 MHz to 7.125 GHz, and the FR2 range is 24.25 GHz to 71.0 GHz, which includes FR2-1 (24.25 GHz to 52.6 GHz) and FR2-2 (52.6 GHz to 71.0 GHz). Although a portion of FR1 actually exceeds 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. In contrast, FR2 is often referred to as the "millimeter wave" (mmW) band. FR2 is a subset that is not the same as, but close to, the "extremely high frequency" (EHF) band, which is sometimes also called the "millimeter wave" band in the 30 GHz to 300 GHz range. The frequencies between FR1 and FR2 are often referred to as “mid-band” frequencies. The operating band for mid-band frequencies is sometimes called Frequency Range 3 (FR3), ranging from 7.125 GHz to 24.25 GHz. The frequency bands within FR3 may include the characteristics of FR1 and / or FR2. Therefore, the characteristics of FR1 and / or FR2 can be extended to mid-band frequencies. Higher operating frequency bands have been identified to extend 5G NR communications beyond 52.6 GHz, which is associated with the upper limit of FR2. Three of these higher operating frequency bands include FR2-2 in the range of 52.6 GHz to 71.0 GHz, FR4 in the range of 71.0 GHz to 114.25 GHz, and FR5 in the range of 114.25 GHz to 300 GHz. The upper limit of FR5 corresponds to the upper limit of the EHF band. Therefore, unless otherwise specified herein, the term “sub-6 GHz” may refer to frequencies below 6 GHz within FR1, or it may include mid-band frequencies. Furthermore, unless otherwise specified herein, the term “millimeter wave” or mmW means frequencies that may include midband frequencies and may be within FR2-1, FR4, FR2-2, and / or FR5, or within the EHF band.

[0028] UE102 and base station 104 / RU106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that can facilitate beamforming operations. For example, RU106b transmits a downlink beamforming signal to UE102b in one or more transmit directions of RU106b based on a first set of communication beams 132. UE102b may receive the downlink beamforming signal from RU106b in one or more receive directions of UE102b based on a second set of communication beams 134b. In a further example, UE102b may also transmit an uplink beamforming signal (e.g., a sounding reference signal (SRS)) to RU106b in one or more transmit directions of UE102b based on a second set of communication beams 134b. RU106b may receive the uplink beamforming signal from UE102b in one or more receive directions of RU106b.

[0029] UE102b may perform beam training to determine the optimal receiving and transmitting directions for beamforming signals. The transmitting and receiving directions of UE102 and base station 104 / RU106 may be the same or different. In a further example, beamforming signals may be communicated between a first base station / RU106a and a second base station 104e. For example, base station 104e in cell 190e may transmit beamforming signals to RU106a based on one or more transmitting communication beams 138 of base station 104e. RU106a may receive beamforming signals from base station 104e in cell 190e based on one or more receiving RU communication beams 136 of RU106a. In a further example, base station 104e transmits downlink beamforming signals to UE102e based on one or more transmitting communication beams 138 of base station 104e. UE102e receives a downlink beamforming signal from base station 104e based on one or more UE communication beams 130 in the receiving direction of UE102e. UE102e may also transmit an uplink beamforming signal to base station 104e based on one or more UE communication beams 130 in the transmitting direction of UE102e, thereby enabling base station 104e to receive the uplink beamforming signal from UE102e in one or more receiving directions of base station 104e.

[0030] Base station 104 may include and / or be referred to as a network entity. That is, “network entity” may refer to base station 104, or at least one unit of base station 104 such as RU106, DU108, and / or CU110. Base station 104 may also include and / or be referred to as next-generation evolved node B (ng-eNB), next-generation NB (gNB), evolved NB (eNB), access point, base transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network equipment, or other related terms. Base station 104 or an entity of base station 104 can be implemented as an IAB node, relay node, sidelink node, aggregated (monolithic) base station, or a distributed base station including one or more RU106, DU108, and / or CU110. A set of aggregated or distributed base stations may be referred to as a next-generation radio access network (NG-RAN). In some examples, UE102a operates in dual-connection (DC) with base station 104e and base station / RU106a. In such cases, base station 104e may be the master node and base station / RU160a may be the secondary node.

[0031] Uplink / downlink signaling may also be communicated via a satellite positioning system (SPS) 114. In the example, the SPS 114 of cell 190c may communicate with one or more UE 102s, such as UE 102c, and one or more base stations 104 / RU 106, such as RU 106c. The SPS 114 may correspond to one or more of the Global Navigation Satellite Systems (GNSS), Global Positioning System (GPS), Non-Terrestrial Networks (NTN), or other satellite positioning / location systems. SPS114 may be associated with LTE signals, NR signals (e.g., those based on round-trip time (RTT) and / or multi-RTT), wireless local area network (WLAN) signals, terrestrial beacon systems (TBS), sensor-based information, NR extended cell ID (NR E-CID) technology, downlink departure angle (DL-AoD), downlink arrival time difference (DL-TDOA), uplink arrival time difference (UL-TDOA), uplink arrival angle (UL-AoA), and / or other systems, signals, or sensors.

[0032] Furthermore, as shown in Figure 1, in certain embodiments, one of the UEs 102 may include a beam switching acceleration component 140 configured to receive multiple beams from a network entity for signal quality measurement. The UE 102 communicates with the network entity via a first beam among the multiple beams. The beam switching acceleration component 140 is further configured to send a message to the network entity indicating that it will accelerate beam switching from the first beam to the second beam among the multiple beams, based on the fact that the signal quality of the second beam is higher than that of the first beam and the signal quality of the first beam exceeds a traffic type threshold.

[0033] In certain embodiments, one of the base stations 104, or a network entity of the base stations 104, may include a beam switching component 150 configured to transmit multiple beams to the UE 102 for signal quality measurement. The network entity communicates with the UE via a first beam of the multiple beams. The beam switching component 150 is further configured to receive a message from the UE indicating that it will accelerate beam switching from the first beam to the second beam of the multiple beams, based on the fact that the signal quality of the second beam is higher than that of the first beam and the signal quality of the first beam exceeds a traffic type threshold.

[0034] Accordingly, Figure 1 illustrates a wireless communication system that may be implemented in relation to one or more other embodiments described herein. Furthermore, although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as 5G Advanced and future versions, LTE, LTE Advanced (LTE-A), and other wireless technologies such as 6G.

[0035] Figure 2 shows an XR traffic model for XR communication. XR communication covers AR communication, VR communication, and MR communication. In VR, users are immersed in a virtual environment that replaces the real environment by wearing a head-mounted device. AR enhances the perception of the real environment with several virtual elements, thereby superimposing several virtual elements onto the perception of the real environment. MR is an extension of AR, where real and virtual elements can interact in real time. Cloud gaming runs video games on remote servers, but does not require a gaming console or high-spec CPU and GPU to play these games. Cloud gaming streams games like streaming video, and the game can respond to the gamer's commands and controls in real time.

[0036] Wireless AR / VR and wireless gaming offer greater freedom of movement, as wireless technology removes geographical or behavioral limitations, allowing VR and AR users to move freely. Wireless AR / VR also enables new applications such as distance education in immersive environments in remote areas. Multiple XR scenarios and applications are being deployed. Offline sharing of 3D objects includes sharing 3D models or objects and 3D mixed reality scenes among users, for example, by using a phone with a depth camera to capture images in 3D and then sharing those images with contacts. XR meetings are another use case, which includes people interacting within a virtual environment, sharing 3D experiences with each other, and even presenting some content in the same meeting and discussing it with others.

[0037] XR traffic (e.g., XR communications) is quasi-periodic traffic with a period equal to the reciprocal of the XR frame rate. For example, if the frame rate is 60 frames per second (fps), the period is 16.67 milliseconds (ms). In some scenarios, XR traffic experiences jitter due to variations in delay in the codec used to encode video frames. For example, jitter is the deviation from the true period of a potentially periodic signal, often in relation to a reference clock signal, in electronics and telecommunications. Jitter is statistically modeled by the Third Generation Partnership Project (3GPP), for example, as a truncated Gaussian distribution. XR packet / frame size is also very large and variable due to the variability of video frame content and is statistically modeled by 3GPP as a truncated Gaussian distribution.

[0038] As shown in Figure 2, XR traffic 205, such as video traffic, is quasi-periodic traffic. For example, XR traffic 205 may have a frame rate of 60 fps. XR traffic 205 may have variable jitter 203 and a variable packet size 209. In the first period 207A, XR traffic 205 may have jitter 203A and a packet size 209A. In the second period 207B, XR traffic 205 may have jitter 203B and a packet size 209B. In the third period 207C, XR traffic 205 may have jitter 203C and a packet size 209C, and so on. Jitter 203 can be modeled as a truncated Gaussian distribution with a mean of 0, a standard deviation of 2 ms, and a range of + / - 4 ms. XR packet / frame size 209 may also be modeled as a truncated Gaussian distribution.

[0039] XR traffic can include two types of traffic flows. The first type of traffic flow is DL VR traffic or UL AR traffic, which is quasi-periodic traffic. DL VR traffic or UL AR traffic can have periodicity, such as 30fps, 60fps, or 120fps. DL VR traffic or UL AR traffic can be subject to jitter. As shown in Figure 2, if there is jitter, arrival times can vary. For example, in Rel-17, the jitter of DL VR traffic may be within the range of + / - 4ms and may follow a Gaussian distribution. The jitter of UL AR traffic may be smaller, but jitter is present, for example in the case of tethering (e.g., when the 5G modem is on a mobile device and the display is on AR glasses or a VR headset). DL VR traffic or UL AR traffic may have variable packet sizes and follow a truncated Gaussian distribution (based on the RAN1 assumption for Rel-17). The bitrate of DL VR traffic or UL AR traffic may be between 10 and 200 Mbps, depending on the frame rate, resolution, and codec efficiency. For example, the latency requirement for DL ​​VR traffic or UL AR traffic may be 10 ms. DL VR traffic or UL AR traffic may include packet data unit (PDU) sets and data bursts. A data burst may be a video frame, and a PDU set is a slice of a video frame. Therefore, a data burst may include multiple PDU sets.

[0040] The second type of traffic flow involves transmitting attitude / control information that reflects the user's position and movement to adjust AR / VR content. This second type of traffic flow is also relevant to cloud gaming. For example, the most common described period for the second type of traffic flow may be 4ms, but in relaxed cases, the same period as the first type of traffic flow can be used. The second type of traffic flow has no jitter. The second type of traffic flow has small packets (e.g., about 100 bytes). The latency requirements for the second type of traffic flow may be in the range of 10-20ms. The packet loss rate for the second type of traffic flow should be lower than 10E-3. Several references to the XR traffic model can be found in 3GPP RAN1 TR 38.835, RAN2 TR 38.838, SA4 TR 26.928, SA4 TR 26.918, and SA4 TR 26.926. Figure 3 illustrates beam switching acceleration in XR communications, based on the XR traffic model shown in Figure 2.

[0041] Figure 3 shows the acceleration of beam switching 318 in XR communication between UE102 and network entity 104. Network entity 104 may correspond to a base station or a base station unit such as RU106, DU108, or CU110.

[0042] XR traffic requires high data rates, high reliability, and very low latency, which is difficult to achieve in wireless networks susceptible to fading, mobility, and other factors. XR traffic is also susceptible to events that may interfere with the transmission of UL AR video traffic or DL ​​VR video traffic. These events may include beam switching, bandwidth partial switching, CSI measurements and reports, and / or RRM measurements.

[0043] Some events can cause latency and jitter in XR traffic, potentially degrading or disrupting the quality of user experience (QoE). However, some of these events can be enhanced to enable seamless transitions that do not affect the user experience, or transitions with reduced impact on the user experience. Accelerating or speeding up these events can reduce latency and jitter in XR traffic, and therefore either not cause or reduce disturbances to user QoE. For example, enhancing beam switching can be very useful in allowing switching to occur without the user noticing any impact on the quality of XR video.

[0044] As shown in Figure 3, the XR traffic 305 between UE 102 and network entity 104 is quasi-periodic traffic and may have periodicity such as 30fps, 60fps, or 120fps. For example, the XR traffic 305 may include configured authorization (CG)-physical uplink shared channels (PUSCH) 301A, 301B, 301C, and 301D. The XR traffic 305 may arrive periodically with some jitter. For example, the XR traffic 305 may include video frames. UE 102 may transmit video frames at specific times. There may be a transmit gap (e.g., a time interval) 317 without UL video transmissions at the end of the first period 307A before the start time of the second period 307B. Depending on the characteristics of the XR traffic, there may be a transmit gap (e.g., a time interval) 317 with neither UL transmissions nor DL ​​transmissions. Events that cause latency and jitter in XR traffic and disrupt the user's QoE may be accelerated or accelerated to have a smaller window. Accelerating or accelerating events such as beam switching can reduce latency and jitter in XR traffic. Therefore, events have little or no impact on XR communications, thus reducing or eliminating disturbances to the user's QoE.

[0045] For example, accelerating beam switching 318 can reduce its impact on the QoE of XR services. Beam switching 318 may be accelerated or made faster. Therefore, beam switching 318 may reduce or have no impact on UL or DL ​​video transmissions. Thus, beam switching 318 may reduce or have no disturbance to the user's QoE.

[0046] Regarding beam switching, the 3GPP specification supports the following operations for beam switching: beam instruction from a network entity, beam fault recovery via UE trigger, and / or random access (RA) procedures (except for the PDCCH sequence PRACH(PCell) only). A network entity constitutes a list of transmission configuration instruction (TCI) states by RRC signaling, each TCI state containing at least one downlink reference signal resource index indicating at least one downlink reference signal resource. A network entity may transmit downlink reference signals with different beams in different TCI states. A network entity provides beam instruction by indicating at least one of the TCI states in the TCI state list by a medium access control (MAC) control element (CE) or DCI signal. To complete a beam switching procedure, for example, to apply a downlink reference corresponding to a TCI state indicated by a network entity, or a beam fault recovery procedure, or an RA procedure, the UE may identify beam switching parameters. The beam switching parameters include a first parameter of the UE beam corresponding to the new NW beam, a second parameter of DL pseudo-collocation (QCL) type A related parameters, and a third parameter of UL power control path loss. To identify the first parameter, if the indicated beam (new beam) is unknown to the UE, for example, if it is not reported within a time window, the UE may perform multiple measurements of the synchronization signal block (SSB). The first parameter is for the UE's receive / transmit (Rx / Tx) beam. The network entity typically indicates a DL reference signal (RS) for both UL and DL beam indication. The UE then identifies the UE beam corresponding to the DL RS. To identify the second parameter, the UE may track the SSB once. To identify the third parameter, the UE may measure the path loss RS associated with the new beam multiple times, for example, measuring the SSB set or determined as the path loss RS five times.

[0047] The delay required for the UE to identify the beam switching parameters can introduce latency and disrupt XR services. For the first parameter, the delay depends on whether the indicated TCI state is known or unknown. For a known TCI state, it is assumed that the UE already knows it. For an unknown TCI state, the delay may be 8*T_SSB, where T_SSB indicates the periodicity of the SSB. It also depends on the discontinuous reception (DRX) configuration. Details are defined in section 8.10 of 3GPP38.133. For the second parameter, the highest latency may be T_SSB. For the third parameter, using the Layer 3 reference signal received power (L3-RSRP) for path loss measurement, the latency may be 5*T_SSB. Assuming no DRX influence, the total delay range may be T_SSB~8*T_SSB. The UE measures the three beam switching parameters to complete the beam switching procedure.

[0048] Figures 4-6 are signaling diagrams illustrating examples of communication between the UE and network entities to accelerate beam switching. In some examples, the new beam is superior to the old beam (e.g., the new beam has higher signal quality than the old beam), and the old beam cannot provide good performance to support the XR service. This is because the old beam cannot provide good performance for the XR service. XR communication may have low UL throughput or high latency. Low UL throughput or high latency may not be sufficient for the XR service. The link may still be functional, but not sufficient to meet the XR QoE requirements. In this situation, the UE and / or network entities can accelerate or speed up the beam switching procedure to the new beam. For example, the UE and / or network entities may accelerate or speed up the procedure to identify beam switching parameters to reduce the downtime of XR communication.

[0049] Figure 4 is a signaling diagram 400 illustrating an example of communication between a UE and a network entity to accelerate beam switching by using aperiodic CSI-RS. Network entity 104 may correspond to a base station or a base station unit such as RU106, DU108, CU110. In some examples, beam indication signaling, and / or BFR responses, and / or RAR messages can trigger aperiodic CSI-RS to accelerate or speed up the procedure for identifying beam switching parameters. UE102 may identify beam switching parameters based on aperiodic CSI-RS. DCI and / or RAR may be enabled to trigger aperiodic CSI measurements and reports.

[0050] In some examples, UE102 and network entity 104 may communicate via a serving beam, e.g., an old beam or a beam in progress (406). UE102 and network entity 104 may transmit / receive data via a serving beam. Network entity 104 may transmit a set of beams, e.g., multiple beams, for example, for the UE to perform signal quality measurements in a beam measurement procedure (408). UE102 may receive a set of beams, e.g., multiple beams, to perform signal quality measurements (408).

[0051] UE102 measures the signal quality of the beamset by performing signal quality measurements (412). For example, UE may measure a synchronous signal block (SSB). Each beamset may contain an SSB or be pseudo-collocated with an SSB. Based on the signal quality measurements, UE determines that a new beam in the beamset is superior to an old beam (413). For example, UE may determine that a new beam is superior to an old beam based on a reference signal received power (RSRP) measurement.

[0052] The UE determines whether the old beam can still provide good performance to support XR traffic (413). A network entity may set thresholds for the UE to determine whether a serving beam, such as an old beam, can still provide good performance to support XR traffic. For example, thresholds may be a block error rate (BER) threshold, a packet error rate (PER) threshold, a BLER threshold, an L1-RSRP threshold, an L1-SINR threshold, a latency threshold, a packet data unit (PDU) set error rate (PSER) threshold, a PDU set latency threshold, a data burst error rate threshold, or a data burst latency threshold. In other examples, a network entity may configure the UE to determine the thresholds. If the signal quality of a serving beam, for example, an older beam, is below a threshold, the UE may determine that the serving beam, for example, an older beam, still provides good performance to support XR traffic and meet the QoE requirements for XR traffic. If the signal quality of a serving beam, for example, an older beam, is above a threshold, the UE may determine that the serving beam, for example, an older beam, cannot provide good performance to support XR traffic and meet the QoE requirements for XR traffic.

[0053] The UE may, for example, send a signal quality measurement report indicating a new beam to the network entity. Based on the signal quality measurement report, the network entity may, for example, send a beam indication signal indicating a new beam.

[0054] In some examples, UE102 and / or network entity 104 may use aperiodic CSI-RS to accelerate or speed up the procedure for identifying beam switching parameters to reduce downtime. The network entity may provide beam indication by indicating at least one of the TCI states in the TCI state list by MAC CE or DCI signal. To complete the beam switching procedure, for example, to apply the TCI state indicated by the network entity, or a downlink reference signal corresponding to a beam fault recovery procedure or associated with an RA procedure, the UE may identify beam switching parameters. The beam switching parameters may include a first parameter of the UE beam corresponding to the new NW beam, a second parameter of DL pseudo-collocation (QCL) type A related parameters, and a third parameter of UL power control path loss.

[0055] UE102 can identify beam switching parameters because beam switching occurs. UE102 can identify beam switching parameters using periodic CSI-RS. However, periodic CSI-RS is transmitted periodically. If the period of the CSI-RS is large or does not match the small transmit gap 317, there may be no CSI-RS to measure after the UE has identified that the old beam is not good enough, due to the periodicity of the periodic CSI-RS. Therefore, by using aperiodic CSI-RS, the UE can identify beam switching parameters as quickly as possible.

[0056] TCI activation / indication delay can be reduced based on aperiodic CSI-RS. Currently, TCI activation / indication delay is based on periodic CSI-RS and SSB as references. Aperiodic CSI-RS may be used as a reference for TCI activation / indication. By using aperiodic CSI-RS as a reference, TCI activation / indication delay can be reduced. Aperiodic CSI-RS can be used to trigger measurements of beam switching parameters.

[0057] For example, network entity 104 may transmit a DCI signal to the UE indicating a new beam (415). The DCI signal may include a bit field for triggering measurements and reports based on a periodic CSI-RS.

[0058] For example, network entity 104 may send a RAR message (416) which may include a bit field for triggering measurement and reporting based on a non-periodic CSI-RS.

[0059] Network entity 104 may transmit aperiodic CSI-RS to the UE (418). The UE may receive aperiodic CSI-RS from the network entity (418). The UE may perform measurements based on the aperiodic CSI-RS (420). For example, the UE may perform measurements on the CSI-RS resource indicator (CRI) and / or RSRP based on the aperiodic CSI-RS.

[0060] UE102 may transmit a report of measurements based on aperiodic CSI-RS to network entity 104 (424). Network entity 104 may receive a report of measurements based on aperiodic CSI-RS from UE102 (424). For example, UE may report measurements regarding CSI-RS resource indicator (CRI) and / or RSRP based on aperiodic CSI-RS. By using aperiodic CSI-RS, UE can provide CSI feedback early to fully stabilize the new beam.

[0061] In some examples, UE102 may receive a beam switching message, e.g., a beam switching command, from network entity 104 that indicates (e.g., commands) the UE to switch from the old first beam to the new beam based on aperiodic CSI-RS, either before or after the UE sends a measurement report. Network entity 104 may perform the beam switching from the old beam to the new beam based on the measurement report based on aperiodic CSI-RS (426).

[0062] Figure 5 is a signaling diagram 500 illustrating an example of communication between the UE and a network entity to accelerate beam switching by measuring and storing beam switching parameters during a beam measurement procedure prior to the beam switching procedure. The network entity 104 may correspond to a base station or a base station unit such as RU106, DU108, or CU110. The UE 102 may measure and store beam switching parameters during the beam measurement procedure (e.g., by performing a signal quality measurement) and report whether the beam switching parameters have been identified.

[0063] As described above, UE102 and network entity 104 can communicate over a serving beam, e.g., an old beam or a beam in progress (406). UE102 and network entity 104 can transmit / receive data over a serving beam. Network entity 104 can transmit a set of beams, e.g., multiple beams, for the UE to perform signal quality measurements (408). UE102 can receive a set of beams, e.g., multiple beams, for example, to perform signal quality measurements in a beam measurement procedure (408). UE102 measures the signal quality of the set of beams by performing signal quality measurements (412). The UE determines whether the old beam can still provide good performance to support the XR service (413). The UE can send a signal quality measurement report to the network entity, e.g., indicating a new beam. Based on the signal quality measurement report, the network entity can send a beam indication signal, e.g., indicating a new beam.

[0064] UE102 measures and stores beam switching parameters in a beam measurement procedure (e.g., performing signal quality measurements) prior to the beam switching procedure (520). UE102 may measure and store beam switching parameters in advance prior to the beam switching procedure (520). The UE may identify beam switching parameters including a first parameter of the UE beam corresponding to the new NW beam, a second parameter of DL pseudo-collocation (QCL) type A related parameters, and a third parameter of UL power control path loss. Before recognizing that the old beam is not sufficiently good, the UE has already performed measurements of the beam switching parameters and has stored them. When the UE can determine the new beam, UE102 has already measured and stored the beam switching parameters. Beam switching latency may include signal decoding latency, UE beam change latency, and additional time for identifying the beam switching parameters. By measuring and storing beam switching parameters during the measurement phase (before beam indication signaling), the UE102 can save additional time for identifying / tracking beam switching parameters. Therefore, the UE can accelerate beam switching by measuring and storing beam switching parameters during the beam measurement procedure.

[0065] The UE may select a subset of multiple beams and measure and store the corresponding beam switching parameters. For example, the subset of multiple beams may be the top N beams of the multiple beams. UE102 may identify the most likely beam or the top N beams (where N is an integer) from the multiple beams in order to measure and store the beam switching parameters. Measuring and storing beam switching parameters can require significant UE implementation effort. To reduce complexity, the UE may select a subset of multiple beams and measure and store the beam switching parameters. In all beam measurements, if there is a beam switch, the UE may select the beam that is most likely to become the new beam. If one of the selected beams could become the new beam, the UE may measure and store the beam switching parameters for each of the selected beams. For example, the UE may measure the RSRP and select the top four beams with the best RSRP. The UE may measure and store the beam switching parameters for each of the top four beams with the best RSRP. For example, a network entity may be configured to select a portion (e.g., a subset) of multiple beams to measure and store beam switching parameters.

[0066] UE102 may receive a control signal from a network entity that sets a first threshold for the UE to measure and store beam switching parameters (510). The first threshold may include one of the following: block error rate (BER) threshold, packet error rate (PER) threshold, BLER threshold, L1-RSRP threshold, L1-SINR threshold, latency threshold, PSER threshold, PDU set latency threshold, data burst error rate threshold, or data burst latency threshold. Network entity 104 may define one or more conditions for the UE to begin measuring and storing beam switching parameters. For example, one or more conditions may include a link degradation threshold, BER threshold, PER threshold, BLER threshold, L1-RSRP threshold, L1-SINR threshold, latency threshold, PSER threshold, PDU set latency threshold, data burst error rate threshold, or data burst latency threshold.

[0067] UE102 may send a message to network entity 104 indicating that the UE has measured and stored beam switching parameters for at least a portion of the beams prior to the beam switching procedure (524). Network entity 104 may receive a message from the UE indicating that the UE has measured and stored beam switching parameters for at least a portion of the beams prior to the beam switching procedure (524). UE102 may send a message to the network entity indicating whether the UE has identified parameters for some particular beams, for example, an instruction on whether the UE is ready to perform beam switching. By measuring and storing beam switching parameters during the measurement phase (before beam instruction signaling), UE102 can accelerate beam switching by saving additional time to identify / track beam switching parameters.

[0068] In some examples, UE102 may receive a beam switching message, e.g., a beam switching command, from network entity 104, instructing the UE to switch from the old first beam to the new beam, either before or after sending a message indicating that the UE has measured and stored the beam switching parameters. Based on the message indicating that the UE has measured and stored the beam switching parameters, network entity 104 may perform the beam switching from the old beam to the new beam (526).

[0069] Figure 6 is a signaling diagram 600 illustrating an example of communication between the UE and a network entity to accelerate beam switching by using L1-RSRP for path loss measurement. The network entity 104 may correspond to a base station or a base station unit such as RU106, DU108, or CU110. The UE 102 may use L1-RSRP for path loss measurement to accelerate the beam switching procedure.

[0070] As described above, UE102 and network entity 104 can communicate over a serving beam, e.g., an old beam or a beam in progress (406). UE102 and network entity 104 can transmit / receive data over a serving beam. Network entity 104 can transmit a set of beams, e.g., multiple beams, for the UE to perform signal quality measurements (408). UE102 can receive a set of beams, e.g., multiple beams, for the UE to perform signal quality measurements (408). UE102 measures the signal quality of the set of beams by performing signal quality measurements (412). The UE determines whether the old beam can still provide good performance to support the XR service (413). The UE can send a signal quality measurement report to the network entity, e.g., indicating a new beam (414). Based on the signal quality measurement report, the network entity can send a beam indication signal, e.g., indicating a new beam (415).

[0071] UE102 may receive a control signal from the network entity to set up path loss measurement using L1-RSRP (616). To accelerate the beam switching procedure, the UE and / or network entity may relax some requirements. The UE may use L1-RSRP for path loss measurement. To mitigate the impact of accuracy, the UE may have a receiver with improved accuracy. The network entity may define restrictions on the use of L1-RSRP for path loss measurement. The control signal may include restrictions on the use of L1-RSRP for path loss measurement. For example, the restriction may include that L1-RSRP may only be for path loss measurement during the transition time (before the UE measures L3-RSRP). As another example, the restriction may include setting a higher transmit power P0 (e.g., uplink transmit power) during the transition time to ensure that the UE's UL performance is sufficiently good. The network entity may set a higher transmit P0 during the transition time. Then, after the transition time, the transmit power P0 can be readjusted. For example, the network entity may set two values ​​for transmit power P0.

[0072] In some cases, a network entity may configure the use of L1-RSRP or L3-RSRP for path loss measurement. The network entity may be configured to use either L1-RSRP or L3-RSRP depending on the channel conditions. For example, if the channel is highly variable and using L1-RSRP for path loss measurement would be too risky, the network entity may decide to use L3-RSRP. If the channel is stable and there is no risk, the network entity may decide to use L1-RSRP for path loss measurement.

[0073] The UE102 may perform path loss measurements using L1-RSRP (620). Path loss measurements based on L1-RSRP are less accurate but faster than path loss measurements based on L3-RSRP. The UE may use L1-RSRP for path loss measurements only during the transition period.

[0074] UE102 may transmit beam switching parameters to network entity 104 based on path loss measurements using L1-RSRP (624). Network entity 104 may receive beam switching parameters from UE based on path loss measurements using L1-RSRP (624).

[0075] In some examples, UE102 may receive a beam switching message, e.g., a beam switching command, from network entity 104 that instructs (e.g., commands) the UE to switch from the old first beam to the new beam, either before or after sending a message indicating an acceleration request to accelerate beam switching for a subset of communication channels. Network entity 104 may perform the beam switching from the old beam to the new beam based on beam switching parameters based on path loss measurements using L1-RSRP (626).

[0076] Figure 7 is a signaling diagram showing an example of communication between a UE and a network entity to accelerate beam switching based on CQI or simplified CQI. Network entity 104 may correspond to a base station or a base station unit such as RU106, DU108, or CU110. UE 102 may measure and report CQI or simplified CQI for each beam of multiple beams to accelerate the beam switching procedure, for example, to enable initial CSI reporting or initial modulation and coding scheme (MCS) selection.

[0077] As described above, UE102 and network entity 104 can communicate over a serving beam, e.g., an old beam or a beam in progress (406). UE102 and network entity 104 can transmit / receive data over a serving beam. Network entity 104 can transmit a set of beams, e.g., multiple beams, for the UE to perform signal quality measurements (408). UE102 can receive a set of beams, e.g., multiple beams, for the UE to perform signal quality measurements (408). UE102 measures the signal quality of the set of beams by performing signal quality measurements (412). The UE determines whether the old beam can still provide good performance to support the XR service (413). The UE can send a signal quality measurement report to the network entity, e.g., indicating a new beam (414). Based on the signal quality measurement report, the network entity can send a beam indication signal, e.g., indicating a new beam (415).

[0078] UE102 may measure the CQI or simplified CQI of each beam, e.g., SSB, in the beam measurement report, BFR request, and / or MsgA / MSg3 (720). UE102 may measure the CQI or simplified CQI in advance of the beam switching procedure. The simplified CQI may refer to a wideband (WB)-CQI from a single port. A network entity may select an MCS for DL ​​traffic, e.g., based on the CQI or simplified CQI. In some embodiments, the UE may measure the simplified CQI based on a separate CQI table. In one example, the CQI table for the simplified CQI measurement may contain fewer entries than other types of CQI; for example, the number of candidate CQIs for the simplified CQI may be 4 or 8. In other exemplary embodiments, a subtable determined from an existing CQI table(s) is used for simplified CQI reporting (e.g., all other CQI values ​​in the table). The subtable may be specified / predefined or configured by the base station (e.g., via an RRC configuration). Measuring CQI or simplified CQI saves time for CQI measurement and reporting after beam selection. The UE has already performed CQI or simplified CQI measurements before beam switching. Therefore, after beam switching, network entities can avoid delays waiting for CQI measurement and reporting. Network entities can accelerate MCS selection. Therefore, the UE can accelerate beam switching by measuring CQI or simplified CQI in the beam measurement procedure.

[0079] UE102 may receive a control signal from a network entity to configure the top N beams or all beams for CQI or Simplified CQI measurement (710). The control signal may configure a subset (e.g., part) of multiple beams for CQI or Simplified CQI measurement. For example, a part may include the top N beams of multiple beams. The UE can measure and report for the top N beams or all beams. The number of beams N may be configured by the network. In some examples, the number of beams N may also be specified by a protocol, configured by a network entity, or reported by the UE.

[0080] UE102 may transmit a report to network entity 104 indicating CQI or simplified broadband (WB)-CQI for at least a portion of multiple beams before beam switching in order to accelerate MCS selection (724). Network entity 104 may receive a report from UE102 indicating CQI or simplified broadband (WB)-CQI for at least a portion of multiple beams before beam switching in order to accelerate MCS selection (724). The report may indicate CQI or simplified CQI for the top N beams or for each of all beams among the multiple beams.

[0081] In some examples, UE102 may receive a beam switching message, e.g., a beam switching command, from network entity 104 before or after sending a message indicating a CQI or a simplified CQI, instructing (e.g., commanding) the UE to switch from the old first beam to the new beam. Network entity 104 may perform the beam switching from the old beam to the new beam based on messages indicating a CQI or a simplified CQI for the top N beams of a plurality of beams or for each of all beams (726).

[0082] Figure 8 is a signaling diagram showing an example of communication between a UE and a network entity for accelerating beam switching by beam fault detection using different BLER thresholds. Network entity 104 may correspond to a base station or a base station unit such as RU106, DU108, or CU110. UE102 may perform beam fault detection (BFD) for XR communication using different target BLERs to accelerate beam switching.

[0083] As described above, UE102 and network entity 104 can communicate over a serving beam, e.g., an old beam or a beam in progress (406). UE102 and network entity 104 can transmit / receive data over a serving beam. Network entity 104 can transmit a set of beams, e.g., multiple beams, for the UE to perform signal quality measurements (408). UE102 can receive a set of beams, e.g., multiple beams, for the UE to perform signal quality measurements (408). UE102 measures the signal quality of the set of beams by performing signal quality measurements (412). The UE determines whether the old beam can still provide good performance to support the XR service (413). The UE can send a signal quality measurement report to the network entity, e.g., indicating a new beam (414). Based on the signal quality measurement report, the network entity can send a beam indication signal, e.g., indicating a new beam (415).

[0084] UE102 may receive a control signal from a network entity that sets a BLER threshold for XR communication (810). The BLER threshold may be a configured RRC signaling. For example, a network entity may send an RRC signal that sets a BLER threshold for XR communication. The BLER threshold for XR communication may be lower than the BLER threshold for other types of traffic.

[0085] UE102 can perform BFD using a BLER threshold for XR communication (820). Since the BLER threshold for XR communication can be lower than the BLER threshold for other types of traffic, the UE can accelerate beam switching.

[0086] UE102 may send a Beam Fault Recovery Request (BFRQ) to network entity 104 based on the BFD, using a BLER threshold for XR communication (824). Network entity 104 may receive a BFRQ from the UE based on the BFD, using a BLER threshold for XR communication (824). In some examples, a network entity may set two BLER thresholds for the BFD in the BFRQ, for example, a first BLER threshold for non-XR traffic and a second BLER threshold for XR traffic, and the UE may report whether it was triggered based on the BFD for either the first or second BLER threshold. In this way, the QoE experience for XR users may be improved.

[0087] In some examples, UE102 may receive a beam switching message, e.g., a beam switching command, from network entity 104 that instructs (e.g., commands) the UE to switch from the old first beam to the new beam, either before or after sending a message indicating an acceleration request to accelerate beam switching for a subset of communication channels. Network entity 104 may perform beam switching from the old beam to the new beam based on BFRQ based on BFD, using a BLER threshold for XR communication (826).

[0088] Figures 3-8 show examples of communication between the UE and the network entity to accelerate beam switching. Figures 9-10 show how to implement one or more embodiments of Figures 3-8. Specifically, Figure 9 shows an embodiment by the UE 102 of one or more embodiments of Figures 3-8. Figure 10 shows an embodiment by the network entity 104 of one or more embodiments of Figures 3-8.

[0089] Figure 9 shows a flowchart 900 of a wireless communication method at the UE. Referring to Figures 1-8 and 11, the method may be performed by UE 102, UE device 1102, etc., which may include memories 1126', 1106', 1116, and may correspond to the entire UE 102 or the entire UE device 1102, or components of UE 102 or UE device 1102 such as the wireless baseband processor 1126 and / or application processor 1106. UE102 receives multiple beams from the network entity for signal quality measurement (908). The UE communicates with the network entity via the first beam of the multiple beams. For example, referring to Figures 4-8, UE102 may receive a set of beams, e.g., multiple beams, to perform signal quality measurement (408).

[0090] UE102 sends a message to the network entity indicating that it will accelerate the beam switching from the first beam to the second beam among multiple beams, based on the fact that the signal quality of the second beam is higher than that of the first beam and the signal quality of the first beam exceeds the traffic type threshold (924). For example, referring to Figure 4, UE102 may send a report of measurements based on aperiodic CSI-RS to the network entity 104 (424). For example, referring to Figure 5, UE102 may send a message to the network entity 104 indicating that the UE has measured and stored beam switching parameters for at least a portion of the multiple beams before the beam switching procedure (524). For example, referring to Figure 6, UE102 may send beam switching parameters to the network entity 104 based on path loss measurements using L1-RSRP (624). For example, referring to Figure 7, UE 102 may send a report to network entity 104 indicating CQI or simplified broadband (WB)-CQI for at least a portion of the multiple beams before beam switching in order to accelerate MCS selection (724). For example, referring to Figure 8, UE 102 may send a Beam Fault Recovery Request (BFRQ) to network entity 104 based on BFD using a BLER threshold for XR communication (824). Figure 9 describes the method from the UE side of the wireless communication link, and Figure 10 describes the method from the network side of the wireless communication link.

[0091] Figure 10 is a flowchart 1000 of a wireless communication method in a network entity. Referring to Figures 1-8 and 12, the method may be performed by one or more network entities 104, one or more network entities 104 may correspond to a base station or a base station unit such as RU106, DU108, CU110, RU processor 1206, DU processor 1226, or CU processor 1246. One or more network entities 104 may correspond to one or more network entities 104 as a whole, or may include a memory 1206' / 1226' / 1246' that corresponds to one or more network entities 104 such as RU processor 1206, DU processor 1226, or CU processor 1246.

[0092] The network entity 104 transmits multiple beams to the UE for signal quality measurement (1008). The network entity communicates with the UE via the first beam of the multiple beams. For example, referring to Figures 4-8, the network entity 104 may transmit a set of beams, e.g., multiple beams, for the UE to perform signal quality measurement (408).

[0093] Network entity 104 receives a message from the UE indicating that it will accelerate beam switching from the first beam to the second beam among multiple beams, based on the fact that the signal quality of the second beam is higher than that of the first beam and the signal quality of the first beam exceeds a traffic type threshold (1024). For example, referring to Figure 4, network entity 104 may receive a report of measurements based on aperiodic CSI-RS from UE 102 (424). For example, referring to Figure 5, network entity 104 may receive a message from the UE indicating that the UE has measured and stored beam switching parameters for at least a portion of the multiple beams before the beam switching procedure (524). For example, referring to Figure 6, network entity 104 may receive beam switching parameters from the UE based on path loss measurements using L1-RSRP (624). For example, referring to Figure 7, network entity 104 may receive a report from UE 102 indicating CQI or simplified broadband (WB)-CQI for at least a portion of multiple beams before beam switching in order to accelerate MCS selection (724). For example, referring to Figure 8, network entity 104 may receive BFRQ from UE based on BFD using a BLER threshold for XR communication (824). UE device 1102 may perform the method of flowchart 900 as shown in Figure 11. One or more network entities 104 may perform the method of flowchart 1100 as shown in Figure 12.

[0094] Figure 11 is Figure 1100, which shows an example of a hardware implementation for UE device 1102. UE device 1102 may be UE 102, a component of UE 102, or may implement UE functionality. UE device 1102 may include an application processor 1106 which may have on-chip memory 1106'. In this example, the application processor 1106 may be coupled to a secure digital (SD) card 1108 and / or a display 1110. The application processor 1106 may also be coupled to a sensor module 1112, a power supply 1114, an additional memory module 1116, a camera 1118, and / or other related components. For example, the sensor module 1112 may control a barometric pressure sensor / altimeter, motion sensors such as an inertial management unit (IMU), a gyroscope, an accelerometer, a light detection and ranging (LIDAR) device, a radio detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, and / or other technologies used for positioning.

[0095] The UE device 1102 may further include a wireless baseband processor 1126, which may be called a modem. The wireless baseband processor 1126 may have on-chip memory 1126'. Together with, and similar to, the application processor 1106, the wireless baseband processor 1126 may also be coupled to a sensor module 1112, a power supply 1114, an additional memory module 1116, a camera 1118, and / or other related components. The wireless baseband processor 1126 may further be coupled to one or more subscriber identification module (SIM) cards 1120, and / or one or more transceivers 1130 (e.g., wireless RF transceivers).

[0096] The UE device 1102 may include a Bluetooth module 1132, a WLAN module 1134, an SPS module 1136 (e.g., a GNSS module), and / or a cellular module 1138 within one or more transceivers 1130. The Bluetooth module 1132, WLAN module 1134, SPS module 1136, and cellular module 1138 may each include an on-chip transceiver (TRX), or, in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1132, WLAN module 1134, SPS module 1136, and cellular module 1138 may each include and / or utilize a dedicated antenna 1140 for communication with one or more other nodes. For example, UE device 1102 can communicate with other UEs (e.g., sidelink communications) and / or network entities 104 (e.g., uplink / downlink communications) via transceiver(s) 1130 and antenna 1140, where network entities 104 may correspond to base stations or base station units such as RU106, DU108, or CU110.

[0097] The wireless baseband processor 1126 and the application processor 1106 may each include computer-readable media / memories 1126' and 1106', respectively. An additional memory module 1116 may also be considered computer-readable media / memories. Each of the computer-readable media / memories 1126', 1106', and 1116 may be non-temporary. The wireless baseband processor 1126 and the application processor 1106 may each be responsible for general processing, including the execution of software stored in the computer-readable media / memories 1126', 1106', and 1116. When the software is executed by the wireless baseband processor 1126 / application processor 1106, it causes the wireless baseband processor 1126 / application processor 1106 to perform various functions described herein. The computer-readable media / memories may also be used to store data that is manipulated by the wireless baseband processor 1126 / application processor 1106 when the software is executed. The wireless baseband processor 1126 / application processor 1106 may be components of UE 102. UE device 1102 may be a processor chip (e.g., a modem and / or application) and may include only the wireless baseband processor 1126 and / or the application processor 1106. In other examples, UE device 1102 may be the entire UE 102 and may include additional modules of device 1102.

[0098] As illustrated in Figure 1 and implemented with respect to Figure 9, the beam switching acceleration component 140 is configured to receive multiple beams from a network entity for signal quality measurement. UE 102 communicates with the network entity via the first beam of the multiple beams. The beam switching acceleration component 140 is further configured to send a message to the network entity indicating that it will accelerate beam switching from the first beam to the second beam of the multiple beams, based on the fact that the signal quality of the second beam is higher than that of the first beam and the signal quality of the first beam exceeds a traffic type threshold. The beam switching acceleration component 140 may reside in the application processor 1106 (e.g., as 140a), in the wireless baseband processor 1126 (e.g., as 140b), or in both the application processor 1106 and the wireless baseband processor 1126. The beam switching acceleration components 140a to 140b may be one or more hardware components specifically configured to perform the described process / algorithm, may be executed by one or more processors configured to perform the described process / algorithm, may be stored in a computer-readable medium for execution by one or more processors, or may be a combination thereof.

[0099] Figure 12 is a diagram 1200 showing an example of a hardware implementation for one or more network entities 104. One or more network entities 104 may be a base station, a component of a base station, or capable of performing the functions of a base station. One or more network entities 104 may include or correspond to at least one of RU106, DU108, or CU110. CU110 may include a CU processor 1246 which may have on-chip memory 1246'. In some embodiments, CU110 may further include an additional memory module 1256 and / or a communication interface 1248, both of which may be coupled to the CU processor 1246. CU110 can communicate with DU108 via a midhall link 162, such as an F1 interface between the communication interface 1248 of CU110 and the communication interface 1228 of DU108.

[0100] DU108 may include a DU processor 1226 which may have on-chip memory 1226'. In some embodiments, DU108 may further include an additional memory module 1236 and / or a communication interface 1228, both of which may be coupled to the DU processor 1226. DU108 can communicate with RU106 via a fronthaul link 160 between the communication interface 1228 of DU108 and the communication interface 1208 of RU106.

[0101] RU106 may include an RU processor 1206 which may have on-chip memory 1206'. In some embodiments, RU106 may further include an additional memory module 1216, a communication interface 1208, and one or more transceivers 1230, all of which may be coupled to the RU processor 1206. RU106 may further include an antenna 1240 which may be coupled to one or more transceivers 1230, thereby enabling RU106 to communicate with UE102 via the antenna 1240 through one or more transceivers 1230.

[0102] The on-chip memories 1206', 1226', 1246', and the additional memory modules 1216, 1236, 1256 may each be considered computer-readable media / memory. Each computer-readable media / memory may be non-temporary. Each of the processors 1206, 1226, and 1246 is responsible for general processing, including the execution of software stored in the computer-readable media / memory. When the software is executed by the corresponding processor(s) 1206, 1226, and 1246, it causes the processor(s) 1206, 1226, and 1246 to perform various functions described herein. The computer-readable media / memory may also be used to store data that is manipulated by the processor(s) 1206, 1226, and 1246 when the software is executed. In the example, the beam switching component 150 may be located in one or more network entities 104, such as in CU110, in both CU110 and DU108, in each of CU110, DU108, and RU106, in DU108, in both DU108 and RU106, or in RU106.

[0103] As illustrated in Figure 1 and implemented with respect to Figure 10, the beam switching acceleration component 150 is configured to transmit multiple beams to the UE 102 for signal quality measurement. The network entity communicates with the UE via the first beam of the multiple beams. The beam switching component 150 is further configured to receive a message from the UE indicating that it will accelerate beam switching from the first beam to the second beam of the multiple beams, based on the fact that the signal quality of the second beam is higher than that of the first beam and the signal quality of the first beam exceeds a traffic type threshold. The beam switching component 150 may reside in one or more processors of one or more network entities 104, such as the RU processor 1206 (e.g., as 150a), the DU processor 1226 (e.g., as 150b), and / or the CU processor 1246 (e.g., as 150c). The beam switching components 150a to 150c may be one or more hardware components specifically configured to perform the described process / algorithm, or may be implemented by one or more processors 1206, 1226, 1246 configured to perform the described process / algorithm, or may be stored in a computer-readable medium for implementation by one or more processors 1206, 1226, 1246, or a combination thereof.

[0104] The specific order or hierarchy of the blocks in the processes and flowcharts disclosed herein is illustrative and describes an exemplary approach. Therefore, the specific order or hierarchy of the blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of the figures. The claims of the accompanying methods present the elements of various blocks in an exemplary order and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0105] The detailed descriptions provided herein illustrate various configurations related to the drawings and do not represent the only configurations in which the concepts described herein may be implemented. The detailed descriptions include specific details for the purpose of providing a complete explanation of the various concepts. However, these concepts may be implemented without these specific details. In some cases, well-known structures and components are shown in block diagrams to avoid obscuring those concepts.

[0106] Embodiments of wireless communication systems, such as telecommunications systems, are presented with reference to various devices and methods. These devices and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as “elements”). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0107] An element, or any part of an element, or any combination of elements, may be implemented as a “processing system” comprising one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other similar hardware configured to perform various functions described throughout this disclosure. One or more processors in a processing system may be referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, and may run software. Software is broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, or combinations thereof.

[0108] If the functions described herein are implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium, such as a non-temporary computer-readable storage medium. Computer-readable media include computer storage media and may include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other media that can be used to store computer executable code in the form of instructions or data structures accessible by a computer. Storage media may be any available medium accessible by a computer.

[0109] The embodiments, examples, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the embodiments, examples, and / or use cases can be implemented through integrated chip implementations and other non-modular component-based devices such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, artificial intelligence (AI)-enabled devices, and machine learning (ML)-enabled devices. The embodiments, examples, and / or use cases may range from chip-level or modular components to non-modular components or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein.

[0110] Devices incorporating the embodiments and features described herein may also include additional components and features for carrying out and practicing the claimed embodiments and features. For example, the transmission and reception of radio signals necessarily include several components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, and adders / summers. The techniques described herein can be implemented in a wide variety of devices, chip-level components, systems, distributed, centralized or distributed components, and end-user devices in various configurations.

[0111] The description is provided to enable those skilled in the art to carry out the various embodiments described herein. Various modifications of these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments. Accordingly, the claims are not limited to the embodiments described herein and should be interpreted in light of the entire scope of this disclosure, consistent with the language of the claims.

[0112] References to elements in the singular form mean "one or more" and not "only one" unless otherwise specified. Terms such as "when," "when," and "while" do not imply an immediate temporal relationship or response. That is, these phrases, for example, "when," do not imply an immediate action in response to or during the occurrence of an action, but simply imply that an action occurs if the conditions are met, without requiring any specific or immediate time constraints for the action to occur. The terms "may," "might," and "can" as used in this disclosure often have specific meanings. For example, "may" refers to an acceptable characteristic that may or may not occur, "might" refers to a characteristic that is likely to occur, and "can" refers to an ability (e.g., "can do"). The phrase "for example" often means the same thing as "may" or "it may be," and therefore, "may" or "it may be" may be excluded from sentences that contain "for example" or other similar phrases.

[0113] Unless otherwise specified, the term "several" refers to one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A, B and C, and may include multiple A's, multiple B's, and / or multiple C's, or may include only A's, only B's, or only C's. A set should be interpreted as a set of elements in which one or more elements are numbered.

[0114] Unless otherwise specified, ordinal terms such as "1st" and "2nd" do not necessarily signify order in time, sequence, or numerical terms, but are used to distinguish different instances of the terms or phrases that follow each ordinal number. Reference numbers used in specifications and drawings may be cross-referenced between drawings to indicate identical or similar features. Features that are exactly the same in multiple drawings may be labeled with the same reference number in multiple drawings. Features that are similar but not strictly identical across multiple drawings may be labeled with reference numbers that have different preceding numbers but one or more of the same ending numbers (e.g., 206, 306, 406, etc. may refer to similar features in drawings). "X" may be used to universally indicate multiple variations of a single feature. For example, "X06" can universally refer to all reference numbers ending in "06" (e.g., 206, 306, 406, etc.).

[0115] Elements and structural and functional equivalents of various aspects described throughout this disclosure, which are known to those skilled in the art or will subsequently become known to those skilled in the art, are expressly incorporated herein by reference and are included in the claims. Words such as “module,” “mechanism,” “element,” and “device” may not be substitutes for the word “means.” Accordingly, claim elements should not be construed as means plus functions unless the elements are expressly enumerated using the phrase “means to do.” Where used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” shall be construed as “at least based on A” unless specifically stated otherwise, where “A” may be information, a condition, a factor, etc.

[0116] The following examples are illustrative and may be combined with other examples or teachings described herein without limitation. Example 1 is a method of wireless communication in a UE, comprising receiving multiple beams from a network entity for signal quality measurement, wherein the UE communicates with the network entity via a first beam of the multiple beams, and the method further comprises The method includes sending a message to the network entity indicating that the beam switching of the plurality of beams from the first beam to the second beam will be accelerated, based on the fact that the signal quality of the second beam is higher than the signal quality of the first beam and the signal quality of the first beam exceeds a traffic type threshold.

[0117] Embodiment 2 may be combined with Embodiment 1, and the transmission of a message to the network entity indicating that the beam switching is to be accelerated further includes transmitting a report of the measurement to the network entity based on a non-periodic channel status information reference signal (CSI-RS).

[0118] Embodiment 3, which may be combined with Embodiment 2, further includes receiving a downlink control information (DCI) signal from the network that includes a bit field that triggers the measurement based on the aperiodic CSI-RS, and receiving the aperiodic CSI-RS for the measurement from the network entity based on the aperiodic CSI-RS.

[0119] Embodiment 4, which may be combined with Embodiment 2, further includes receiving a random access response (RAR) message from the network that includes a bit field that triggers the measurement based on the aperiodic CSI-RS, and receiving the aperiodic CSI-RS for the measurement from the network entity based on the aperiodic CSI-RS.

[0120] Embodiment 5 may be combined with Embodiment 1 and further includes sending a message to the network entity indicating that the beam switching is to be accelerated, which includes sending a message to the network entity indicating that the UE has measured and stored the beam switching parameters for at least the portion of the plurality of beams prior to the beam switching.

[0121] Embodiment 6 may be combined with Embodiment 15 and further include receiving a control signal from the network entity that sets a first threshold for the UE to measure and store the beam switching parameters, the first threshold being one of a block error rate (BLER) threshold, a packet error rate (PER) threshold, or a latency threshold.

[0122] Example 7 may be combined with any of Examples 5 to 6 and further includes measuring and storing beam switching parameters for at least a portion of the plurality of beams before the beam switching.

[0123] Embodiment 8 may be combined with Embodiment 1 and further includes transmitting a message to the network entity indicating that the beam switching is to be accelerated, which includes transmitting beam switching parameters to the network entity based on path loss measurements using Layer 1 reference signal received power (L1-RSRP).

[0124] Embodiment 9 may be combined with Embodiment 8 and further includes receiving a control signal from the network entity to configure the path loss measurement using the L1-RSRP, and performing the path loss measurement using the L1-RSRP.

[0125] Example 10 may be combined with Example 1, and the transmission of a message to the network entity indicating that the beam switching will be accelerated further includes transmitting to the network entity a report indicating a channel quality indicator (CQI) or simplified wide-area (WB)-CQI for at least a portion of the plurality of beams before the beam switching, in order to accelerate the modulation and coding scheme (MCS) selection.

[0126] Example 11 may be combined with Example 11 and further includes measuring the CQI or the simplified WB-CQI over the portion of the plurality of beams, and the method further includes receiving a control signal from the network entity that sets the portion of the plurality of beams.

[0127] Embodiment 12 may be combined with Embodiment 1 and further includes sending a message to the network entity indicating that the beam switching is to be accelerated, and sending a beam fault recovery request (BFRQ) to the network entity based on beam fault detection (BFD) using a block error rate (BLER) threshold for Extended Reality (XR) communications.

[0128] Embodiment 13 may be combined with Embodiment 12 and further includes receiving a control signal from the network entity to set the BLER threshold for the XR communication and performing the BFD using the BLER threshold for the XR communication.

[0129] Embodiment 14 is a method for wireless communication in a network entity, comprising transmitting a plurality of beams to a user equipment (UE) for signal quality measurement, wherein the network entity communicates with the UE via a first beam of the plurality of beams, and the method further includes receiving a message from the UE indicating that the beam switching of the plurality of beams from the first beam to the second beam is accelerated based on the signal quality of the second beam being higher than that of the first beam and the signal quality of the first beam exceeding a traffic type threshold.

[0130] Example 15 may be combined with Example 14, and the receiving of a message from the UE indicating that the beam switching is to be accelerated further includes receiving a report of the measurement from the UE based on a non-periodic channel status information reference signal (CSI-RS).

[0131] Embodiment 16, which may be combined with Embodiment 15, further includes transmitting a downlink control information (DCI) signal to the UE that includes a bit field that triggers the measurement based on the aperiodic CSI-RS, and transmitting the aperiodic CSI-RS for the measurement to the UE based on the aperiodic CSI-RS.

[0132] Example 17, which may be combined with Example 15, further includes sending a random access response (RAR) message to the UE that includes a bit field that triggers the measurement based on the aperiodic CSI-RS, and sending the aperiodic CSI-RS for the measurement to the UE based on the aperiodic CSI-RS.

[0133] Example 18 may be combined with Example 14, and the receiving of a message from the UE indicating that the beam switching is to be accelerated further includes receiving a message from the UE indicating that the UE has measured and stored the beam switching parameters for at least the portion of the plurality of beams prior to the beam switching.

[0134] Embodiment 19 may be combined with Embodiment 18 and further includes transmitting a control signal to the UE that sets a first threshold for the UE to measure and store the beam switching parameters, the first threshold being one of a block error rate (BLER) threshold, a packet error rate (PER) threshold, or a latency threshold.

[0135] Example 20 may be combined with Example 14, and the receiving of a message from the UE indicating that the beam switching is to be accelerated further includes receiving beam switching parameters from the UE based on path loss measurements using Layer 1 reference signal received power (L1-RSRP).

[0136] Example 21 may be combined with Example 20 and further includes sending a control signal to the UE that sets up the path loss measurement using the L1-RSRP. Example 22 may be combined with Example 14, and the receiving of a message from the UE indicating that the beam switching will be accelerated further includes receiving a report from the UE indicating a channel quality indicator (CQI) or simplified wide-area (WB)-CQI for at least a portion of the plurality of beams before the beam switching in order to accelerate the modulation and coding scheme (MCS) selection.

[0137] Example 23 may be combined with Example 22 and further includes measuring the CQI or the simplified WB-CQI over the portion of the plurality of beams, the method further includes transmitting a control signal to the UE that sets the portion of the plurality of beams.

[0138] Example 24 may be combined with Example 14 and further includes receiving a message from the UE indicating that the beam switching is to be accelerated, and receiving a beam fault recovery request (BFRQ) from the UE based on beam fault detection (BFD) using a block error rate (BLER) threshold for Extended Reality (XR) communications (824).

[0139] Example 25 may be combined with Example 24 and further includes transmitting a control signal to the UE to configure the BLER for the XR communication. Example 26 may be combined with any of Examples 1 to 13 and further includes receiving a beam switching signal from the network entity indicating that the UE is switching from the first beam to the second beam before or after sending the message.

[0140] Example 27 may be combined with any of Examples 14 to 25 and further includes sending a beam switching signal to the UE indicating a switch from the first beam to the second beam before or after receiving the message.

[0141] Example 28 is a device for wireless communication including a transceiver, a memory, and a processor coupled to the memory and the transceiver, wherein the device is configured to carry out the method described in any of Examples 1 to 27.

[0142] Example 29 is a wireless communication device that includes means for carrying out the method described in any of Examples 1 to 27. Example 30 is a non-temporary computer-readable medium for storing computer executable code, which, when executed by a processor, causes the processor to perform the method described in any of Examples 1 to 27.

Claims

1. A method of wireless communication in user equipment (UE), The method includes receiving multiple beams from a network entity for signal quality measurement (408, 908), wherein the UE communicates with the network entity via a first beam of the multiple beams, and the method further includes Sending a message to the network entity indicating that beam switching from the first beam to the second beam will be accelerated based on the fact that the signal quality of the second beam is higher than that of the first beam and that the signal quality of the first beam exceeds a traffic type threshold (424, 524, 624, 724, 824, 924) A method of wireless communication, including [specific example].

2. Sending a message to the network entity indicating that the beam switching will be accelerated (424, 524, 624, 724, 824, 924) The method according to claim 1, comprising transmitting a measurement report to the network entity based on a non-periodic channel state information reference signal (CSI-RS) (424).

3. Receiving a downlink control information (DCI) signal from the network that includes a bit field that triggers the measurement based on the aperiodic CSI-RS (415), Based on the aperiodic CSI-RS, receiving the aperiodic CSI-RS for measurement from the network entity (418) The method according to claim 2, further comprising:

4. Receiving a random access response (RAR) message from the network that includes a bit field that triggers the measurement based on the aperiodic CSI-RS (416), Based on the aperiodic CSI-RS, receiving the aperiodic CSI-RS for measurement from the network entity (418) The method according to claim 2, further comprising:

5. Sending a message to the network entity indicating that the beam switching will be accelerated (424, 524, 624, 724, 824, 924) Prior to the beam switching, the UE sends a message to the network entity indicating that it has measured and stored the beam switching parameters for at least the portion of the plurality of beams (524). The method according to claim 1, including the method described in claim 1.

6. The method according to claim 5, further comprising receiving a control signal from the network entity (510) that sets a first threshold for the UE to measure and store the beam switching parameters, wherein the first threshold is one of a block error rate (BLER) threshold, a packet error rate (PER) threshold, or a latency threshold.

7. The method according to any one of claims 5 to 6, further comprising measuring and storing beam switching parameters for at least a portion of the plurality of beams before the beam switching (520).

8. Sending a message to the network entity indicating that the beam switching will be accelerated (424, 524, 624, 724, 824, 924) Using Layer 1 – Reference signal received power (L1 – RSRP), transmit beam switching parameters to the network entity based on path loss measurements (624) The method according to claim 1, including the method described in claim 1.

9. Receiving a control signal from the network entity to set the path loss measurement using the L1-RSRP (616), (620) Perform the path loss measurement using the L1-RSRP The method according to claim 8, further comprising:

10. Sending a message to the network entity indicating that the beam switching will be accelerated (424, 524, 624, 724, 824, 924) To accelerate the selection of a modulation and coding scheme (MCS), transmit to the network entity a report indicating channel quality indicators (CQI) or simplified broadband (WB)-CQI for at least a portion of the multiple beams before the beam switching (724) The method according to claim 1, including the method described in claim 1.

11. The CQI or the simplified WB-CQI is measured for the portion of the plurality of beams, and the method is Receiving a control signal from the network entity to set a portion of the plurality of beams (710) The method according to claim 10, including the method described in claim 10.

12. Sending a message to the network entity indicating that the beam switching will be accelerated (424, 524, 624, 724, 824, 924) Sending a beam fault recovery request (BFRQ) to the network entity based on beam fault detection (BFD) using a block error rate (BLER) threshold for extended reality (XR) communications (824) The method according to claim 1, including the method described in claim 1.

13. Receiving a control signal from the network entity to set the BLER threshold for the XR communication (810), The method of claim 12, further comprising performing the BFD using the BLER threshold for the XR communication (820).

14. A method for wireless communication in a network entity, The method includes transmitting multiple beams to a user device (UE) for signal quality measurement (408, 1008), wherein the network entity communicates with the UE via a first beam of the multiple beams, and the method further includes, Receiving a message from the UE indicating that beam switching from the first beam to the second beam will be accelerated based on the fact that the signal quality of the second beam is higher than that of the first beam, and that the signal quality of the first beam exceeds a traffic type threshold (424, 524, 624, 724, 824, 1024). A method of wireless communication, including [specific example].

15. Receiving a message from the UE indicating that the beam switching should be accelerated (424, 524, 624, 724, 824, 1024) is, Receiving a measurement report from the UE based on a non-periodic channel state information reference signal (CSI-RS) (424) The method according to claim 14, including the method described in claim 14.

16. Receiving a message from the UE indicating that the beam switching should be accelerated (424, 524, 624, 724, 824, 1024) is, Prior to the beam switching, the UE receives a message from the UE indicating that it has measured and stored the beam switching parameters for at least a portion of the plurality of beams (524). The method according to claim 14, including the method described in claim 14.

17. Receiving a message from the UE indicating that the beam switching should be accelerated (424, 524, 624, 724, 824, 1024) is, Layer 1 - Using the reference signal received power (L1-RSRP), beam switching parameters are received from the UE based on path loss measurements (624). The method according to claim 14, including the method described in claim 14.

18. Receiving a message from the UE indicating that the beam switching should be accelerated (424, 524, 624, 724, 824, 1024) is, To accelerate the selection of the modulation and coding scheme (MCS), the UE receives a report from the UE indicating channel quality indicators (CQI) or simplified broadband (WB)-CQI for at least a portion of the multiple beams before the beam switching (724). The method according to claim 14, including the method described in claim 14.

19. Receiving a message from the UE indicating that the beam switching should be accelerated (424, 524, 624, 724, 824, 1024) is, Receiving a beam fault recovery request (BFRQ) from the UE based on beam fault detection (BFD) using a block error rate (BLER) threshold for extended reality (XR) communication (824) The method according to claim 14, including the method described in claim 14.

20. A wireless communication device comprising a transceiver, a memory, and a processor coupled to the memory and the transceiver, configured to carry out the method according to any one of claims 1 to 19.

Images