Model selection and switching

Abstract

Certain aspects of the present disclosure provide techniques for model selection and switching. In some aspects, a user equipment (UE) may perform a compressed communication between the UE and a network entity using a first model, determine a condition based at least in part on channel state information, send an identifier associated with a second model to the network entity based at least in part on the condition, and perform a compressed communication between the UE and the network entity using the second model. And performing compressed communication between the UE and the network entity using the second model. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to PCT patent application No. PCT / CN2022 / 123108, entitled “MODEL SELECTION AND SWITCHING”, filed on September 30, 2022 and assigned to the assignee of this application. The disclosure of the prior application is considered part of this patent application and is incorporated into this patent application by reference. background Technical Field

[0004] Aspects of the present disclosure relate to wireless communications, and more particularly to techniques for selecting and switching between models for compressing communications.

[0005] Related technical description

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with those users.

[0007] Although wireless communication systems have made tremendous technical progress over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continued desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need to further improve wireless communication systems to overcome the above-mentioned technical challenges and other challenges. Summary of the invention

[0008] One aspect provides a method for wireless communication by a user equipment (UE). The method includes performing compressed communication between the UE and a network entity using a first model; determining a condition based at least in part on channel state information; sending an identifier associated with a second model to the network entity based at least in part on the condition; and performing compressed communication between the UE and the network entity using the second model.

[0009] Another aspect provides a method for wireless communication by a network entity. The method includes performing compressed communication between the network entity and a UE using a first network entity model; receiving from the UE an identifier associated with a UE model for compressed communication between the UE and the network entity; determining compatibility information associated with the UE model and each of a plurality of network entity models; and performing compressed communication between the network entity and the UE using a second network entity model based at least in part on the compatibility information.

[0010] One aspect provides a method for wireless communication by a UE. The method includes determining a state based at least in part on channel state information; sending a state identifier associated with the state or one or more model identifiers associated with one or more models, respectively, to a network entity; receiving a switching indication from the network entity indicating whether to switch from a first model to a second model; and performing compressed communication with the network entity using the first model or the second model based at least in part on the switching indication.

[0011] Another aspect provides a method for wireless communication by a network entity. The method includes receiving from a UE a situation identifier associated with a situation or one or more UE model identifiers respectively associated with one or more UE models for compressed communication between the UE and the network entity; obtaining an indication of whether to switch from a first network entity model to a second network entity model based at least in part on the situation identifier or the one or more UE model identifiers; and selectively sending a switching indication to the UE, the switching indication including an identifier associated with the UE model corresponding to the second network entity model.

[0012] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform any one or more of the foregoing methods and / or those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those described elsewhere herein; a computer program product embodied on a computer-readable storage medium, comprising code for performing the foregoing methods and those described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating through one or more networks.

[0013] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings depict certain features of the various aspects described herein and should not be considered to limit the scope of the disclosure.

[0015] Figure 1 An example wireless communication network is depicted.

[0016] Figure 2 An example disaggregated base station architecture is depicted.

[0017] Figure 3 Aspects of an example base station and an example user equipment (UE) are depicted.

[0018] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures for a wireless communication network are described.

[0019] Figure 5 Depicts the physical channels and reference signals in wireless networks.

[0020] Figure 6 Depicts a machine learning model.

[0021] Figure 7 A process flow for communication in a network between a UE and a network entity is depicted.

[0022] Figure 8 A process flow for communication in a network between a UE and a network entity is depicted.

[0023] Fig. 9 A method for wireless communication is described.

[0024] Fig.10 A method for wireless communication is described.

[0025] Fig.11 A method for wireless communication is described.

[0026] Fig.12 A method for wireless communication is described.

[0027] Fig.13 Aspects of an example communications device are depicted.

[0028] Fig.14 Aspects of an example communications device are depicted. DETAILED DESCRIPTION

[0029] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for selecting and switching between models for compressing communications.

[0030] User equipment (UE) and network entity (NE) can communicate using artificial intelligence (AI) models and / or machine learning (ML) models. AI / ML models can be used to communicate compressed information between UE and network entity, such as compressed information associated with channel conditions or reference signal measurements. UE and network entity can be configured with different models or different variants of models. The UE side model may need to be compatible with the NE side model in order to accurately decode the compressed information included in the communication. For example, the UE can determine channel measurements, can generate compressed communications based at least in part on the UE side model including the channel measurements, and can send compressed communications to the network entity. If the network entity is able to receive the communication and accurately decode the channel information using the NE side model, the UE side model and the NE side model can be considered compatible. Alternatively, if the network entity cannot accurately decode the channel information included in the communication, the UE side model and the NE side model can be considered incompatible.

[0031] In one example, the UE may detect a change in a condition and may switch from a first UE-side model to a second UE-side model capable of processing information associated with the condition. By way of example, the condition may include any of the following: the UE switches between an indoor state and an outdoor state; the UE switches between line-of-sight communication and non-line-of-sight communication; the UE switches between a first provider and a second provider; the UE switches between a first geographic location or region and a second geographic location or region; the UE switches between a first serving cell and a second serving cell; a change in one or more channel conditions; a change in one or more features of the first model or the second model; or other conditions.

[0032] The NE side model currently being used by the network entity may be compatible with the first UE side model, but may not be compatible with the second UE side model. When the UE switches from the first UE side model to the second UE side model, this may cause unsuccessful communication between the UE and the network entity.

[0033] This article describes techniques and devices for selecting a model for compressed communication and switching between models for compressed communication. In some aspects, the UE may determine a situation and may switch from a first UE-side model to a second UE-side model. For example, the UE may switch from a first UE-side model to a second UE-side model based at least in part on determining that the first UE-side model cannot be used for the situation and the second UE-side model can be used for the situation or based at least in part on determining that the second UE-side model will perform better (e.g., have a better performance indicator) than the first UE-side model for the situation. The UE may send a model identifier associated with the second UE-side model to a network entity. The network entity may receive an identifier associated with the second UE-side model and may determine whether the current NE-side model is compatible with the second UE-side model. If the current NE-side model is compatible with the second UE-side model, the network entity may not switch to another NE-side model. Alternatively, if the current NE-side model is incompatible with the second UE-side model, the network entity may switch to another NE-side model compatible with the second UE-side model. Alternatively, even if the current NE-side model is compatible with the second UE-side model, when the second UE-side model is in use, the network entity may switch to another NE-side model that is preferred over the current NE-side model.

[0034] In some other aspects, the UE may determine a condition and may send a condition identifier associated with the condition to a network entity. The network entity may identify a NE-side model that can be used for the condition and may selectively switch the NE-side model based at least in part on the identified NE-side model. For example, if the current NE-side model cannot be used for the condition, the network entity may switch between models, but if the current NE-side model can be used for the condition, the network entity may not switch the model. Alternatively, even if the current NE-side model can be used for the condition, the network entity may switch to another NE-side model that is superior to the current NE-side model for the condition. The network identity may identify a UE-side model that is compatible with the NE-side model and may send an identifier associated with the UE-side model. The UE may receive an identifier associated with the UE-side model and may switch to the identified UE-side model.

[0035] In some other aspects, the UE may determine a situation and may determine one or more UE-side models and / or one or more NE-side models that can be used for the situation. The UE may send one or more UE-side model identifiers corresponding to one or more UE-side models and / or one or more NE-side model identifiers corresponding to one or more NE-side models, respectively. The network entity may receive the UE-side model identifier and / or the NE-side model identifier and may selectively switch to the NE-side model based at least in part on receiving the UE-side model identifier and / or the NE-side model identifier. In some aspects, the NE-side model to which the network entity switches is identified by one of the identifiers. For example, the network entity may switch from a first NE-side model to a second NE-side model and may send an indication for the UE to switch to a UE-side model compatible with the second NE-side model. The UE may switch to the UE-side model based at least in part on receiving the indication from the network entity.

[0036] As described above, the UE or the network entity may switch models based at least in part on the compatibility between the situation and the model. The UE may switch from a first UE-side model to a second UE-side model that can be used in association with the detected situation, and the network entity may switch from a first NE-side model that is incompatible with the second UE-side model to a second NE-side model that is compatible with the second UE-side model. This may reduce the number of communications missed or otherwise interrupted between the UE and the network entity.

[0037] In addition, this can reduce unnecessary model switching by the UE and the network entity. For example, if the first NE side model is compatible with the second UE side model, the network entity can determine not to switch between the first NE side model and the second NE side model.

[0038] Additional details are described herein.

[0039] Introduction to wireless communication networks

[0040] The techniques and methods described herein can be used in various wireless communication networks. Although various aspects may be described herein using terms commonly associated with 3G, 4G and / or 5G wireless technologies, various aspects of the present disclosure may also be applicable to other communication systems and standards not explicitly mentioned herein.

[0041] Figure 1 An example of a wireless communication network 100 is depicted in which various aspects described herein may be implemented.

[0042] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., user equipment (UE), base station (BS), component of a BS, server, etc.). For example, various functions of a network and various devices associated with and interacting with the network may be considered network entities. In addition, the wireless communication network 100 includes ground aspects, such as ground-based network entities (e.g., BS 110), and non-ground aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) that can communicate with other network elements (e.g., ground BSs) and UEs.

[0043] In the depicted example, the wireless communication network 100 includes a BS 110, a UE 120, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) 190) that interoperate to provide communication services over various communication links (including wired and wireless links).

[0044] Figure 1 Various example UEs 120 are depicted, which may more generally include: a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an Always-On (AON) device, an edge processing device, or another similar device. UE 120 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, or a handset, etc.

[0045] BS 110 may wirelessly communicate with (e.g., send signals to or receive signals from) UE 120 via communication link 170. Communication link 170 between BS 110 and UE 120 may carry uplink (UL) (also referred to as a reverse link) transmissions from UE 120 to BS 110 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 110 to UE 120. In various aspects, communication link 170 may employ multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity.

