Beam prediction mode switching in wireless communications

By using a beam prediction model in a wireless communication system to predict a second beam set based on a first beam set and reconfigure it according to the prediction conditions, the communication failure problem caused by beam pair misalignment is solved, achieving more efficient and low-overhead communication.

CN119054209APending Publication Date: 2024-11-29QUALCOMM INC
View PDF 0 Cites 4 Cited by

Patent Information

Application Number
CN202280095013.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-05-06
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

In existing wireless communication systems, beam misalignment leads to communication failures, necessitating improved beam management techniques to reduce overhead and latency.

Method used

A beam prediction model is adopted to predict the second beam set based on the first beam set, and the beam prediction model is reconfigured according to changes in prediction conditions, including discontinuous reception mode, changes in UE mobility, prediction error of the beam prediction model, or interference level.

Benefits of technology

Beam prediction models can reduce overhead and latency in wireless communication, improve communication reliability and efficiency, and reduce power consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119054209A_ABST
    Figure CN119054209A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure disclose techniques and apparatus for beam prediction and configuration of beam prediction modules. Beam prediction may reduce overhead and latency in wireless communications. The wireless communication device may select one or more beams based on beam prediction or beam measurements. A wireless device may communicate with a network entity using a first set of beams. The wireless device may communicate with the network entity using a second set of beams predicted based at least in part on the first set of beams using a beam prediction model. The wireless device may change the beam prediction model in response to a change in prediction conditions including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The techniques discussed below relate generally to wireless communication systems, and more particularly to beam prediction and switching between beam prediction modes. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems. These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. Some wireless communication systems (e.g., NR systems) may use beamforming technology for communication between wireless devices. Beamforming can be used to improve signal quality and overcome path loss in these systems. Summary of the invention

[0003] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This overview is not an extensive review of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description presented later.

[0004] One aspect of the present disclosure provides a method for wireless communication at a user equipment (UE). The UE communicates with a network entity using a first beam set. The UE communicates with the network entity using a second beam set, the second beam set being predicted using a beam prediction model at least partially based on the first beam set. The UE reconfigures the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0005] One aspect of the present disclosure provides a user equipment (UE) for wireless communication. The UE includes a transceiver for communicating with a network entity, a memory, and a processor coupled to the transceiver and the memory. The processor and the memory are configured to communicate with the network entity using a first beam set. The processor and the memory are configured to communicate with the network entity using a second beam set, which is predicted at least in part based on the first beam set using a beam prediction model. The processor and the memory are configured to reconfigure the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0006] One aspect of the present disclosure provides a UE for wireless communication. The UE includes a component for communicating with a network entity using a first beam set. The UE also includes a component for communicating with the network entity using a second beam set, the second beam set being predicted at least in part based on the first beam set using a beam prediction model. The UE also includes a component for reconfiguring the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0007] One aspect of the present disclosure provides a computer-readable storage medium storing executable code for wireless communication. The executable code includes instructions for causing a UE to communicate with a network entity using a first beam set. The instructions also cause the UE to communicate with the network entity using a second beam set, the second beam set being predicted at least in part based on the first beam set using a beam prediction model. The instructions also cause the UE to reconfigure the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0008] One aspect of the present disclosure provides a method for wireless communication at a network entity. The network entity communicates with a UE using a first beam set. The network entity communicates with the UE using a second beam set, the second beam set being predicted using a beam prediction model at least partially based on the first beam set. The network entity reconfigures the beam prediction model in response to a change in a prediction condition, the prediction condition comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0009] One aspect of the present disclosure provides a network entity of a wireless communication network. The network entity includes a memory and a processor coupled to the memory. The processor and the memory are configured to communicate with a UE using a first beam set. The processor and the memory are also configured to communicate with the UE using a second beam set, which is predicted at least in part based on the first beam set using a beam prediction model. The processor and the memory are also configured to reconfigure the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0010] One aspect of the present disclosure provides a network entity of a wireless communication network. The network entity includes a component for communicating with a UE using a first beam set. The network entity also includes a component for communicating with the UE using a second beam set, the second beam set being predicted at least in part based on the first beam set using a beam prediction model. The network entity also includes a component for reconfiguring the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0011] One aspect of the present disclosure provides a computer-readable storage medium storing executable code for wireless communication. The executable code includes instructions for causing a network entity to communicate with a UE using a first beam set. The instructions also cause the network entity to communicate with the UE using a second beam set, which is predicted at least in part based on the first beam set using a beam prediction model. The instructions also cause the network entity to reconfigure the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0012] After reading the following specific embodiments, these and other aspects of the present invention will become more fully understood. After reading the following description of specific exemplary implementations in conjunction with the accompanying drawings, other aspects, features and specific implementations will become apparent to those of ordinary skill in the art. Although each feature may be discussed with respect to certain examples and drawings below, all specific implementations may include one or more advantageous features in the advantageous features discussed herein. In other words, although one or more specific implementations may be discussed as having certain advantageous features, one or more features in such features may also be used according to the various examples discussed herein. In a similar manner, although each example may be discussed as a device, system or method specific implementation below, it should be understood that such examples can be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a schematic diagram of a wireless communication system according to some aspects.

[0014] Figure 2 is an illustration of an example radio access network (RAN) in accordance with some aspects.

[0015] Figure 3 is a schematic diagram of an exemplary decomposed base station architecture.

[0016] Figure 4 is a schematic diagram of the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects.

[0017] Figure 5 is a block diagram illustrating a wireless communication system supporting Multiple-Input Multiple-Output (MIMO) communication.

[0018] Figure 6 is a diagram illustrating communication between a network entity and a UE using beamformed signals according to some aspects.

[0019] Figure 7 is a diagram illustrating example channel state information (CSI) resource mappings in accordance with some aspects.

[0020] Figure 8 is a signaling diagram illustrating exemplary signaling between wireless devices for providing channel state information feedback (CSF) within a wireless network in accordance with some aspects.

[0021] Fig. 9 is a block diagram illustrating a beam prediction model for beam prediction according to some aspects.

[0022] Fig.10 is a block diagram illustrating a specific implementation of beam prediction functionality for beam prediction according to some aspects.

[0023] Fig.11 is a diagram illustrating a first implementation of beam prediction at a network entity in accordance with some aspects.

[0024] Fig.12 is a diagram illustrating a second implementation of beam prediction at a user equipment (UE) in accordance with some aspects.

[0025] Fig.13 is a diagram illustrating a third implementation of beam prediction at both a network entity and a UE in accordance with some aspects.

[0026] Fig.14is a flow chart illustrating an example process for performing beam prediction in accordance with some aspects.

[0027] Fig.15 is a flow chart illustrating an exemplary process for determining a type of event that causes a mode switch of a beam prediction model in accordance with some aspects.

[0028] Fig.16 is a diagram illustrating an example of switching between modes of a beam prediction model based on a discontinuous reception (DRX) configuration in accordance with some aspects.

[0029] Fig.17 is a block diagram conceptually illustrating an example of a hardware implementation for user equipment in accordance with some aspects.

[0030] Fig.18 is a flow chart illustrating an example process for wireless communications using beam prediction at a UE in accordance with some aspects.

[0031] Fig.19 is a block diagram conceptually illustrating an example of a hardware implementation of a network entity according to some aspects of the present disclosure.

[0032] Fig. 20 is a flow chart illustrating an example process for wireless communications using beam prediction at a network entity in accordance with some aspects. DETAILED DESCRIPTION

[0033] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts may be practiced without these specific details. In some examples, in order to avoid obscuring such concepts, well-known structures and components are shown in block diagram form.

[0034] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many other arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, specific implementations and / or uses may occur via integrated chips and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. Specific implementations may have a range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovation. In some actual settings, the device incorporating the described aspects and features may also necessarily include additional components and features for the implementation and implementation of the examples claimed and described. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and UEs), end-user devices, etc.

[0035] Various aspects of the present disclosure disclose techniques and apparatus for beam prediction and configuration of a beam prediction module. In some aspects, a wireless device may be configured to use beamforming for wireless communication. However, one or more active beam pairs between two wireless devices may become misaligned, which may result in beam and / or communication failures. Therefore, improved beam management techniques may be required. In some scenarios, a wireless communication device may select one or more beams based on beam prediction or beam measurement. Beam prediction can reduce overhead and latency in wireless communications.

[0036] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as an illustrative example and not as a limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0037] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR, commonly referred to as Long Term Evolution (LTE), and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards. 3GPP refers to such a hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0038] As shown, RAN 104 includes multiple network entities (e.g., base station 108). In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a node B (NB), an evolved node B (eNB), a next generation node B (gNB), a transmit receive point (TRP), or some other suitable terminology by those skilled in the art. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands.

[0039] RAN 104 is also illustrated as supporting wireless communications for multiple mobile devices. In the 3GPP standards, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also refer to it as a mobile station (MS), a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be a device (e.g., a mobile device) that provides access to network services to a user.

[0040] In this document, a "mobile" device does not necessarily need to have the ability to move, and it can be stationary. The term mobile device or mobile device refers to a wide variety of devices and technologies. A UE may include a number of hardware structural components of a size, shape, and arrangement that facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide range of embedded systems, for example, corresponding to the "Internet of Things" (IoT). A mobile device may additionally be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc.). The mobile device may additionally be a digital home or smart home device, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. The mobile device may additionally be a smart energy device, security device, solar panel or solar array, municipal infrastructure equipment that controls power (e.g., smart grid), lighting, water, etc.; industrial automation and enterprise equipment; logistics controller; agricultural equipment, etc. Further, the mobile device may provide connected medicine or telemedicine support, such as health care at a distance. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or access over other types of information, for example, in terms of priority access for transmission of critical service data and / or associated QoS for transmission of critical service data.

[0041] Wireless communication between the RAN 104 and the UE 106 may be described as utilizing an air interface. Transmissions over the air interface from a network entity (e.g., a base station 108) to one or more UEs (e.g., a UE 106) may be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term "downlink" may refer to point-to-multipoint transmissions originating at a scheduling entity (described further below; e.g., a base station 108). Another way to describe this scheme may be to use the term "broadcast channel multiplexing." Transmissions from a UE (e.g., a UE 106) to a network entity (e.g., a base station 108) may be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term "uplink" may refer to point-to-point transmissions originating at a scheduled entity (described further below; e.g., a UE 106).

[0042] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communication between some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE 106 (which may be a scheduled entity) may utilize resources allocated by the scheduling entity 108.

[0043] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs).

[0044] like Figure 1 As shown, a network entity (e.g., a scheduling entity 108) may broadcast downlink traffic 112 to one or more scheduled entities 106. In a broad sense, a scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and (in some examples) uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, a scheduled entity 106 is a node or device that receives downlink control information 114 (including, but not limited to, scheduling information (e.g., grants), synchronization or timing information, or other control information) from another entity in the wireless communication network (such as the scheduling entity 108). The scheduled entity 106 may also send uplink control information 118 (including, but not limited to, scheduling requests or feedback information or other control information) to the scheduling entity 108.

[0045] In addition, uplink and / or downlink control information 114 and / or 118 and / or business information 112 and / or 116 may be sent on a waveform that may be divided into frames, subframes, time slots and / or symbols by time. As used herein, a symbol may refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. In the present disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes of 1 ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any suitable duration.

[0046] Generally speaking, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the base stations 108 and the core network 102. Furthermore, in some examples, the backhaul network may provide interconnections between the respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, or the like.

[0047] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other appropriate standard or configuration.

[0048] See now Figure 2 , a schematic diagram of a RAN 200 is provided by way of example and not limitation. In some examples, the RAN 200 may be similar to the RAN 200 described above and in Figure 1 The geographic area covered by the RAN 200 may be divided into cells that a user equipment (UE) may uniquely identify based on an identity broadcast from an access point or base station. Figure 2 Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with a UE in a portion of the cell.

[0049] Various base station arrangements can be used. Figure 2 , two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH 216 by a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a micro cell, a femto cell, a home base station, a home node B, a home evolved node B, etc.), because base station 218 supports a cell with a relatively small range. The cell size setting may be performed according to the system design and component constraints.

[0050] It should be understood that the radio access network 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The same as the base station / scheduling entity 108 illustrated in FIG.

[0051] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be a quadcopter or a drone. UAV 220 may be configured to function as a base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move based on the location of a mobile base station (such as a quadcopter 220).

[0052] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and Figure 1 The UE / scheduled entity 106 illustrated in FIG.

[0053] In some examples, UAV 220 (e.g., a quadcopter) can be configured to function as a UE. For example, UAV 220 can operate within cell 202 by communicating with base station 210.

[0054] In other aspects of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. Sidelink communications can be utilized in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other appropriate sidelink networks. For example, two or more UEs (e.g., UE 238, 240, and 242) can communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UE 238, 240, and 242 can each act as a scheduling entity or a transmitting sidelink device and / or a scheduled entity or a receiving sidelink device to schedule resources and communicate sidelink signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UE 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) can also communicate sidelink signals 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communications.

[0055] In some examples, a D2D relay framework may be included within a cellular network to facilitate relaying of communications to / from base station 212 via a D2D link (e.g., side link 227 or 237). For example, one or more UEs (e.g., UE 228) within the coverage area of ​​base station 212 may operate as relay UEs to extend the coverage of base station 212, improve transmission reliability to one or more UEs (e.g., UE 226), and / or allow the base station to recover from a failed UE link due to, for example, blocking or fading.

[0056] In RAN 200, the ability for a UE to communicate while moving (independent of its location) is called mobility. The various physical channels between the UE and the radio access network are typically managed by an access and mobility management function (AMF, not shown). Figure 1 The function may include a security context management function (SCMF) and a security anchor function (SEAF) for performing authentication. The SCMF may manage the security context for both the control plane functionality and the user plane functionality in whole or in part.

[0057] In various aspects of the present disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the UE's connection is switched from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, a UE 224 (illustrated as a vehicle, although any suitable form of UE may be used) may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighboring cell 206 exceeds the signal strength and quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message indicating this to its serving base station 210. In response, UE 224 may receive the handover command, and the UE may proceed with the handover to cell 206 .

