Beam switching prediction and reporting
By using machine learning in a wireless communication system to predict communication parameter changes after beam switching and reporting to network entities, the problem of beam switching configuration update delay in the prior art is solved, and communication quality and response speed are improved.
Patent Information
- Application Number
- CN202280095196.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-29
- Publication Date
- 2024-12-03
AI Technical Summary
Existing wireless communication systems are difficult to predict and report changes in communication parameters in time during beam switching, resulting in delays in network entity configuration updates and affecting communication quality.
User equipment (UE) predicts the parameter changes of the communication beam to be switched to through machine learning or artificial intelligence, and sends predicted parameter changes and switching time information to the network entity so that the network entity can update the configuration in advance.
By predicting and reporting changes in beam switching-related parameters in advance, the delay during beam switching is reduced, and the communication quality and response speed of network entities are improved.
Smart Images

Figure CN119072937A_ABST
Abstract
Description
Technical Field
[0001] The following relates to wireless communications, including beam switching prediction and reporting. Background Art
[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE).
[0003] In some examples, a UE may use communication beams to communicate with a network entity. Improved techniques for switching between communication beams may be needed. Summary of the invention
[0004] The described technology relates to improved methods, systems, devices, and apparatuses that support beam switching prediction and reporting. A user equipment (UE) can use a first communication beam (e.g., a transmit beam, a receive beam) to communicate with a network entity. While using the first communication beam, the UE can determine (e.g., using machine learning, using artificial intelligence) a second communication beam to use after the first communication beam. Based on the determination, the UE can predict a change in a communication parameter of the UE associated with the second communication beam. Before switching from the first communication beam to the second communication beam, the UE can send a message to the network entity indicating the predicted change in the communication parameter and the time to switch to the second communication beam.
[0005] A method for wireless communication at a user equipment (UE) is described. The method may include: communicating with a network entity using a first communication beam; determining a second communication beam to be used for communicating with the network entity after using the first communication beam; predicting a change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam; and before switching to the second communication beam, sending a message to the network entity indicating the predicted change in the communication parameter and a time parameter indicating a time to switch to the second communication beam.
[0006] An apparatus for wireless communication is described. The apparatus may include: a memory; a transceiver; and at least one processor of a UE, the at least one processor coupled to the memory and the transceiver. The at least one processor may be configured to: communicate with a network entity via the transceiver using a first communication beam; determine a second communication beam to be used for communicating with the network entity after using the first communication beam; predict a change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam; and before switching to the second communication beam, send a message to the network entity indicating the predicted change in the communication parameter and a time parameter, the time parameter indicating a time to switch to the second communication beam.
[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for communicating with a network entity using a first communication beam; means for determining a second communication beam to be used for communicating with the network entity after using the first communication beam; means for predicting a change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam; and means for sending a message to the network entity indicating the predicted change in the communication parameter and a time parameter indicating a time to switch to the second communication beam before switching to the second communication beam.
[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: communicate with a network entity using a first communication beam; determine a second communication beam to be used for communicating with the network entity after using the first communication beam; predict a change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam; and before switching to the second communication beam, send a message to the network entity indicating the predicted change in the communication parameter and a time parameter indicating a time to switch to the second communication beam.
[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: determining a communication beam for a network entity based on the second communication beam; and indicating the communication beam for the network entity before switching from the first communication beam to the second communication beam.
[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: before switching to the second communication beam, requesting a set of uplink reference signal resources for sending an uplink reference signal using the second communication beam.
[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: requesting a downlink reference signal for measurement using the second communication beam before switching to the second communication beam; and sending channel state information that may be based on measuring the downlink reference signal using the second communication beam.
[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: before switching to the second communication beam, requesting the network entity to perform a beam scanning process after the time of switching to the second communication beam.
[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: determining a duration for which communications with a network entity may be suspended based on sending a message, the duration relative to a time to switch to a second communication beam.
[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, machine learning may be used to determine a second communication beam, and the methods, apparatus, and non-transitory computer-readable media may include additional operations, features, components, or instructions for performing the following operations: determining a change in the position of the UE, a change in the orientation of the UE, a change in the physical configuration of the UE, a change in surrounding obstacles, or any combination thereof, wherein the second communication beam may be determined based on the change in the position of the UE, the change in the orientation of the UE, the change in the physical configuration of the UE, the change in surrounding obstacles, or any combination thereof.
[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the change in the communication parameter includes a change in a multiple-input multiple-output rank or a change in a directional gain.
[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, messages may be sent according to a periodicity.
[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that a threshold duration may have elapsed since a previous message indicating a switch between communication beams was sent, wherein the message may have been sent based on determining that the threshold duration may have elapsed.
[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: determining that continued use of a first communication beam may be associated with a first predicted signal strength that may be lower than a second predicted signal strength associated with use of a second communication beam, wherein a message may be sent based on determining that the first predicted signal strength may be lower than the second predicted signal strength.
[0019] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: determining that a duration between the sending of a message and the time of a switch may be less than a threshold duration, wherein the message may be sent based on determining that the duration may be less than the threshold duration.
[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: determining that a duration between the sending of a message and the time of a switch may be greater than a threshold duration, wherein the message may be sent based on determining that the duration may be greater than the threshold duration.
[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a second message confirming receipt of the message by the network entity; and switching to a second communication beam at a time and based on receiving the second message.
[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be conveyed in a physical uplink control channel and the second message may be included in downlink control information for the UE.
[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be transmitted in a physical uplink shared channel, and the second message may be included in an uplink grant that may have the same hybrid automatic repeat request identifier as the physical uplink shared channel.
[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be included in uplink control information or in a medium access control (MAC) control element.
[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for initiating a random access procedure, wherein the message may be part of the random access procedure.
[0026] A method for wireless communication at a network entity is described. The method may include: communicating with a UE that is using a first communication beam; receiving a message indicating a time parameter and a predicted change of a communication parameter of the UE associated with switching from the first communication beam to a second communication beam, the time parameter indicating a time at which the UE is to switch from the first communication beam to the second communication beam; and changing a configuration of the network entity, a configuration of the UE, or both based on the time parameter and the predicted change of the communication parameter of the UE.
[0027] An apparatus for wireless communication is described. The apparatus may include: a memory; and at least one processor of a network entity, the at least one processor coupled to the memory. The at least one processor may be configured to: communicate with a UE that is using a first communication beam; receive a message indicating a time parameter and a predicted change of a communication parameter of the UE associated with switching from the first communication beam to the second communication beam, the time parameter indicating a time at which the UE is to switch from the first communication beam to the second communication beam; and change a configuration of the network entity, a configuration of the UE, or both based on the time parameter and the predicted change of the communication parameter of the UE.
[0028] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for communicating with a UE that is using a first communication beam; means for receiving a message indicating a time parameter and a predicted change of a communication parameter of the UE associated with switching from the first communication beam to a second communication beam, the time parameter indicating a time at which the UE is to switch from the first communication beam to the second communication beam; and means for changing a configuration of the network entity, a configuration of the UE, or both based on the time parameter and the predicted change of the communication parameter of the UE.
[0029] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: communicate with a UE that is using a first communication beam; receive a message indicating a time parameter and a predicted change of a communication parameter of the UE associated with switching from the first communication beam to a second communication beam, the time parameter indicating a time at which the UE is to switch from the first communication beam to the second communication beam; and change a configuration of the network entity, a configuration of the UE, or both based on the predicted change of the time parameter and the communication parameter of the UE.
[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: receiving an indication of a communication beam for use by a network entity after the UE switches to the second communication beam before the time when the UE may switch to the second communication beam; and communicating with the UE using the communication beam after the UE switches to the second communication beam based on the indication of the communication beam.
[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: receiving a request for a downlink reference signal for the UE to use a second communication beam for measurement before the UE may switch to the second communication beam; and receiving channel state information that may be based on the downlink reference signal.
[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: receiving a request to a network entity to perform a beam scanning process after the UE switches to the second communication beam before the UE may switch to the second communication beam; and performing the beam scanning process after the UE switches to the second communication beam and based on the request.
[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: determining a duration for suspending communication with the UE based on the message, the duration relative to a time when the UE may switch to a second communication beam.
[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the duration may be based on the capabilities of the UE and the cyclic prefix length.
[0035] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending a second message to the UE confirming receipt of the message.
[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be conveyed in a physical uplink control channel and the second message may be included in downlink control information for the UE.
[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the message may be conveyed in a physical uplink shared channel and the second message may be included in an uplink grant that may have the same hybrid automatic repeat request identifier as the physical uplink shared channel.
[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for performing a random access procedure with the UE, wherein the message may be part of the random access procedure. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] Figure 1 An example of a wireless communication system supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is illustrated.
[0040] Figure 2 An example of a wireless communication system supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is illustrated.
[0041] Figure 3 An example of a process flow supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is illustrated.
[0042] Figure 4 and Figure 5 A block diagram of a device supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown.
[0043] Figure 6 A block diagram of a communication manager supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown.
[0044] Figure 7 A diagram of a system including a device supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown.
[0045] Figure 8 and Fig. 9 A block diagram of a device supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown.
[0046] Fig.10 A block diagram of a communication manager supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown.
[0047] Fig.11 A diagram of a system including a device supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown.
[0048] Fig.12 and Fig.13 A flow chart illustrating a method of supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION
[0049] In some wireless communication systems, a user equipment (UE) may use beamforming to communicate with another wireless communication device such as a network entity. For example, a UE may use beamforming to focus a communication beam (e.g., a transmit beam, a receive beam) in a direction that facilitates communication with a network entity. When conditions change due to, for example, movement of the UE or movement of various surrounding obstacles, the UE may switch the communication beam to maintain a threshold quality of connectivity with the network entity. However, switching the communication beam may change one or more communication parameters of the UE, which in turn affects one or more configurations set by the network entity.
[0050] According to the techniques described herein, a UE may predict an upcoming switch between communication beams (referred to as a beam switch) and report the predicted beam switch and any associated changes in communication parameters to a network entity, which may use the reported information to change one or more configurations. In some examples, the UE may also report the time at which the UE expects to implement the beam switch, which may allow the network entity to select an appropriate time to implement changes to one or more configurations.
[0051] First, aspects of the present disclosure are described in the context of a wireless communication system. Additional aspects are described with reference to process flows. Aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to beam switching prediction and reporting.
[0052] Figure 1 An example of a wireless communication system 100 supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).
[0053] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).
[0054] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be able to communicate with various types of devices such as Figure 1 Communicating with other UEs 115 or network entities 105 as shown.
[0055] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.
[0056] In some examples, the network entities 105 may communicate with the core network 130 or with each other or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other directly (e.g., directly between each network entity 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .
[0057] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).
[0058] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0059] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, channel) between layers of a protocol stack supported by the respective network entities 105 communicating over those communication links.
[0060] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.
[0061] Where the techniques described herein are applied to the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support beam switching prediction and reporting as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).
[0062] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.
[0063] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.
[0064] UE 115 and network entity 105 can communicate with each other wirelessly via one or more communication links 125 (e.g., access links) through one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined to support communication link 125. For example, a carrier for communication link 125 may include a portion of an RF spectrum band (e.g., bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-APro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).
[0065] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located according to a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.
[0066] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode).
[0067] The signal waveform transmitted through the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.
[0068] The time interval of the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N fThe maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).
[0069] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.
[0070] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).
[0071] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .
[0072] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
[0073] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
[0074] In some examples, a UE 115 may be able to communicate directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), and the one or more UEs may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in the group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling of resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .
[0075] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0076] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0077] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, there may be even greater atmospheric attenuation and a shorter range for the propagation of EHF transmissions than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.
[0078] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be based on a carrier aggregation configuration in conjunction with a component carrier (e.g., LAA) operating in a licensed band. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.
[0079] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located in different geographic locations. The network entity 105 may have an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.
[0080] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.
[0081] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).
[0082] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as network entity 105, or by a receiving device, such as UE 115) beam directions for later transmission or reception by the network entity 105.
[0083] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.
[0084] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured beam set across a system bandwidth or one or more subbands. Network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information (CSI) reference signal (CSI-RS)), which may be precoded or not precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-faceted codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).
[0085] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105), the receiving device (e.g., UE 115) may perform receiving operations (e.g., directional listening) according to multiple receiving configurations. For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).
[0086] UE 115 and network entity 105 may support retransmission of data to increase the possibility of successfully receiving data. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility of correctly receiving data through a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.
[0087] In some examples of the wireless communication system 100, a UE 115 that is using beamforming may predict future switching between communication beams of the UE 115. For example, a UE 115 that is using a first communication beam may use mobility information (for the UE 115 and / or for surrounding obstacles) and information from past communication sessions to predict a second communication beam to be used in the future. When predicting switching between communication beams, the UE 115 may predict one or more expected changes in communication parameters associated with the switching. The UE 115 may report the predicted timing of the beam switching and the predicted changes in the communication parameters to the network entity 105 so that the network entity 105 may react accordingly (e.g., update one or more configurations).
[0088] Figure 2 An example of a wireless communication system 200 supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may be implemented as shown in FIG. Figure 1 Various aspects of the wireless communication system 100 described herein may be implemented by various aspects of the wireless communication system. For example, the wireless communication system 200 may include a network entity 105-a and a UE 115-a, which may be represented as shown in FIG. Figure 1 Examples of network entities 105 and UEs 115 described herein. The network entity 105-a may communicate with the UE 115-a within the geographic coverage area 110-a. According to the techniques described herein, the UE 115-a may predict switching in a communication beam and report information related to the beam switching to the network entity 105-a. In some examples, the communication beam referred to herein may be a side beam. In some examples, the wireless communication system 200 may be a mmW wireless communication system (e.g., a wireless communication system that supports mmW communication).
[0089] UE 115-a may communicate with network entity 105-a using communication beam 205-a, which may be defined by a set of parameters such as beam width and beam direction. UE 115-a may select a set of parameters for communication beam 205-a based on communication conditions (e.g., signal strength, noise, interference).
[0090] When UE 115-a is operating, UE 115-a may move in various ways. For example, UE 115-a may change position, rotate (e.g., change orientation), or (if UE 115-a is a flip UE, a UE with a flexible display, or both) change physical configuration (e.g., from an open or unfolded configuration to a closed or folded configuration). Additionally or alternatively, various obstacles (e.g., vehicles) around UE 115-a may change position. Such changes may be accompanied by changes in communication conditions, which may make the set of parameters initially selected for communication beam 205-a less than ideal. Therefore, UE 115-a may switch to communication beam 205-b, which may have different characteristics (e.g., beam width, directionality) than communication beam 205-a. Communication beam 205 may be a transmit beam (which may also be referred to as an uplink beam) or a receive beam (which may also be referred to as a downlink beam).
[0091] However, waiting for communication conditions to switch communication beams may increase latency associated with beam adjustment, etc. According to the techniques described herein, UE 115-a may predict the use of a new communication beam before communication conditions prompt UE 115-a to switch to the new communication beam. Switching to the new communication beam may involve activating new antenna panels (relative to those activated for the current communication beam) or modifying beamforming weights applied to the activated antenna panels, etc.
[0092] In some examples, UE 115-a may use machine learning or artificial intelligence to predict future usage of communication beams. The prediction may be based on movement of UE 115-a (e.g., a change in the location of UE 115-a, a change in the orientation of UE 115-a, a change in the physical configuration of UE 115-a), a change in obstacles, or any combination thereof, etc. UE 115-a may detect movement (e.g., rotation) of UE 115-a using signal strength (e.g., reference signal received power (RSRP)) measurements of synchronization signals or reference signals, directional gain measurements, sensor measurements (e.g., radio frequency (RF) sensor measurements, inertial measurement unit (IMU) sensor measurements, accelerometer measurements), camera information, or a combination thereof.
[0093] By tracking the movement (e.g., rotation) of UE 115-a and referring to past communication sessions within similar movements, UE 115-a can predict a switch from communication beam 205-a to communication beam 205-b. In some examples, UE 115-a can predict a switch between communication beams in a situation where the likelihood of switching communication beams is greater than a threshold likelihood. UE 115-a can predict the use of communication beam 205-b based on RSRP measurements (e.g., based on degradation of directional gain), even if the movement (e.g., rotation) of UE 115-a is different from past movements and even in the absence of information about the movement from sensors.
[0094] In anticipating an upcoming switch to communication beam 205-b, UE 115-a may anticipate changes in one or more communication parameters or configurations of UE 115-a. For example, UE 115-a may determine a change in MIMO rank (e.g., decrease, increase), a change in directional gain (e.g., decrease, increase), a change in power headroom, a change in transmit configuration indicator (TCI) state, or a combination thereof, etc. In some examples, the change in communication parameters may be caused by changing an antenna panel to form communication beam 205-b, and thus may correspond to a beam switch time.
[0095] Changes in communication parameters caused by switching communication beams may affect one or more configurations set by the network entity 105-a. To help the network entity 105-a account for changes in communication parameters in a timely manner (e.g., close in time to the beam switch), the UE 115-a may indicate these changes in the message 210.
[0096] UE 115-a sends message 210 after predicting a switch to communication beam 205-b but before switching to communication beam 205-b. In addition to indicating a change in communication parameters, message 210 may also include a time parameter (which may be referred to as a timestamp) indicating the time (which may be referred to as a beam switching time) at which UE 115-a switches from communication beam 205-a to communication beam 205-b. Thus, the time parameter may indicate the time at which the change in communication parameters will occur. The information in message 210 may allow network entity 105-a to update one or more configurations in parallel (e.g., concurrently) with UE 115-a switching to communication beam 205-b or before the switch.
[0097] Upon receiving message 210, network entity 105-a may change one or more configurations of network entity 105-a, one or more configurations of UE 115-a, or one or more configurations of both. For example, where message 210 indicates a new MIMO rank associated with communication beam 205-b for UE 115-a, network entity 105-a may change the MIMO rank associated with an upcoming transmission for UE 115-a. In another example, network entity 105-a may set and indicate a new configuration for periodic or persistent transmissions, such as periodic SRS or a configured grant (CG) physical uplink shared channel (PUSCH), based on the new MIMO rank of UE 115-a. In another example, where message 210 indicates a change in directional gain, network entity 105-a may change a modulation and coding scheme (MCS) used to communicate with UE 115-a. In another example, where message 210 indicates a new power headroom associated with communication beam 205-b, network entity 105-a may change the MCS, one or more power control parameters, or both for uplink communications by UE 115-a. Other examples of configuration changes are contemplated and within the scope of the present disclosure.
[0098] In some examples, the network entity 105-a may determine a duration (which may be referred to as a beam switching gap) to suspend communications with the UE 115-a so that the UE 115-a may switch communication beams without dropping content. The beam switching gap may be relative to a beam switching time (a time at which switching between communication beams is to occur) and may be based on the capabilities of the UE 115-a (e.g., a beam switching capability that may be communicated by 115-a) and a cyclic prefix length. For example, in a situation where the time it takes the UE 115-a to switch between communication beams (as indicated by the beam switching capability) is greater than the cyclic prefix length, the network entity 105-a may determine to implement a beam switching gap. In such a scenario, which may occur in a mmW communication system, the network entity 105-a may determine the duration of the beam switching gap based on the beam switching capability of the UE 115-a.
[0099] In some examples, the network entity 105-a may schedule the beam switching gap by indicating the beam switching gap to the UE 115-a. In other examples, the network entity 105-a and the UE 115-a may autonomously implement the beam switching gap. For example, the network entity 105-a may implement the beam switching gap based on receiving the message 210, and the UE 115-a may autonomously implement the beam switching gap based on sending the message 210 or based on receiving a message from the network entity 105-a confirming receipt of the message 210. In this scenario, the beam switching gap may be configured at the network entity 105-a and the UE 115-a before the UE 115-a sends the message 210.
[0100] In some examples, UE 115-a may indicate to network entity 105-a a preferred communication beam for network entity 105-a to use after UE 115-a switches to communication beam 205-b. The preferred communication beam may be based on communication beam 205-b and may be indicated in message 210 or in a separate message. Network entity 105-a may switch to the preferred communication beam based on a time parameter. For example, network entity 105-a may switch to the preferred communication beam at substantially the same time as UE 115-a switches to communication beam 205-b, or a threshold amount of time before or after.
[0101] After predicting a switch to communication beam 205-b (but possibly before switching to communication beam 205-b), UE 115-a may request one or more reference signals or uplink resources from network entity 105-a. For example, UE 115-a may request a set of reference signal resources (e.g., a set of sounding reference signal (SRS) resources) within which UE 115-a may send an SRS (e.g., a codebook-based SRS or a non-codebook-based SRS) for uplink channel estimation by network entity 105-a. In this example, network entity 105-a may schedule reference signal resources for UE 115-a based on a beam switching time (e.g., network entity 105-a may schedule UE 115-a using reference signal resources that occur after UE 115-a switches to communication beam 205-b).
[0102] In another example, UE 115-a may request network entity 105-a to send a reference signal (e.g., a channel state information reference signal (CSI-RS)), which UE 115-a may use for downlink channel estimation (e.g., by measuring the CSI-RS using communication beam 205-b). After determining the channel state information based on the CSI-RS, UE 115-a may send channel state information associated with communication beam 205-b (e.g., precoding matrix indicator (PMI), rank indicator (RI), channel quality indicator (CQI)) to network entity 105-a. In this example, network entity 105-a may send the reference signal to UE 115-a based on a beam switching time (e.g., network entity 105-a may send the reference signal to UE 115-a after UE 115-a switches to communication beam 205-b). UE 115-a may send associated channel state information in resources already scheduled by network entity 105-a or in resources requested by UE 115-a after predicting a switch to communication beam 205-b (but possibly before switching to communication beam 205-b).
[0103] After predicting switching to communication beam 205-b (but possibly before switching to communication beam 205-b), UE 115-a may request network entity 105-a to perform a beam scanning process. For example, UE 115-a may request network entity 105-a to perform a P3 beam scanning process, in which network entity 105-a repeatedly transmits on the same transmit beam so that UE 115-a can calibrate, refine, and confirm communication beam 205-b. Additionally or alternatively, UE 115-a may perform a beam scanning process after switching to communication beam 205-b so that UE 115-a can calibrate, refine, and confirm communication beam 205-b.
[0104] The requests of UE 115-a may be sent using communication beam 205-a or communication beam 205-b and may be included in message 210 or a different message. As noted, the requests of UE 115-a may correspond to beam switching times because the requests may indicate timing for the requests based on the beam switching times.
[0105] Thus, UE 115-a can facilitate timely configuration updates by predicting switches in communication beams and reporting information related to beam switches to network entity 105-a.Although described with reference to communication beams, the techniques described herein may be implemented for any number of communication beams, including multiple communication beams.
[0106] Figure 3An example of a process flow 300 for supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is illustrated. The process flow 300 may be performed by referring to Figure 1 and Figure 2 The process flow 300 may be implemented by the network entity 105-b and the UE 115-b, which may be implemented as described in reference to FIG. Figure 1 and Figure 2 Examples of described network entities and UEs. By implementing process flow 300, UE 115-b may facilitate beam management in scenarios where UE 115-b switches communication beams.
[0107] In the following description of process flow 300, operations between UE 115-b and network entity 105-b may be performed in a different order or at a different time. Some operations may also be excluded from process flow 300, or other operations may be added. Although UE 115-b and network entity 105-b are shown as performing operations of process flow 300, some aspects of some operations may also be performed by one or more other wireless devices.
[0108] At 305, UE 115-b may communicate with network entity 105-b using a first communication beam. At 310, UE 115-b may determine movement of UE 115-b, may determine movement of nearby obstacles, or both. For example, UE 115-a may determine that UE 115-b is changing position (e.g., changing latitude, longitude, altitude), changing orientation (e.g., rotating), changing physical configuration (e.g., folding or unfolding), or any combination thereof. Additionally or alternatively, UE 115-b may determine movement of one or more surrounding obstacles. UE 115-b may determine movement at 310 based on sensor information, camera information, synchronization signal measurements (e.g., synchronization signal block (SSB) measurements), reference signal measurements (e.g., CSI-RS measurements), or any combination thereof, and the like.
[0109] At 315, the UE 115-b may use machine learning or artificial intelligence or some other mechanism to predict a second communication beam to use based on the movement determined at 310. At 320, the UE 115-b may predict a change in one or more communication parameters associated with switching to the second communication beam. For example, the UE 115-b may predict a change in rank (e.g., MIMO rank), a change in directional gain (e.g., receive directional gain), a change in power headroom, a change in TCI state, or any combination thereof, and the like.
[0110] After the UE 115-b switches to the second communication beam, the UE 115-b may determine a preferred communication beam for use by the network entity 105-b at 325. The UE 115-b may determine the preferred communication beam based on the second communication beam.
[0111] At 330, UE 115-b may send a first message to network entity 105-b. The first message may indicate a change to one or more communication parameters, a time parameter indicating a time for UE 115-b to switch to a second communication beam (e.g., a beam switching time), or both. Additionally or alternatively, the first message may indicate the preferred communication beam determined at 325. In the event that UE 115-a requests uplink resources, reference signals, or a beam scanning procedure, these requests may be included in the first message, included in a separate message, or split between the first message and the separate message.
[0112] The first message may be included in uplink control information (UCI) conveyed by an uplink control channel (e.g., a physical uplink control channel (PUCCH)) or an uplink data channel (e.g., a PUSCH). In this scenario, uplink resources for the UCI may be pre-configured, or the UCI may be carried in uplink resources from an existing uplink grant. Alternatively, the first message may be included in a medium access control (MAC) control element (MAC-CE). In this scenario, the MAC-CE may be carried in uplink resources for an existing uplink grant or in uplink resources requested by the UE 115-b via a scheduling request (SR). The scheduling request may be a beam switching specific scheduling request or a non-beam switching specific scheduling request. In the case where the scheduling request is not supported or configured, or in other examples, the UE 115-b may initiate a random access procedure (e.g., a random access channel (RACH) procedure) and use one of the random access messages to convey the first message. For example, the first message may be included in MsgA of a two-step RACH procedure, or may be included in Msg3 of a four-step RACH procedure. In other words, the first message may be part of a random access procedure.
[0113] The first message may be sent according to a periodicity (e.g., in a scenario where the beam switching message is configured to occur periodically). For example, the first message may be included in a persistent or semi-persistent PUCCH. Additionally or alternatively, the first message may be sent in response to a trigger factor, such as satisfaction of a condition. For example, in a scenario where UE 115-b determines that continued use of the first communication beam is associated with a first predicted signal strength that is lower than a second predicted signal strength associated with use of the second communication beam, UE 115-b may send the first message. As an example, in a scenario where UE 115-b determines that continued use of the first communication beam is associated with a -X dB gain relative to use of the second communication beam, UE 115-b may send the first message.
[0114] In some examples, UE 115-b may send the first message if one or more timing conditions are met. In one example, there may be a limit on the frequency with which UE 115-b is permitted to send beam switching messages. For example, UE 115-b may track (e.g., via a timer) a duration that has elapsed since UE 115-b transmitted a previous beam switching message, and if the duration is greater than a threshold duration, UE 115-b may send the first message. If the elapsed duration is less than the threshold duration, UE 115-b may delay sending the first message until after the threshold duration has elapsed.
[0115] In another example of a timing condition, UE 115-b may avoid sending the first message too early before a beam switch time (e.g., the time at which the beam switch is to occur). For example, UE 115-b may wait to send the first message until A) the transmission of the first message and B) the beam switch time is less than a threshold duration (e.g., Y ms). In a similar example, UE 115-b may send the first message if the duration between A) the prediction of the beam switch and B) the beam switch time is less than the threshold duration. By setting a limit on how early (relative to the beam switch time) UE 115-b may send the beam switch message, UE 115-b may reduce the likelihood that the beam switch prediction will fail due to changing conditions.
[0116] In another example of a timing condition, UE 115-b may avoid sending the first message too close in time to a beam switching time. For example, UE 115-b may avoid sending the first message in a situation where A) the sending of the first message and B) the beam switching time is less than a threshold duration (e.g., X ms, where X is less than Y). In other words, UE 115-b may send the first message in a situation where A) the sending of the first message and B) the beam switching time is greater than a threshold duration (e.g., X ms). By setting a limit on how late UE 115-b may send the beam switching message (relative to the beam switching time), UE 115-b may reduce the likelihood that network entity 105-b will be unable to process the beam switching message before the beam switching time. In some examples, UE 115-b may use the timing conditions described herein to define a time window during which the sending of the first message is permitted.
[0117] The conditions for sending the first message may be specific to the UE 115-b or may be configurable by the network entity 105-b.
[0118] At 335, network entity 105-b may determine a beam switching gap based on the first message (e.g., network entity 105-b may determine a duration of a communication pause). The timing of the beam switching gap may be based on a time parameter indicating a beam switching time, and the duration of the beam switching gap may be based on a beam switching capability of UE 115-b, a cyclic prefix length used to communicate with UE 115-b, or both. In some examples, network entity 105-b may indicate the beam switching gap to UE 115-b. In other examples, the beam switching gap may be determined autonomously by UE 115-b.
[0119] At 340, the network entity 105-b may change one or more configurations of the network entity 105-b, may change one or more configurations of the UE 115-b, or both. For example, the network entity 105-b may change the MIMO rank used for communication with the UE 115-b, or schedule new transmissions based on the MIMO rank indicated in the first message. In another example, the network entity 105-b may use the new MIMO rank of the UE 115-b as a basis for a new configuration for periodic or persistent transmissions, such as a periodic SRS or a configured granted PUSCH. In another example, the network entity 105-b may use the new directional gain of the UE 115-b as a basis for changing the MCS used for communication with the UE 115-b. In another example, the network entity 105-b may use the new power headroom of the UE 115-b as a basis for changing the MCS, one or more power control parameters, or both for communication by (or with) the UE 115-b.
[0120] Although shown as occurring before 345, one or more of the operations at 340 may occur concurrently with 345, or after 345. In some examples, changing the configuration may include sending an indication of the changed configuration to UE 115-b.
[0121] At 345, the network entity 105-b may send a second message confirming (e.g., acknowledging) receipt of the first message at 330. In some examples, the second message (which may be referred to as an acknowledgment) may be included in downlink control information (DCI) for the UE 115-b. For example, in a case where the first message is included in the PUCCH, the second message may be included in the DCI. In a case where the first message indicates a change in the TCI state, the second message may be included in the DCI for switching the TCI to the reported beam. In some examples, the second message may be included in a physical uplink data channel (e.g., PUSCH). For example, in a case where the first message is included in the PUSCH (e.g., in the UCI or MAC-CE), the second message may be a new uplink grant with the same HARQ identifier as the PUSCH.
[0122] At 350, UE 115-b may switch from the first communication beam to the second communication beam. UE 115-b may switch to the second communication beam at a beam switching time indicated by a time parameter in the first message. In some examples, UE 115-b may switch to the second communication beam based on receiving a second message from network entity 105-b.
[0123] In some examples, the network entity 105-b may switch to the preferred communication beam indicated by the first message at 355. The timing for switching to the preferred communication beam may be based on the beam switching time indicated in the first message. For example, the network entity 105-b may switch to the preferred communication beam simultaneously with the beam switching time or within a threshold duration before or after the beam switching time.
[0124] In some examples (e.g., where the first message or a separate message requests a downlink reference signal (such as a CSI-RS)), the network entity 105-b may send one or more reference signals (e.g., CSI-RS) at 355. The network entity 105-b may send the one or more reference signals after the beam switching time (e.g., after 350) so that the UE 115-b may use the second communication beam to measure the reference signal for downlink channel estimation. The transmission timing for the reference signal may be requested by the UE 115-b, or may be determined by the network entity 105-b based on the beam switching time indicated by the time parameter. After measuring the reference signal using the second communication beam, the UE 115-b may send a report indicating channel state information based on the measurement.
[0125] In some examples (e.g., where the first message or a separate message requests uplink resources), the network entity 105-b may schedule UE 115-b with the uplink resources so that UE 115-b may send an uplink reference signal (e.g., SRS) using the second communication beam at 360. The timing of the uplink resources may be requested by UE 115-b or may be determined by the network entity 105-b based on a beam switching time indicated by a time parameter. The network entity 105-b may measure the SRS in the uplink resources to estimate an uplink channel between UE 115-b and the network entity 105-b.
[0126] In some examples (e.g., where the first message or a separate message requests a beam scanning procedure), the network entity 105-b may perform a beam scanning procedure (e.g., a P3 beam scanning procedure) at 365 so that the UE 115-b can characterize the second communication beam. The timing of the beam scanning procedure may be requested by the UE 115-b, or may be determined by the network entity 105-b based on a beam switching time indicated by a time parameter. Additionally or alternatively, the UE 115-b may characterize the second communication beam by performing a beam scanning procedure at 370 using the second communication beam.
[0127] Thus, UE 115-b can facilitate beam management in scenarios where UE 115-b switches communication beams.
[0128] Figure 4 A block diagram 400 of a device 405 supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown. The device 405 can be an example of aspects of the UE 115 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. The device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0129] The receiver 410 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to beam switching prediction and reporting). The information may be communicated to other components of the device 405. The receiver 410 may utilize a single antenna or a collection of multiple antennas.
[0130] The transmitter 415 may provide means for transmitting signals generated by other components of the device 405. For example, the transmitter 415 may transmit information associated with various information channels (e.g., control channels related to beam switching prediction and reporting, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 415 may be co-located with the receiver 410 in a transceiver module. The transmitter 415 may utilize a single antenna or a collection of multiple antennas.
[0131] The communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof or various components thereof may be examples of means for performing various aspects of beam switching prediction and reporting as described herein. For example, the communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.
[0132] In some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports means for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0133] Additionally or alternatively, in some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.
[0134] In some examples, communication manager 420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 410, transmitter 415, or both. For example, communication manager 420 may receive information from receiver 410, transmit information to transmitter 415, or be integrated with receiver 410, transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.
[0135] According to examples as disclosed herein, the communication manager 420 may support wireless communications at the UE. For example, the communication manager 420 may be configured to or otherwise support a component for communicating with a network entity using a first communication beam. The communication manager 420 may be configured to or otherwise support a component for determining a second communication beam to be used for communicating with the network entity after using the first communication beam. The communication manager 420 may be configured to or otherwise support a component for predicting a change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam. The communication manager 420 may be configured to or otherwise support a component for sending a message indicating a predicted change in the communication parameter and a time parameter to the network entity before switching to the second communication beam, the time parameter indicating the time of switching to the second communication beam.
[0136] By including or configuring a communication manager 420 according to examples as described herein, a device 405 (e.g., a processor controlling or otherwise coupled to a receiver 410, a transmitter 415, a communication manager 420, or a combination thereof) may support techniques for reducing latency associated with beam switching.
[0137] Figure 5A block diagram 500 of a device 505 supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown. The device 505 may be an example of aspects of the device 405 or UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0138] The receiver 510 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to beam switching prediction and reporting). The information may be communicated to other components of the device 505. The receiver 510 may utilize a single antenna or a collection of multiple antennas.
[0139] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information associated with various information channels (e.g., control channels related to beam switching prediction and reporting, data channels, information channels), such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a collection of multiple antennas.
[0140] The device 505 or its various components may be examples of components for performing various aspects of beam switching prediction and reporting as described herein. For example, the communication manager 520 may include a communication component 525, a beam prediction component 530, a parameter prediction component 535, or any combination thereof. The communication manager 520 may be an example of various aspects of the communication manager 420 as described herein. In some examples, the communication manager 520 or its various components may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.
[0141] According to examples as disclosed herein, the communication manager 520 may support wireless communications at the UE. The communication component 525 may be configured to or otherwise support a component for communicating with a network entity using a first communication beam. The beam prediction component 530 may be configured to or otherwise support a component for determining a second communication beam to be used for communicating with a network entity after using the first communication beam. The parameter prediction component 535 may be configured to or otherwise support a component for predicting a change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam. The communication component 525 may be configured to or otherwise support a component for sending a message indicating the predicted change in the communication parameter and a time parameter to the network entity before switching to the second communication beam, the time parameter indicating the time of switching to the second communication beam.
[0142] Figure 6 A block diagram 600 of a communication manager 620 supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown. The communication manager 620 can be an example of aspects of the communication manager 420, the communication manager 520, or both as described herein. The communication manager 620 or its various components can be examples of means for performing various aspects of beam switching prediction and reporting as described herein. For example, the communication manager 620 may include a communication component 625, a beam prediction component 630, a parameter prediction component 635, a beam pairing component 640, a CSI component 645, a beam scanning component 650, a beam switching timing component 655, a beam comparison component 660, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).
[0143] According to examples as disclosed herein, the communication manager 620 may support wireless communications at the UE. The communication component 625 may be configured to or otherwise support a component for communicating with a network entity using a first communication beam. The beam prediction component 630 may be configured to or otherwise support a component for determining a second communication beam to be used for communicating with a network entity after using the first communication beam. The parameter prediction component 635 may be configured to or otherwise support a component for predicting a change in a communication parameter of the UE associated with switching from a first communication beam to a second communication beam. In some examples, the communication component 625 may be configured to or otherwise support a component for sending a message indicating a predicted change in the communication parameter and a time parameter to the network entity before switching to the second communication beam, the time parameter indicating the time of switching to the second communication beam.
[0144] In some examples, beam pairing component 640 can be configured or otherwise support means for determining a communication beam for a network entity based on the second communication beam. In some examples, communication component 625 can be configured or otherwise support means for indicating a communication beam for a network entity before switching from a first communication beam to a second communication beam.
[0145] In some examples, communication component 625 can be configured or otherwise support means for requesting a set of uplink reference signal resources for transmitting an uplink reference signal using the second communication beam prior to switching to the second communication beam.
[0146] In some examples, communication component 625 can be configured or otherwise support means for requesting a downlink reference signal for measurement using the second communication beam prior to switching to the second communication beam. In some examples, CSI component 645 can be configured or otherwise support means for sending channel state information based on measuring the downlink reference signal using the second communication beam.
[0147] In some examples, beam scanning component 650 can be configured or otherwise support means for requesting, prior to switching to the second communication beam, that a network entity perform a beam scanning procedure after a time of switching to the second communication beam.
[0148] In some examples, the beam switching timing component 655 may be configured as or otherwise support means for determining a duration of a pause in communications with a network entity based on sending a message, relative to a time to switch to a second communication beam.
[0149] In some examples, machine learning is used to determine a second communication beam, and the beam prediction component 630 may be configured as or otherwise support components for determining a change in the UE's position, a change in the UE's orientation, a change in the UE's physical configuration, a change in surrounding obstacles, or any combination thereof, wherein the second communication beam is determined based on the change in the UE's position, the change in the UE's orientation, the change in the UE's physical configuration, the change in surrounding obstacles, or any combination thereof.
[0150] In some examples, the change in the communication parameter includes a change in the MIMO rank or a change in the directional gain. In some examples, the message is sent according to a periodicity.
[0151] In some examples, the beam switch timing component 655 may be configured as or otherwise support a component for determining that a threshold duration has elapsed since a previous message indicating a switch between communication beams was sent, wherein the message is sent based on determining that the threshold duration has elapsed.
[0152] In some examples, beam comparison component 660 may be configured to or otherwise support components for determining that continued use of a first communication beam is associated with a first predicted signal strength that is lower than a second predicted signal strength associated with use of a second communication beam, wherein the message is sent based on determining that the first predicted signal strength is lower than the second predicted signal strength.
[0153] In some examples, the beam switching timing component 655 may be configured as or otherwise support a component for determining that a duration between the transmission of a message and the time of the switch is less than a threshold duration, wherein the message is transmitted based on determining that the duration is less than the threshold duration.
[0154] In some examples, the beam switch timing component 655 may be configured as or otherwise support a component for determining that a duration between the transmission of a message and the time of the switch is greater than a threshold duration, wherein the message is transmitted based on determining that the duration is greater than the threshold duration.
[0155] In some examples, the communication component 625 can be configured or otherwise support means for receiving a second message confirming receipt of the message by the network entity. In some examples, the communication component 625 can be configured or otherwise support means for switching to a second communication beam at the time and based on receiving the second message.
[0156] In some examples, the message is conveyed in a physical uplink control channel. In some examples, the second message is included in downlink control information for the UE.
[0157] In some examples, the message is conveyed in a physical uplink shared channel.In some examples, the second message is included in an uplink grant having the same hybrid automatic repeat request identifier as the physical uplink shared channel.
[0158] In some examples, the message is included in uplink control information or in a medium access control (MAC) control element.
[0159] In some examples, communication component 625 may be configured or otherwise support means for initiating a random access procedure, wherein the message is part of the random access procedure.
[0160] Figure 7A diagram of a system 700 including a device 705 that supports beam switching prediction and reporting according to one or more aspects of the present disclosure is shown. The device 705 may be an example of a device 405, a device 505, or a UE 115 as described herein, or include components thereof. The device 705 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, a memory 730, a code 735, and a processor 740. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745).
[0161] I / O controller 710 can manage input and output signals for device 705. I / O controller 710 can also manage peripheral devices that are not integrated into device 705. In some cases, I / O controller 710 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 can utilize an operating system such as or another known operating system. Additionally or alternatively, I / O controller 710 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 710 may be implemented as part of a processor (such as processor 740). In some cases, a user may interact with device 705 via I / O controller 710 or via hardware components controlled by I / O controller 710.
[0162] In some cases, the device 705 may include a single antenna 725. However, in some other cases, the device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 715 may communicate bidirectionally via one or more antennas 725, a wired or wireless link, as described herein. For example, the transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 715 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 725 for transmission, and demodulating packets received from one or more antennas 725. The transceiver 715 or the transceiver 715 and the one or more antennas 725 may be examples of transmitters 415, transmitters 515, receivers 410, receivers 510, or any combination thereof or components thereof as described herein.
[0163] The memory 730 may include random access memory (RAM) and read-only memory (ROM). The memory 730 may store computer-readable, computer-executable code 735 including instructions that, when executed by the processor 740, cause the device 705 to perform various functions described herein. The code 735 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 735 may not be directly executable by the processor 740, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 730 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0164] The processor 740 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 730) to cause the device 705 to perform various functions (e.g., functions or tasks that support beam switching prediction and reporting). For example, the device 705 or a component of the device 705 may include a processor 740 and a memory 730 coupled to or coupled to the processor 740, and the processor 740 and the memory 730 are configured to perform the various functions described herein.
[0165] According to the examples disclosed herein, the communication manager 720 may support wireless communications at the UE. For example, the communication manager 720 may be configured to or otherwise support a component for communicating with a network entity using a first communication beam. The communication manager 720 may be configured to or otherwise support a component for determining a second communication beam to be used for communicating with a network entity after using the first communication beam. The communication manager 720 may be configured to or otherwise support a component for predicting a change in a communication parameter of the UE associated with switching from a first communication beam to a second communication beam. The communication manager 720 may be configured to or otherwise support a component for sending a message indicating a predicted change in the communication parameter and a time parameter to the network entity before switching to the second communication beam, the time parameter indicating the time of switching to the second communication beam.
[0166] By including or configuring a communication manager 720 according to examples as described herein, the device 705 can support techniques for improving communication reliability, reducing latency, and improving coordination between devices.
[0167] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 715, one or more antennas 725, or any combination thereof. For example, the communication manager 720 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 715. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or performed by the processor 740, the memory 730, the code 735, or any combination thereof. For example, the code 735 may include instructions that may be executed by the processor 740 to cause the device 705 to perform various aspects of beam switching prediction and reporting as described herein, or the processor 740 and the memory 730 may be otherwise configured to perform or support such operations.
[0168] Figure 8 A block diagram 800 of a device 805 supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0169] The receiver 810 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.
[0170] The transmitter 815 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 805. For example, the transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 815 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 815 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include a modem or be coupled to a modem.
[0171] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of beam switching prediction and reporting as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.
[0172] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microprocessor, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0173] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.
[0174] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.
[0175] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a network entity. For example, the communication manager 820 may be configured to or otherwise support a component for communicating with a UE that is using a first communication beam. The communication manager 820 may be configured to or otherwise support a component for receiving a message indicating a predicted change in a time parameter and a communication parameter of the UE associated with switching from the first communication beam to the second communication beam, the time parameter indicating the time at which the UE is to switch from the first communication beam to the second communication beam. The communication manager 820 may be configured to or otherwise support a component for changing a configuration of the network entity, a configuration of the UE, or both based on the predicted change in the time parameter and the communication parameter of the UE.
[0176] By including or configuring a communication manager 820 according to examples as described herein, a device 805 (e.g., a processor controlling or otherwise coupled to a receiver 810, a transmitter 815, a communication manager 820, or a combination thereof) may support techniques for reducing latency associated with beam switching.
[0177] Fig. 9 A block diagram 900 of a device 905 supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0178] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof.
[0179] The transmitter 915 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.
[0180] The device 905 or its various components may be examples of components for performing various aspects of beam switching prediction and reporting as described herein. For example, the communication manager 920 may include a communication component 925, a beam switching component 930, a configuration component 935, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
[0181] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. The communication component 925 may be configured to or otherwise support a means for communicating with a UE that is using a first communication beam. The beam switching component 930 may be configured to or otherwise support a means for receiving a message indicating a time parameter and a predicted change of a communication parameter of the UE associated with switching from the first communication beam to the second communication beam, the time parameter indicating the time at which the UE is to switch from the first communication beam to the second communication beam. The configuration component 935 may be configured to or otherwise support a means for changing a configuration of the network entity, a configuration of the UE, or both based on the predicted change of the time parameter and the communication parameter of the UE.
[0182] Fig.10 A block diagram 1000 of a communication manager 1020 supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of means for performing various aspects of beam switching prediction and reporting as described herein. For example, the communication manager 1020 may include a communication component 1025, a beam switching component 1030, a configuration component 1035, a beam pairing component component 1040, a beam scanning component 1045, a beam switching gap component 1050, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.
[0183] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. The communication component 1025 may be configured to or otherwise support means for communicating with a UE that is using a first communication beam. The beam switching component 1030 may be configured to or otherwise support means for receiving a message indicating a time parameter and a predicted change of a communication parameter of the UE associated with switching from the first communication beam to the second communication beam, the time parameter indicating the time at which the UE is to switch from the first communication beam to the second communication beam. The configuration component 1035 may be configured to or otherwise support means for changing a configuration of the network entity, a configuration of the UE, or both based on the predicted change of the time parameter and the communication parameter of the UE.
[0184] In some examples, beam pairing component 1040 may be configured or otherwise support means for receiving an indication of a communication beam for use by the network entity after the UE switches to the second communication beam prior to the time at which the UE is to switch to the second communication beam. In some examples, communication component 1025 may be configured or otherwise support means for communicating with the UE using the communication beam after the UE switches to the second communication beam based on the indication of the communication beam.
[0185] In some examples, communication component 1025 can be configured to or otherwise support means for receiving a request for a downlink reference signal for the UE to measure using the second communication beam prior to the time when the UE is to switch to the second communication beam. In some examples, communication component 1025 can be configured to or otherwise support means for receiving channel state information based on the downlink reference signal.
[0186] In some examples, beam scanning component 1045 may be configured or otherwise support means for receiving a request to a network entity to perform a beam scanning procedure after the UE switches to the second communication beam before the time when the UE is to switch to the second communication beam. In some examples, beam scanning component 1045 may be configured or otherwise support means for performing a beam scanning procedure after the UE switches to the second communication beam and based on the request.
[0187] In some examples, beam switching gap component 1050 may be configured as or otherwise support means for determining, based on the message, a duration for suspending communications with the UE relative to a time at which the UE is to switch to a second communication beam.
[0188] In some examples, the duration is based on the capabilities of the UE and the cyclic prefix length.In some examples, the communication component 1025 can be configured to or otherwise support means for sending a second message to the UE confirming receipt of the message.
[0189] In some examples, the message is conveyed in a physical uplink control channel. In some examples, the second message is included in downlink control information for the UE.
[0190] In some examples, the message is conveyed in a physical uplink shared channel.In some examples, the second message is included in an uplink grant having the same hybrid automatic repeat request identifier as the physical uplink shared channel.
[0191] In some examples, communication component 1025 may be configured or otherwise support means for performing a random access procedure with the UE, wherein the message is part of the random access procedure.
[0192] Fig.11 A diagram of a system 1100 including a device 1105 supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a network entity 105 as described herein, or include components thereof. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support output and acquisition of communications, such as a communication manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, a code 1130, and a processor 1135. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1140).
[0193] The transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115 that may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1110 may also include a modem for modulating a signal, providing the modulated signal for transmission (e.g., by one or more antennas 1115, by a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1115, from a wired receiver), and demodulating the signal. The transceiver 1110 or the transceiver 1110 and one or more antennas 1115 or a wired interface (where applicable) may be an example of a transmitter 815, a transmitter 915, a receiver 810, a receiver 910, or any combination thereof or any component thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).
[0194] The memory 1125 may include RAM and ROM. The memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by the processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 1130 may not be directly executable by the processor 1135, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1125 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0195] The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic element, a discrete hardware component, or any combination thereof). In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1125) to enable the device 1105 to perform various functions (e.g., various functions or tasks supporting beam switching prediction and reporting). For example, the device 1105 or a component of the device 1105 may include a processor 1135 and a memory 1125 coupled to the processor 1135, and the processor 1135 and the memory 1125 are configured to perform the various functions described herein. Processor 1135 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 1105 (e.g., by executing code 1130).
[0196] In some examples, bus 1140 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1105, or communications performed between different components of device 1105 that may be co-located or located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, memory 1125, code 1130, and processor 1135 may be located in one of these different components or divided between different components).
[0197] In some examples, the communication manager 1120 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1120 may manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1120 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UE 115 in coordination with the other network entities 105. In some examples, the communication manager 1120 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.
[0198] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. For example, the communication manager 1120 may be configured to or otherwise support a component for communicating with a UE that is using a first communication beam. The communication manager 1120 may be configured to or otherwise support a component for receiving a message indicating a time parameter and a predicted change of a communication parameter of the UE associated with switching from the first communication beam to the second communication beam, the time parameter indicating the time at which the UE is to switch from the first communication beam to the second communication beam. The communication manager 1120 may be configured to or otherwise support a component for changing a configuration of the network entity, a configuration of the UE, or both based on the predicted change of the time parameter and the communication parameter of the UE.
[0199] By including or configuring a communications manager 1120 according to examples as described herein, the device 1105 can support techniques for improving communications reliability, reducing latency, and improving coordination between devices.
[0200] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof. For example, the communication manager 1120 may be configured to receive or transmit messages or other signaling as described herein via the transceiver 1110. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1135, the memory 1125, the code 1130, the transceiver 1110, or any combination thereof. For example, the code 1130 may include instructions that may be executed by the processor 1135 to cause the device 1105 to perform various aspects of beam switching prediction and reporting as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.
[0201] Fig.12 A flowchart illustrating a method 1200 for supporting beam switching prediction and reporting according to one or more aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0202] At 1205, the method may include communicating with a network entity using a first communication beam. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Figure 6 Additionally or alternatively, the means for performing 1205 may (but not necessarily) include, for example, an antenna 725, a transceiver 715, a communication manager 720, a memory 730 (including code 735), a processor 740, and / or a bus 745.
[0203] At 1210, the method may include determining a second communication beam to be used for communicating with the network entity after using the first communication beam. That is, the determined second communication beam is a beam determined to be used for communicating with the network entity once the first communication beam is no longer used. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be described with reference to Figure 6 Additionally or alternatively, the means for performing 1210 may (but not necessarily) include, for example, antenna 725, transceiver 715, communication manager 720, memory 730 (including code 735), processor 740, and / or bus 745.
[0204] At 1215, the method may include predicting a change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Figure 6 Additionally or alternatively, the means for performing 1215 may (but not necessarily) include, for example, an antenna 725, a transceiver 715, a communication manager 720, a memory 730 (including code 735), a processor 740, and / or a bus 745.
[0205] At 1220, the method may include, before switching to the second communication beam, sending a message to the network entity indicating the predicted change in the communication parameter and a time parameter indicating the time to switch to the second communication beam. The operations of 1220 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1220 may be performed as described in reference to Figure 6 Additionally or alternatively, the means for performing 1220 may (but not necessarily) include, for example, an antenna 725, a transceiver 715, a communication manager 720, a memory 730 (including code 735), a processor 740, and / or a bus 745.
[0206] Fig.13 1 is a flowchart illustrating a method 1300 for supporting beam switching prediction and reporting according to one or more aspects of the present disclosure. The operations of the method 1300 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 3 as well as Figures 8 to 11 The network entity described herein may be executed by the network entity. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.
[0207] At 1305, the method may include communicating with a UE that is using a first communication beam. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Fig.10 Additionally or alternatively, the means for performing 1305 may (but not necessarily) include, for example, an antenna 1115, a transceiver 1110, a communication manager 1120, a memory 1125 (including code 1130), a processor 1135, and / or a bus 1140.
[0208] At 1310, the method may include receiving a message indicating a time parameter and a predicted change of a communication parameter of the UE associated with switching from a first communication beam to a second communication beam, the time parameter indicating a time at which the UE is to switch from the first communication beam to the second communication beam. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Fig.10 The beam switching component 1030 described above is performed. Additionally or alternatively, the means for performing 1310 may (but not necessarily) include, for example, an antenna 1115, a transceiver 1110, a communication manager 1120, a memory 1125 (including code 1130), a processor 1135, and / or a bus 1140.
[0209] At 1315, the method may include changing the configuration of the network entity, the configuration of the UE, or both based on the predicted change in the time parameter and the communication parameter of the UE. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Fig.10 Additionally or alternatively, the means for performing 1315 may (but not necessarily) include, for example, an antenna 1115, a transceiver 1110, a communication manager 1120, a memory 1125 (including code 1130), a processor 1135, and / or a bus 1140.
[0210] The following provides an overview of various aspects of the disclosure:
[0211] Aspect 1: A method for performing wireless communications at a UE, comprising: communicating with a network entity using a first communication beam; determining a second communication beam to be used for communicating with the network entity after using the first communication beam; predicting a change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam; and before switching to the second communication beam, sending a message to the network entity indicating the predicted change in the communication parameter and a time parameter, the time parameter indicating the time to switch to the second communication beam.
[0212] Aspect 2: The method according to Aspect 1 also includes: determining a communication beam for the network entity based at least in part on the second communication beam; and indicating the communication beam for the network entity before switching from the first communication beam to the second communication beam.
[0213] Aspect 3: The method according to any one of Aspects 1 to 2 further includes: before switching to the second communication beam, requesting an uplink reference signal resource set for sending an uplink reference signal using the second communication beam.
[0214] Aspect 4: The method according to any one of Aspects 1 to 3 further includes: before switching to the second communication beam, requesting a downlink reference signal to perform measurement using the second communication beam; and sending channel state information based at least in part on measuring the downlink reference signal using the second communication beam.
[0215] Aspect 5: The method according to any one of Aspects 1 to 4 further includes: before switching to the second communication beam, requesting the network entity to perform a beam scanning process after the time of switching to the second communication beam.
[0216] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: determining a duration of the suspension of communication with the network entity based at least in part on sending the message, the duration relative to the time of switching to the second communication beam.
[0217] Aspect 7: A method according to any one of Aspects 1 to 6, wherein the second communication beam is determined using machine learning, and the method further includes: determining a change in the position of the UE, a change in the orientation of the UE, a change in the physical configuration of the UE, a change in surrounding obstacles, or any combination thereof, wherein the second communication beam is determined at least in part based on the change in the position of the UE, the change in the orientation of the UE, the change in the physical configuration of the UE, the change in surrounding obstacles, or any combination thereof.
[0218] Aspect 8: The method according to any one of aspects 1 to 7, wherein the change of the communication parameter comprises a change of a multiple-input multiple-output rank or a change of a directional gain.
[0219] Aspect 9: The method according to any one of aspects 1 to 8, wherein the message is sent according to a periodicity.
[0220] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: determining that a threshold duration has passed since sending a previous message indicating a switch between communication beams, wherein the message is sent at least in part based on determining that the threshold duration has passed.
[0221] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: determining that continued use of the first communication beam is associated with a first predicted signal strength, the first predicted signal strength being lower than a second predicted signal strength associated with use of the second communication beam, wherein the message is sent at least in part based on determining that the first predicted signal strength is lower than the second predicted signal strength.
[0222] Aspect 12: The method according to any one of Aspects 1 to 11 further includes: determining that the duration between the sending of the message and the time of switching is less than a threshold duration, wherein the message is sent at least in part based on determining that the duration is less than the threshold duration.
[0223] Aspect 13: The method according to any one of Aspects 1 to 12 further includes: determining that the duration between the sending of the message and the time of switching is greater than a threshold duration, wherein the message is sent at least in part based on determining that the duration is greater than the threshold duration.
[0224] Aspect 14: The method according to any one of Aspects 1 to 13 further includes: receiving a second message confirming that the message is received by the network entity; and switching to the second communication beam at the time and at least in part based on receiving the second message.
[0225] Aspect 15: The method according to aspect 14, wherein the message is transmitted in a physical uplink control channel, and the second message is included in downlink control information for the UE.
[0226] Aspect 16: The method according to aspect 14, wherein the message is conveyed in a physical uplink shared channel, and the second message is included in an uplink grant having the same hybrid automatic repeat request identifier as the physical uplink shared channel.
[0227] Aspect 17: A method according to any one of aspects 1 to 16, wherein the message is included in uplink control information or a medium access control (MAC) control element.
[0228] Aspect 18: The method according to any one of Aspects 1 to 17 further comprises: initiating a random access procedure, wherein the message is part of the random access procedure.
[0229] Aspect 19: A method for performing wireless communications at a network entity, comprising: communicating with a UE that is using a first communication beam; receiving a message indicating a time parameter and a predicted change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam, the time parameter indicating the time at which the UE is to switch from the first communication beam to the second communication beam; and changing a configuration of the network entity, a configuration of the UE, or both based at least in part on the time parameter and the predicted change in the communication parameter of the UE.
[0230] Aspect 20: The method according to Aspect 19 further includes: before the time when the UE is to switch to the second communication beam, receiving an indication of a communication beam for use by the network entity after the UE switches to the second communication beam; and using the communication beam to communicate with the UE after the UE switches to the second communication beam based at least in part on the indication of the communication beam.
[0231] Aspect 21: The method according to any one of Aspects 19 to 20 further includes: receiving a request for a downlink reference signal for the UE to use the second communication beam for measurement before the time when the UE is to switch to the second communication beam; and receiving channel state information based at least in part on the downlink reference signal.
[0232] Aspect 22: The method according to any one of Aspects 19 to 21 further includes: before the time when the UE is to switch to the second communication beam, receiving a request for the network entity to perform a beam scanning process after the UE switches to the second communication beam; and performing the beam scanning process after the UE switches to the second communication beam and at least partly based on the request.
[0233] Aspect 23: The method according to any one of Aspects 19 to 22 also includes: determining a duration of suspending communication with the UE based at least in part on the message, the duration being relative to the time when the UE is to switch to the second communication beam.
[0234] Aspect 24: The method according to aspect 23, wherein the duration is based at least in part on the capabilities of the UE and a cyclic prefix length.
[0235] Aspect 25: The method according to any one of Aspects 19 to 24 further includes: sending a second message to the UE confirming receipt of the message.
[0236] Aspect 26: The method according to aspect 25, wherein the message is conveyed in a physical uplink control channel, and the second message is included in downlink control information for the UE.
[0237] Aspect 27: The method according to aspect 25, wherein the message is conveyed in a physical uplink shared channel, and the second message is included in an uplink grant having the same hybrid automatic repeat request identifier as the physical uplink shared channel.
[0238] Aspect 28: The method according to any one of Aspects 19 to 27 further includes: performing a random access procedure with the UE, wherein the message is part of the random access procedure.
[0239] Aspect 29: An apparatus for wireless communication, comprising: a memory; a transceiver; and at least one processor, the at least one processor being coupled to the memory and the transceiver, the at least one processor being configured to execute a method according to any one of Aspects 1 to 18.
[0240] Aspect 30: An apparatus for wireless communication at a UE, comprising at least one means for performing a method according to any one of aspects 1 to 18.
[0241] Aspect 31: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 18.
[0242] Aspect 32: An apparatus for wireless communication, comprising: a memory; and at least one processor, the at least one processor coupled to the memory, the at least one processor configured to perform the method according to any one of aspects 19 to 28.
[0243] Aspect 33: An apparatus for wireless communication at a network entity, comprising at least one means for performing a method according to any one of aspects 19 to 28.
[0244] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 19 to 28.
[0245] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0246] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.
[0247] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.
[0248] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0249] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that various parts of the functions are implemented at different physical locations.
[0250] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes the transfer of computer program from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device or can be used for carrying or storing desired program code member and can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure Any other non-transient medium.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0251] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items introduced by a phrase such as "at least one of..." or "one or more of...") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on".
[0252] The term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), etc. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
[0253] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.
[0254] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0255] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for wireless communication at a user equipment (UE), comprising: communicating with a network entity using a first communication beam; determining a second communication beam to be used for communicating with the network entity after using the first communication beam; predicting a change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam; as well as Prior to switching to the second communication beam, a message is sent to the network entity indicating the predicted change of the communication parameter and a time parameter indicating a time to switch to the second communication beam.
2. The method according to claim 1, further comprising: determining a communication beam for the network entity based at least in part on the second communication beam; as well as Prior to switching from the first communication beam to the second communication beam, indicating the communication beam to the network entity.
3. The method according to claim 1, further comprising: Prior to switching to the second communication beam, a set of uplink reference signal resources for sending an uplink reference signal using the second communication beam is requested.
4. The method according to claim 1, further comprising: Before switching to the second communication beam, requesting a downlink reference signal to perform measurements using the second communication beam; as well as Transmitting channel state information based at least in part on measuring the downlink reference signal using the second communication beam.
5. The method according to claim 1, further comprising: Before switching to the second communication beam, the network entity is requested to perform a beam scanning procedure after the time of switching to the second communication beam.
6. The method according to claim 1, further comprising: A duration of a pause in communications with the network entity is determined based at least in part on sending the message, the duration relative to the time of switching to the second communication beam.
7. The method of claim 1 , wherein the second communication beam is determined using machine learning, the method further comprising: Determine a change in the position of the UE, a change in the orientation of the UE, a change in the physical configuration of the UE, a change in surrounding obstacles, or any combination thereof, wherein the second communication beam is determined at least in part based on the change in the position of the UE, the change in the orientation of the UE, the change in the physical configuration of the UE, the change in surrounding obstacles, or any combination thereof.
8. The method of claim 1, wherein the change of the communication parameter comprises a change of a multiple-input multiple-output rank or a change of a directional gain.
9. The method of claim 1, wherein the message is sent according to a periodicity.
10. The method according to claim 1, further comprising: A determination is made that a threshold duration has elapsed since sending a previous message indicating a switch between communication beams, wherein the message was sent based at least in part on the determination that the threshold duration has elapsed.
11. The method according to claim 1, further comprising: Determining that continued use of the first communication beam is associated with a first predicted signal strength that is lower than a second predicted signal strength associated with use of the second communication beam, wherein the message is sent based at least in part on determining that the first predicted signal strength is lower than the second predicted signal strength.
12. The method according to claim 1, further comprising: A determination is made that a duration between the sending of the message and the time of the switching is less than a threshold duration, wherein the message is sent based at least in part on determining that the duration is less than the threshold duration.
13. The method according to claim 1, further comprising: A determination is made that a duration between the sending of the message and the time of the switch is greater than a threshold duration, wherein the message is sent based at least in part on determining that the duration is greater than the threshold duration.
14. The method according to claim 1, further comprising: receiving a second message confirming receipt of the message by the network entity; as well as Switching to the second communication beam at the time and based at least in part on receiving the second message.
15. The method of claim 14, wherein the message is conveyed in a physical uplink control channel, and wherein the second message is included in downlink control information for the UE.
16. The method of claim 14, wherein the message is conveyed in a physical uplink shared channel, and wherein the second message is included in an uplink grant having the same hybrid automatic repeat request identifier as the physical uplink shared channel.
17. The method of claim 1, wherein the message is included in uplink control information or in a medium access control (MAC) control element.
18. The method of claim 1, further comprising: A random access procedure is initiated, wherein the message is a part of the random access procedure.
19. A method for wireless communication at a network entity, comprising: communicating with a user equipment (UE) that is using a first communication beam; receiving a message indicating a time parameter and a predicted change of a communication parameter of the UE associated with switching from the first communication beam to the second communication beam, the time parameter indicating a time at which the UE is to switch from the first communication beam to the second communication beam; as well as A configuration of the network entity, a configuration of the UE, or both is changed based at least in part on the predicted change in the time parameter and the communication parameter of the UE.
20. The method according to claim 19, further comprising: receiving, before the time at which the UE is to switch to the second communication beam, an indication of a communication beam for use by the network entity after the UE switches to the second communication beam; and Based at least in part on the indication of the communication beam, communicating with the UE using the communication beam after the UE switches to the second communication beam.
21. The method of claim 19, further comprising: receiving, before the time at which the UE is to switch to the second communication beam, a request for a downlink reference signal for the UE to measure using the second communication beam; as well as Channel state information based at least in part on the downlink reference signal is received.
22. The method of claim 19, further comprising: receiving, before the time at which the UE is to switch to the second communication beam, a request for the network entity to perform a beam scanning procedure after the UE switches to the second communication beam; as well as The beam scanning procedure is performed after the UE switches to the second communication beam and based at least in part on the request.
23. The method of claim 19, further comprising: A duration for suspending communications with the UE is determined based at least in part on the message, the duration relative to the time at which the UE is to switch to the second communication beam.
24. The method of claim 23, wherein the duration is based at least in part on capabilities of the UE and a cyclic prefix length.
25. The method of claim 19, further comprising: A second message is sent to the UE confirming receipt of the message.
26. The method of claim 25, wherein the message is conveyed in a physical uplink control channel, and wherein the second message is included in downlink control information for the UE.
27. The method of claim 25, wherein the message is conveyed in a physical uplink shared channel, and wherein the second message is included in an uplink grant having the same hybrid automatic repeat request identifier as the physical uplink shared channel.
28. The method of claim 19, further comprising: A random access procedure is performed with the UE, wherein the message is a part of the random access procedure.
29. An apparatus for wireless communication, comprising: Memory; Transceiver; and at least one processor of a user equipment (UE), the at least one processor being coupled to the memory and the transceiver, and the at least one processor being configured to: communicating with a network entity via the transceiver using a first communication beam; determining a second communication beam to be used for communicating with the network entity after using the first communication beam; predicting a change in a communication parameter of the UE associated with switching from the first communication beam to the second communication beam; as well as A message is sent to the network entity via the transceiver and prior to switching to the second communication beam indicating the predicted change of the communication parameter and a time parameter indicating a time to switch to the second communication beam.
30. An apparatus for wireless communication, comprising: Memory; and at least one processor of a network entity, the at least one processor being coupled to the memory and configured to: communicating with a user equipment (UE) that is using a first communication beam; receiving a message indicating a time parameter and a predicted change of a communication parameter of the UE associated with switching from the first communication beam to the second communication beam, the time parameter indicating a time at which the UE is to switch from the first communication beam to the second communication beam; as well as A configuration of the network entity, a configuration of the UE, or both is changed based at least in part on the predicted change in the time parameter and the communication parameter of the UE.
Citation Information
Cited By
Devices and methods for communication
WO2026199237A1