[0046] BS 110 may generally include: NodeB, enhanced NodeB (eNB), next generation enhanced NodeB (ng-eNB), next generation NodeB (gNB or gNodeB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission and reception point, and / or other. BS 110 may provide communication coverage for a corresponding geographic coverage area 112, which may sometimes be referred to as a cell and may overlap in some cases (e.g., a small cell provided by BS 110a may have a coverage area 112' that overlaps with the coverage area 112 of a macro cell). For example, a BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0047] Although BS110 is depicted as a single communication device in various aspects, BS110 can be implemented in various configurations. For example, one or more components of the base station may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of the base station may be virtualized. More generally, a base station (e.g., BS110) may include components located at a single physical location or components located at various physical locations. In an example in which the base station includes components located at various physical locations, the various components may each perform a function so that the various components together implement functionality similar to that of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations may be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0048] Different BSs 110 within the wireless communication network 100 may also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G. For example, a BS 110 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 110 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 110 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0049] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based at least in part on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410 MHz-7125 MHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250 MHz-52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station (e.g., a mmWave base station such as BS110b) configured to communicate using mmWave or near mmWave radio bands may utilize beamforming (e.g., as shown by 182) with a UE (e.g., 120) to improve path loss and range.

[0050] The communication link 170 between the BS 110 and, for example, the UE 120 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other bandwidths) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. In some examples, the allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0051] Communications using higher frequency bands may have higher path loss and shorter range than communications at lower frequencies. Accordingly, some base stations (e.g., Figure 1A base station 110b in the wireless communication network may utilize beamforming with a UE 120 to improve path loss and range, as shown at 182. For example, BS 110b and UE 120 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS 110b may transmit beamformed signals to UE 120 in one or more transmit directions 182'. UE 120 may receive beamformed signals from BS 110b in one or more receive directions 182". UE 120 may also transmit beamformed signals to BS 110b in one or more transmit directions 182". BS 110b may also receive beamformed signals from UE 120 in one or more receive directions 182'. BS 110b and UE 120 may then perform beam training to determine optimal receive and transmit directions for each of BS 110b and UE 120. It is worth noting that the transmission direction and the reception direction of BS 110b may be the same or may not be the same. Similarly, the transmission direction and the reception direction of UE 120 may be the same or may not be the same.

[0052] The wireless communication network 100 further includes a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0053] Certain UEs 120 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0054] The EPC 160 may include various functional components, including: a mobility management entity (MME) 161, other MMEs 162, a serving gateway 163, a multimedia broadcast multicast service (MBMS) gateway 164, a broadcast multicast service center (BM-SC) 165, and / or a packet data network (PDN) gateway 166, such as in the depicted example. The MME 161 may communicate with a home subscriber server (HSS) 167. The MME 161 is a control node that handles signaling between the UE 120 and the EPC 160. Generally speaking, the MME 161 provides bearer and connection management.

[0055] Generally, user Internet Protocol (IP) packets are transmitted through the Serving Gateway 163, which itself is connected to the PDN Gateway 166. The PDN Gateway 166 provides UE IP address allocation and other functions. The PDN Gateway 166 and the BM-SC 165 are connected to the IP Services 168, which may include, for example, the Internet, an Intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming media service, and / or other IP services.

[0056] The BM-SC 165 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 165 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS delivery. The MBMS Gateway 164 may be used to distribute MBMS services to BSs 110 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0057] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 191, other AMF 192, session management function (SMF) 193, and user plane function (UPF) 194. AMF 191 may communicate with unified data management (UDM) 195.

[0058] AMF 191 is a control node that processes signaling between UE 120 and 5GC 190. AMF 191 provides, for example, Quality of Service (QoS) flow and session management.

[0059] IP packets are transported through UPF 194, which is connected to IP services 196 and provides UE IP address allocation and other functions for 5GC 190. IP services 196 may include, for example, the Internet, intranet, IMS, PS streaming services, and / or other IP services.

[0060] In various aspects, a network entity or network node may be implemented as a converged base station, a decomposed base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, or a transmit receive point (TRP), to name a few examples.

[0061] Figure 2An example disaggregated base station 200 architecture is depicted. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 240.

[0062] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0063] In some aspects, CU 210 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 210. CU 210 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 210 may be logically divided 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 210 may be implemented to communicate with DU 230 for network control and signaling.

[0064] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, DU 230 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.) at least in part according to a functional split such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 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 230 or with control functions hosted by CU 210.

[0065] The lower layer functionality may be implemented by one or more RUs 240. In some deployments, the RU 240 controlled by the DU 230 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 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the implementation of the DU 230 and the CU 210 in a cloud-based RAN architecture (such as a vRAN architecture).

[0066] The SMO framework 205 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 205 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 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element lifecycle management (such as to instantiate 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 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 211), via the O1 interface. In addition, in some specific implementations, the SMO framework 205 may communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0067] The non-RT RIC 215 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 225. The non-RT RIC 215 may be coupled to or in communication with the near-RT RIC 225 (such as via an A1 interface). The near-RT RIC 225 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 connecting one or more CUs 210, one or more DUs 230, or both, and an O-eNB with the near-RT RIC 225 (such as via an E2 interface).

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

[0069] Figure 3 Aspects of an example BS 110 and UE 120 are depicted.

[0070] In general, BS 110 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively 334), transceivers 332a-332t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 110 can transmit and receive data between BS 110 and UE 120. BS 110 includes controller / processor 340 that can be configured to implement various functions described herein related to wireless communication.

[0071] Generally speaking, the UE 120 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively 352), transceivers 354a-354r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 120 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.

[0072] Regarding example downlink transmissions, BS 110 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0073] The transmit processor 320 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS)).

[0074] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to a modulator (MOD) in a transceiver 332a-332t. Each modulator in the transceiver 332a-332t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in the transceivers 332a-332t may be transmitted via antennas 334a-334t, respectively.

[0075] To receive downlink transmissions, UE 120 includes antennas 352a-352r that can receive downlink signals from BS 110 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0076] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0077] For example uplink transmissions, the UE 120 also includes a transmit processor 364 that can receive and process data from a data source 362 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 can also generate reference symbols for reference signals (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 364 can be pre-decoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 110.

[0078] At BS 110, uplink signals from UE 120 may be received by antennas 334a-334t, processed by demodulators in transceivers 332a-332t, detected by MIMO detector 336 where applicable, and further processed by receive processor 338 to obtain decoded data and control information transmitted by UE 120. Receive processor 338 may provide decoded data to data sink 339 and decoded control information to controller / processor 340. Memories 342 and 382 may store data and program codes for BS 110 and UE 120, respectively. Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0079] In various aspects, the BS 110 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 312, a scheduler 344, a memory 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, a transceiver 332a-332t, an antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 334a-334t, a transceiver 332a-332t, a RX MIMO detector 336, a controller / processor 340, a receive processor 338, a scheduler 344, a memory 342, and / or other aspects described herein.

[0080] In various aspects, the UE 120 may also be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 362, a memory 382, ​​a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, ​​and / or other aspects described herein.

[0081] In some aspects, the processor may be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.

[0082] In some aspects, a single processor may perform all of the functions described as being performed by the one or more processors. In some aspects, the one or more processors may perform a set of functions together. For example, a first set of (one or more) of the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of (one or more) of the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. References to "one or more processors" should be understood to refer to the combination Figure 2 Any one or more of the processors described. References to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as in conjunction with Figure 2 For example, functions described as being performed by one or more memories may be performed by the same subset of the one or more memories or by a different subset of the one or more memories.

[0083] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes a method for use in a wireless communication network such as Figure 1 Various aspects of the data structure of the wireless communication network 100).

[0084] Specifically, Figure 4Ais a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D FIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0085] Wireless communication systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems may also support half-duplex operation using time division duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) will (for example, Figure 4B and Figure 4D The system bandwidth (as depicted in FIG. 1 ) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0086] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0087] exist Figure 4A and Figure 4C In the wireless communication frame structure, TDD is used, where D is DL, U is UL, and F is used flexibly between DL / UL. The UE can be configured with a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by RRC signaling) through a received slot format indicator (SFI). In the depicted example, a 10ms frame is divided into 10 1ms subframes of equal size. Each subframe may include one or more slots. In some examples, each slot may include 7 or 14 symbols, depending on the slot format. A subframe may also include a microslot, which typically has fewer symbols than a whole slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0088] In certain aspects, the number of time slots within a subframe is based at least in part on the time slot configuration and the parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 time slots per subframe, respectively. Accordingly, for time slot configuration 0 and parameter set μ, there are 14 symbols per time slot and 2 per subframe. μtime slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ × 15kHz, where μ is parameter set 0 to 5. Accordingly, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0089] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted in FIG, a resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending, for example, over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0090] like Figure 4A As illustrated, some of the REs carry data for UEs (eg, Figure 1 and Figure 3 The RS may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0091] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE Groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0092] The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identification.

[0093] A Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0094] Based at least in part on the physical layer identifier and the physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Based at least in part on the PCI, the UE can determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the system bandwidth and the number of RBs in the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)) that is not sent via the PBCH, and / or paging messages.

[0095] like Figure 4C As illustrated, some of the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE may send DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. UE 120 may send a sounding reference signal (SRS). The SRS may be sent, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0096] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0097] Aspects related to selecting a model for compressed communications and switching between models for compressed communications

[0098] Figure 5 is a diagram illustrating an example 500 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 5 As shown, a downlink channel and a downlink reference signal may carry information from network entity 110 to UE 120 , and an uplink channel and an uplink reference signal may carry information from UE 120 to network entity 110 .

[0099] As shown, the downlink channel may include a physical downlink control channel (PDCCH) carrying downlink control information (DCI), a physical downlink shared channel (PDSCH) carrying downlink data, or a physical broadcast channel (PBCH) carrying system information, etc. In some aspects, PDSCH communication may be scheduled by PDCCH communication. As further shown, the uplink channel may include a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a physical random access channel (PRACH) for initial network access, etc. In some aspects, UE 120 may send confirmation (ACK) or negative confirmation (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on PUCCH and / or PUSCH.

[0100] As further shown in the figure, the downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS) or a phase tracking reference signal (PTRS), etc. As also shown in the figure, the uplink reference signal may include a sounding reference signal (SRS), a DMRS or a PTRS, etc.

[0101] The SSB may carry information used for initial network acquisition and synchronization, such as a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH, and a PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, the network entity 110 may send multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection.

[0102] The CSI-RS may carry information for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, etc. The network entity 110 may configure a set of CSI-RS for the UE 120, and the UE 120 may measure the configured set of CSI-RS. Based at least in part on these measurements, the UE 120 may perform channel estimation and may report channel estimation parameters such as a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), or a reference signal received power (RSRP), etc., to the network entity 110 (e.g., in a CSI report). The network entity 110 can use the CSI report to select transmission parameters for downlink communication to the UE 120, such as the number of transmission layers (e.g., rank), the precoding matrix (e.g., precoder), the modulation and coding scheme (MCS), or the refined downlink beam (e.g., using a beam refinement procedure or a beam management procedure), etc.