[0058] In a network configured for UL-based mobility, the network can select a serving cell for each UE using a UL reference signal from each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UE222, 224, 226, 228, 230, and 232 can receive a unified synchronization signal, derive a carrier frequency and a time slot timing based on the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) can be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each of the cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) may determine a serving cell for the UE 224. As the UE 224 moves through the radio access network 200, the network may continue to monitor the uplink pilot signal sent by the UE 224. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength and quality measured by the serving cell, the network 200 may hand over the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0059] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or using the same timing. Using zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network, because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0060] In various specific implementations, the air interface in the RAN 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although some technical rules generally still need to be followed to access the unlicensed spectrum, generally any operator or device can obtain access. Shared spectrum may fall between licensed spectrum and unlicensed spectrum, where some technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0061] The air interface in the RAN 200 may utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex emulation is often implemented for wireless links using time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at certain times, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in another direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of transmitters and receivers and suitable interference cancellation techniques. Full-duplex emulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0062] In addition, the air interface in the RAN 200 can utilize one or more multiplexing and multiple access algorithms to achieve simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and can be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA) or other appropriate multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0063] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) performing base station functions) can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NRBS, a 5G NB, a gNB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0064] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CU), one or more distributed units (DU), or one or more radio units (RU). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, namely a virtual centralized unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0065] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0066] Figure 3 A diagram illustrating an example of a disaggregated base station 300 architecture is shown. The disaggregated base station 300 architecture may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units DU 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RU 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 312 via one or more radio frequency (RF) access links. In some implementations, a UE 312 may be served simultaneously by multiple RUs 340.

[0067] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. In addition, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0068] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0069] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as defined by 3GPP. In some aspects, DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0070] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 312. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0071] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. In addition, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0072] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0073] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0074] Will refer to Figure 4 Various aspects of the present disclosure are described using OFDM waveforms schematically illustrated in . It should be understood by those skilled in the art that various aspects of the present disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described herein below. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0075] See now Figure 4 , illustrates an expanded view of an exemplary subframe 402 showing an OFDM resource grid. However, as will be readily apparent to one skilled in the art, the PHY transmit structure for any particular application may differ from the example described herein, depending on any number of factors. Here, time is in units of OFDM symbols in the horizontal direction; and frequency is in units of subcarriers of a carrier in the vertical direction.

[0076] Resource grid 404 can be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding plurality of resource grids 404 can be available for communication. Resource grid 404 is divided into a plurality of resource elements (REs) 406. RE (which is 1 subcarrier×1 symbol) is the smallest discrete portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE can represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB), or more simply a resource block (RB) 408, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB (such as RB 408) corresponds entirely to communication in a single direction (transmission or reception for a given device).

[0077] A collection of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 406 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of a resource grid 404. In some examples, an RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a scheduling entity such as a base station (e.g., a gNB, eNB, etc.), or may be self-scheduled by a UE implementing D2D sidelink communication.

[0078] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers illustrated above and below RB 408. In a given implementation, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Furthermore, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, although this is only one possible example.

[0079] Each 1 ms subframe 402 may consist of one or more adjacent time slots. Figure 4In the example shown, as an illustrative example, a subframe 402 includes four time slots 410. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include micro-slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). These micro-slots or shortened transmission time intervals (TTIs) may be transmitted in some cases by occupying resources scheduled for ongoing time slot transmissions for the same UE or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0080] An expanded view of one of the time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. In general, the control region 412 may carry control channels, and the data region 414 may carry data channels. Of course, a time slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. Figure 4 The structures illustrated in are merely exemplary in nature and different slot structures may be utilized and include one or more of each control region or data region.

[0081] Although in Figure 4 408, but each RE 406 within the RB 408 may be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 406 within the RB 408 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of the control channel and / or data channel within the RB 408.

[0082] In some examples, time slot 410 may be used for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended receiving devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0083] In an example of cellular communication on a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 406 (e.g., within a control region 412) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (such as a physical downlink control channel (PDCCH)). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL ​​transmission and UL transmission. The PDCCH may also carry hybrid automatic repeat request (HARQ) feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those of ordinary skill in the art, in which the integrity of packet transmissions may be checked for accuracy at the receiving side, for example, using any appropriate integrity check mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if it is not confirmed, a NACK may be sent. In response to the NACK, the sending device may transmit a HARQ retransmission, which may implement trace combining, incremental redundancy, and the like.

[0084] The base station may also allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5ms, 10ms, 20ms, 40ms, 80ms, or 160ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may use the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0085] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB 1), which may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, grid offset, and search space for SIB 1. Examples of the remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also send other system information (OSI).

[0086] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 406 to a scheduling entity to carry UL control information (UCI) including one or more UL control channels, such as a physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include a sounding reference signal (SRS) and an uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request to a scheduling entity to schedule an uplink transmission. In this document, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other appropriate UCI.

[0087] In addition to control information, one or more REs 406 (e.g., within the data region 414) may also be allocated for data services. Such data services may be carried on one or more service channels, such as for DL ​​transmissions, on a physical downlink shared channel (PDSCH); or for UL transmissions, on a physical uplink shared channel (PUSCH). In some examples, one or more REs 406 within the data region 414 may be configured to carry other signals (such as one or more SIBs and DMRS). In some examples, the PDSCH may carry multiple SIBs, not limited to the SIB1 discussed above. For example, OSI may be provided in these SIBs (e.g., SIB2 and above SIBs).

[0088] In an example of sidelink communication on a sidelink carrier via a proximity service (ProSe) PC5 interface, a control region 412 of a time slot 410 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) toward a set of one or more other receiving sidelink devices (e.g., an Rx V2X device or other Rx UE). A data region 414 of the time slot 410 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by an initiating (transmitting) sidelink device in resources reserved by the transmitting sidelink device via the SCI on the sidelink carrier. Other information may also be sent via various REs 406 within the time slot 410. For example, HARQ feedback information may be sent from a receiving sidelink device to a transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 410. Additionally, one or more reference signals, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS), may be sent within time slot 410 .

[0089] These physical channels described above are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. The transport channels carry information blocks called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0090] Figure 4 The illustrated channels or carriers are not necessarily all channels or carriers that may be utilized between devices, and one of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those shown, such as other traffic, control, and feedback channels.

[0091] These physical channels described above are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. The transport channels carry information blocks called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0092] In some aspects of the present disclosure, a network entity (eg, a base station) and / or a scheduled entity (eg, a UE) may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 5An example of a wireless communication system 500 supporting MIMO is shown. In a MIMO system, a transmitter 502 includes multiple transmit antennas 504 (e.g., N transmit antennas), and a receiver 506 includes multiple receive antennas 508 (e.g., M receive antennas). Therefore, there are N×M signal paths 510 from the transmit antennas 504 to the receive antennas 508. Each of the transmitter 502 and the receiver 506 may be implemented, for example, within the scheduling entity 108, the scheduled entity 106, or any other suitable wireless communication device.

[0093] The use of such multi-antenna technology enables wireless communication systems to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously send different data streams (also referred to as layers) on the same time-frequency resources. These data streams can be sent to a single UE to increase the data rate or to multiple UEs to increase the total system capacity, the latter of which is called multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data stream by different weights and phase shifts) and then sending each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at UEs with different spatial characteristics, and the different spatial characteristics enable each UE in the UE to recover one or more data streams destined for the UE. On the uplink, each UE sends a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.

[0094] The number of data streams or layers corresponds to the rank of transmission. In general, the rank of the MIMO system 500 is limited to the lower of the number of transmit or receive antennas 504 or 508. In addition, the channel conditions at the UE and other considerations (such as the available resources at the base station) can also affect the transmission rank. For example, the rank assigned to a specific UE on the downlink (and therefore the number of data streams) can be determined based on a rank indicator (RI) sent from the UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit antennas and receive antennas) on each receive antenna in the receive antenna and the measured signal to interference and noise ratio (SINR). For example, the RI can indicate the number of layers that can be supported under the current channel conditions. The base station can use the RI and resource information (e.g., the available resources and amount of data to be scheduled for the UE) to assign the rank of transmission to the UE.

[0095] In a time division duplex (TDD) system, UL and DL are reciprocal because they each use different time slots of the same frequency bandwidth. Therefore, in a TDD system, the base station can allocate a rank for DL ​​MIMO transmission based on UL SINR measurements (e.g., based on a sounding reference signal (SRS) or other pilot signal sent from the UE). Based on the assigned rank, the base station can then send a CSI-RS with a separate C-RS sequence for each layer to provide multi-layer channel estimation. The UE can measure the channel quality across each layer and each resource block based on the CSI-RS, and feed back the RI and channel quality indicator (CQI) (which indicates to the base station the modulation and coding scheme (MCS) to be used for transmission to the UE) to the base station for updating the rank and allocating REs for future downlink transmissions.

[0096] In the simplest case, Figure 5 As shown in , rank 2 spatial multiplexing transmission on a 2x2 MIMO antenna configuration, one data stream is sent from each transmit antenna 504. Each data stream follows a different signal path 510 to each receive antenna 508. The receiver 506 can then use the received signal from each receive antenna 508 to reconstruct the data stream.

[0097] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0098] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4-a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0099] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0100] Beamforming is a signal processing technique that can be used at a transmitter 502 or a receiver 506 to shape or direct an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitter 502 and the receiver 506. Beamforming can be achieved by combining signals transmitted via antennas 504 or 508 (e.g., antenna elements of an antenna array module) so that some of the signals experience constructive interference and other signals experience destructive interference. In order to produce the desired constructive / destructive interference, the transmitter 502 or the receiver 506 may apply an amplitude and / or phase offset to the signal transmitted or received from each of the antennas 504 or 508 associated with the transmitter 502 or the receiver 506.

[0101] In 5G NR systems, especially for FR2 (millimeter wave) systems, beamformed signals can be used for most downlink channels, including PDCCH and PDSCH. In addition, broadcast control information (e.g., SSB, slot format indicator (SFI), and paging information) can be sent in a beam scanning manner so that all scheduled entities (UEs) in the coverage area of ​​the transmit and receive point (TRP) (e.g., gNB, base station) can receive the broadcast control information. In addition, for UEs configured with beamforming antenna arrays, beamformed signals can also be used for uplink channels (including PUCCH and PUSCH). In addition, beamformed signals can also be used in D2D systems (such as NR sidelink (SL) or V2X, which utilize FR2).

[0102] Figure 6 6 is a diagram illustrating communication between a network entity (eg, a base station 604) and a UE 602 using beamforming signals according to some aspects. The base station 604 may be Figure 1 , Figure 2 and / or Figure 3 Any of the base stations (e.g., gNBs), scheduling entities, or network entities illustrated in FIG. , and UE 602 may be Figure 1 , Figure 2 and / or Figure 3 Any of the UEs or scheduled entities illustrated in .

[0103] The base station 604 may generally be capable of communicating with the UE 602 using one or more transmit beams, and the UE 602 may further be capable of communicating with the base station 604 using one or more receive beams. As used herein, the term transmit beam refers to a beam on the base station 604 that may be used for downlink communication or uplink communication with the UE 602. Additionally, the term receive beam refers to a beam on the UE 602 that may be used for downlink communication or uplink communication with the base station 604.

[0104] exist Figure 6In the example shown, the base station 604 is configured to generate multiple transmit beams 606a-606h, each of which is associated with a different spatial direction. In addition, the UE 602 is configured to generate multiple receive beams 608a-608e, each of which is associated with a different spatial direction. It should be noted that although some beams are shown as being adjacent to each other, such an arrangement may be different in different aspects. For example, the transmit beams 606a-606h transmitted during the same symbol may not be adjacent to each other. In some examples, the base station 604 and the UE 602 may each transmit more or fewer beams distributed in all directions (e.g., 360 degrees) and in three dimensions. In addition, the transmit beams 606a-606h may include beams with varying beam widths. For example, the base station 604 may transmit certain signals (e.g., SSB) on a wider beam and other signals (e.g., CSI-RS) on a narrower beam.

[0105] The base station 604 and the UE 602 may use a beam management procedure to select one or more transmit beams 606a-606h on the base station 604 and one or more receive beams 608a-608e on the UE 602 for communicating uplink signals and downlink signals between the base station and the UE. In one example, during initial cell acquisition, the UE 602 may perform a P1 beam management procedure to scan the multiple transmit beams 606a-606h on the multiple receive beams 608a-608e to select a beam pair link (e.g., one of the transmit beams 606a-606h and one of the receive beams 608a-608e) for a physical random access channel (PRACH) procedure for initial access to the cell. For example, periodic SSB beam sweeping may be implemented at a specific interval (e.g., based on SSB periodicity) on the base station 604. Thus, the base station 604 may be configured to sweep or transmit an SSB on each of the plurality of wider transmit beams 606a-606h during a beam sweep interval. The UE may measure the reference signal received power (RSRP) of each SSB transmit beam on each receive beam of the UE and select transmit and receive beams based on the measured RSRP. In an example, the selected receive beam may be the receive beam on which the highest RSRP is measured, and the selected transmit beam may have the highest RSRP measured on the selected receive beam.

[0106] After completing the PRACH procedure, the base station 604 and the UE 602 may perform a P2 beam management procedure for beam refinement at the base station 604. For example, the base station 604 may be configured to sweep or transmit CSI-RS on each of a plurality of narrower transmit beams 606a-606h. Each of the narrower CSI-RS beams may be a sub-beam of a selected SSB transmit beam (e.g., within a spatial direction of the SSB transmit beam). Transmission of the CSI-RS transmit beam may occur periodically (e.g., as configured by the gNB via radio resource control (RRC) signaling), semi-persistently (e.g., as configured by the gNB via RRC signaling and activated / deactivated via medium access control-control element (MAC-CE) signaling), or aperiodically (e.g., as triggered by the gNB via downlink control information (DCI)). The UE 602 is configured to scan the multiple CSI-RS transmit beams 606a-606h across the multiple receive beams 608a-608e. The UE 602 then performs beam measurements (e.g., RSRP, SINR, etc.) on the CSI-RS received on each of the receive beams 608a-608e to determine the respective beam quality of each of the CSI-RS transmit beams 606a-606h, as measured on each of the receive beams 608a-608e.

[0107] The UE 602 may then generate and send a layer 1 (L1) measurement report to the base station 604 that includes a corresponding beam index (e.g., CSI-RS resource indicator (CRI)) and beam measurements (e.g., RSRP or SINR) for one or more of the CSI-RS transmit beams 606a-606h on one or more of the receive beams 608a-608e. The base station 604 may then select one or more CSI-RS transmit beams on which to communicate downlink and / or uplink control and / or data with the UE 602. In some examples, the selected CSI-RS transmit beam has the highest RSRP from the L1 measurement report. The sending of the L1 measurement report may occur periodically (e.g., as configured by the gNB via RRC signaling), semi-persistently (e.g., as configured by the gNB via RRC signaling and activated / deactivated via MAC-CE signaling), or aperiodically (e.g., triggered by the gNB via DCI).

[0108] The UE 602 may further select a corresponding receive beam on the UE 602 for each selected serving CSI-RS transmit beam to form a corresponding beam pair link (BPL) for each selected serving CSI-RS transmit beam. For example, the UE 602 may utilize beam measurements obtained during a P2 procedure or perform a P3 beam management procedure to obtain new beam measurements for the selected CSI-RS transmit beam to select a corresponding receive beam for each selected transmit beam. In some examples, the selected receive beam to be paired with a particular CSI-RS transmit beam may be the receive beam on which the highest RSRP is measured for the particular CSI-RS transmit beam.

[0109] In some examples, in addition to performing CSI-RS beam measurements, the base station 604 can configure the UE 602 to perform SSB beam measurements and provide an L1 measurement report containing beam measurements of the SSB transmit beams 606a-606h. For example, the base station 604 can configure the UE 602 to perform SSB beam measurements and / or CSI-RS beam measurements for beam failure detection (BRD), beam failure recovery (BFR), cell reselection, beam tracking (e.g., for mobile UE 602 and / or base station 604), or another beam optimization purpose.

[0110] In addition, when the channel is reciprocal, an uplink beam management scheme may be used to select transmit beams and receive beams. In an example, the UE 602 may be configured to sweep or transmit on each of the multiple receive beams 608a-608e. For example, the UE 602 may transmit an SRS on each beam in different beam directions. In addition, the base station 604 may be configured to receive uplink beam reference signals on multiple transmit beams 606a-606h. The base station 604 then performs beam measurements (e.g., RSRP, SINR, etc.) of the beam reference signals on each of the transmit beams 606a-606h to determine the corresponding beam quality of each of the receive beams 608a-608e as measured on each of the transmit beams 606a-606h.

[0111] The base station 604 may then select one or more transmit beams on which to communicate downlink and / or uplink control and / or data with the UE 602. In some examples, the selected transmit beam has the highest RSRP. The UE 602 may then select a corresponding receive beam for each selected serving transmit beam using, for example, the P3 beam management procedure as described above to form a corresponding beam pair link (BPL) for each selected serving transmit beam.

[0112] In one example, a single CSI-RS transmit beam (e.g., beam 606d) on the base station 604 and a single receive beam (e.g., beam 608c) on the UE may form a single BPL for communication between the base station 604 and the UE 602. In another example, multiple CSI-RS transmit beams (e.g., beams 606c, 606d, and 606e) on the base station 604 and a single receive beam (e.g., beam 608c) on the UE 602 may form respective BPLs for communication between the base station 604 and the UE 602. In another example, multiple CSI-RS transmit beams (e.g., beams 606c, 606d, and 606e) on the base station 604 and multiple receive beams (e.g., beams 608c and 608d) on the UE 602 may form multiple BPLs for communication between the base station 604 and the UE 602. In this example, a first BPL may include a transmit beam 606c and a receive beam 608c, a second BPL may include a transmit beam 608d and a receive beam 608c, and a third BPL may include a transmit beam 608e and a receive beam 608d.

[0113] In addition to the L1 measurement report, the UE 602 may further utilize the beam reference signal to estimate the channel quality of the channel between the network entity 604 and the UE 602. For example, the UE 602 may measure the SINR of each received CSI-RS and generate a CSI report based on the measured SINR. The CSI report may include, for example, a channel quality indicator (CQI), a rank indicator (RI), a precoding matrix indicator (PMI), and / or a layer indicator (LI). The network entity (e.g., a gNB) may use the CSI report to select a rank for the UE, along with a precoding matrix and an MCS for future downlink transmissions to the UE. The MCS may be selected from one or more MCS tables, each MCS table being associated with a particular type of coding (e.g., polar coding, LDPC, etc.) or modulation (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), 16 quadrature amplitude modulation (QAM), 64QAM, 256QAM, etc.). The LI may be used to indicate which column of the precoding matrix for the reported PMI corresponds to the strongest layer codeword corresponding to the reported maximum wideband CQI.

[0114] To distinguish between different types of reports (including CSI reports and L1 measurement reports) and different types of measurements, the network entity 604 can configure the UE 602 with one or more report settings. Each report setting can be associated with a reference signal configuration indicating a configuration of one or more reference signals (e.g., CSI-RS) used to generate a CSI report. In some examples, the report setting can be associated with a combined reference signal configuration.

[0115] Figure 7 An exemplary CSI resource mapping for supporting different reporting / measurement configurations is illustrated. The CSI resource mapping includes a CSI report setting 702, a CSI resource setting 704, a CSI resource set 706, and a CSI resource 708. Each CSI resource setting 704 includes one or more CSI resource sets 706, and each CSI resource set 706 includes one or more CSI resources 708. Figure 7 In the illustrated example, a single CSI resource setting (eg, CSI resource setting 0) is illustrated. However, it should be appreciated that any suitable number of CSI resource settings 704 may be supported.

[0116] Each CSI report setting 702 may include a reportQuantity, which indicates, for example, specific CSI parameters and their granularity to be included in the CSI report (e.g., wideband / subband CQI, PMI, RI, etc.) or L1 parameters (e.g., L1-RSRP, L1-SINR). The CSI report setting 702 may further indicate the periodicity of the CSI report. For example, the CSI report setting 702 may indicate that the report should be generated periodically, aperiodically, or semi-persistently. For an aperiodic CSI report setting, the CSI report may be transmitted on the PUSCH. For a periodic CSI report setting, the CSI report may be transmitted on the PUCCH. For a semi-persistent CSI report setting, the CSI report may be transmitted on the PUCCH or the PUSCH. For example, a medium access control (MAC) control element (MAC-CE) may be used to activate or deactivate a semi-persistent CSI report transmitted on the PUCCH. Semi-persistent CSI reporting transmitted on PUSCH may be triggered using downlink control information (DCI) scrambled with a semi-persistent CSI (SP-CP) radio network temporary identifier (SP-CP-RNTI).CSI reporting settings 702 may also include corresponding priorities and other suitable parameters.

[0117] Each CSI report setting 702 may be linked to a CSI resource setting 704. Each CSI resource setting 704 may be associated with a specific time domain behavior of a reference signal. For example, each CSI resource setting 704 may include periodic, semi-persistent, or aperiodic CSI resources 708. For periodic and semi-persistent CSI resource settings 704, the number of configured CSI resource sets 706 may be limited to one. In general, a CSI resource setting 704 that may be linked to a specific CSI report setting 702 may be limited by the time domain behavior of the CSI resource setting 704 and the CSI report setting 702. For example, an aperiodic CSI report setting 702 may be linked to a periodic, semi-persistent, or aperiodic CSI resource setting 704. However, a semi-persistent CSI report setting 702 may be linked to a periodic or semi-persistent CSI resource setting 704 only. In addition, a periodic CSI report setting 702 may be linked to a periodic CSI resource setting 704 only.

[0118] Each CSI resource set 706 may be associated with a CSI resource type. For example, a CSI resource type may include a non-zero power (NZP) CSI-RS resource, an SSB resource, or a channel state information interference measurement (CSI-IM) resource. Thus, the CSI resources 708 may include channel measurement resources (CMRs) such as NZP CSI-RS or SSB resources and / or interference measurement resources (IMRs) such as CSI-IM resources. Each CSI resource set 706 includes a list of CSI resources 708 of a particular CSI resource type. In addition, each CSI resource set 706 may be further associated with one or more of a frequency resource set (e.g., bandwidth and / or OFDM symbols within a time slot), a particular port set, power, or other suitable parameters.

[0119] Each CSI resource 708 indicates a specific beam (e.g., port), frequency resource, and OFDM symbol on which the wireless communication device can measure a reference signal. For example, each CSI-RS resource 708 can indicate an RE on which a CSI-RS pilot or SSB transmitted from a specific set of ports (e.g., on a specific beam) can be measured. Figure 7 In the example shown, CSI-RS resource set 0.1 includes four CSI-RS resources (CSI-RS resource 0.10, CSI-RS resource 0.11, CSI-RS resource 0.12, and CSI-RS resource 0.13). Each CSI resource 708 may be further indexed by a corresponding beam identifier (ID). The beam ID may not only identify a specific beam (e.g., a port), but may also identify a resource on which a reference signal may be measured. For example, the beam ID may include a CSI-RS source indicator (CRI) or an SSB source indicator (SSBRI).

[0120] The scheduling entity (e.g., network entity gNB) may configure the scheduled entity (e.g., UE) with one or more CSI reporting settings 702 and CSI resource settings 704 via, for example, radio resource control (RRC) signaling. For example, the scheduling entity may configure the scheduled entity with a list of periodic CSI reporting settings 702 indicating associated CSI resource sets 706 that the scheduled entity may use to generate periodic CSI reports. As another example, the scheduling entity may configure the scheduled entity with a list of aperiodic CSI reporting settings in CSI-AperiodicTriggerStateList. Each trigger state in CSI-AperiodicTriggerStateList may include a list of aperiodic CSI reporting settings 702 indicating associated CSI resource sets 706 for channel (and optionally for interference) measurements. As another example, the scheduling entity may configure the scheduled entity with a list of semi-persistent CSI reporting settings in CSI-SemiPersistentOnPUSCH-TriggerStateList. Each trigger state in CSI-SemiPersistentOnPUSCH-TriggerStateList may include one CSI reporting setting 702 indicating an associated CSI resource set 706. The scheduling entity may then use, for example, DCI to trigger one or more of the aperiodic trigger state or the semi-persistent trigger state. As indicated above, the MAC-CE may be used to activate or deactivate the semi-persistent CSI reporting setting 702 for CSI reports transmitted on the PUCCH.

[0121] For L1-RSRP measurement reporting, the scheduled entity may be configured with a CSI resource setting 704 having up to sixteen CSI resource sets 706. Each of the CSI resource sets 706 may include up to sixty-four CSI resources 708 in each set. The total number of different CSI resources 708 across all CSI resource sets 706 may not exceed 128. For L1-SINR measurement reporting, the scheduled entity may be configured with a CSI resource setting 704 that may include up to 64 CSI resources 708 (e.g., up to 64 CSI-RS resources or up to 64 SSB resources).

[0122] Figure 8 800 is a signaling diagram illustrating exemplary signaling 800 between a network entity 802 and a UE 804 for providing channel state information feedback (CSF) within a wireless network. In the illustrated scenario, the UE 804 may provide a CSI report to the network entity 802. The network entity 802 may correspond to, for example, Figure 1 , Figure 2 and / or Figure 3 The network entity 802 may be implemented as a converged base station or a decomposed base station. In a decomposed base station architecture, the network entity 802 may include one or more of a CU, a DU, or a RU. For example, the UE 804 may correspond to Figure 1 , Figure 2 and / or Figure 3 The UE or other scheduled node is shown.

[0123] At 806, the network entity 802 may send a reference signal, such as a DL-RS (e.g., CSI-RS, SSB) to the UE 804. In some examples, the reference signal may include multiple reference signals or a burst of reference signals. The reference signal may be sent via a corresponding channel measurement resource. The channel measurement resource may include a time-frequency resource in which a specific reference signal may be sent, and a beam direction. For example, the channel measurement resource may include a non-zero power (NZP) CSI-RS resource. The NZP resource may be used for channel measurement together with one or more interference measurement resources that can be used for interference measurement. The interference measurement resource may include a zero power (ZP) CSI-RS resource and an NZP CSI-RS resource having properties similar to those of the NZP CSI-RS resource used for channel measurement. In addition, each reference signal may include a number of pilots allocated within the corresponding channel measurement resource.

[0124] At 808, UE 804 may estimate the wireless channel based on the reference signals. For example, UE 804 may measure SINR and / or RSRP of one or more of the reference signals to obtain signal quality and / or channel estimation of the wireless channel.

[0125] At 810, UE 804 may determine various CSI values ​​based on signal quality and / or channel estimation. For example, UE 804 may determine RI, PMI and / or CQI based on channel estimation. CQI may include an index (e.g., CQI index) ranging from 0 to 15, for example. The CQI index may indicate, for example, the highest MCS at which the block error rate (BLER) of the channel does not exceed 10%. Once determined, the CSI value may be fed back. For example, at 812, UE 804 may send a CSI report including the determined signal quality and / or CSI value to network entity 802.

[0126] The network entity 802 and the UE 804 may each support different types of CSI reports (including L1 measurement reports) and / or different types of measurements. To distinguish between different report / measurement types and measurement configurations, the network entity 802 may configure the UE 804 with one or more report settings. Each report setting may be associated with a resource setting indicating a configuration of one or more reference signals (e.g., CSI-RS, SSB) used to generate a CSI report.

[0127] Beam Prediction

[0128] Various aspects of the present disclosure disclose techniques and apparatus for beam prediction and switching beam prediction modes. In some aspects, a UE may select one or more beams based on beam prediction, rather than simply selecting a beam based on beam measurements (e.g., RSRP of a reference signal (e.g., CSI-RS or SSB)). Beam prediction may be performed in the time domain and / or the spatial domain to reduce overhead and latency. Given past beam measurements (e.g., RSRP), future beam predictions may be affected by channel fading and noise, future UE locations, errors in prediction models, and the like. Therefore, predicting beam RSRP alone (e.g., average RSRP) may not be sufficient to make reliable beam predictions for future scheduling decisions.

[0129] In some aspects, the UE may predict the average beam RSRP and associated standard deviation (SD) of one or more beams based on past beam measurements (e.g., RSRP). The SD of the predicted RSRP may indicate the confidence level of the average RSRP prediction. For example, the SD information may indicate the level of prediction error and help the UE proactively avoid using poor beam predictions. Beam prediction with confidence indication (e.g., SD) may enable more reliable beam prediction and efficient beam measurement control. For example, the confidence indication enables the UE to proactively reject poor beam prediction results to achieve more accurate beam selection / prediction. Through beam prediction, the UE can reduce beam failures, achieve higher throughput, and reduce power consumption and reporting overhead.