[0103] DMRS may carry information for estimating a radio channel to demodulate an associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS may be specific to the physical channel that the DMRS is used to estimate. DMRS is UE-specific, may be beamformed, may be restricted to scheduled resources (e.g., rather than being sent over a wideband), and may be sent only when necessary. As shown, DMRS is used for both downlink and uplink communications.

[0104] PTRS can carry information for compensating for oscillator phase noise. Typically, phase noise increases with the increase of the oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communications (e.g., on PDSCH) and uplink communications (e.g., on PUSCH).

[0105] The PRS may carry information for implementing timing measurements or ranging measurements of the UE 120 based at least in part on signals sent by the network node 110 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with a frequency offset and a time offset to avoid collisions with cell-specific reference signals and control channels (e.g., PDCCH). In general, the PRS may be designed to improve detectability of the UE 120, which may need to detect downlink signals from multiple neighboring network entities in order to perform OTDOA-based positioning. Accordingly, the UE 120 may receive the PRS from multiple cells (e.g., a reference cell and one or more neighboring cells), and may report a reference signal time difference (RSTD) based at least in part on OTDOA measurements associated with the PRS received from the multiple cells. In some aspects, the network entity 110 may then calculate the position of the UE 120 based at least in part on the RSTD measurements reported by the UE 120.

[0106] The SRS may carry information for uplink channel estimation, which may be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. The network entity 110 may configure one or more SRS resource sets for the UE 120, and the UE 120 may send the SRS on the configured SRS resource sets. The SRS resource sets may have configured purposes such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. The network entity 110 may measure the SRS, may perform channel estimation based at least in part on these measurements, and may use the SRS measurements to configure communications with the UE 120.

[0107] In some cases, UE 120 and network entity 110 may be configured with one or more models, such as an artificial intelligence (AI) model and / or a machine learning (ML) model. UE 120 and network entity 110 may use these models to communicate information such as reference signal (e.g., CSI-RS) measurements. Additional details about these features are described below.

[0108] As mentioned above, Figure 5 are provided as examples. Other examples may vary from Figure 5 An example of description.

[0109] Figure 6 is a diagram illustrating an example of a machine learning model according to the present disclosure.

[0110] In some cases, the UE 120 and the network entity 110 may use a model such as an AI or ML model to perform one or more functions. For example, the AI / ML model may be used to convey compressed information. Communications including compressed information may be referred to herein as compressed communications. The UE 120 and the network entity 110 may use an interface such as an AI / ML-based air interface to convey information associated with the model. In one example, the information may be compressed information associated with one or more reference signal measurements. In one example, the UE 120 may determine CSI for transmission to the network entity 110. The UE 120 may use a model such as a neural network ML model to derive a compressed representation of the CSI for transmission to the network entity 110. The network entity 110 may receive a compressed representation of the CSI, and may use another model such as another neural network model to reconstruct the CSI from the compressed representation. In order to make the reconstruction accurate, it may be necessary to train the UE-side model and the NE-side model in a collaborative manner so that the compressed representation generated by the UE-side model is correctly interpreted and decoded by the NE-side model. If the network entity is able to receive the communication and accurately decode the channel information using the NE-side model, the UE-side model and the NE-side model may be considered compatible. Alternatively, if the network entity is unable to accurately decode channel information included in the communication, the UE-side model and the NE-side model may be considered incompatible.

[0111] In some cases, the AI / ML model can be used in different conditions or scenarios. For example, the model can be used for indoor UE conditions and / or outdoor UE conditions. In another example, the model can be used for line-of-sight (LOS) UE conditions and / or non-line-of-sight (NLOS) UE conditions. In another example, the model can be used for UEs associated with a first supplier and / or can be used for UEs associated with a second supplier. In another example, the model can be used in a first geographic location or region and / or can be used in a second geographic location or region. In another example, the model can be used for UEs associated with a first serving cell and / or can be used for UEs associated with a second serving cell. In another example, the model can be used for one or more channel conditions, such as certain delay spread conditions or signal-to-noise ratio (SNR) conditions. In another example, the model can be used with one or more model feature conditions, such as a model size condition or a mode category condition. Other conditions can be considered.

[0112] In some cases, if a model trained using data samples associated with a particular condition is used for another condition, the model may not perform well. If a model is trained using data samples from many conditions, the model may work well in many conditions and / or other conditions. However, this may result in a large and computationally complex model. This may be problematic because the model may be too large or too complex to be used by the UE 120 and / or the network entity 110.

[0113] In some cases, the UE side model may be situation specific, while the NE side model may be trained with data samples associated with multiple situations. In this case, the NE side model may be compatible with many different situation specific UE side models. In some other cases, the NE side model may be situation specific, while the UE side model may be trained with data samples associated with multiple situations. In this case, the UE side model may be compatible with many different situation specific NE side models.

[0114] As shown in example 600, the UE side model 605 may include a UE model 610 for situation 1 and a UE model 615 for situations 2 and 3. The NE side model 620 may include a NE model 625 for situations 1 and 2 and a NE model 630 for situation 3. In this example, the UE model 610 for situation 1 may be situation specific, while the UE model 615 for situations 2 and 3 may be trained with data samples associated with multiple situations. Similarly, the NE model 625 for situations 1 and 2 may be trained with data samples associated with multiple situations, while the NE model for situation 3 may be situation specific.

[0115] In some cases, it may be necessary to identify the current situation and use a model suitable for the situation. Once the situation is identified by the UE 120, a mechanism may be needed for the UE 120 to notify the network entity 110 of the situation so that the network entity 110 can respond accordingly. It may also be necessary to define responses and actions from the network entity 110 to such indications. In one example, the UE 120 may use the UE model 610 for situation 1, and the network entity 110 may use the NE model 625 for situations 1 and 2. If the UE 120 detects situation 2, such as the UE 120 moves to an external situation, the UE 120 may need to switch from the UE model 610 for situation 1 to the UE model 615 for situations 2 and 3. However, the network entity 110 may not need to switch models because the NE model 625 for situations 1 and 2 may be able to be used for situation 2. At another time, the UE 120 may detect situation 3, such as the UE moves to a specific geographical location or area associated with situation 3. UE 120 may not need to switch models because UE model 615 for cases 2 and 3 is capable of case 3. However, network entity 110 may need to switch models from NE model 625 for cases 1 and 2 to NE model 630 for case 3.

[0116] As described above, the UE 120 or the network entity 110 may switch models based at least in part on the situation. This may result in interruption of communication between the UE 120 and the network entity 110. Using the techniques and apparatus described herein, the UE 120 and the network entity 110 may communicate situation information and / or model information to ensure that the UE-side model and the NE-side model are compatible. This may improve communication between the UE 120 and the network entity 110 by reducing the likelihood that the UE 120 and / or the network entity 110 cannot decode the communication due to model incompatibility.

[0117] In some aspects, the UE 120 may determine a situation and may switch from a first UE-side model to a second UE-side model. For example, the UE 120 may switch from the first UE-side model to the second UE-side model based at least in part on determining that the first UE-side model cannot be used for the situation and the second UE-side model can be used for the situation or based at least in part on determining that the second UE-side model has better performance indicators for the situation than the first UE-side model for the situation. The UE 120 may send a model identifier associated with the second UE-side model to the network entity 110. The network entity 110 may receive the identifier associated with the second UE-side model and may determine whether the current NE-side model is compatible with the second UE-side model. If the current NE-side model is compatible with the second UE-side model, the network entity 110 may not switch to another NE-side model. Alternatively, if the current NE-side model is incompatible with the second UE-side model, the network entity 110 may switch to another NE-side model that is compatible with the second UE-side model. The following is in conjunction with Figure 7 Additional details about these features are described.

[0118] In some other aspects, the UE 120 may determine a situation and may send a situation identifier associated with the situation to the network entity 110. The network entity 110 may identify a NE side model that can be used for the situation and may selectively switch the NE side model based at least in part on the identified NE side model. For example, if the current NE side model cannot be used for the situation, the network entity 110 may switch between models, but if the current NE side model can be used for the situation, the network entity may not switch the model. The network entity 110 may identify a UE side model that is compatible with the NE side model and may send an identifier associated with the UE side model. The UE 120 may receive an identifier associated with the UE side model and may switch to the identified UE side model. In some other aspects, the UE 120 may determine a situation and may determine one or more UE side models and / or one or more NE side models that can be used for the situation. The UE 120 may send one or more UE model identifiers corresponding to one or more UE side models and / or one or more NE model identifiers corresponding to one or more NE side models, respectively. The network entity 110 may receive the UE model identifier and / or the NE model identifier, and may selectively switch to the NE side model based at least in part on receiving the UE model identifier and / or the NE model identifier. For example, the network entity 110 may switch from a first NE side model to a second NE side model, and may send an indication for the UE to switch to a UE side model compatible with the second UE side model. The UE 120 may switch to the UE side model based at least in part on receiving the indication from the network entity 110. Figure 8 Additional details about these features are described.

[0119] As mentioned above, Figure 6 are provided as examples. Other examples may vary from Figure 6 An example of description.

[0120] Aspects related to channel classification with machine learning channel state feedback

[0121] In some cases, the channel state feedback (CSF) may be a codebook-based CSF. In this case, the UE 120 may calculate a predecoder and may map the predecoder to a CSF payload, and the network entity 110 may reconstruct the predecoder based at least in part on the CSF payload. An equation or other indicator for reconstructing the predecoder based at least in part on the CSF payload may be configured in the network entity 110. In some cases, the CSF is ML-based. In this case, the UE 120 may compress the predecoder and may map the output of the compression operation to a CSF payload, and the network entity 110 may reconstruct the predecoder based at least in part on the CSF payload.

[0122] In some cases, the UE 120 and the network entity 110 may use a CSI compression neural network (e.g., an encoder) and a CSI reconstruction neural network (e.g., a decoder). A general encoder / decoder may cover a larger number of channel variations. However, the neural network may not be optimal for every channel variation. In contrast, a dedicated encoder / decoder may only cover specific channel variations. For these channel variations, the neural network may be optimal. However, the UE 120 and the network entity 110 may not be configured with information for training a dedicated encoder / decoder. In addition, the UE 120 and / or the network entity 110 may need to determine the trade-off between performance and channel variation coverage.