[0130] Fig. 9 is a block diagram illustrating a beam prediction model 900 for beam prediction according to some aspects. In one aspect, the beam prediction model 900 may use a machine learning model (e.g., a neural network function (NNF)) to predict one or more beams or beam metrics for communication between a network entity and a UE. In one example, the beam prediction model 900 may be predefined in a communication standard (e.g., a 3GPP 5GNR specification) or based on a UE-specific implementation. In one aspect, the beam prediction model 900 may be configured to use one or more NNFs for beam prediction, and each configured NNF may be identified by an NNF ID. The input (X) parameters and output (Y) parameters of the beam prediction model 900 may be preconfigured for each NNF. Different NNFs may use different input and / or output parameters.

[0131] In some aspects, the beam prediction model 900 may be defined in terms of a model structure 902 and a parameter set 904. The model structure 902 may be identified by a unique model ID and associated with the NNF. Each model structure 902 has a default parameter set 904 that may include various parameters. For example, the parameter set 904 may include various parameters used by the model structure 902. For example, the parameter set 904 may include location and / or configuration specific machine learning parameters.

[0132] In one aspect, the input (X) of the beam prediction model 900 may be past measurements of a first beam set (beam set 1), and the output (Y) of the beam prediction model 900 may be a predicted beam metric (e.g., RSRP) of a second beam set (beam set 2). The beam prediction model 900 may perform beam prediction based on past beam measurements using a trained algorithm. For example, the algorithm may be a machine learning (ML) algorithm (e.g., a recursive neural network algorithm) or a non-learning algorithm. The algorithm may be trained and maintained by a network entity (e.g., a base station, gNB, CU, or DU). In some aspects, the beam prediction model or its associated NNF may be implemented at a network entity and / or a UE to predict one or more future beams or beam qualities. If the beam prediction model is implemented at a UE, the network entity may configure a specific beam prediction model used at the UE. In some aspects, the beam prediction model 900 may be implemented at both the network entity and the UE.

[0133] In some aspects, the input and output of the beam prediction model 900 may be associated with the same, overlapping, or completely different beam sets. In one example, the UE may measure a subset of SSB beams to predict all SSB beams to be used in the future. In one example, the UE may measure a coarse beam (e.g., an SSB beam) to predict a more refined or narrower beam (e.g., a CSI-RS beam) for unicast PDSCH / PDCCH transmission. In some examples, the beam prediction model 900 may be configured to output one or more beam indices and / or other related beam metrics for future times. Using beam prediction, the UE can reduce reference signal (RS) measurement overhead (e.g., RS does not need to be transmitted frequently to track beams / channels). The UE can also reduce the overhead of UL feedback because the UE can provide channel feedback or estimates less frequently. In addition, the UE can reduce power consumption because the UE can measure and feedback beam / channel quality less frequently.

[0134] Fig.101 is a block diagram illustrating a specific implementation of a neural network function (NNF) 1000 for beam prediction according to some aspects. In one example, the NNF 1000 may be implemented in the beam prediction model 900 (e.g., in the model structure 902). The NNF 1000 may output a predicted beam metric 1002 based at least in part on an input beam metric 1004. Examples of the input beam metric 1004 may include measured beam metrics (e.g., RSRP, received signal strength indication (RSSI) and / or SINR) of one or more beams. Examples of the output beam metric 1002 may include predicted beam metrics (e.g., RSRP, RSSI and / or SINR) of one or more beams, or one or more predicted beam indices. The NNF 1000 may include multiple input ports, and each input port may receive a beam metric associated with a particular beam. For example, each input port may be associated with an SSB resource, a CSI-RS resource, or a transmit configuration indicator (TCI) state. Each TCI state may include parameters for determining a quasi co-location (QCL) relationship between a downlink reference signal and a DM-RS port of a PDSCH, a DM-RS port of a PDCCH, or a CSI-RS port of a CSI-RS resource. The NNF 1000 may include multiple output ports for outputting predicted beam metrics 1002. Each output port may be associated with a TCI state of an SSB resource, a CSI-RS resource, or a predicted beam. In an example, the output port may provide a predicted beam metric including RSRPs and associated standard deviations for multiple SSBs (e.g., SSB IDs 1 to 10).

[0135] In some aspects, TCI states are configured for PDCCH, PDSCH, and CSI-RS in order to convey QCL indications to associated reference signals. A network entity (e.g., a base station) may configure the TCI state using RRC signaling and activate the configured TCI state by sending a MAC-CE command to the UE. TCI state changes and corresponding beam switching may be initiated via MAC-CE or DCI. When the TCI state for PDSCH is indicated by DCI, the TCI state change or associated beam switching may be configured via DCI. If the MAC-CE activation command includes only DL or joint TCI states and / or UL TCI states mapped to one TCI code point, the UE may apply the TCI state associated with the code point to the UE-specific PDSCH / PDCCH channel (e.g., 3 milliseconds (ms)) after the time slot containing the acknowledgment (ACK) of the MAC-CE command. Alternatively, the MAC-CE command may activate multiple TCI states corresponding to multiple TCI code points.

[0136] In some aspects, the DCI command may select a TCI code point from a plurality of TCI code points activated by the MAC-CE. The selected TCI code point may take effect after the first time slot after the beam application time counted from the last symbol containing the ACK for the DCI command. The DCI command may be applied to multiple component carriers (CCs) or bandwidth parts (BWPs). In this case, the first time slot when the TCI code point selection takes effect and the beam application time may be determined based on the configured BWP with the smallest subcarrier spacing (SCS) among all configured BWPs in the carrier to which the beam indication is applied. Alternatively, both the first time slot when the TCI code point selection takes effect and the beam application time may be determined based on the active BWP with the smallest SCS among all active BWPs in the carrier to which the beam indication is applied.

[0137] In some aspects, a list of CSI-RS and SRS resources may be configured for maximum permitted emission (MPE) candidate beam management. In some aspects, only periodic CSI-RS or SRS resources may be included in the list.

[0138] In some aspects, the UE may report the index of the capability value set associated with the TCI state or CSI-RS resource together with the measurement report (e.g., L1 RSRP or L1 SINR report). For example, the index of the capability value set may indicate the maximum number of SRS ports associated with the TCI state or RS resource. In such a report, the bit width of the index of the reported capability value set may be determined based on the UE capability report, such as the maximum capability number or the total number of capability indexes reported by the UE. For example, if the UE reports that up to 4 SRS ports can be supported based on the UE capability, a bit width of 2 bits can be used to report the index of the capability value set for the number of supported SRS ports, for example, "00" for 1 port, "01" for 2 ports, "10" for 3 ports, and "11" for 4 ports.

[0139] In some aspects, the NNF 1000 may optionally output a confidence indication 1006. The confidence indication 1006 may provide information for determining the likelihood or confidence that the predicted beam metric is correct or useful for predicting future beams. Examples of the confidence indication 1006 may include a standard deviation (SD) and variance of the predicted beam metric (e.g., RSRP and / or SINR), a confidence range for the predicted beam metric, and / or a probability of failure for the predicted beam metric.

[0140] In some aspects, the NNF 1000 may optionally consider supplemental information 1008 for beam prediction based on the input beam metrics 1004. The supplemental information 1008 may provide information for interpreting, qualifying, and / or modifying the input beam metrics. Examples of the supplemental information 1008 may include a timestamp of the beam metrics, a type of RSRP measurement (e.g., RSRP measured or interpolated), an expected error of the RSRP measurement (e.g., error due to interpolation or measurement), etc. In one example, the supplemental information 1008 may provide measurement mode information of the input metrics (e.g., beams measured in the past) to help the NNF 1000 evaluate a confidence level of the prediction.

[0141] Fig.11 1 is a diagram illustrating a first specific implementation of beam prediction at a network entity according to some aspects. In one example, a network entity 1102 (e.g., a base station or gNB) can be configured to use a beam prediction model to perform beam prediction for communicating with a UE 1104. For example, the network entity can use the above-mentioned Fig. 9 and Fig.10 Described beam prediction model 900. The network entity may configure the UE 1104 to provide UE feedback or information that may be used for beam prediction at the network entity.

[0142] At 1106, the UE may transmit UE feedback to the network entity. For example, the UE feedback may include a CSI report or a beam report on one or more beams. The report may provide various beam or channel quality information (e.g., RSRP, RSSI, and / or SINR) associated with the one or more beams. In some aspects, the UE 1104 may also send an SRS for UL channel measurement at the network entity to facilitate beam prediction.

[0143] At 1108, the network entity 1102 may use a beam prediction model to generate a beam prediction result based at least in part on UE feedback and / or SRS measurements. Running the beam prediction model on the network side allows power-constrained UEs (e.g., IoT devices) to benefit from using beam prediction because the power-constrained UEs may not have enough power and / or resources to run the beam prediction model. In some aspects, the beam prediction result may include predicted beam metrics (e.g., RSRP, RSSI, and / or SINR) of one or more beams that the UE may use to communicate with the network entity in the future. In some aspects, the beam prediction result may include a beam index of one or more beams that the UE may use in the future. In some aspects, the prediction result may also include a confidence indication (e.g., SD, variance, confidence range, probability of failure, etc.) about the predicted beam metric. At 1112, the UE may perform a beam management procedure based on the prediction result. Using beam prediction to select or change a beam, the UE can reduce the overhead involved in beam and RS measurements and reporting.

[0144] Fig.12 1 is a diagram illustrating a specific implementation of beam prediction at a UE according to some aspects. In one example, a UE 1202 may be configured to perform beam prediction using a beam prediction model. A network entity 1204 may configure the UE 1202 to use the beam prediction model to predict one or more future beams or corresponding beam measurements or metrics. For example, the UE 1202 may be configured to use the above-described beam prediction model. Fig. 9 and Fig.10 Beam prediction model 900 is described.

[0145] At 1206, the network entity 1204 may configure the UE 1202 to use a beam prediction model to predict one or more future beams for communication between the UE and the network entity 1204. For example, the beam prediction model may be based on a machine learning (ML) model, which may be a neural network function (e.g., NNF 1000). In one aspect, the network entity may transmit an RRC message, a MAC-CE, and / or a DCI to indicate the beam prediction model to the UE. The UE may be pre-configured with multiple beam prediction models, and the network entity may indicate one of the configured beam prediction models.

[0146] At 1208, the network entity 1204 may send one or more DL reference signals (e.g., SSB and / or CSI-RS) on one or more beams that may be measured by the UE for beam prediction using a beam prediction model. For example, the UE may measure RSRP, RSSI, and / or SINR of one or more beams carrying the DL reference signals. At 1210, the UE 1202 may use a beam prediction model (e.g., beam prediction model 900) configured or indicated by the network entity to generate a beam prediction result or metric based at least in part on the measurement of the DL reference signal 1208. In some aspects, the beam prediction model may take into account additional information (e.g., supplemental information 1008) to generate a beam prediction result. The additional information (e.g., interference from other UEs or cells) may include signal measurements available locally at the UE. The beam prediction result may include a predicted beam measurement or metric (e.g., RSRP, RSSI, and / or SINR) and / or one or more predicted beam indices.

[0147] At 1212, UE 1202 may transmit beam prediction results to network entity 1204. For example, the UE may transmit the beam prediction results in an UL report (e.g., a CSI report or a beam report) for one or more beams based on a report configuration or trigger condition configured by network entity 1204. In one aspect, the beam prediction results may include various beam or channel quality information (e.g., RSRP, RSSI, and / or SINR) associated with one or more beams that the UE may use to communicate with the network entity in the future. In some aspects, the beam prediction results may include beam indices of one or more beams that the UE may use in the future. In some aspects, beam prediction results 1212 may also include confidence indications about the prediction results (e.g., SD, variance, confidence range, probability of failure, etc.).

[0148] At 1214, UE 1202 may perform a beam management procedure based on the beam prediction results. Running the beam prediction model on the UE side may provide more measurement inputs to the beam prediction model that may not be available at the network entity. In addition, running the beam prediction model at the UE may reduce the UE overhead of transmitting CSI reports or beam reports, which may not be required when the UE can use the beam prediction model to predict future beam measurements or metrics.

[0149] Fig.13 1 is a diagram illustrating a specific implementation of beam prediction at both a UE and a network entity according to some aspects. In this example, the network entity 1302 and the UE 1304 can coordinate to use the same beam prediction model to predict one or more future beams or corresponding beam metrics. For example, the beam prediction model can be the same as described above with respect to Fig. 9 and Fig.10 Beam prediction model 900 is described.