[0123] In some aspects, the channel classification neural network may be configured to determine the channel classification of an encoder / decoder (such as a dedicated encoder / decoder). In some aspects, the channel classification may divide all channel inputs into multiple clusters, and multiple encoders / decoders may be used (e.g., instead of a single encoder / decoder for each channel). In some aspects, multiple encoders (or encoders with cluster indicators as inputs) and a single decoder may be used. For each input, the channel classification operation may output a cluster indicator. The corresponding encoder / decoder may be used to generate a cluster indicator. For each input, the channel classification operation may also output a distribution indicator. In this case, an encoder / decoder may not be required. The determination of the current status may be based on the cluster indicator.

[0124] In some aspects, data sharing may be performed for sequential training. If the encoder / decoder is trained separately starting from UE-side training or NE-side training, the UE 120 and the network entity 110 may share a training data set. In one example, each encoder / decoder output may be considered an independent neural network. Encoder output / decoder output may be shared for each encoder / decoder pair, and channel classification may be transparent to the network entity 110. In another example, multiple encoders / decoders may be considered as encoder / decoder groups. Encoder / decoder outputs may be shared with groups (e.g., clusters), and channel classification may not be transparent to the network entity 110. In another example, for multiple encoders but a single (universal) decoder, multiple encoder outputs and a single decoder output may be shared between the UE 120 and the network entity 110.

[0125] In some aspects, the UE 120 and the network entity 110 may communicate cluster indicator signaling. Since the UE 120 may use a different encoder than the network entity 110, a single neural network ID (NNID) may not be sufficient to align the encoder / decoder pair. In one example, multiple NNIDs may be used. Each NNID may correspond to a single encoder. The network entity may send an indication to the UE 120 indicating the NNID to be used. In this case, channel classification may be performed at the network entity 110. If UE reporting is enabled (e.g., allowed), the UE 120 may report the NNID to the network entity 110 and / or may report an out-of-distribution (OOD) message. In another example, a single NNID and one or more sub-NNIDs may be used. The NNID may correspond to a primary NNID and one or more sub-NNIDs. In some aspects, the network entity 110 may indicate the primary NNID to the UE 120. The UE 120 may identify the sub-NNID based at least in part on the primary NNID. The UE 120 may send an indication of the sub-NNID to the network entity 110, or may send an OOD message. Channel classification may be performed at the UE 120. The primary NNID may correspond to a network entity 110 antenna setting or a network entity 110 encoder. In some other aspects, the network entity 110 may indicate both a NNID and a sub-NNID to the UE 120. For example, the network entity 110 may indicate one or more sub-NNIDs and / or a list of sub-NNIDs. The UE 120 may report the sub-NNID based at least in part on the configured sub-NNID. If the UE 120 detects an OOD, the sub-NNID for the OOD may be reported. In some aspects, an RRC message may be used to report the list of sub-NNIDs.

[0126] In some aspects, UE 120 may be configured with information that enables UE 120 to send NNID, sub-NNID and / or OOD. In some aspects, CSI reports may enable UE 120 to send NNID reports. For example, the reportQuantity indicator may be used to enable UE 120 to send NNID reports. In another example, CSI reports may enable UE 120 to send sub-NNID reports. Additionally or alternatively, a new codebook type may enable UE 120 to send sub-NNID reports. In some aspects, NNID reports and OOD reports may be associated with different CSF payloads (e.g., similar to PMI and CQI). In some aspects, NNID reports and OOD reports may be included in the same CSF payload. In this case, a mapping may be used to map payload information and NNID / OOD information.

[0127] The example mapping is shown in Table 1:

[0128] Table 1

[0129] Sub-NNID OOD Mark 0 N / A 1 1 0 0 2 1 0 3 2 0

[0130] In some aspects, if OOD is reported, the other CSF payload may be a dummy payload. For example, the other CSF payload may be all zeros. In some aspects, the other payload may be a neural network payload. Even if the network entity 110 cannot decode the neural network payload, the other payload may be a neural network payload. In this case, the UE 120 may use the best subencoder or may use the default subencoder. The default subencoder may be configured by the network entity 110. In some aspects, the other CSF payload may be based at least in part on Type I, Type II, or eTypeII fallback information. In this case, if the payload size does not match, zero padding may be used. The fallback information may correspond to a legacy CSF. For example, if OOD is detected and / or reported, the UE 120 may follow a predefined mapping to determine the fallback CSF. An example of the mapping is shown in Table 2.

[0131] Table 2

[0132] NNID eTypeII 0 PC1 1 PC2 2 PC3 3 PC4

[0133] In some aspects, the NNID / OOD report may be included in CSI Part 1, while the encoder output may (potentially) be included in CSI Part 2. This may allow each NNID to have its own latency size. In some aspects, the UE 120 may discard CSI Part 2. For example, if OOD is indicated in CSI Part 1, the UE 120 may discard CSI Part 2.

[0134] Example Operations of Entities in a Communication Network

[0135] Figure 7 A process flow 700 is depicted for communication in a network between a UE 702 and a network entity 704. In some aspects, the UE 702 may be a network entity. Figure 1 and Figure 3 An example of a UE 702 is depicted and described. Similarly, a network entity 704 may be associated with Figure 1 and Figure 3 BS 704 depicting and describing or relating to Figure 2 An example of a decomposed base station is depicted and described. In other aspects, however, UE 702 may be another type of wireless communication device, and network entity 704 may be another type of network entity or network node, such as those described herein.

[0136] As indicated by reference numeral 706, the UE 702 and the network entity 704 may communicate compressed information using a first model. For example, the UE 702 may obtain reference signal measurements (such as CSI-RS measurements), may generate compressed communications including reference signal measurements (using a first UE model), and may send compressed communications. The network entity 704 may receive the compressed communications and may decode the compressed communications using a first NE model. The first UE model and the first NE model may be compatible. For example, the network entity 704 may be able to receive compressed communications generated by the first UE model and may be able to accurately decode information included in the compressed communications using the first NE model.

[0137] As indicated by reference numeral 708, UE 702 may determine a condition. The condition may include, for example, Figure 6 The UE 702 may determine the condition based at least in part on reference signal measurements and / or at least in part on one or more rules, such as one or more threshold-based rules that may be applied to one or more channel parameters. For example, the UE 702 may determine the condition based at least in part on a delay spread that satisfies a delay spread threshold, an SNR that satisfies an SNR threshold, or a Doppler spread that satisfies a Doppler spread threshold, etc. In some aspects, a condition classifier (e.g., a scene classifier) ​​may be configured to determine the one or more rules and / or apply the one or more rules. The condition classifier may be an ML model that has been trained to identify conditions based at least in part on reference signal measurements, such as CSI.

[0138] As shown in reference numeral 710, UE 702 may identify a second UE model for sending compressed communications based at least in part on a condition. For example, UE 702 may identify a second UE model that can be used for the condition. In one example, the condition may include an outdoor condition, and determining the condition may include determining that UE 702 has moved to an outdoor condition. In this case, UE 702 may identify a second UE model that can be used for an outdoor condition. In another example, the condition may be associated with a specific geographic location or region, and determining the condition may include determining that UE 702 has moved to a specific geographic location or region. In this case, UE 702 may identify a second UE model that can be used in a specific geographic location or region. UE 702 may switch from a first UE model to a second UE model based at least in part on determining that a first UE model cannot be used for the condition and a second UE model can be used for the condition. In another example, UE 702 may switch from a first UE model to a second UE model based at least in part on determining that a second UE model has a better performance indicator for the condition than a first UE model for the condition. In some aspects, the UE 702 may not switch from the first UE model to the second UE model based at least in part on determining that the first UE model can be used for the situation.

[0139] In some aspects, the UE 120 may monitor multiple models including at least one inactive model. The UE 120 may detect the condition or another condition based at least in part on monitoring at least one active model in the multiple models and at least one inactive model in the multiple models. The UE 120 may switch to a third model in the multiple models based at least in part on detecting the condition or another condition. For example, the UE 120 may be configured with a model for the currently active condition 1 and a model for the currently inactive condition 2. The UE 120 may determine whether it is in condition 1 or condition 2 based on monitoring the performance of the two models. For example, if the model for condition 2 performs better than the model for condition 1, the condition may be determined to be condition 2.

[0140] As shown by reference numeral 712, the UE 702 may send and the network entity 704 may receive an identifier associated with a second UE model. The UE 702 and / or the network entity 704 may be configured with a plurality of model identifiers corresponding to respective models, such as a UE model identifier corresponding to a UE model and a NE model identifier corresponding to a NE model. In some aspects, sending the identifier associated with the second UE model may include sending an index indicating the second UE model.

[0141] As shown by reference numeral 714, the network entity 704 may selectively identify the second NE model and / or may selectively switch from the first NE model to the second NE model based at least in part on receiving an identifier associated with the second UE model. In some aspects, the network entity 704 may determine whether the first NE side model is compatible with the second UE side model. If the network entity 704 determines that the first NE model is compatible with the second UE model, the network entity 704 may determine not to identify and / or switch to the second NE model. For example, if the network entity 704 determines that the first NE model is able to accurately decode information generated by the second UE model, the network entity 704 may determine not to identify and / or switch to the second NE model. Alternatively, if the network entity 704 determines that the first NE model is incompatible with the second UE model, the network entity 704 may identify the second NE model and / or may switch to the second NE model. For example, if the network entity 704 determines that the first NE model cannot accurately decode information generated by the second UE model, the network entity 704 may determine to identify the second NE model and / or switch to the second NE model.

[0142] As indicated by reference numeral 716, UE 702 and network entity 704 may perform compressed communication. UE 702 may perform compressed communication using a second UE model. For example, UE 702 may compress (e.g., encode) information such as reference signal measurement information using a second UE model. Network entity 704 may perform compressed communication using a first NE model or a second NE model. For example, network entity 704 may perform compressed communication using a first NE model based at least in part on determining that the first NE model is compatible with a second UE model. In this case, network entity 704 may receive compressed communication from UE 702 that is using the second UE model, and may decode the compressed information using the first NE model. Alternatively, network entity 704 may perform compressed communication using a second NE model based at least in part on determining that the first NE model is incompatible with the second UE model and at least in part on switching to the second NE model. In this case, network entity 704 may receive compressed communication from UE 702 that is using the second UE model, and may decode the compressed information using the second NE model.

[0143] As mentioned above, Figure 7 are provided as examples. Other examples may vary from Figure 7 An example of description.

[0144] Figure 8 A process flow 800 is depicted for communication in a network between a UE 802 and a network entity 804. In some aspects, the UE 802 may be a network entity. Figure 1 and Figure 3An example of a UE 802 is depicted and described. Similarly, a network entity 804 may be associated with Figure 1 and Figure 3 BS 804 depicts and describes or is about Figure 2 An example of a decomposed base station is depicted and described. In other aspects, however, UE 802 may be another type of wireless communication device, and network entity 804 may be another type of network entity or network node, such as those described herein.

[0145] As indicated by reference numeral 806, the UE 802 and the network entity 804 may perform compressed communications. For example, the UE 802 may obtain reference signal measurements (such as CSI-RS measurements), may generate compressed communications including the reference signal measurements (using the first UE model), and may send the compressed communications. The network entity 804 may receive the compressed communications and may decode the compressed communications using the first NE model. The first UE model and the first NE model may be compatible. For example, the network entity 804 may be able to receive compressed communications generated by the first UE model and may be able to accurately decode information included in the compressed communications using the first NE model.

[0146] As indicated by reference numeral 808, UE 802 may determine a condition. The condition may include, for example, Figure 6 The UE 802 may determine the condition based at least in part on reference signal measurements and / or at least in part on one or more rules, such as one or more threshold-based rules that may be applied to one or more channel parameters. For example, the UE 802 may determine the condition based at least in part on a delay spread that satisfies a delay spread threshold, an SNR that satisfies an SNR threshold, or a Doppler spread that satisfies a Doppler spread threshold, etc. In some aspects, a condition classifier (e.g., a scene classifier) ​​may be configured to determine the one or more rules and / or apply the one or more rules. The condition classifier may be an ML model that has been trained to identify conditions based at least in part on reference signal measurements, such as CSI.

[0147] As shown by reference numeral 810, UE 802 may send an indication of a condition identifier or a model identifier. UE 802 may determine a condition identifier associated with a condition. For example, UE 802 and network entity 804 may be configured with multiple condition identifiers associated with multiple corresponding conditions. UE 802 may determine an identifier corresponding to a condition based at least in part on multiple condition identifiers stored at UE 802, and may send the condition identifier to network entity 804. Network entity 804 may receive the condition identifier, and may identify the condition based at least in part on multiple condition identifiers stored at network entity 804. In some aspects, network entity 804 may configure a condition list to UE 802, and UE 802 may indicate a condition using an index included in the condition list. In some aspects, the indication of the condition may indicate multiple conditions, wherein one or more of the conditions are associated with a confidence indicator. For example, UE 802 may send two status identifiers, where a first status identifier includes a first confidence indicator (eg, high confidence) and a second status indicator includes a second confidence indicator (eg, low confidence).

[0148] In some aspects, the UE 802 may determine a UE model identifier. The UE 802 may determine the UE model identifier based at least in part on a corresponding UE model that can be used for the situation. In one example, the UE model may correspond to a first UE model currently being used by the UE 802. In this example, the UE 802 may determine that the first UE model can be used for the situation, and may send an indication of the first UE model to the network entity 804. In another example, the UE model may correspond to a second UE model that is not currently being used by the UE 802. In this example, the UE 802 may determine that the first UE model cannot be used for the situation and the second UE model can be used for the situation, or may determine that the second UE model has a better performance indicator for the situation than the first UE model for the situation, and may send an indication of the second UE model to the network entity 804. In some aspects, the network entity 804 may send information indicating one or more rules for selecting the second UE model to the UE 802. For example, the one or more rules may instruct the UE 802 to select a UE model that is compatible with the NE model currently being used (e.g., to avoid model switching by the network entity 804).

[0149] In some aspects, the UE 802 may determine a second NE model and / or an identifier associated with the second NE model. The UE 802 may determine the second NE model based at least in part on the situation. In some aspects, the network entity 804 may send information or rules (such as a lookup table) indicating how the UE 802 selects a NE model based at least in part on the situation. The UE 802 may send an identifier associated with the second NE model based at least in part on determining a second NE model that can be used for the situation.

[0150] In some aspects, the network entity 804 may send and the UE 802 may receive one or more reporting rules for sending a condition identifier and / or a model identifier (UE model identifier or NE model identifier). For example, not all condition changes need to be communicated to the network entity 804, such as if the current NE side model can be used for many conditions including the condition. In some aspects, the one or more reporting rules may indicate one or more conditions for which the UE 802 is to send a condition identifier and / or a model identifier. In some other aspects, the one or more reporting rules may indicate one or more conditions for which the UE 802 will not send a condition identifier and / or a model identifier.

[0151] As indicated by reference numeral 812, the network entity 804 may determine whether to accept the indication received from the UE 802. For example, the network entity 804 may determine whether to accept an indication including a condition identifier or a model identifier, which suggests that the UE 802 and / or the network entity 804 is to perform a model switch. In some aspects, the network entity 804 may determine whether to accept the indication from the UE 802 based at least in part on implementation-specific information or compatibility information. For example, the network entity 804 may not initiate a model selection or model switching process at the network entity 804 based at least in part on a processing delay being greater than a processing delay threshold. In some aspects, the network entity 804 may accept the indication based only at least in part on the second UE model included in the model indication being compatible with the NE model currently being used by the network entity 804. If the second UE model is not compatible with the NE model currently being used by the network entity 804, the network entity 804 may not accept the model identifier, for example, to avoid a switching operation at the network entity 804.

[0152] As shown by reference numeral 814, the network entity 804 may identify a second NE model and / or may switch to a second NE model. In some aspects, the network entity 804 may identify the second NE model based at least in part on the model information. For example, the network entity 804 may receive model information indicating the second NE model, and may switch from the first NE model to the second NE model based at least in part on the model information. In another example, the network entity 804 may receive model information indicating a second UE model, and may switch from a first NE model incompatible with the second UE model to a second NE model compatible with the second UE model. In some aspects, the network entity 804 may identify the second NE model based at least in part on a condition identifier. For example, the network entity 804 may receive a condition identifier indicating a condition, and may switch from a first NE model that cannot be used for the condition to a second NE model that can be used for the condition.

[0153] As indicated by reference numeral 816, the network entity 804 may identify a second UE model. In some aspects, the network entity 804 may identify the second UE model based at least in part on the model information. For example, the network entity 804 may receive model information indicating the second UE model from the UE 802, and may determine that the UE 802 should switch from the first UE model to the second UE model. The network entity 804 may determine that the UE 802 should switch from the first UE model to the second UE model based at least in part on the second UE model being compatible with a current NE model such as the first NE model (if the network entity does not switch from the first NE model to the second NE model) or the second NE model (if the network entity switches from the first NE model to the second NE model). In some aspects, the network entity 804 may identify the second UE model based at least in part on a situation identifier. For example, the network entity 804 may receive a situation identifier indicating a situation, and may determine the second UE model based at least in part on determining that the second UE model can be used for a situation associated with the situation identifier.

[0154] As indicated by reference numeral 818, the network entity 804 may send, and the UE 802 may receive, a handover indication. The handover indication may be an indication that the UE 802 should handover to a second UE model and may include an identifier associated with the second UE model. The network entity 804 may send the handover indication based at least in part on determining the second UE model and / or the identifier associated with the second UE model.

[0155] UE 802 may switch to the second UE model, as indicated by reference numeral 820. UE 802 may switch to the second UE model based at least in part on receiving a switching indication from network entity 804.

[0156] As indicated by reference numeral 822, the UE 802 and the network entity 804 may perform compressed communications. The UE 802 may perform compressed communications using the first UE model based at least in part on the UE 802 or the network entity 804 determining that the UE 802 should not switch from the first UE model to the second UE model. Alternatively, the UE 802 may perform compressed communications using the second UE model based at least in part on the UE 802 or the network entity 804 determining that the UE 802 should switch from the first UE model to the second UE model. The network entity 804 may perform compressed communications using the first NE model based at least in part on the UE 802 or the network entity 804 determining that the network entity 804 should not switch from the first NE model to the second NE model. Alternatively, the network entity 804 may perform compressed communications using the second NE model based at least in part on the UE 802 or the network entity 804 determining that the network entity 804 should switch from the first NE model to the second NE model.

[0157] As mentioned above, Figure 8 are provided as examples. Other examples may vary from Figure 8 An example of description.

[0158] Example Operation of User Equipment

[0159] Fig. 9 shows a method for use by a UE such as Figure 1 and Figure 3 Method 900 for wireless communication performed by UE 120.

[0160] Method 900 begins at step 902, where compressed communication is performed between a UE and a network entity using a first model.

[0161] Method 900 then proceeds to step 904 where a condition is determined based at least in part on the channel state information.

[0162] Method 900 then proceeds to step 906 where an identifier associated with the second model is sent to a network entity based at least in part on the condition.

[0163] Method 900 then proceeds to step 908, where compressed communication is performed between the UE and the network entity using the second model.

[0164] In one aspect, sending an identifier associated with the second model to the network entity includes identifying the second model based at least in part on the condition; and switching from the first model to the second model based at least in part on identifying the second model.

[0165] In one aspect, switching from the first model to the second model includes determining that the second model is to be used for the condition and the first model is not to be used for the condition.

[0166] In one aspect, switching from a first model to a second model includes determining, based at least in part on information associated with the first model and the second model, that performance of the second model associated with the condition is better than performance of the first model associated with the condition (e.g., has a better performance metric for the condition).

[0167] In one aspect, the condition is at least one of: the UE switching between an indoor state and an outdoor state; the UE switching between line-of-sight communication and non-line-of-sight communication; the UE switching between a first provider and a second provider; the UE switching between a first geographic location or area and a second geographic location or area; the UE switching between a first serving cell and a second serving cell; a change in one or more channel conditions; or a change in one or more features of the first model or the second model.

[0168] In one aspect, method 900 further includes receiving, from a network entity, information indicative of a plurality of conditions including the condition.

[0169] In one aspect, the one or more rules indicate a delay spread threshold, a signal-to-noise ratio (SNR) threshold, or a Doppler spread threshold, and wherein determining the condition based at least in part on the channel state information and the one or more rules includes determining that the delay spread satisfies the delay spread threshold, determining that the SNR satisfies the SNR threshold, or determining that the Doppler spread satisfies the Doppler spread threshold.

[0170] In one aspect, one of the first model or the second model is based on only a single condition, and the other of the first model and the second model is based on multiple conditions.