[0150] At 1306, the network entity 1302 may configure the UE 1304 to use the same beam prediction model for future beam or beam measurement / metric predictions. In one example, the beam prediction model may be based on using a neural network function (e.g., Fig.10 In one aspect, the network entity transmits an RRC message, MAC-CE, and / or DCI to the UE to indicate the beam prediction model used for beam prediction. In some aspects, the UE may be configured with multiple beam prediction models, and the network entity may indicate which of these beam prediction models is used for beam prediction.

[0151] At 1308, the network entity 1302 may send one or more DL reference signals (e.g., SSB and / or CSI-RS) on one or more beams that may be measured by the UE for beam or beam measurement / metric prediction. For example, the UE may measure RSRP, RSSI, and / or SINR associated with one or more beams carrying the DL reference signals.

[0152] At 1310, UE 1304 may transmit UE feedback regarding the measured beams to the network entity. For example, the UE feedback may include an UL report (e.g., a CSI report or a beam report) on one or more beams. The report may provide various beam or channel quality information (e.g., RSRP, RSSI, and / or SINR) associated with the one or more beams. In some aspects, UE 1304 may also send a UL RS (e.g., an SRS) for UL channel measurement at the network entity to facilitate beam prediction.

[0153] At 1312, the network entity 1302 and the UE 1304 may run the same beam prediction model (e.g., beam prediction model 900) to generate beam prediction results based at least in part on measurements of DL reference signals 1308 on one or more beams. For example, the UE may generate the beam prediction results based on local measurements of the DL reference signals 1308, and the network entity 1302 may generate the prediction results based on UE feedback 1310 including the beam measurements. In one aspect, the beam prediction results may include various beam or channel quality information (e.g., RSRP, RSSI, and / or SINR) associated with one or more beams that the network entity and the UE may use in the future. In some aspects, the beam prediction results may include beam indices of one or more beams that may be used in the future. In some aspects, the beam prediction results may also include confidence indications about the prediction results (e.g., SD, variance, confidence range, probability of failure, etc.).

[0154] At 1314, the network entity 1302 synchronized with the UE 1304 may perform a beam management procedure based on the beam prediction results. Running the same beam prediction model at both the network entity and the UE may trigger synchronized beam configuration updates without further signaling between the network entity and the UE. For example, the beam prediction results may indicate a potential beam failure on one or more current beams in the future. In this case, the beam prediction results may trigger both the network entity and the UE to change to a new beam or beams at a predetermined time before the potential beam failure may occur.

[0155] In some aspects, a beam prediction model (e.g., beam prediction model 900) may be configured in different modes in various scenarios. In one aspect, when a UE uses a discontinuous reception (DRX) mode to reduce power consumption, the UE may change or reconfigure the beam prediction model to minimize the use of beam prediction, for example, in a DRX off period. In one aspect, the UE may change the beam prediction model due to changes in UE mobility. For example, a beam prediction model (e.g., NNF 1000) may be configured to use different parameters for beam prediction based on the speed and / or position of the UE. In one aspect, when beam prediction errors occur continuously or frequently, the network entity / UE may deactivate the beam prediction model and use other available beam management techniques (e.g., measurement-based beam management) for beam management. In one aspect, when the channel interference level rises, the beam prediction model may be configured to consider interference (e.g., SINR) during beam prediction.

[0156] Fig.14 1400 is a flow chart illustrating an exemplary process 1400 for performing beam prediction according to some aspects of the present disclosure. In some examples, process 1400 may be performed at a network entity and / or a UE. In some examples, process 1400 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0157] At 1402, a device (e.g., a UE or a network entity) may be configured to operate a beam prediction model in a first mode. For example, a network entity (e.g., a gNB) may configure the UE to operate the beam prediction model 900 in a first mode to predict one or more future beams and / or associated beam measurements / metrics. At 1404, the device may determine whether a beam prediction model mode switching event (hereinafter referred to as a "switching event") has occurred. Some examples of switching events may be a DRX mode change, a UE mobility change, a prediction error, an interference level change, etc. The device may determine a switching event when one or more of the above changes occurs. If the device determines that a switching event has not occurred, the device does not switch or change the mode of the beam prediction model. Conversely, at box 1406, the UE may switch or change the mode of the beam prediction model to a second mode in response to determining that a switching event has occurred.

[0158] Fig.15 1 is a flow chart illustrating an exemplary process 1500 for determining an event type that causes a mode switch of a beam prediction model according to some aspects of the present disclosure. In some examples, process 1500 may be performed by a network entity or UE as described herein. In some examples, process 1500 may be performed by any suitable device or component for performing the functions or algorithms described below. In one example, a device (e.g., a network entity or UE) has determined to change the mode of a beam prediction model used for beam prediction, as described above with respect to Fig.14 To this end, at 1502, the apparatus may determine a type of switching event that triggers a beam prediction model mode switch.

[0159] At 1504, a first type of switching event may result in activation or deactivation of a beam prediction model. When the beam prediction model is deactivated, the device (e.g., UE or network entity) may perform beam management using techniques based on beam measurements. In some aspects, deactivation / activation of the beam prediction model may be performed on a per-beam basis (i.e., partial activation / deactivation for a subset of active beams). For example, the UE may activate beam prediction models for one or more beams and deactivate beam prediction models for one or more different beams.

[0160] At 1506, the second type of event may change the configuration and / or parameters of the beam prediction model used for beam prediction. In one aspect, the device may use the same / different NNF (e.g., NNF 1000) for the beam prediction model, but use different input and / or output parameters (e.g., different input / beam parameters). In one aspect, the device may use different periodicities of beam and / or RS measurements as inputs to the beam prediction model (e.g., NNF) depending on the mobility level of the UE. For example, the UE may use a shorter periodicity for beam and / or RS measurements in a high mobility scenario (e.g., UE high speed movement) and a longer periodicity for beam and / or RS measurements in a low mobility scenario (e.g., UE stationary). In one aspect, when interference in the communication channel is significant, the device may include interference prediction (e.g., predicted SINR) in the output of the beam prediction model. When interference is negligible, a predicted beam metric (e.g., predicted beam RSRP) may be sufficient for beam prediction. In this case, the interference prediction information may not be included as an input parameter of the beam prediction model.

[0161] At 1508, a third type of event may change the periodicity of the beam prediction model. In one aspect, the device (e.g., a network entity or a UE) may operate the same beam prediction model (e.g., a trained ML model) with different periodicities in different scenarios. In one aspect, the UE may operate in a DRX off mode to reduce power consumption. The UE / network entity may operate the beam prediction model based on the DRX cycle of the UE. For example, the UE may use a longer periodicity for the beam prediction model during the DRX off period and a shorter periodicity during the DRX on period. During the DRX off period, beam prediction may be performed less frequently.

[0162] In some aspects, a network entity may explicitly configure a mode switch of a beam prediction model. For example, a network entity may activate, deactivate, or change the configuration of a beam prediction model via RRC, MAC-CE, and / or DCI signaling. In some aspects, a mode switch may be triggered autonomously or implicitly by a UE report / event. For example, a UE may send a report (e.g., a beam / CSI report) that may trigger one of the above-mentioned mode switching events. In one example, a determination of a large prediction error may cause the UE to autonomously deactivate, reconfigure, or change a beam prediction model (e.g., change an NNF, input parameters, and / or output parameters). In one example, the device may deactivate or change a beam prediction model during a DRX off cycle.

[0163] Forecast Error Events

[0164] In one aspect, the device may switch, reconfigure, or change (e.g., activate / deactivate) the mode of the beam prediction model when the beam prediction model outputs a prediction error that satisfies a predetermined condition. For example, the UE may transmit an UL report (e.g., a CSI report, a beam report, or an error report) indicating the prediction error. In one example, the UE may compare a predicted beam metric (e.g., a predicted RSRP) with a measured beam metric (e.g., a measured RSRP) to determine the prediction error. In response to a large prediction error, the network entity may configure the UE to deactivate the beam prediction model. In one aspect, after transmitting a report indicating a large prediction error, the UE may autonomously or implicitly (i.e., without receiving a command from the network entity) deactivate the beam prediction model. In one example, a predetermined condition (e.g., a large prediction error) may occur when the prediction error is greater than a predetermined threshold (e.g., an RSRP or RSSI error threshold) and / or when the prediction error occurs a predetermined number of times or more within a predetermined period of time (e.g., X or more errors within Y seconds).

[0165] Once the beam prediction model is disabled, the UE may use measurement-based techniques for beam management, e.g., as described above with respect to Figure 6 Described. After switching the mode of the beam prediction model, beam management-related reports and reference signal (RS) configurations may be changed or reconfigured. Depending on the mode of the beam prediction model, different beam reporting configurations may configure the UE to include different report content and / or use different reporting periodicities. In one example, when the beam prediction model is activated, the beam report may be configured to include predicted beam measurements / metrics, beam indexes, and / or prediction errors. When the beam prediction model is deactivated, the beam report may be configured to include measured beam metrics (e.g., RSRP, RSSI, and SINR). In addition, the beam reporting periodicity may be sparse in time when the beam prediction model is deactivated, relative to the more frequent beam reporting periodicity when the beam prediction model is activated.

[0166] When the beam prediction model is disabled, the UE may need to transmit UL reports (e.g., beam / CSI reports and / or error reports) more frequently when measurement-based techniques are used for beam management. When the beam prediction model is activated, the RS configuration may be configured to use a longer periodicity for DL ​​reference signals (e.g., SSB and CSI-RS), for example, to reduce measurement and reporting overhead at the UE. When the beam prediction model is disabled, the RS configuration may be configured to use a shorter periodicity to measure DL reference signals to facilitate beam management.

[0167] In some aspects, activation / deactivation of the beam prediction model may be performed on a per-beam basis. For example, the UE may report large prediction errors only for a subset of beams (or one or more outputs of the beam prediction model), and other beams (or outputs of the beam prediction model) do not have large prediction errors. In this case, a trigger event for switching the mode of the beam prediction model may be applied on the basis of each beam / prediction model output. In one example, a network entity may receive a report indicating large prediction errors for a subset of beams from a UE. The network entity may then deactivate the beam prediction model for the subset of beams. In this case, the beam prediction model is partially deactivated. In one example, the network entity may transmit a message (e.g., using RRC, MAC-CE, or DCI) to configure the UE to partially deactivate the beam prediction model. Since the beam prediction model is only partially deactivated, the UE / network entity may still use the beam prediction model for other beams / outputs that are not deactivated. The device may ignore the deactivated output of the beam prediction model. In some aspects, the UE may still monitor the disabled outputs of the partially disabled beam prediction models and determine and report the errors (if any) corresponding to those partially disabled beams / outputs. When the errors of the disabled beams / outputs are below a predetermined level, the network entity / UE may reactivate these outputs of the beam prediction models.

[0168] In some aspects, the UE may use different beam reporting configurations and / or RS configurations for activated beams / outputs and deactivated beams / outputs of a beam prediction model. In one example, the UE may transmit separate reports for activated beams and deactivated beams, respectively. For example, the report for the deactivated beam may include measured beam metrics (e.g., measured RSRP and SINR), and the report for the activated beam may include predicted beam metrics (e.g., predicted RSRP and SINR). In some aspects, the UE may transmit a single report for activated beams and deactivated beams of a beam prediction model. The single report may include measured beam metrics (e.g., measured RSRP, RSSI, SINR) for deactivated beams and predicted beam metrics (e.g., predicted RSRP, RSSI, SINR) for activated beams.

[0169] Events based on DRX configuration

[0170] Fig.1616 is a diagram illustrating an example of switching between modes of a beam prediction model based on a DRX configuration. In one aspect, a DRX cycle includes a DRX on period and a DRX off period. In the DRX off period, the UE monitors a DL control channel (e.g., PDCCH) for a predefined duration and then goes to sleep to reduce power consumption. The UE may switch between the DRX on period and the DRX off period according to the DRX configuration, which may specify the periodicity, duration, and cycle information of the DRX on and DRX off periods. For example, when the UE is in the first DRX off period 1602, the UE may deactivate the beam prediction model at 1604. When the UE deactivates the beam prediction model, the UE may stop transmitting prediction results (e.g., beam reports) and error reports to a network entity in the DRX off period. In some aspects, the UE may adjust the periodicity of prediction reports (e.g., beam reports and error reports) based on a DRX cycle (e.g., always on, micro sleep, deep sleep, etc.).

[0171] While the UE is still in the first DRX off period 1602, the UE may activate the beam prediction model at 1608 in anticipation of the upcoming DRX on period. In some aspects, the UE may activate the beam prediction model before switching from the DRX off period 1602 to the DRX on period 1606, so that the UE may perform beam prediction and reporting before entering the DRX on period. When the UE enters the second DRX off period 1610, the UE may deactivate the beam prediction model again at 1612. In some aspects, the UE may receive a wake-up signal 1613 from the network entity before the default or configured end time of the second DRX off period 1610. In this case, the UE may switch to the second DRX on period 1614 in advance and activate the beam prediction model at 1616.

[0172] Disturbance-based events

[0173] In some aspects, a baseline or default beam prediction model may be used to predict future beam metrics without considering potential interference from other beams, devices, network entities, and / or cells, as long as the interference level does not cause significant errors in the prediction results. When the interference level rises, the baseline beam prediction model may not provide reliable predictions. In some aspects, the UE may switch to measurement-based beam management (i.e., legacy mode). For example, the UE may measure and report interference information (e.g., L1 SINR) to illustrate interference during beam management.

[0174] In some aspects, interference is predictable for a specific time, area, and / or beam. In this case, the UE may switch the beam prediction model to an interference-aware beam prediction mode. For example, when the UE has interference statistics and / or historical information that helps the UE use a beam prediction model to predict interference, the network entity may configure the UE to enable interference-aware beam prediction. In one aspect, when the network entity receives an interference report from the UE, the network entity (e.g., gNB) may configure (e.g., via RRC, MAC-CE, DCI) the UE to switch the beam prediction model to an interference-aware mode. In one aspect, the UE may autonomously change the mode of the beam prediction model after transmitting an interference report that satisfies a predefined condition (e.g., the interference is greater than a predetermined threshold).

[0175] In some aspects, different beam reporting configurations and / or reference signal configurations may be configured depending on whether a device (e.g., a UE or a network entity) uses measurement-based beam management or interference-aware beam prediction. When the UE uses measurement-based beam management, the beam report may include measured beam metrics with interference information (e.g., L1-SINR). When the UE uses interference-aware beam prediction, the report may include predicted beam metrics (e.g., predicted L1-SINR) with predicted interference information and interference statistics. In some aspects, the network entity may send a specific reference signal (e.g., CSI-RS) for interference measurement when the UE uses measurement-based beam management, or as input to an interference-aware beam prediction model.

[0176] Fig.17 17 is a block diagram illustrating an example of a hardware implementation for a UE 1700 employing a processing system 1714. For example, the UE 1700 may be Figure 1 , Figure 2 , Figure 3 , Figure 6 , Figure 8 , Fig.11 , Fig.12 and / or Fig.13 A UE illustrated in any one or more of the .

[0177] The UE 1700 may be implemented using a processing system 1714 including one or more processors 1704. Examples of the processor 1704 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic, a discrete hardware circuit, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. In various examples, the UE 1700 may be configured to perform any one or more of the functions described herein. That is, the processor 1704 as utilized in the UE 1700 may be used to implement any one or more of the processes and procedures described and illustrated herein.

[0178] In some examples, processor 1704 may be implemented via a baseband or modem chip, and in other implementations, processor 1704 may include multiple devices distinct and different from a baseband or modem chip (e.g., in scenarios that may work together to implement the examples discussed herein). And as mentioned above, various hardware arrangements and components outside of a baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0179] In this example, the processing system 1714 may be implemented using a bus architecture (generally represented by bus 1702). The bus 1702 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1714 and the overall design constraints. The bus 1702 communicatively couples various circuits including one or more processors (generally represented by processor 1704), memory 1705, and computer-readable media (generally represented by computer-readable media 1706). The bus 1702 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. The bus interface 1708 provides an interface between the bus 1702 and the transceiver 1710. The transceiver 1710 provides a communication interface or component for communicating with various other devices through a transmission medium. Depending on the nature of the device, a user interface 1712 (e.g., a keypad, display, speaker, microphone, joystick, touch screen) may also be provided. Of course, such a user interface 1712 is optional and may be omitted in some examples (such as a base station).