[0171] In one aspect, method 900 also includes monitoring a plurality of models including at least one inactive model; and performing compressed communications between the UE and the network entity using a third model based at least in part on determining another condition.

[0172] In one aspect, method 900 or any aspect related thereto may be performed by an apparatus such as Fig.13 The method 900 is performed by a communication device 1300, which includes various components that are operable to, configured to, or adapted to perform the method 900. The communication device 900 is described in more detail below.

[0173] Please note that Fig. 9 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in accordance with the present disclosure.

[0174] Fig.10 shows a method for use by a UE such as Figure 1 and Figure 3 Method 1000 for wireless communication performed by UE 120.

[0175] Method 1000 begins at step 1002, where conditions are determined based at least in part on channel state information.

[0176] The method 1000 then proceeds to step 1004 where a situation identifier associated with the situation or one or more model identifiers respectively associated with the one or more models are transmitted.

[0177] The method 1000 then proceeds to step 1006, where a switching indication is received from a network entity indicating whether to switch from the first model to the second model.

[0178] Method 1000 then proceeds to step 1008 where compressed communications are performed with the network entity using the first model or the second model based at least in part on the handover indication.

[0179] In one aspect, performing compressed communications with a network entity using the first model or the second model includes determining to switch from the first model to the second model based at least in part on a switching indication; and switching from the first model to the second model based at least in part on a determination to switch from the first model to the second model.

[0180] In one aspect, method 1000 also includes receiving information indicative of a plurality of conditions including the condition.

[0181] In one aspect, sending the condition identifier includes sending an index associated with the condition.

[0182] In one aspect, sending the condition identifier includes sending a plurality of condition identifiers and a confidence indicator associated with each condition identifier of the plurality of condition identifiers.

[0183] In one aspect, method 1000 also includes receiving information indicating one or more reporting rules associated with the condition identifier or the one or more model identifiers.

[0184] In one aspect, sending the situation identifier or the one or more model identifiers includes sending only the situation identifier, and receiving the switching indication includes receiving the switching indication including an indication of the second model.

[0185] In one aspect, sending the one or more model identifiers includes sending at least one of a UE model identifier and a network entity model identifier.

[0186] In one aspect, method 1000 also includes receiving information indicating one or more other rules to be used by the UE to select one or more model identifiers based at least in part on the condition.

[0187] In one aspect, method 1000 or any aspect related thereto may be performed by an apparatus such as Fig.13The method 1000 is performed by a communication device 1300, which includes various components that are operable to, configured to, or adapted to perform the method 1000. The communication device 1300 is described in more detail below.

[0188] Please note that Fig.10 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in accordance with the present disclosure.

[0189] Example Operations of Network Entities

[0190] Fig.11 A method for transmitting data to a network entity such as Figure 1 and Figure 3 BS110 or such Figure 2 A method 1100 for performing wireless communications using a decomposed base station) as discussed above.

[0191] Method 1100 begins at step 1102, where compressed communication is performed between a network entity and a UE using a first network entity model.

[0192] The method 1100 then proceeds to step 1104, where an identifier associated with a UE model for compressed communications between the UE and a network entity is received from the UE.

[0193] The method 1100 then proceeds to step 1106 where compatibility information associated with the UE model and each of the plurality of network entity models is determined.

[0194] Method 1100 then proceeds to step 1108 where compressed communication is performed between the network entity and the UE using the second network entity model based at least in part on the compatibility information.

[0195] In one aspect, method 1100 also includes determining, based at least in part on the compatibility information, that the first network entity model is incompatible with the UE model and that the second network entity model is compatible with the UE model, wherein performing compressed communications using the second network entity model includes switching from the first network entity model to the second network entity model based at least in part on the second network entity model being compatible with the UE model.

[0196] In one aspect, method 1100 also includes identifying a plurality of network entity models compatible with the UE model, wherein switching from the first network entity model to the second network entity model includes determining that the second network entity model is more compatible with the UE model than other network entity models in the plurality of network entity models are compatible with the UE model.

[0197] In one aspect, method 1100 also includes determining, based at least in part on the compatibility information, that the first network entity model is less compatible with the UE model than the second network entity model is compatible with the UE model, wherein switching from the first network entity model to the second network entity model includes switching from the first network entity model to the second network entity model based at least in part on determining that the first network entity model is less compatible with the UE model than the second network entity model is compatible with the UE model.

[0198] In one aspect, method 1100 also includes determining, based at least in part on the compatibility information, that the first network entity model is compatible with the UE model, wherein switching from the first network entity model to the second network entity model includes determining not to switch from the first network entity model to the second network entity model based at least in part on determining that the first network entity model is compatible with the UE model.

[0199] In one aspect, determining that the first network entity model is compatible with the UE model includes determining that the first network entity model is more compatible with the UE model than other network entity models are compatible with the UE model.

[0200] In one aspect, method 1100 or any aspect related thereto may be performed by an apparatus such as Fig.14 The method 1100 is performed by a communication device 1400, which includes various components that are operable to, configured to, or adapted to perform the method 1100. The communication device 1400 is described in more detail below.

[0201] It should be noted that Fig.11 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with the present disclosure.

[0202] Fig.12 shows a method for use by network entities such as Figure 1 and Figure 3 BS110 or such Figure 2 A method 1200 of performing wireless communications with a decomposed base station is discussed.

[0203] The method 1200 begins at step 1202, where a situation identifier associated with a situation or one or more UE model identifiers respectively associated with one or more UE models for compressed communication between a UE and a network entity are received.

[0204] Method 1200 then proceeds to step 1204, where an indication of whether to switch from the first network entity model to the second network entity model is obtained based at least in part on the situation identifier or the one or more UE model identifiers.

[0205] The method 1200 then proceeds to step 1206, where a handover indication is selectively sent to the UE, the handover indication including an identifier associated with the UE model corresponding to the second network entity model.

[0206] In one aspect, receiving the situation identifier or one or more UE model identifiers includes receiving only the situation identifier, wherein the UE identifies the second network entity model and the UE model corresponding to the second network entity model based at least in part on the situation identifier.

[0207] In one aspect, the method 1200 also includes switching from the first network entity model to the second network entity model, wherein selectively sending the switching indication includes sending the switching indication based at least in part on switching from the first network entity model to the second network entity model.

[0208] In one aspect, method 1200 also includes determining whether to accept the one or more UE model identifiers based at least in part on the network constraint or based at least in part on the compatibility information.

[0209] In one aspect, method 1200 also includes switching from the first network entity model to the second network entity model based at least in part on accepting the one or more UE model identifiers, wherein selectively sending a switching indication includes sending a switching indication based at least in part on switching from the first network entity model to the second network entity model.

[0210] In one aspect, method 1200 also includes sending information indicative of a plurality of conditions including the condition.

[0211] In one aspect, receiving the condition identifier includes receiving an index associated with the condition.

[0212] In one aspect, receiving the condition identifier includes receiving a plurality of condition identifiers and a confidence indicator associated with each condition identifier of the plurality of condition identifiers.

[0213] In one aspect, the method 1200 further includes sending information indicating one or more reporting rules associated with the condition identifier or the one or more UE model identifiers.

[0214] In one aspect, the method 1200 also includes sending information indicating one or more other rules to be used by the UE to select one or more UE model identifiers based at least in part on the condition.

[0215] In one aspect, method 1200 or any aspect related thereto may be performed by an apparatus such as Fig.14 The method 1200 is performed by a communication device 1400, which includes various components that are operable to, configured to, or adapted to perform the method 1200. The communication device 1400 is described in more detail below.

[0216] Please note that Fig.12 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in accordance with the present disclosure.

[0217] Example Communication Device

[0218] Fig.13 Depicted are aspects of an example communication device 1300. In some aspects, the communication device 1300 is user equipment, such as described above with respect to Figure 1 and Figure 3 UE 120 is described.

[0219] The communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and / or a receiver). The transceiver 1308 is configured to transmit and receive signals for the communication device 1300, such as various signals as described herein, via an antenna 1310. The processing system 1302 may be configured to perform processing functions for the communication device 1300, including processing signals received and / or to be transmitted by the communication device 1300.

[0220] The processing system 1302 includes one or more processors 1320. In various aspects, the one or more processors 1320 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380, as described with respect to FIG. Figure 3 The one or more processors 1320 are coupled to the computer readable medium / memory 1330 via the bus 1306. In some aspects, the computer readable medium / memory 1330 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1320, cause the one or more processors 1320 to perform operations related to Fig. 9 Method 900 described Fig.10 Note that reference to a processor performing a function of the communication device 1300 may include one or more processors performing the function of the communication device 1300.

[0221] In the depicted example, computer readable medium / memory 1330 stores code 1331 (e.g., executable instructions) for performing, code 1332 for determining, code 1333 for transmitting, and code 1334 for receiving. The processing of codes 1331-1334 may enable communication device 1300 to perform operations related to Fig. 9 Method 900 described Fig.10 The method 1000 described herein or any related aspects.

[0222] The one or more processors 1320 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1330, including circuits for executing 1321, circuits for determining 1322, circuits for sending 1323, and circuits for receiving 1324. Processing using circuits 1321-1324 may enable the communication device 1300 to perform operations related to Fig. 9 Method 900 described Fig.10 The method 1000 described herein or any related aspects.

[0223] The various components of the communication device 1300 may provide for performing Fig. 9 Method 900 described Fig.10 Components of the method 1000 or any related aspects described herein. For example, components for sending, transmitting, or outputting for sending may include Figure 3 The transceiver 354 and / or antenna 352 and / or Fig.13 The transceiver 1308 and antenna 1310 of the communication device 1300 in FIG. 1304 may include Figure 3 The transceiver 354 and / or antenna 352 and / or Fig.13 The transceiver 1308 and antenna 1310 of the communication device 1300 in FIG.

[0224] Fig.14 Depicted are aspects of an example communication device. In some aspects, the communication device 1400 is a network entity such as Figure 1 and Figure 3 BS110 or such Figure 2 The decomposed base station in question.

[0225] The communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and / or a receiver) and / or a network interface 1412. The transceiver 1408 is configured to transmit and receive signals for the communication device 1400 via an antenna 1410, such as the various signals described herein. The network interface 1412 is configured to transmit and receive signals for the communication device 1400 via a communication link (such as the various signals described herein). Figure 2 The processing system 1402 may be configured to obtain and transmit signals for the communication device 1400 using the backhaul link, midhaul link, and / or fronthaul link described herein. The processing system 1402 may be configured to perform processing functions of the communication device 1400, including processing signals received and / or to be transmitted by the communication device 1400.