[0180] The processor 1704 is responsible for managing the bus 1702 and general processing, which includes executing software stored on the computer-readable medium 1706. The software, when executed by the processor 1704, causes the processing system 1714 to perform the various functions described below for any particular device. The computer-readable medium 1706 and the memory 17105 can also be used to store data that is manipulated by the processor 1704 when executing the software.

[0181] One or more processors 1704 in the processing system can execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language or other. Software may reside on a computer-readable medium 1706. Computer-readable medium 1706 may be a non-transient computer-readable medium. By way of example, non-transient computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software, codes, and / or instructions that can be accessed and read by a computer. The computer readable medium 1706 may reside in the processing system 1714, be external to the processing system 1714, or be distributed across multiple entities including the processing system 1714. The computer readable medium 1706 may be embodied in a computer program product. By way of example, a computer program product may include a computer readable medium in packaging materials. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system.

[0182] In some aspects of the present disclosure, the processor 1704 may include circuits configured for various functions, including, for example, communication beam prediction using a beam prediction model. For example, the circuits may be configured to implement the present invention, for example, with respect to Figures 9 to 16 and Fig.18 One or more of the described functions.

[0183] In some aspects of the present disclosure, the processor 1704 may include a communication and processing circuit 1740 configured for various functions, including, for example, communicating with a network entity (e.g., a base station gNB). In some examples, the communication and processing circuit 1740 may include one or more hardware components that provide a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, the communication and processing circuit 1740 may include one or more transmit / receive chains. In addition, the communication and processing circuit 1740 may be configured to send and process uplink traffic and uplink control messages (e.g., similar to Figure 1 The communication and processing circuit 1740 may also be configured to execute communication and processing software 1750 stored on the computer-readable medium 1706 to implement one or more functions described herein.

[0184] In some implementations where the communication involves receiving information, the communication and processing circuit 1740 may obtain information from a component of the UE 1700 (e.g., from a transceiver 1710 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuit 1740 may output the information to another component of the processor 1704, to the memory 1705, or to the bus interface 1708. In some examples, the communication and processing circuit 1740 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 1740 may receive information via one or more channels. In some examples, the communication and processing circuit 1740 may include functionality for components for receiving. In some examples, the communication and processing circuit 1740 may include functionality for components for processing, including components for demodulation, components for decoding, and the like.

[0185] In some implementations where the communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1740 may obtain information (e.g., from another component of the processor 1704, the memory 1705, or the bus interface 1708), process (e.g., modulate, encode, etc.) the information, and output the processed information. For example, the communication and processing circuitry 1740 may output the information to the transceiver 1710 (e.g., which transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1740 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1740 may transmit information via one or more channels. In some examples, the communication and processing circuitry 1740 may include functionality for components for transmitting (e.g., components for sending). In some examples, the communication and processing circuitry 1740 may include functionality for components for generating, including components for modulating, components for encoding, and the like.

[0186] In some aspects of the present disclosure, the processor 1704 may include a beam prediction circuit 1742 configured for various functions, including, for example, beam prediction using a beam prediction model having different modes. In one aspect, the beam prediction circuit 1742 may be configured to switch between different modes of a beam prediction model (e.g., beam prediction model 900) used for beam prediction. For example, the beam prediction circuit 1742 may be configured to switch between different modes of a beam prediction model (e.g., beam prediction model 900) used for beam prediction. Figures 9 to 16 The described past beam measurements / metrics are used to predict future beams and / or interference metrics (e.g., RSRP, RSSI, SINR) of the beam set. The beam prediction circuit 1742 can be configured to switch between different modes of the beam prediction model in response to changes in beam prediction conditions, including, for example, a discontinuous reception (DRX) mode of the UE, changes in UE mobility, prediction errors of the beam prediction model, and / or interference levels.

[0187] In some aspects, the beam prediction circuit 1742 can be configured to activate or deactivate the beam prediction model, reconfigure the beam prediction model from a first mode to a second mode, and / or change the periodicity of operating the beam prediction model. The beam prediction circuit 1742 can also be configured to execute the beam prediction software 1752 stored on the computer-readable medium 1706 to implement one or more functions described herein.

[0188] Fig.181800 is a flow chart illustrating an exemplary process 1800 for wireless communication using beam prediction according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for all example implementations. In some examples, process 1800 may be performed by Fig.17 In some examples, process 1800 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0189] At block 1802, the UE may communicate with a network entity (e.g., a base station, a gNB, or a CU / DU) using a first beam set. In one aspect, the communication and processing circuitry 1740 may provide means for communicating with the network entity via the transceiver 1710. The first beam set may include one or more beams / BPLs (e.g., beams 606a-606h and 608a-608e).

[0190] At block 1804, the UE may communicate with a network entity using a second beam set that is predicted based at least in part on the first beam set using a beam prediction model. In one aspect, the beam prediction circuit 1742 may provide means for predicting the second beam set. The first beam set and the second beam set may have the same beams, overlap in some beams, or have completely different beams. In one aspect, the beam prediction circuit 1742 may implement the beam prediction model using software, hardware, or a combination of both. In one example, the beam prediction model may be similar to the one described with respect to Fig. 9 and Fig.10 Beam prediction model 900 is described.

[0191] At block 1806, the UE may reconfigure or change the beam prediction model in response to a change in a prediction condition, the prediction condition comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level. The beam prediction circuit 1742 may provide a component for determining a change in the prediction condition. In one aspect, changing the beam prediction model may activate or deactivate the beam prediction model. In one aspect, changing the beam prediction model may reconfigure the beam prediction model from a first mode to a second mode. The first mode and the second mode may differ in a prediction function configured to predict one or more future beams or beam metrics. The first mode and the second mode may differ in at least one input parameter of the beam prediction model (e.g., measured beam metrics, supplemental information). The first mode and the second mode may differ in at least one output parameter of the beam prediction model (e.g., predicted beam metrics, confidence indication). In one aspect, changing the beam prediction model may change the periodicity of operating the beam prediction model.

[0192] In one aspect, the UE may initiate a change in the beam prediction model based on a command from a network entity in response to a change in the prediction condition. In one aspect, the UE may autonomously initiate a change in the beam prediction model in response to a change in the prediction condition. In one aspect, the UE may deactivate the beam prediction model in response to a beam prediction error being greater than a predetermined threshold. In one aspect, the UE may deactivate the beam prediction model in response to the UE being in a DRX off mode, and activate the beam prediction model in response to the UE being in a DRX off mode. In one aspect, the UE may activate the beam prediction model in response to receiving a wake-up signal in the DRX off mode. In one aspect, when the interference level is greater than a predetermined threshold, the UE may change the beam prediction model to an interference-aware mode. In one aspect, the UE may change the beam prediction model to a mode based on beam measurements in response to an interference level greater than a predetermined threshold. In one aspect, the UE may change the beam prediction model to a mode based on beam measurements in response to a change in UE mobility. In one aspect, the UE may change the beam prediction model on a per-beam basis. In one aspect, changing the beam prediction model may include changing a beam reporting configuration and / or a reference signal configuration.

[0193] In one configuration, the UE 1700 includes means for switching between different modes of a beam prediction model for wireless communication. In one aspect, the aforementioned means may be Fig.17 The processor 1704 shown in the figure is configured to perform the functions described by the aforementioned components. On the other hand, the aforementioned components can be a circuit or any device configured to perform the functions described by the aforementioned components.

[0194] Of course, in the above examples, the circuits included in the processor 1704 are provided only as examples, and other components for performing the functions may be included in various aspects of the present disclosure, including but not limited to storage in the computer-readable storage medium 1706, or in the computer-readable storage medium 1706. Figure 1 , Figure 2 , Figure 3 , Figure 6 , Figure 8 , Fig.11 , Fig.12 and / or Fig.13 In any other suitable device or component described in any of the above and using, for example, Figures 9 to 16 and / or Fig.18 Instructions (eg, executable code) of the described processes and / or algorithms.

[0195] Fig.191904 is a conceptual diagram illustrating an example of a hardware implementation of an exemplary network entity 1900 employing a processing system 1914. According to various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1914 including one or more processors 1904. For example, the network entity 1900 may be such as Figure 1 , Figure 2 , Figure 3 , Figure 6 , Figure 8 , Fig.11 , Fig.12 and / or Fig.13 The network entity 1900 may also be implemented in an aggregated or monolithic base station architecture, or in a decomposed base station architecture, and may include one or more of a CU, a DU, a RU, a near-RT RAN RIC, or a non-RT RIC.

[0196] Processing system 1914 can be used with Fig.17 The illustrated processing system 1714 is substantially the same, including a bus interface 1908, a bus 1902, a memory 1905, a processor 1904, and a computer-readable medium 1906. In addition, the network entity 1900 may include the same as described above in Fig.17 That is, the processor 1904 as utilized in the network entity 1900 may be used to implement the methods described herein and in, for example, Figure 9-Figure 16 and Fig. 20 Any one or more of the processes illustrated in .

[0197] In some aspects of the present disclosure, the processor 1704 may include circuits configured for various functions, including, for example, communication beam prediction using a beam prediction model. For example, the circuits may be configured to implement the present invention, for example, with respect to Figures 9 to 16 and Fig. 20 One or more of the described functions.

[0198] In some aspects of the present disclosure, processor 1904 may include communication and processing circuitry 1940 configured for various functions, including, for example, communicating with a UE or a scheduled entity. In some examples, communication and processing circuitry 1940 may include one or more hardware components that provide a physical structure that performs processes associated with wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, communication and processing circuitry 1940 may include one or more transmit / receive chains. In addition, communication and processing circuitry 1940 may be configured to receive and process uplink traffic and uplink control messages (e.g., similar to Figure 1 The communication and processing circuit 1940 may also be configured to execute communication and processing software 1950 stored on the computer-readable medium 1706 to implement one or more functions described herein.

[0199] In some implementations where the communication involves receiving information, the communication and processing circuitry 1940 may obtain information from a component of the network entity 1900 (e.g., from a transceiver 1910 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuitry 1940 may output the information to another component of the processor 1904, to the memory 1905, or to the bus interface 1908. In some examples, the communication and processing circuitry 1940 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1940 may receive information via one or more channels. In some examples, the communication and processing circuitry 1940 may include functionality for components for receiving. In some examples, the communication and processing circuitry 1940 may include functionality for components for processing, including components for demodulating, components for decoding, and the like.

[0200] In some implementations where the communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1940 may obtain information (e.g., from another component of the processor 1904, the memory 1905, or the bus interface 1908), process (e.g., modulate, encode, etc.) the information, and output the processed information. For example, the communication and processing circuitry 1940 may output the information to the transceiver 1910 (e.g., which transmits the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1940 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1940 may transmit information via one or more channels. In some examples, the communication and processing circuitry 1940 may include functionality for components for transmitting (e.g., components for sending). In some examples, the communication and processing circuitry 1940 may include functionality for components for generating, including components for modulating, components for encoding, and the like.

[0201] In some aspects of the present disclosure, the processor 1904 may include a beam prediction circuit 1942 configured for various functions, including, for example, performing beam prediction using different beam prediction models or modes. In one aspect, the beam prediction circuit 1942 may be configured to perform beam prediction using a beam prediction model (e.g., the beam prediction model 900). For example, the beam prediction circuit 1942 may be based on the beam prediction model described above. Figures 9 to 16 The beam prediction circuit 1942 may be configured to switch between different modes of the beam prediction model in response to changes in beam prediction conditions, including one or more of the DRX mode of the UE, changes in UE mobility, prediction errors of the beam prediction model, and interference levels.

[0202] In some aspects, the beam prediction circuit 1942 can be configured to activate or deactivate the beam prediction model, reconfigure the beam prediction model from a first mode to a second mode, and / or change the periodicity of operating the beam prediction model. The beam prediction circuit 1942 can also be configured to execute the beam prediction software 1952 stored on the computer-readable medium 1906 to implement one or more functions described herein.

[0203] Fig. 20is a flow chart illustrating an exemplary process 2000 for wireless communication using beam prediction according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for all example implementations. In some examples, process 2000 may be performed by Fig.19 The process 2000 is performed by the network entity 1900 illustrated in FIG. In some examples, the process 2000 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0204] At block 2002, a network entity may communicate with a UE using a first beam set. In one aspect, the communication and processing circuit 2040 may provide means for communicating with the UE directly or via another network entity. The first beam set may include one or more beams / BPLs (e.g., beams 606a-606h and 608a-608e).

[0205] At block 2004, the network entity may communicate with the UE using a second beam set that is predicted based at least in part on the first beam set using a beam prediction model. In one aspect, the beam prediction circuit 1942 may provide means for predicting the second beam set. The first beam set and the second beam set may have the same beams, overlap in some beams, or have completely different beams. In one aspect, the beam prediction circuit 1942 may implement the beam prediction model using software, hardware, or a combination of both. In one example, the beam prediction model may be similar to the one described with respect to Fig. 9 and Fig.10 Beam prediction model 900 is described.

[0206] At block 2006, the network entity may change or reconfigure the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level. The beam prediction circuit 1942 may provide a component for determining a change in the prediction condition. In one aspect, changing the beam prediction model may activate or deactivate the beam prediction model. In one aspect, changing the beam prediction model may reconfigure the beam prediction model from a first mode to a second mode. The first mode and the second mode may differ in a prediction function configured to predict one or more future beams or beam metrics. The first mode and the second mode may differ in at least one input parameter of the beam prediction model (e.g., measured beam metrics, supplemental information). The first mode and the second mode may differ in at least one output parameter of the beam prediction model (e.g., predicted beam metrics, confidence indication). In one aspect, changing the beam prediction model may change the periodicity of operating the beam prediction model.

[0207] In one aspect, the network entity may initiate a change in the beam prediction model by transmitting a command to the UE in response to a change in the prediction condition. In one aspect, the network entity may initiate a change in the beam prediction model synchronously with the UE in response to a change in the prediction condition. In one aspect, the network entity may deactivate the beam prediction model in response to a beam prediction error being greater than a predetermined threshold. In one aspect, the network entity may deactivate the beam prediction model in response to the UE being in a DRX off mode, and activate the beam prediction model in response to the UE being in a DRX off mode. In one aspect, when the interference level is greater than a predetermined threshold, the network entity may change the beam prediction model to an interference-aware mode. In one aspect, the network entity may change the beam prediction model to a mode based on beam measurements in response to an interference level being greater than a predetermined threshold. In one aspect, the network entity may change the beam prediction model to a mode based on beam measurements in response to a change in UE mobility. In one aspect, the network entity may change the beam prediction model on a per-beam basis. In one aspect, changing the beam prediction model may include changing a beam reporting configuration and / or a reference signal configuration.

[0208] In one configuration, the network entity 1900 includes means for switching between different modes of a beam prediction model for wireless communication. In one aspect, the aforementioned means may be Fig.19 The processor 1904 shown in the figure is configured to perform the functions described by the aforementioned components. On the other hand, the aforementioned components can be a circuit or any device configured to perform the functions described by the aforementioned components.

[0209] Of course, in the above examples, the circuits included in the processor 1904 are provided only as examples, and other components for performing the functions may be included in various aspects of the present disclosure, including but not limited to those stored in the computer-readable storage medium 1906 or in the computer-readable storage medium 1906. Figure 1 , Figure 2 , Figure 3 , Figure 6 , Figure 8 , Fig.11 , Fig.12 and / or Fig.13 In any other suitable device or component described in any of the above and using, for example, Figures 9 to 16 and / or Fig. 20 Instructions (eg, executable code) of the described processes and / or algorithms.

[0210] In a first aspect, a method of wireless communication at a user equipment (UE) is provided. The method includes: communicating with a network entity using a first beam set; communicating with the network entity using a second beam set, the second beam set being predicted using a beam prediction model at least partially based on the first beam set; and reconfiguring the beam prediction model in response to a change in a prediction condition, the prediction condition comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0211] In a second aspect, either alone or in combination with the first aspect, reconfiguring the beam prediction model comprises at least one of: activating or deactivating the beam prediction model; changing the beam prediction model from a first mode to a second mode; or changing the periodicity of operating the beam prediction model.

[0212] In a third aspect, either alone or in combination with the second aspect, the first mode and the second mode differ in at least one of: a prediction function configured to predict one or more beams; at least one input parameter of the beam prediction model; or at least one output parameter of the beam prediction model.

[0213] In a fourth aspect, alone or in combination with any one of the first to third aspects, reconfiguring the beam prediction model includes: initiating reconfiguration of the beam prediction model based on a command from the network entity in response to the change in the prediction condition.

[0214] In a fifth aspect, either alone or in combination with any one of aspects 1 to 3, reconfiguring the beam prediction model comprises autonomously initiating reconfiguration of the beam prediction model in response to transmitting a report to the network entity, the report indicating the change in the prediction condition.

[0215] In a sixth aspect, alone or in combination with any one of the first to third aspects, reconfiguring the beam prediction model comprises: deactivating the beam prediction model in response to a beam prediction error being greater than a predetermined threshold.

[0216] In the seventh aspect, alone or in combination with any one of the first to third aspects, reconfiguring the beam prediction model includes: deactivating the beam prediction model in response to the UE being in DRX off mode; and activating the beam prediction model in response to the UE being in DRX off mode.

[0217] In an eighth aspect, alone or in combination with the seventh aspect, reconfiguring the beam prediction model further comprises: activating the beam prediction model in response to receiving a wake-up signal in a DRX off mode.

[0218] In a ninth aspect, alone or in combination with any one of the first to third aspects, reconfiguring the beam prediction model comprises: when the interference level is greater than a predetermined threshold, changing the beam prediction model to an interference-aware mode.

[0219] In a tenth aspect, alone or in combination with any one of the first to third aspects, reconfiguring the beam prediction model comprises: changing the beam prediction model to a beam measurement-based mode in response to the interference level being greater than a predetermined threshold.

[0220] In an eleventh aspect, alone or in combination with any one of the first to third aspects, reconfiguring the beam prediction model comprises: changing the beam prediction model to a mode based on beam measurement in response to the change in the UE mobility.

[0221] In a twelfth aspect, alone or in combination with any one of the first to third aspects, reconfiguring the beam prediction model comprises: changing the beam prediction model on a per-beam basis.

[0222] In the thirteenth aspect, alone or in combination with any one of the first to third aspects, reconfiguring the beam prediction model includes at least one of the following: selecting a beam reporting configuration from a plurality of beam reporting configurations that differ in at least one aspect of report content or report periodicity; or selecting a reference signal configuration from a plurality of reference signal configurations that differ in reference signal periodicity.

[0223] In a fourteenth aspect, a user equipment (UE) for wireless communication is provided. The UE includes: a transceiver for communicating with a network entity; a processor; and a memory coupled to the processor, the memory including instructions executable by the processor to enable the UE to: communicate with the network entity using a first beam set; communicate with the network entity using a second beam set, the second beam set being predicted using a beam prediction model at least partially based on the first beam set; and reconfigure the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0224] In the fifteenth aspect, alone or in combination with the fourteenth aspect, wherein, in order to reconfigure the beam prediction model, the instruction also causes the UE to perform at least one of the following operations: activating or deactivating the beam prediction model; changing the beam prediction model from a first mode to a second mode; or changing the periodicity of operating the beam prediction model.

[0225] In the sixteenth aspect, alone or in combination with the fifteenth aspect, the first mode and the second mode differ in at least one of: a prediction function configured to predict one or more beams; at least one input parameter of the beam prediction model; or at least one output parameter of the beam prediction model.

[0226] In the seventh aspect, alone or in combination with any one of aspects 14 to 16, wherein, in order to reconfigure the beam prediction model, the instruction also causes the UE to: initiate reconfiguration of the beam prediction model based on a command from the network entity in response to the change in the prediction condition.

[0227] In the eighteenth aspect, alone or in combination with any one of aspects from the fourteenth to the sixteenth aspect, wherein, in order to reconfigure the beam prediction model, the instruction also causes the UE to: autonomously initiate reconfiguration of the beam prediction model in response to transmitting a report to the network entity, wherein the report indicates the change in the prediction condition.

[0228] In the nineteenth aspect, alone or in combination with any one of the fourteenth to sixteenth aspects, wherein, in order to reconfigure the beam prediction model, the instruction also causes the UE to: deactivate the beam prediction model in response to a beam prediction error being greater than a predetermined threshold.

[0229] In the twentieth aspect, alone or in combination with any one of the fourteenth to sixteenth aspects, wherein, in order to reconfigure the beam prediction model, the instruction also causes the UE to: deactivate the beam prediction model in response to the UE being in a DRX off mode; and activate the beam prediction model in response to the UE being in a DRX off mode.

[0230] In the twenty-first aspect, alone or in combination with the twentieth aspect, wherein, in order to reconfigure the beam prediction model, the instruction further causes the UE to: activate the beam prediction model in response to receiving a wake-up signal in the DRX off mode.

[0231] In aspect twenty-second, alone or in combination with any one of aspects fourteen to sixteen, wherein, in order to reconfigure the beam prediction model, the instruction also causes the UE to: change the beam prediction model to an interference-aware mode when the interference level is greater than a predetermined threshold.

[0232] In aspect twenty-third, alone or in combination with any one of aspects fourteen to sixteen, wherein, in order to reconfigure the beam prediction model, the instruction also causes the UE to: change the beam prediction model to a beam measurement-based mode in response to the interference level being greater than a predetermined threshold.

[0233] In aspect twenty-four, alone or in combination with any one of aspects fourteen to sixteen, wherein, in order to reconfigure the beam prediction model, the instruction also causes the UE to: change the beam prediction model to a mode based on beam measurement in response to the change in the UE mobility.

[0234] In the twenty-fifth aspect, alone or in combination with any one of the fourteenth to sixteenth aspects, wherein, in order to reconfigure the beam prediction model, the instruction further causes the UE to: change the beam prediction model on a per-beam basis.

[0235] In aspect twenty-six, alone or in combination with any one of aspects fourteen to sixteen, wherein, in order to reconfigure the beam prediction model, the instruction also causes the UE to perform at least one of the following operations: selecting a beam reporting configuration from multiple beam reporting configurations that differ in at least one aspect of the reporting content or the reporting periodicity; or selecting a reference signal configuration from multiple reference signal configurations that differ in the reference signal periodicity.

[0236] In a twenty-seventh aspect, a user equipment (UE) for wireless communication is provided. The UE includes: means for communicating with a network entity using a first beam set; means for communicating with the network entity using a second beam set, the second beam set being predicted using a beam prediction model at least partially based on the first beam set; and means for reconfiguring the beam prediction model in response to a change in a prediction condition, the prediction condition comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0237] In a twenty-eighth aspect, a computer-readable storage medium storing executable code for wireless communication is provided. The executable code includes instructions for causing a user equipment (UE) to: communicate with a network entity using a first beam set; communicate with the network entity using a second beam set, the second beam set being predicted using a beam prediction model at least partially based on the first beam set; and reconfigure the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0238] In a twenty-ninth aspect, a method for wireless communication at a network entity is provided. The method includes: communicating with a user equipment (UE) using a first beam set; communicating with the UE using a second beam set, the second beam set being predicted using a beam prediction model at least partially based on the first beam set; and reconfiguring the beam prediction model in response to a change in a prediction condition, the prediction condition comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0239] In the thirtieth aspect, alone or in combination with the twenty-ninth aspect, reconfiguring the beam prediction model includes at least one of the following: activating or deactivating the beam prediction model; changing the beam prediction model from a first mode to a second mode; or changing the periodicity of operating the beam prediction model.