[0226] The processing system 1402 includes one or more processors 1420. In various aspects, the one or more processors 1420 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340, as described with respect to FIG. Figure 3 The one or more processors 1420 are coupled to the computer readable medium / memory 1430 via the bus 1406. In some aspects, the computer readable medium / memory 1430 is configured to store instructions (e.g., computer executable code) that, when executed by the one or more processors 1420, cause the one or more processors 1420 to perform operations related to the computer readable medium / memory 1430. Fig.11 Method 1100 described Fig.12 Note that reference to a processor of the communication device 1400 performing a function may include one or more processors of the communication device 1400 performing the function.

[0227] In the depicted example, computer readable medium / memory 1430 stores code 1431 (e.g., executable instructions) for executing, code 1432 for receiving, code 1433 for determining, code 1434 for obtaining, and code 1435 for sending. The processing of codes 1431-1435 may enable communication device 1400 to perform operations related to Fig.11 Method 1100 described Fig.12 The method 1200 described herein or any related aspects.

[0228] The one or more processors 1420 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1430, including circuits 1421 for executing, circuits 1422 for receiving, circuits 1423 for determining, circuits 1424 for obtaining, and circuits 1425 for sending. Processing using circuits 1421-1425 may enable the communication device 1400 to perform operations related to Fig.11 Method 1100 described Fig.12 The method 1200 described herein or any related aspects.

[0229] The various components of the communication device 1400 may provide for performing Fig.11 Method 1100 described Fig.12 Components of the method 1200 or any related aspects described herein. Components for sending, transmitting, or outputting for sending may include Figure 3 The transceiver 332 and / or antenna 334 and / or Fig.14 The transceiver 1408 and antenna 1410 of the communication device 1400 in FIG. 1404 may include Figure 3 The transceiver 332 and / or antenna 334 and / or Fig.14 The transceiver 1408 and antenna 1410 of the communication device 1400 in FIG.

[0230] Sample Clauses

[0231] Specific implementation examples are described in the following numbered clauses:

[0232] Clause 1: A method of wireless communication performed by a user equipment (UE), the method comprising: performing compressed communication between the UE and a network entity using a first model; determining a condition based at least in part on channel state information; sending an identifier associated with a second model to the network entity based at least in part on the condition; and performing compressed communication between the UE and the network entity using the second model.

[0233] Clause 2: A method according to clause 1, wherein sending the identifier associated with the second model to the network entity includes: identifying the second model based at least in part on the condition; and switching from the first model to the second model based at least in part on identifying the second model.

[0234] Clause 3: The method of clause 2, wherein switching from the first model to the second model comprises determining that the second model is to be used for the condition and the first model is not to be used for the condition.

[0235] Clause 4: A method according to clause 2, wherein switching from the first model to the second model includes determining, at least in part based on information associated with the first model and the second model, that performance of the second model associated with the condition is better than performance of the first model associated with the condition.

[0236] Clause 5: A method according to any one of clauses 1 to 4, wherein the condition is at least one of the following: the UE is in an indoor state or an outdoor state; the UE performs line-of-sight communication or non-line-of-sight communication; the UE uses a first provider or a second provider; the UE is in a first geographical location or a second geographical location; the UE communicates with a first service cell or a second service cell; channel conditions; or model characteristics.

[0237] Clause 6: A method as recited in any of clauses 1 to 5, further comprising receiving, from the network entity, information indicative of a plurality of conditions including the condition.

[0238] Clause 7: A method according to any one of clauses 1 to 6, wherein the one or more rules indicate a delay spread threshold, a signal-to-noise ratio (SNR) threshold or a Doppler spread threshold, and wherein determining the condition based at least in part on the channel state information and the one or more rules includes determining that the delay spread satisfies the delay spread threshold, determining that the SNR satisfies the SNR threshold or determining that the Doppler spread satisfies the Doppler spread threshold.

[0239] Clause 8: The method of any one of clauses 1 to 7, wherein one of the first model or the second model is based on only a single condition, and the other of the first model and the second model is based on multiple conditions.

[0240] Clause 9: According to the method described in any one of clauses 1 to 8, the method further includes: monitoring multiple models including at least one inactive model; detecting the condition or another condition based at least in part on monitoring at least one active model among the multiple models and at least one inactive model among the multiple models; and switching to a third model among the multiple models based at least in part on detecting the condition or the other condition.

[0241] Clause 10: A method of wireless communication performed by a network entity, the method comprising: performing compressed communication between the network entity and a user equipment (UE) using a first network entity model; receiving from the UE an identifier associated with a UE model used for compressed communication between the UE and the network entity; determining compatibility information associated with the UE model and each of a plurality of network entity models; and performing compressed communication between the network entity and the UE using a second network entity model based at least in part on the compatibility information.

[0242] Clause 11: The method according to clause 10 further comprises: determining, based at least in part on the compatibility information, that the first network entity model is incompatible with the UE model and that the second network entity model is compatible with the UE model, wherein performing compressed communication using the second network entity model comprises: switching from the first network entity model to the second network entity model based at least in part on the compatibility of the second network entity model with the UE model.

[0243] Clause 12: The method of clause 11, further comprising identifying a plurality of network entity models compatible with the UE model, wherein switching from the first network entity model to the second network entity model comprises determining that the second network entity model is more compatible with the UE model than other network entity models in the plurality of network entity models are compatible with the UE model.

[0244] Clause 13: A method according to clause 11, the method also includes determining, based at least in part on the compatibility information, that the first network entity model is less compatible with the UE model than the second network entity model is compatible with the UE model, wherein switching from the first network entity model to the second network entity model includes: switching from the first network entity model to the second network entity model based at least in part on determining that the first network entity model is less compatible with the UE model than the second network entity model is compatible with the UE model.

[0245] Clause 14: A method according to clause 11, the method also includes determining, based at least in part on the compatibility information, that the first network entity model is compatible with the UE model, wherein switching from the first network entity model to the second network entity model includes determining not to switch from the first network entity model to the second network entity model based at least in part on determining that the first network entity model is compatible with the UE model.

[0246] Clause 15: The method of clause 14, wherein determining that the first network entity model is compatible with the UE model comprises determining that the first network entity model is more compatible with the UE model than other network entity models are compatible with the UE model.

[0247] Clause 16: A method of wireless communication performed by a user equipment (UE), the method comprising: determining a condition based at least in part on channel state information; sending a condition identifier associated with the condition or one or more model identifiers respectively associated with one or more models to a network entity; receiving a switching indication from the network entity indicating whether to switch from a first model to a second model; and performing compressed communication with the network entity using the first model or the second model based at least in part on the switching indication.

[0248] Clause 17: A method according to clause 16, wherein performing the compressed communication with the network entity using the first model or the second model includes: determining to switch from the first model to the second model based at least in part on the switching indication; and switching from the first model to the second model based at least in part on determining to switch from the first model to the second model.

[0249] Clause 18: The method of any of clauses 16 to 17, further comprising receiving information indicative of a plurality of conditions including the condition.

[0250] Clause 19: The method of clause 18, wherein sending the status identifier comprises sending an index associated with the status.

[0251] Clause 20: The method of any of clauses 16 to 19, wherein sending the situation identifier comprises sending a plurality of situation identifiers and a confidence indicator associated with each of the plurality of situation identifiers.

[0252] Clause 21: The method of any of clauses 16 to 20, further comprising receiving information indicative of one or more reporting rules associated with the condition identifier or the one or more model identifiers.

[0253] Clause 22: A method according to any one of clauses 16 to 21, wherein sending the condition identifier or the one or more model identifiers comprises sending only the condition identifier, and wherein receiving the switching indication comprises receiving a switching indication including an indication of the second model.

[0254] Clause 23: A method as described in any of clauses 16 to 22, wherein sending the one or more model identifiers comprises sending at least one of a UE model identifier and a network entity model identifier.

[0255] Clause 24: A method as set forth in any of clauses 16 to 23, the method further comprising receiving information indicative of one or more further rules to be used by the UE to select the one or more model identifiers based at least in part on the condition.

[0256] Clause 25: A method according to any one of clauses 16 to 24, wherein the condition is at least one of the following: the UE is in an indoor state or an outdoor state; the UE performs line-of-sight communication or non-line-of-sight communication; the UE uses a first provider or a second provider; the UE is in a first geographical location or a second geographical location; the UE communicates with a first service cell or a second service cell; channel conditions; or model characteristics.

[0257] Clause 26: A method according to any one of clauses 16 to 25, wherein the one or more rules indicate a delay spread threshold, a signal-to-noise ratio (SNR) threshold, or a Doppler spread threshold, and wherein determining the condition based at least in part on the one or more rules includes determining that the delay spread satisfies the delay spread threshold, determining that the SNR satisfies the SNR threshold, or determining that the Doppler spread satisfies the Doppler spread threshold.

[0258] Clause 27: A method of wireless communication performed by a network entity, the method comprising: receiving from a user equipment (UE) a situation identifier associated with a situation or one or more UE model identifiers respectively associated with one or more UE models used for compressed communication between the UE and the network entity; obtaining an indication of whether to switch from a first network entity model to a second network entity model based at least in part on the situation identifier or the one or more UE model identifiers; and selectively sending a switching indication to the UE, the switching indication including an identifier associated with the UE model corresponding to the second network entity model.

[0259] Clause 28: A method according to clause 27, wherein receiving the situation identifier or the one or more UE model identifiers includes receiving only the situation identifier, wherein the UE identifies the second network entity model and the UE model corresponding to the second network entity model based at least in part on the situation identifier.

[0260] Clause 29: The method of clause 28, further comprising switching from the first network entity model to the second network entity model, wherein selectively sending the switching indication comprises sending the switching indication based at least in part on switching from the first network entity model to the second network entity model.

[0261] Clause 30: A method as described in any of clauses 27 to 29, the method further comprising determining whether to accept the one or more UE model identifiers based at least in part on a network constraint or based at least in part on compatibility information.

[0262] Clause 31: A method according to clause 30, the method also includes switching from the first network entity model to the second network entity model based at least in part on accepting the one or more UE model identifiers, wherein selectively sending the switching indication includes sending the switching indication based at least in part on switching from the first network entity model to the second network entity model.

[0263] Clause 32: A method as described in any of clauses 27 to 31, further comprising sending information indicative of a plurality of conditions including the condition.