[0240] In the thirty-first aspect, alone or in combination with the thirtieth aspect, the first mode and the second mode differ in at least one of: a prediction function configured to predict one or more beams; at least one input parameter of the beam prediction model; or at least one output parameter of the beam prediction model.

[0241] In aspect 32, alone or in combination with any one of aspects 29 to 31, reconfiguring the beam prediction model includes: transmitting a command for initiating reconfiguration of the beam prediction model in response to a report from the UE, the report indicating the change in the prediction condition.

[0242] In aspect 33, alone or in combination with any one of aspects 29 to 31, reconfiguring the beam prediction model comprises: changing the beam prediction model synchronously with the UE in response to the change in the prediction condition.

[0243] In aspect 34, either alone or in combination with any one of aspects 29 to 31, reconfiguring the beam prediction model comprises deactivating the beam prediction model in response to a beam prediction error being greater than a predetermined threshold.

[0244] In aspect 35, alone or in combination with any one of aspects 29 to 31, reconfiguring the beam prediction model includes: deactivating the beam prediction model in response to the UE being in DRX off mode; and activating the beam prediction model in response to the UE being in DRX off mode.

[0245] In the thirty-sixth aspect, alone or in combination with the thirty-fifth aspect, reconfiguring the beam prediction model further comprises: transmitting a wake-up signal to activate the beam prediction model at the UE in the DRX off mode.

[0246] In aspect 37, alone or in combination with any one of aspects 29 to 31, reconfiguring the beam prediction model comprises changing the beam prediction model to an interference-aware mode when the interference level is greater than a predetermined threshold.

[0247] In aspect 38, either alone or in combination with any one of aspects 29 to 31, reconfiguring the beam prediction model comprises changing the beam prediction model to a beam measurement-based mode in response to the interference level being greater than a predetermined threshold.

[0248] In aspect thirty-ninth, alone or in combination with any one of aspects twenty-ninth to thirty-first, reconfiguring the beam prediction model comprises: changing the beam prediction model to a mode based on beam measurement in response to the change in the UE mobility.

[0249] In the 40th aspect, alone or in combination with any one of the 29th to 31st aspects, reconfiguring the beam prediction model includes: changing the beam prediction model on a per-beam basis.

[0250] In the forty-first aspect, alone or in combination with any one of aspects 29 to 31, reconfiguring the beam prediction model includes at least one of the following: selecting a beam reporting configuration from a plurality of beam reporting configurations that differ in at least one aspect of report content or report periodicity; or selecting a reference signal configuration from a plurality of reference signal configurations that differ in reference signal periodicity.

[0251] In a 42nd aspect, a network entity of a wireless communication network is provided. The network entity includes: a processor; and a memory coupled to the processor, the memory including instructions executable by the processor to enable the network entity to: communicate with a user equipment (UE) using a first beam set; communicate with the UE using a second beam set, the second beam set being predicted using a beam prediction model at least partially based on the first beam set; and reconfigure the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0252] In the forty-third aspect, alone or in combination with the forty-second aspect, wherein, in order to reconfigure the beam prediction model, the instruction also causes the network entity to perform at least one of the following operations: activating or deactivating the beam prediction model; changing the beam prediction model from a first mode to a second mode; or changing the periodicity of operating the beam prediction model.

[0253] In a 44th aspect, alone or in combination with the 43rd aspect, the first mode and the second mode differ in at least one of: a prediction function configured to predict one or more beams; at least one input parameter of the beam prediction model; or at least one output parameter of the beam prediction model.

[0254] In aspect 45, alone or in combination with any one of aspects 42 to 44, wherein, in order to reconfigure the beam prediction model, the instruction also causes the network entity to: transmit a command for initiating reconfiguration of the beam prediction model in response to a report from the UE, the report indicating the change in the prediction condition.

[0255] In aspect 46, alone or in combination with any one of aspects 42 to 44, wherein, in order to reconfigure the beam prediction model, the instruction also causes the network entity to: change the beam prediction model synchronously with the UE in response to the change in the prediction condition.

[0256] In aspect 47, either alone or in combination with any one of aspects 42 to 44, wherein, in order to reconfigure the beam prediction model, the instruction further causes the network entity to: deactivate the beam prediction model in response to a beam prediction error being greater than a predetermined threshold.

[0257] In aspect 48, alone or in combination with any one of aspects 42 to 44, wherein, in order to reconfigure the beam prediction model, the instruction also causes the network entity to: deactivate the beam prediction model in response to the UE being in DRX off mode; and activate the beam prediction model in response to the UE being in DRX off mode.

[0258] In a 49th aspect, either alone or in combination with the 48th aspect, wherein, in order to reconfigure the beam prediction model, the instruction further causes the network entity to: transmit a wake-up signal to activate the beam prediction model at the UE in the DRX off mode.