[0264] Clause 33: The method of clause 32, wherein receiving the condition identifier comprises receiving an index associated with the condition.

[0265] Clause 34: The method of clause 32, wherein receiving the condition identifier comprises receiving a plurality of condition identifiers and a confidence indicator associated with each of the plurality of condition identifiers.

[0266] Clause 35: A method as described in any of clauses 27 to 34, the method further comprising sending information indicating one or more reporting rules associated with the situation identifier or the one or more UE model identifiers.

[0267] Clause 36: The method of clause 35, further comprising: sending information indicating one or more other rules to be used by the UE to select the one or more UE model identifiers based at least in part on the condition.

[0268] Clause 37: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of clauses 1 to 36.

[0269] Clause 38: An apparatus for wireless communications, the apparatus comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of clauses 1 to 36.

[0270] Clause 39: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of clauses 1 to 36.

[0271] Clause 40: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of clauses 1-36.

[0272] Clause 41: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method according to one or more of clauses 1 to 36.

[0273] Additional considerations

[0274] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limited to the scope, applicability or aspects set forth in the claims. 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. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may omit, replace or add various procedures or components as appropriate. For example, the described methods may be performed in an order different from the order described, and various actions may be added, omitted or combined. In addition, the features described for some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality or structures and functionality that are supplementary or alternative to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0275] The various illustrative logic blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration).

[0276] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items (including single members). For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0277] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, etc. In addition, "determine" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. In addition, "determine" may include resolving, selecting, choosing, establishing, etc.

[0278] The method disclosed herein includes one or more actions for implementing the method. The method actions are interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. In addition, the various operations of the method described above may be performed by any appropriate component capable of performing the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0279] The following claims are not intended to be limited to the various aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless otherwise specified, 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. Any claim element is not interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "parts for...". All structural and functional equivalents of the elements of the various aspects described throughout this 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, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims.

Claims

1. A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: one or more memories including processor-executable instructions; and one or more processors configured to execute the processor-executable instructions and cause the UE to: performing compressed communication between the UE and a network entity using a first model; determining a condition based at least in part on the channel state information; sending, based at least in part on the condition, an identifier associated with a second model to the network entity; as well as Compressed communications are performed between the UE and the network entity using the second model based at least in part on the condition.

2. The UE according to claim 1, wherein in order for the UE to send the identifier associated with the second model to the network entity, the one or more processors are configured to cause the UE to: identifying the second model based at least in part on the condition; and The method switches from the first model to the second model based at least in part on identifying the second model.

3. The UE of claim 2, wherein in order to cause the UE to switch from the first model to the second model, the one or more processors are configured to cause the UE to determine that the second model is to be used for the situation and the first model is not to be used for the situation.

4. The UE according to claim 2, wherein in order to cause the UE to switch from the first model to the second model, the one or more processors are configured to cause the UE to determine, at least in part based on information associated with the first model and the second model, that the performance of the second model associated with the condition is better than the performance of the first model associated with the condition.

5. The UE according to claim 1, wherein the condition is at least one of the following: The UE is in an indoor state or an outdoor state; The UE performs line-of-sight communication or non-line-of-sight communication; The UE uses a first supplier or a second supplier; The UE is in a first geographical location or a second geographical location; The UE communicates with the first serving cell or the second serving cell; Channel conditions; or Model features.

6. The UE of claim 1 , wherein determining the condition based at least in part on the channel state information comprises determining the condition based at least in part on the channel state information and one or more rules, wherein the one or more rules indicate a delay spread threshold, a signal-to-noise ratio (SNR) threshold, or a Doppler spread threshold, and wherein in order for the UE to determine the condition based at least in part on the channel state information and the one or more rules, the one or more processors are configured to cause the UE to determine that the delay spread satisfies the delay spread threshold, determines that the SNR satisfies the SNR threshold, or determines that the Doppler spread satisfies the Doppler spread threshold. 7 . The UE of claim 1 , wherein one of the first model or the second model is trained based on only a single condition, and the other of the first model and the second model is trained based on multiple conditions.

8. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: monitoring a plurality of models including at least one inactive model; detecting the condition or another condition based at least in part on monitoring at least one active model of the plurality of models and the at least one inactive model of the plurality of models; and Switching to a third model of the plurality of models is performed based at least in part on detecting the condition or the other condition.

9. The UE of claim 1, wherein in order for the UE to perform the compressed communication, the one or more processors are configured to cause the UE to send or receive a compressed representation of channel state information.

10. A network entity configured for wireless communication, the network entity comprising: one or more memories including processor-executable instructions; and one or more processors configured to execute the processor-executable instructions and cause the network entity to: performing compressed communications between the network entity and a user equipment (UE) using a first network entity model; receiving, from the UE, an identifier associated with a UE model for compressed communications between the UE and the network entity; determining compatibility information associated with the UE model and each of a plurality of network entity models; as well as Compressed communications are performed between the network entity and the UE using a second network entity model based at least in part on the compatibility information.

11. The network entity of claim 10, wherein the one or more processors are further configured to cause the network entity to: determining, based at least in part on the compatibility information, that the first network entity model is incompatible with the UE model and the second network entity model is compatible with the UE model, Wherein, in order to enable the network entity to perform compressed communication using the second network entity model, the one or more processors are configured to enable the network entity to: Switching from the first network entity model to the second network entity model is based at least in part on the second network entity model being compatible with the UE model.

12. The network entity of claim 11, wherein the one or more processors are further configured to cause the network entity to identify a plurality of network entity models that are compatible with the UE model, wherein in order to cause the network entity to switch from the first network entity model to the second network entity model, the one or more processors are configured to cause the network entity to determine that the second network entity model is more compatible with the UE model than other network entity models in the plurality of network entity models are compatible with the UE model.

13. The network entity of claim 11 , wherein the one or more processors are further configured to cause the network entity to determine, based at least in part on the compatibility information, that the first network entity model is less compatible with the UE model than the second network entity model is compatible with the UE model, and wherein in order to cause the network entity to switch from the first network entity model to the second network entity model, the one or more processors are configured to cause the network entity to switch from the first network entity model to the second network entity model based at least in part on determining that the first network entity model is less compatible with the UE model than the second network entity model is compatible with the UE model.

14. The network entity of claim 11, wherein the one or more processors are further configured to cause the network entity to determine that the first network entity model is compatible with the UE model based at least in part on the compatibility information, wherein in order to cause the network entity to switch from the first network entity model to the second network entity model, the one or more processors are configured to cause the network entity to determine not to switch from the first network entity model to the second network entity model based at least in part on determining that the first network entity model is compatible with the UE model.

15. A user equipment (UE) configured for wireless communication, the user equipment (UE) comprising: one or more memories including processor-executable instructions; and one or more processors configured to execute the processor-executable instructions and cause the UE to: determining a condition based at least in part on the channel state information; sending a situation identifier associated with the situation or one or more model identifiers respectively associated with one or more models to a network entity; receiving a switching indication from the network entity indicating whether to switch from the first model to the second model; and Compressed communications are performed with the network entity using the first model or the second model based at least in part on the handover indication.

16. The UE of claim 15, wherein in order for the UE to perform the compressed communication with the network entity using the first model or the second model, the one or more processors are configured to cause the UE to: Determining to switch from the first model to the second model based at least in part on the switching indication; and Switching from the first model to the second model is based at least in part on determining to switch from the first model to the second model.

17. The UE of claim 15, wherein the one or more processors are further configured to cause the UE to receive information indicating multiple conditions including the condition, wherein in order for the UE to send the condition identifier, the one or more processors are configured to cause the UE to send an index associated with the condition.

18. The UE of claim 15, wherein in order for the UE to send the situation identifier, the one or more processors are configured to cause the UE to send a plurality of situation identifiers and a confidence indicator associated with each of the plurality of situation identifiers.

19. The UE of claim 15, wherein the one or more processors are further configured to cause the UE to receive information indicating one or more reporting rules associated with the condition identifier or the one or more model identifiers.

20. The UE according to claim 15, wherein in order for the UE to send the situation identifier or the one or more model identifiers, the one or more processors are configured to cause the UE to send only the situation identifier, and wherein in order for the UE to receive the switching indication, the one or more processors are configured to cause the UE to receive a switching indication including an indication of the second model.

21. The UE of claim 15, wherein in order for the UE to transmit the one or more model identifiers, the one or more processors are configured to cause the UE to transmit at least one of a UE model identifier and a network entity model identifier.

22. The UE of claim 15, wherein the one or more processors are further configured to cause the UE to receive information indicative of one or more rules to be used by the UE to select the one or more model identifiers based at least in part on the condition.

23. A method of wireless communication performed by a user equipment (UE), the method comprising: performing compressed communication between the UE and a network entity using a first model; determining a condition based at least in part on the channel state information; sending, based at least in part on the condition, an identifier associated with a second model to the network entity; as well as Compressed communications are performed between the UE and the network entity using the second model based at least in part on the condition.

24. The method of claim 23, wherein sending the identifier associated with the second model to the network entity comprises: identifying the second model based at least in part on the condition; as well as The method switches from the first model to the second model based at least in part on identifying the second model.

25. The method of claim 24, wherein switching from the first model to the second model comprises determining that the second model is to be used for the condition and the first model is not to be used for the condition.

26. The method of claim 24, wherein switching from the first model to the second model comprises determining, based at least in part on information associated with the first model and the second model, that performance of the second model associated with the condition is better than performance of the first model associated with the condition.

27. The method of claim 23, wherein the condition is at least one of: The UE is in an indoor state or an outdoor state; The UE performs line-of-sight communication or non-line-of-sight communication; The UE uses a first supplier or a second supplier; The UE is in a first geographical location or a second geographical location; The UE communicates with the first serving cell or the second serving cell; Channel conditions; or Model features.

28. The method of claim 23, further comprising receiving information from the network entity indicating a plurality of conditions including the condition.

29. A method according to claim 23, wherein determining the condition based at least in part on the channel state information includes determining the condition based at least in part on the channel state information and one or more rules, wherein the one or more rules indicate a delay spread threshold, a signal-to-noise ratio (SNR) threshold, or a Doppler spread threshold, and wherein determining the condition based at least in part on the channel state information and the one or more rules includes determining that the delay spread satisfies the delay spread threshold, determining that the SNR satisfies the SNR threshold, or determining that the Doppler spread satisfies the Doppler spread threshold.

30. The method of claim 23, wherein performing the compressed communication comprises sending or receiving a compressed representation of channel state information.

Images