[0259] In the fiftieth aspect, alone or in combination with any one of aspects 42 to 44, wherein, in order to reconfigure the beam prediction model, the instruction also causes the network entity to: change the beam prediction model to an interference-aware mode when the interference level is greater than a predetermined threshold.

[0260] In the fifty-first aspect, alone or in combination with any one of aspects 42 to 44, wherein, in order to reconfigure the beam prediction model, the instruction also causes the network entity to: change the beam prediction model to a beam measurement-based mode in response to the interference level being greater than a predetermined threshold.

[0261] In aspect 52, alone or in combination with any one of aspects 42 to 44, wherein, in order to reconfigure the beam prediction model, the instruction also causes the network entity to: change the beam prediction model to a beam measurement-based mode in response to the change in the UE mobility.

[0262] In aspect 53, either alone or in combination with any one of aspects 42 to 44, wherein, in order to reconfigure the beam prediction model, the instructions further cause the network entity to: change the beam prediction model on a per-beam basis.

[0263] In aspect 54, alone or in combination with any one of aspects 42 to 44, wherein, in order to reconfigure the beam prediction model, the instruction also causes the network entity to perform at least one of the following: select a beam reporting configuration from multiple beam reporting configurations that differ in at least one aspect of report content or report periodicity; or select a reference signal configuration from multiple reference signal configurations that differ in reference signal periodicity.

[0264] In a fifty-fifth aspect, a network entity of a wireless communication network is provided. The network entity includes: a component for communicating with a user equipment (UE) using a first beam set; a component for communicating with the UE using a second beam set, the second beam set being predicted using a beam prediction model at least partially based on the first beam set; and a component for reconfiguring the beam prediction model in response to a change in a prediction condition, the prediction condition comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0265] In a fifty-sixth aspect, a computer-readable storage medium storing executable code for wireless communication is provided. The executable code includes instructions for causing a network entity to: communicate with a user equipment (UE) using a first beam set; communicate with the UE using a second beam set, the second beam set being predicted using a beam prediction model at least partially based on the first beam set; and reconfigure the beam prediction model in response to a change in a prediction condition, the prediction condition including at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

[0266] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

[0267] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0268] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages, or modes of operation. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly, and are intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation as to the type of electronic circuits) and software implementations of information and instructions (where these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure).

[0269] Figures 1 to 20 One or more of the illustrated components, steps, features, and / or functions may be rearranged and / or combined into a single component, step, feature, or function or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1 to 20 The apparatus, devices and / or components illustrated in the examples may be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.

[0270] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged based on design preferences. The attached method claims provide elements of various steps in an exemplary order, but are not intended to be limited to the specific order or hierarchy provided unless explicitly stated herein.

[0271] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the text of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. The phrase "at least one" referring to a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, regardless of whether such disclosures are explicitly cited in the claims, any content disclosed herein is not intended to be disclosed to the public.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: communicating with a network entity using a first beam set; communicating with the network entity using a second set of beams, the second set of beams predicted based at least in part on the first set of beams using a beam prediction model; as well as The beam prediction model is reconfigured in response to a change in prediction conditions, the prediction conditions comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

2. The method of claim 1 , wherein reconfiguring the beam prediction model comprises at least one of: activating or deactivating the beam prediction model; changing the beam prediction model from a first mode to a second mode; or Changing the periodicity with which the beam prediction model is operated.

3. The method of claim 2, wherein the first mode and the second mode differ in at least one of the following aspects: a prediction function configured to predict one or more beams; at least one input parameter of the beam prediction model; or At least one output parameter of the beam prediction model.

4. The method of claim 1 , wherein reconfiguring the beam prediction model comprises: Reconfiguration of the beam prediction model is initiated based on a command from the network entity in response to the change in the prediction condition.

5. The method of claim 1 , wherein reconfiguring the beam prediction model comprises: Reconfiguration of the beam prediction model is autonomously initiated in response to transmitting a report to the network entity, the report indicating the change in the prediction condition.

6. The method of claim 1 , wherein reconfiguring the beam prediction model comprises: The beam prediction model is deactivated in response to a beam prediction error being greater than a predetermined threshold.

7. The method of claim 1 , wherein reconfiguring the beam prediction model comprises: deactivating the beam prediction model in response to the UE being in a DRX off mode; as well as The beam prediction model is activated in response to the UE being in a DRX off mode.

8. The method of claim 7, wherein reconfiguring the beam prediction model further comprises: The beam prediction model is activated in response to receiving a wake-up signal in the DRX off mode.

9. The method of claim 1 , wherein reconfiguring the beam prediction model comprises: When the interference level is greater than a predetermined threshold, the beam prediction model is changed to an interference-aware mode.

10. The method of claim 1, wherein reconfiguring the beam prediction model comprises: The beam prediction model is changed to a beam measurement based mode in response to the interference level being greater than a predetermined threshold.

11. The method of claim 1 , wherein reconfiguring the beam prediction model comprises: The beam prediction model is changed to a mode based on beam measurements in response to the change in the UE mobility.

12. The method of claim 1 , wherein reconfiguring the beam prediction model comprises: The beam prediction model is varied on a per-beam basis.

13. The method of claim 1 , wherein reconfiguring the beam prediction model comprises at least one of: selecting a beam reporting configuration from among a plurality of beam reporting configurations that differ in at least one of report content or report periodicity; or A reference signal configuration is selected among a plurality of reference signal configurations that differ in reference signal periodicity.

14. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: a transceiver for communicating with a network entity; processor; as well as a memory coupled to the processor; The memory includes instructions executable by the processor to cause the UE to: communicating with the network entity using a first beam set; communicating with the network entity using a second set of beams, the second set of beams predicted based at least in part on the first set of beams using a beam prediction model; as well as The beam prediction model is reconfigured in response to a change in prediction conditions, the prediction conditions comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

15. The UE according to claim 14, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to perform at least one of the following operations: activating or deactivating the beam prediction model; changing the beam prediction model from a first mode to a second mode; or Changing the periodicity with which the beam prediction model is operated.

16. The UE of claim 15, wherein the first mode and the second mode are different in at least one of the following aspects: a prediction function configured to predict one or more beams; at least one input parameter of the beam prediction model; or At least one output parameter of the beam prediction model.

17. The UE according to claim 14, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to: Reconfiguration of the beam prediction model is initiated based on a command from the network entity in response to the change in the prediction condition.

18. The UE according to claim 14, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to: Reconfiguration of the beam prediction model is autonomously initiated in response to transmitting a report to the network entity, the report indicating the change in the prediction condition.

19. The UE according to claim 14, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to: The beam prediction model is deactivated in response to a beam prediction error being greater than a predetermined threshold.

20. The UE according to claim 14, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to: deactivating the beam prediction model in response to the UE being in a DRX off mode; and The beam prediction model is activated in response to the UE being in a DRX off mode.

21. The UE according to claim 20, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to: The beam prediction model is activated in response to receiving a wake-up signal in the DRX off mode.

22. The UE according to claim 14, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to: When the interference level is greater than a predetermined threshold, the beam prediction model is changed to an interference-aware mode.

23. The UE according to claim 14, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to: The beam prediction model is changed to a beam measurement based mode in response to the interference level being greater than a predetermined threshold.

24. The UE according to claim 14, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to: The beam prediction model is changed to a mode based on beam measurements in response to the change in the UE mobility.

25. The UE according to claim 14, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to: The beam prediction model is varied on a per-beam basis.

26. The UE according to claim 14, wherein: To reconfigure the beam prediction model, the instructions further cause the UE to perform at least one of the following operations: selecting a beam reporting configuration from among a plurality of beam reporting configurations that differ in at least one of report content or report periodicity; or A reference signal configuration is selected among a plurality of reference signal configurations that differ in reference signal periodicity.

27. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: means for communicating with a network entity using a first beam set; means for communicating with the network entity using a second set of beams predicted based at least in part on the first set of beams using a beam prediction model; as well as Means for reconfiguring the beam prediction model in response to a change in prediction conditions, the prediction conditions comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

28. A computer-readable storage medium storing executable code for wireless communication, the executable code comprising instructions for causing a user equipment (UE) to: communicating with a network entity using a first beam set; communicating with the network entity using a second set of beams, the second set of beams predicted based at least in part on the first set of beams using a beam prediction model; and The beam prediction model is reconfigured in response to a change in prediction conditions, the prediction conditions comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

29. A method for wireless communication at a network entity, the method comprising: communicating with a user equipment (UE) using a first beam set; communicating with the UE using a second beam set predicted based at least in part on the first beam set using a beam prediction model; as well as The beam prediction model is reconfigured in response to a change in prediction conditions, the prediction conditions comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

30. The method of claim 29, wherein reconfiguring the beam prediction model comprises at least one of: activating or deactivating the beam prediction model; changing the beam prediction model from a first mode to a second mode; or Changing the periodicity with which the beam prediction model is operated.

31. The method of claim 30, wherein the first mode and the second mode differ in at least one of the following aspects: a prediction function configured to predict one or more beams; at least one input parameter of the beam prediction model; or At least one output parameter of the beam prediction model.

32. The method of claim 29, wherein reconfiguring the beam prediction model comprises: A command for initiating reconfiguration of the beam prediction model is transmitted in response to a report from the UE, the report indicating the change in the prediction condition.

33. The method of claim 29, wherein reconfiguring the beam prediction model comprises: The beam prediction model is changed synchronously with the UE in response to the change in the prediction condition.

34. The method of claim 29, wherein reconfiguring the beam prediction model comprises: The beam prediction model is deactivated in response to a beam prediction error being greater than a predetermined threshold.

35. The method of claim 29, wherein reconfiguring the beam prediction model comprises: deactivating the beam prediction model in response to the UE being in a DRX off mode; as well as The beam prediction model is activated in response to the UE being in a DRX off mode.

36. The method of claim 35, wherein reconfiguring the beam prediction model further comprises: A wake-up signal is transmitted to activate the beam prediction model at the UE in the DRX off mode.

37. The method of claim 29, wherein reconfiguring the beam prediction model comprises: When the interference level is greater than a predetermined threshold, the beam prediction model is changed to an interference-aware mode.

38. The method of claim 29, wherein reconfiguring the beam prediction model comprises: The beam prediction model is changed to a beam measurement based mode in response to the interference level being greater than a predetermined threshold.

39. The method of claim 29, wherein reconfiguring the beam prediction model comprises: The beam prediction model is changed to a mode based on beam measurements in response to the change in the UE mobility.

40. The method of claim 29, wherein reconfiguring the beam prediction model comprises: The beam prediction model is varied on a per-beam basis.

41. The method of claim 29, wherein reconfiguring the beam prediction model comprises at least one of: selecting a beam reporting configuration from among a plurality of beam reporting configurations that differ in at least one of report content or report periodicity; or A reference signal configuration is selected among a plurality of reference signal configurations that differ in reference signal periodicity.

42. A network entity of a wireless communication network, the network entity comprising: processor; as well as A memory coupled to the processor, the memory comprising instructions executable by the processor to cause the network entity to: communicating with a user equipment (UE) using a first beam set; communicating with the UE using a second beam set predicted based at least in part on the first beam set using a beam prediction model; as well as The beam prediction model is reconfigured in response to a change in prediction conditions, the prediction conditions comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

43. The network entity according to claim 42, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to perform at least one of the following: activating or deactivating the beam prediction model; changing the beam prediction model from a first mode to a second mode; or Changing the periodicity with which the beam prediction model is operated.

44. The network entity of claim 43, wherein the first mode and the second mode differ in at least one of the following aspects: a prediction function configured to predict one or more beams; at least one input parameter of the beam prediction model; or At least one output parameter of the beam prediction model.

45. The network entity according to claim 42, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to: A command for initiating reconfiguration of the beam prediction model is transmitted in response to a report from the UE, the report indicating the change in the prediction condition.

46. ​​The network entity of claim 42, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to: The beam prediction model is changed synchronously with the UE in response to the change in the prediction condition.

47. The network entity according to claim 42, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to: The beam prediction model is deactivated in response to a beam prediction error being greater than a predetermined threshold.

48. The network entity of claim 42, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to: deactivating the beam prediction model in response to the UE being in a DRX off mode; and The beam prediction model is activated in response to the UE being in a DRX off mode.

49. The network entity according to claim 48, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to: A wake-up signal is transmitted to activate the beam prediction model at the UE in the DRX off mode.

50. The network entity of claim 42, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to: When the interference level is greater than a predetermined threshold, the beam prediction model is changed to an interference-aware mode.

51. The network entity of claim 42, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to: The beam prediction model is changed to a beam measurement based mode in response to the interference level being greater than a predetermined threshold.

52. The network entity of claim 42, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to: The beam prediction model is changed to a mode based on beam measurements in response to the change in the UE mobility.

53. The network entity of claim 42, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to: The beam prediction model is varied on a per-beam basis.

54. The network entity of claim 42, wherein: To reconfigure the beam prediction model, the instructions further cause the network entity to perform at least one of the following: selecting a beam reporting configuration from among a plurality of beam reporting configurations that differ in at least one of report content or report periodicity; or A reference signal configuration is selected among a plurality of reference signal configurations that differ in reference signal periodicity.

55. A network entity of a wireless communication network, the network entity comprising: means for communicating with a user equipment (UE) using a first beam set; means for communicating with the UE using a second set of beams, the second set of beams predicted based at least in part on the first set of beams using a beam prediction model; as well as Means for reconfiguring the beam prediction model in response to a change in prediction conditions, the prediction conditions comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

56. A computer-readable storage medium storing executable code for wireless communication, the executable code comprising instructions for causing a network entity to: communicating with a user equipment (UE) using a first beam set; communicating with the UE using a second beam set predicted based at least in part on the first beam set using a beam prediction model; and The beam prediction model is reconfigured in response to a change in prediction conditions, the prediction conditions comprising at least one of a discontinuous reception (DRX) mode of the UE, a change in UE mobility, a prediction error of the beam prediction model, or an interference level.

Citation Information

Cited By

  • Communication method and device, communication chip, storage medium and computer program product

    CN120475508A

  • Communication method and apparatus, communication chip, storage medium and computer program product

    CN120475508B

  • System condition prediction

    WO2026118207A1

  • Associated id and reference signal identification for beam prediction aided beam failure detection and radio link monitoring

    WO2026170427A1