Techniques for downloading models in wireless communications

Abstract

Aspects described herein relate to receiving, from a network node, a list of support model or model structure (MS) identifiers (IDs) for each machine learning function name (MLFN) or machine learning feature (MLF) at the network node; updating the capability at the UE to an updated capability based on the support model or the list of MS IDs for each MLFN or MLF at the network node; and downloading, at the UE and from a model repository, one or more models or MSs for each MLFN or MLF based on the updated capabilities and available resources at the UE. Other aspects relate to sending the list that supports a model or MS ID and the use of a model or MS ID configured for a particular MLFN or MLF.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application No. 17 / 886,381, filed on August 11, 2022, entitled “TECHNIQUES FOR DOWNLOADING MODELS IN WIRELESS COMMUNICATIONS,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to techniques for downloading artificial intelligence (AI) or machine learning (ML) based models. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. For example, the fifth generation (5G) wireless communication technology, which may be referred to as 5G New Radio (5G NR), is designed to expand and support diverse usage scenarios and applications for current mobile network generations. On the one hand, 5G communication technology may include: enhanced mobile broadband addressing people-centric use cases for accessing multimedia content, services, and data; ultra-reliable low-latency communications (URLLC) with certain specifications for latency and reliability; and massive machine-type communications that may allow very large numbers of connected devices and the transmission of relatively small amounts of non-delay-sensitive information. Summary of the invention

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] According to one aspect, a device for wireless communication is provided, the device comprising: a processor; a memory coupled to the processor, and instructions stored in the memory. The instructions, when executed by the processor, are operable to cause the device to: receive a list of supported models or model structure (MS) identifiers (IDs) for each machine learning function name (MLFN) or machine learning feature (MLF) at the network node from a network node; update the capabilities at the device to updated capabilities based on the list of supported models or MS IDs for each MLFN or MLF at the network node; and download one or more models or MSs for each MLFN or MLF from a model repository based on the updated capabilities and available resources at the device.

[0008] According to another aspect, an apparatus for wireless communication is provided, the apparatus comprising: a processor; a memory coupled to the processor, and instructions stored in the memory. The instructions, when executed by the processor, are operable to cause the apparatus to: send a list of supported models or MS IDs for each MLFN or MLF at the apparatus to a UE, and receive a request for downloading one or more models or MSs from a model repository based on the list of supported models or MS IDs at the apparatus to the UE and based on the list of supported models or MS IDs.

[0009] According to another aspect, a method for wireless communication at a UE is provided, the method comprising: receiving a list of supported models or MS IDs for each MLFN or MLF at the network node from a network node; updating capabilities at the UE to updated capabilities based on the list of supported models or MS IDs for each MLFN or MLF at the network node; and downloading one or more models or MSs for each MLFN or MLF at the UE and from a model repository based on the updated capabilities and available resources at the UE.

[0010] On the other hand, a method for performing wireless communication at a network node is provided, the method comprising: sending, to a UE, a list of supported models or MS IDs for each MLFN or MLF at the network node; and receiving, to the UE and based on the list of supported models or MS IDs, a request to download one or more models or MSs from a model repository based on the list of supported models or MS IDs at the network node.

[0011] In a further aspect, an apparatus for wireless communication is provided, the apparatus comprising: a transceiver; a memory configured to store instructions; and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute the instructions to perform the operations of the methods described herein. In another aspect, an apparatus for wireless communication is provided, the apparatus comprising means for performing the operations of the methods described herein. In yet another aspect, a computer-readable medium is provided, the computer-readable medium comprising code executable by one or more processors to perform the operations of the methods described herein.

[0012] To achieve the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided to illustrate rather than limit the disclosed aspects, wherein like numerals represent like elements, and in which:

[0014] Figure 1 An example of a wireless communication system according to various aspects of the present disclosure is illustrated;

[0015] Figure 2 is a diagram illustrating an example of a decomposed base station architecture according to various aspects of the present disclosure;

[0016] Figure 3 is a block diagram illustrating an example of a user equipment (UE) according to various aspects of the present disclosure;

[0017] Figure 4 is a block diagram illustrating an example of a base station according to various aspects of the present disclosure;

[0018] Figure 5 is a flow chart illustrating an example of a method for downloading a model or model structure (MS) identifier (ID) supported or to be used for one or more machine learning function names (MLFNs) or machine learning features (MLFs) according to aspects described herein;

[0019] Figure 6 is a flow chart illustrating an example of a method for configuring a node to download models or MS IDs supported or to be used for one or more MLFNs or MLFs in accordance with aspects described herein;

[0020] Figure 7An example of a system for out-of-band model download and model update at a UE is illustrated;

[0021] Figure 8 An example of a system for on-demand model download and model update at a UE is illustrated;

[0022] Fig. 9 An example of a system for model downloading by a UE is illustrated; and

[0023] Fig.10 is a block diagram illustrating an example of a multiple-input multiple-output (MIMO) communication system including a base station and UEs according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0024] Various aspects are now described with reference to the accompanying drawings. In the following description, for the purpose of explanation, in order to provide a thorough understanding of one or more aspects, numerous specific details are described. However, it is apparent that such aspects can be practiced without these specific details.

[0025] The features described overall relate to downloading artificial intelligence (AI) or machine learning (ML) based models in wireless communications. In some wireless communication technologies, such as the fifth generation (5G) new radio (NR), AI or ML can be used to perform various processes, such as encoding and sending channel state information (CSI) feedback, performing beam management, performing high positioning accuracy of indoor and outdoor devices, performing dynamic discontinuous reception (DRX) switching, or other physical layer procedures, medium access control (MAC) layer processes, etc. In some examples, the user equipment (UE) and / or the network node can obtain models for performing these processes to reduce the amount of information to be sent as part of these processes. This can improve the efficiency of performing these processes, can allow for increased data throughput, improved resource utilization, etc. In some examples of AI / ML-based processes, multiple models can be defined for each machine learning function name (MLFN) or machine learning feature (MLF), where each MLFN can be an identifier corresponding to a machine learning function that can be performed between the UE and the network node. The MLF can also indicate a machine learning feature or function that can be performed between the UE and the network node. A single ML structure (MS) may have multiple parameter sets (PS), for example, each PS may have a different weight.

[0026] As AI / ML-based processes are further enhanced, more features may be introduced, which may be associated with a large number of models and associated parameter sets. However, the UE may have limited memory to store the MS or PS. Therefore, the various aspects described herein relate to an efficient mechanism for UE capability signaling and / or dynamic model downloading so that the UE can store the models that it can use or prefer to use. In one example, support for MS or PS may be dynamically updated at the UE or network, and therefore, the aspects described herein may facilitate the UE to download the required MS or PS at runtime. In addition, actual hardware such as memory, processors, and hardware accelerators may be limited at the UE. Therefore, a limited number of models or MSs and corresponding PSs are available at the UE. In some aspects described herein, the MS or PS may be dynamically downloaded and removed (from memory) based on the available hardware at the UE. According to the various aspects described herein, downloading the model at the UE may be out-of-band or on-demand. In any case, the dynamic download of the model may allow the UE to store and use the required models, MS, and PS when the required models, MS, and PS become available, and prevent the storage of other unused models to release memory and processing resources at the UE.

[0027] The following will refer to Figures 1 to 10 The described features are presented in more detail.

[0028] As used in this application, the terms "component", "module", "system", etc. are intended to include computer-related entities, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but not limited to: a process running on a processor, a processor, an object, an executable file, a thread of execution, a program, and / or a computer. By way of example, both an application running on a computing device and a computing device can be a component. One or more components may exist in a process and / or a thread of execution, and a component may be located in a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components may communicate by means of local and / or remote processes, such as according to signals having one or more data packets (such as data from a component as follows: the component interacts with another component in a local system, a distributed system, and / or interacts with other systems across a network such as the Internet).

[0029] The technology described herein can be used for various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, single carrier FDMA and other systems. The terms "system" and "network" can often be used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 versions 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Speed ​​Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM TM Etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents of an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents of an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used for the above-mentioned systems and radio technologies as well as other systems and radio technologies, including cellular (e.g., LTE) communications on shared radio frequency spectrum bands. However, the following description describes an LTE / LTE-A system for example purposes, and LTE terminology is used in most of the following descriptions, but these techniques can also be applied beyond LTE / LTE-A applications (e.g., to fifth generation (5G) new radio (NR) networks or other next generation communication systems).

[0030] The following description provides examples, but does not limit the scope, applicability or examples set forth in the claims. Without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Each example may ignore, replace or add each procedure or component as appropriate. For example, the method described may be performed in a different order than described, and various steps may be added, omitted or combined. In addition, the features described with respect to some examples may be combined in other examples.

[0031] Various aspects or features will be presented with respect to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that the various systems may include additional devices, components, modules, etc. and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Combinations of these methods may also be used.

[0032] Figure 1 1 is a diagram illustrating an example of a wireless communication system and an access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) may include a base station 102, a UE 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. The base station 102 may include a macro cell (a high power cellular base station) and / or a small cell (a low power cellular base station). The macro cell may include a base station. The small cell may include a femto cell, a pico cell, and a micro cell. In one example, the base station 102 may also include a gNB 180, as further described herein. In one example, in accordance with various aspects described herein, some nodes of the wireless communication system may have a modem 340 and a UE communication component 342 for downloading a model or MS ID supported or to be used for one or more MLFNs or MLFs. In addition, in accordance with various aspects described herein, some nodes may have a modem 440 and a BS communication component 442 for configuring the node to download a model or MS ID supported or used for one or more MLFNs or MLFs. Although UE 104 is shown as having a modem 340 and a UE communication component 342, and base station 102 / gNB 180 is shown as having a modem 440 and a BS communication component 442, this is an illustrative example, and substantially any node or type of node may include a modem 340 and a UE communication component 342 and / or a modem 440 and a BS communication component 442 to provide the corresponding functionality described herein.

[0033] The base station 102 configured for 4G LTE (which may be 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 backhaul link 132 (e.g., using an S1 interface). The base station 102 configured for 5G NR (which may be collectively referred to as the Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a backhaul link 184. The base station 102 may perform one or more of the following functions, among other functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., through EPC 160 or 5GC 190) over backhaul link 134 (e.g., using an X2 interface). Backhaul link 134 may be wired or wireless.

[0034] The base station 102 may communicate wirelessly with one or more UEs 104. Each of the base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group (which may be referred to as a closed subscriber group (CSG)). The communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth per carrier allocated in a carrier aggregation of up to Yx MHz (e.g., corresponding to x component carriers) for transmission in the DL and / or UL directions. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0035] In another example, some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. 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), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

[0036] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communication.

[0037] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as the 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0038] The base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include an eNB, a gNodeB (gNB), or other types of base stations. Some base stations (such as gNB 180) may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When the gNB 180 operates at mmW or near mmW frequencies, the gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz with a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can extend down to frequencies of 3 GHz with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using the mmW / near mmW radio frequency bands have extremely high path losses and short distances. The mmW base station 180 can utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range. The base station 102 mentioned in this article may include gNB180.

[0039] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. The MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related billing information.

[0040] 5GC 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196. AMF 192 may be a control node that handles signaling between UE 104 and 5GC 190. In general, AMF 192 may provide QoS flow and session management. User Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be transmitted through UPF 195. UPF 195 may provide UE IP address allocation and other functions for one or more UEs. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0041] Base stations may also be referred to as gNBs, Node Bs, evolved Node Bs (eNBs), access points, transceiver base stations, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmit receive points (TRPs), or some other suitable terminology. Base station 102 provides an access point to EPC 160 or 5GC 190 for UE 104. Examples of UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). IoT UEs may include machine type communication (MTC) / enhanced MTC (eMTC, also referred to as Category (CAT)-M or Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, and other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0042] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS, e.g., BS102), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

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

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

[0045] In one example, the BS communication component 442 may send a list of models or MS IDs supported by each MLFN or MLF. The UE communication component 342 may receive a list of models or MS IDs supported by each MLFN or MLF from a network node (e.g., such as or via the base station 102). The UE communication component 342 may update its capabilities based on the received list. In one example, the UE communication component 342 may use the list to download one or more models or MSs, for example, from a model repository (MR), and may update capability information to the network node to receive configured models or MS IDs (and / or PS) for one or more MLFNs or MLFs. For example, the BS communication component 442 may receive updated capability information from the UE 104, and may configure one or more of the models or MSs for use by the UE 104. In another example, the UE communication component 342 may use the list received from the network node to update capability information to the network point, and the network node may select one or more models or MS IDs for the UE 104 to use for one or more MLFNs or MLFs. For example, BS communication component 442 can indicate the selected one or more models or MS IDs to UE 104, and if necessary, UE communication component 342 can download the selected one or more models or MS IDs, for example, from MR. UE communication component 342 can indicate to BS communication component 442 when the one or more models or MS are ready for use.

[0046] Figure 2 A diagram illustrating an example of a disaggregated base station 200 architecture is shown. 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 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 240.

[0047] 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 these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0048] 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. CU210 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 210 may be implemented to communicate with DU 230 for network control and signaling.

[0049] 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.) depending at least in part on functional splits such as those defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 230 may further 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.

[0050] 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 104. In some implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the DU 230 and CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0051] 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 instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 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. Additionally, 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 .

[0052] The non-RT RIC 215 may be configured to include logic functions that implement 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 communicate 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 implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.

[0053] 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 adjust 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 the creation of RAN management policies (such as A1 policies).

[0054] In one example, as described herein, the BS communication component 442 can be implemented at least partially within the CU 210, and can send a list of supported models or MS IDs to the UE via one or more DUs 230, receive UE capability information via one or more DUs 230, select a model or MS for the UE via one or more DUs 230, etc. In another example, as described herein, the BS communication component 442 can be implemented at least partially within the DU 230, and can send a list of supported models or MS IDs to the UE via one or more RUs 240, receive UE capability information via one or more RUs 240, select a model or MS for the UE via one or more RUs 240, etc.

[0055] Now turn to Figures 3 to 10 , various aspects are described with reference to one or more components and one or more methods that can perform the actions or operations described herein, where aspects in dashed lines may be optional. Figures 5 to 9 The operations described in the present invention are presented in a particular order and / or as being performed by example components, but it should be understood that the order of these actions and the components performing these actions may vary depending on the specific implementation. In addition, it should be understood that the following actions, functions, and / or components described may be performed by a specially programmed processor, a processor executing specially programmed software or computer-readable media, or any other combination of hardware components and / or software components capable of performing the described actions or functions.

[0056] refer to Figure 3In accordance with various aspects described herein, an example of a specific implementation of UE 104 may include a variety of components, some of which have been described above and are further described herein, including components such as one or more processors 312 and memory 316 that communicate via one or more buses 344 and a transceiver 302, which can operate in conjunction with a modem 340 and / or UE communication component 342 to download models or MS IDs supported or to be used for one or more MLFNs or MLFs.

[0057] In one aspect, the one or more processors 312 may include the modem 340 and / or may be part of the modem 340 using one or more modem processors. Thus, various functions associated with the UE communication component 342 may be included in the modem 340 and / or the processor 312, and in one aspect, may be performed by a single processor, while in other aspects, different ones of these functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 312 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with the transceiver 302. In other aspects, some of the features of the one or more processors 312 and / or the modem 340 associated with the UE communication component 342 may be performed by the transceiver 302.

[0058] In addition, the memory 316 may be configured to store local versions of the data and / or applications 375 used herein, or one or more of the UE communication components 342 and / or its subcomponents executed by the at least one processor 312. The memory 316 may include any type of computer-readable medium that can be used by a computer or at least one processor 312, such as random access memory (RAM), read-only memory (ROM), tape, disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, when the UE 104 is operating at least one processor 312 to execute one or more of the UE communication components 342 and / or its subcomponents, the memory 316 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes and / or data associated therewith that define the UE communication components 342 and / or its subcomponents.

[0059] The transceiver 302 may include at least one receiver 306 and at least one transmitter 308. The receiver 306 may include hardware, firmware, and / or software code executable by a processor for receiving data, the code including instructions and stored in a memory (e.g., a computer-readable medium). The receiver 306 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 306 may receive signals transmitted by at least one base station 102. Additionally, the receiver 306 may process such received signals and may also obtain measurements of these signals, such as but not limited to Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. The transmitter 308 may include hardware, firmware, and / or software code executable by a processor for transmitting data, the code including instructions and stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 308 may include, but are not limited to, an RF transmitter.

[0060] In addition, in an aspect, the UE 104 may include an RF front end 388 that may operate in communication with the one or more antennas 365 and the transceiver 302 to receive and transmit radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by the UE 104. The RF front end 388 may be connected to the one or more antennas 365 and may include one or more low noise amplifiers (LNAs) 390, one or more switches 392, one or more power amplifiers (PAs) 398, and one or more filters 396 for transmitting and receiving RF signals.

[0061] In one aspect, the LNA 390 can amplify the received signal at a desired output level. In one aspect, each LNA 390 can have a specified minimum gain value and a maximum gain value. In one aspect, the RF front end 388 can use one or more switches 392 to select a particular LNA 390 and its specified gain value based on the desired gain value for a particular application.

[0062] In addition, for example, the RF front end 388 can use one or more PAs 398 to amplify the signal for RF output at a desired output power level. In one aspect, each PA 398 can have a specified minimum gain value and a maximum gain value. In one aspect, the RF front end 388 can use one or more switches 392 to select a particular PA 398 and its specified gain value based on a desired gain value for a particular application.

[0063] In addition, for example, the RF front end 388 can use one or more filters 396 to filter the received signal to obtain an input RF signal. Similarly, in one aspect, for example, the output from the corresponding PA 398 can be filtered using a corresponding filter 396 to produce an output signal for transmission. In one aspect, each filter 396 can be connected to a specific LNA 390 and / or PA 398. In one aspect, the RF front end 388 can use one or more switches 392 to select a transmit path or a receive path using a specified filter 396, LNA 390, and / or PA 398 based on a configuration as specified by the transceiver 302 and / or the processor 312.

[0064] Thus, the transceiver 302 can be configured to transmit and receive wireless signals through one or more antennas 365 via the RF front end 388. In one aspect, the transceiver can be tuned to operate at a specified frequency so that the UE 104 can communicate with, for example, one or more base stations 102 or one or more cells associated with one or more base stations 102. In one aspect, for example, the modem 340 can configure the transceiver 302 to operate at a specified frequency and power level based on a UE configuration of the UE 104 and a communication protocol used by the modem 340.

[0065] In one aspect, the modem 340 may be a multi-band multi-mode modem that processes digital data and communicates with the transceiver 302 so that the digital data is transmitted and received using the transceiver 302. In one aspect, the modem 340 may be multi-band and configured to support multiple frequency bands for a specific communication protocol. In one aspect, the modem 340 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 340 may control one or more components (e.g., RF front end 388, transceiver 302) of the UE 104 to enable the sending and / or receiving of signals from the network based on a specified modem configuration. In one aspect, the modem configuration may be based on the mode of the modem and the frequency band used. In another aspect, the modem configuration may be based on UE configuration information associated with the UE 104 as provided by the network during cell selection and / or cell reselection.

[0066] In one aspect, according to various aspects described herein, the UE communication component 342 may optionally include: a capability component 352 for indicating UE capabilities relative to a model or MS ID; a model download component 354 for downloading one or more models or MSs from an MR; and / or a model utilization component 356 for utilizing or indicating utilization or preparation of a model or MS for one or more MLFNs or MLFs.

[0067] In one aspect, processor 312 may correspond to combining Fig.10 Similarly, the memory 316 may correspond to one or more processors in conjunction with the UE described in the embodiment of the present invention. Fig.10 The memory described by the UE in.

[0068] refer to Figure 4 In accordance with various aspects described herein, an example of a specific implementation of a base station 102 (e.g., base station 102 and / or gNB 180 as described above) may include various components, some of which have been described above, but include components such as one or more processors 412 and memory 416 that communicate via one or more buses 444 and a transceiver 402, which may operate in conjunction with a modem 440 and a BS communication component 442 for configuring a node to download models or MS IDs supported or to be used for one or more MLFNs or MLFs.

[0069] The transceiver 402, receiver 406, transmitter 408, one or more processors 412, memory 416, applications 475, bus 444, RF front end 488, LNA 490, switch 492, filter 496, PA 498 and one or more antennas 465 may be the same as or similar to the corresponding components of UE 104 described above, but are configured or otherwise programmed for base station operation rather than UE operation.

[0070] In one aspect, in accordance with the aspects described herein, the BS communication component 442 may optionally include: a model indication component 452 for indicating a list of supported models or MS IDs for one or more MLFNs or MLFs; and / or a model selection component 454 for selecting a model or MS to be used for one or more MLFNs or MLFs for the UE.

[0071] In one aspect, processor 412 may correspond to combining Fig.10 Similarly, the memory 416 may correspond to one or more processors in conjunction with the base station described in the embodiment of the present invention. Fig.10 The memory described in the base station.

[0072] Figure 5 A flow chart illustrating an example of a method 500 for downloading models or MS IDs supported or to be used for one or more MLFNs or MLFs in accordance with various aspects described herein. Figure 6 A flowchart illustrating an example of a method 600 for configuring a node to download models or MS IDs supported or to be used for one or more MLFNs or MLFs in accordance with various aspects described herein. In one example, a UE 104 may use Figure 1 and Figure 3One or more of the components described in the method 500 may be used to perform the functions described in the method 500. In one example, a network node (such as a base station 102, a gNB, a monolithic base station or a gNB, a decomposed base station or a portion of a gNB, etc.) may use Figure 1 and Figure 4 One or more of the components described in the method 600 may be used to perform the functions described in the method 600. For ease of explanation, the methods 500 and 600 are described in conjunction with each other; however, the methods 500 and 600 need not be performed together and may in fact be performed independently using separate devices.

[0073] In method 600, at block 602, a list of supported models or MS IDs for each MLFN or MLF may be sent. In one aspect, model indication component 452 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) may send a list of supported models or MS IDs for each MLFN or MLF. For example, model indication component 452 may send the list of supported models to UE 104 in dedicated signaling (e.g., downlink control information (DCI) or other transmissions via a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), etc.), a system information (SI) broadcast, a multicast broadcast service (MBS) signaling, etc. In one example, the list of supported models or MS IDs may also indicate a priority of a model or MS for a given MLFN or MLF.

[0074] In method 500, at block 502, a list of supported models or MS IDs for each MLFN or MLF may be received. In one aspect, capability component 352 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) may receive (e.g., from a network node) a list of supported models or MS IDs for each MLFN or MLF. For example, capability component 352 may receive the list of supported models in dedicated signaling (e.g., DCI or other transmissions via PDCCH, PDSCH, etc.), SI broadcast, MBS signaling, or other radio resource control (RRC) layer signaling, etc. In one example, the list of supported models or MS IDs may also indicate a priority of a model or MS for a given MLFN or MLF.

[0075] In one example, the model indication component 452 may filter the list based on the initial UE capability information indicated to the network node. For example, in the method 600, optionally at box 604, the capability information includes one or more items in the list of UE supported models or MS IDs for each MLFN or MLF. In one aspect, the model indication component 452 (e.g., in conjunction with the processor 412, the memory 416, the transceiver 402, the BS communication component 442, etc.) may receive capability information (e.g., from the UE 104), which may include one or more items in the list of UE supported models or MS IDs for each MLFN or MLF. For example, the model indication component 452 may receive the capability information in uplink signaling (e.g., UE 104 in uplink control information (UCI) or other transmissions in a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), etc.), in residual minimum system information (RMSI) through RRC layer signaling, etc.

[0076] Similarly, for example, in method 500, optionally at block 504, the capability information includes one or more items in a list of UE supported models or MS IDs for each MLFN or MLF. In one aspect, capability component 352 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) may send capability information (e.g., to a network node), which may include one or more items in a list of UE supported models or MS IDs for each MLFN or MLF. For example, capability component 352 may send capability information in uplink signaling (e.g., UCI or other transmissions of UE 104 in PUCCH, PUSCH, etc.), RMSI via RRC layer signaling, etc.

[0077] In one example, communicating a list of supported models or MS IDs and / or initial capability information can be part of establishing a connection (e.g., registration or connection establishment) between the UE 104 and a network node. For example, in the method 600, optionally at block 606, a connection for communicating with the UE can be established, and transmitting a list of supported models or MS IDs and / or receiving capability information can be part of establishing the connection. In one aspect, the BS communication component 442 (e.g., in conjunction with the processor 412, the memory 416, the transceiver 402, etc.) can establish a connection for communicating with the UE 104, which can be based on a random access request received from the UE 104, or can otherwise include communications for establishing the connection. Similarly, for example, in the method 500, optionally at block 506, a connection for communicating with the network node can be established, and receiving a list of supported models or MS IDs and / or sending capability information can be part of establishing the connection. In an aspect, UE communication component 342 (e.g., in conjunction with processor 312, memory 316, transceiver 302, etc.) can establish a connection for communicating with a network node. For example, UE communication component 342 can perform a random access procedure or other signaling exchange with a network node, and can send the capability information and / or receive the list as part of a signaling exchange or other procedure performed prior to or as part of receiving a resource grant from the network node for communicating therewith.

[0078] After establishing the connection and based on the UE capability information received from the UE, the network may send a list of supported models or MS IDs for each MLFN or MLF at the network node. The list of supported models or MS IDs sent by the network may additionally include a list of one or more newly developed models or MS IDs for each MLFN or MLF deployed or registered at the network. In one example, the one or more newly developed models or MS IDs for each MLFN or MLF deployed or registered at the network may include: a UE vendor-specific model or MS ID for each MLFN or MLF deployed or registered at the network, a network vendor-specific model or MS ID for each MLFN or MLF deployed or registered at the network, or a third-party model or MS ID for each MLFN or MLF deployed or registered at the network. In one example, the network node may be located within a valid area for one or more models or MS IDs, which may be determined by the network based on registration or deployment information.

[0079] For example, based on receiving a list of supported models or MS IDs, UE 104 may update capabilities based on the list received from the network node. For example, in method 500, at block 508, capabilities may be updated to updated capabilities based on a list of supported models or MS IDs for each MLFN or MLF. On the one hand, capability component 352 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) may update the capabilities of UE 104 to updated capabilities based on a list of supported models or MS IDs for each MLFN or MLF. For example, capability component 352 may update the capabilities of UE 104 to use one or more updated or newly developed models or MSs, or models or MSs deployed or registered at the network, as described above. Thus, for example, capability component 352 may locally update capabilities to include support, requests, preferences, etc. for one or more updated or newly developed models or MSs, or models or MSs deployed or registered at the network, or other models or MSs supported by UE, etc. This may facilitate use and / or downloading of the corresponding model or MS from the MR to the UE 104, as further described herein.

[0080] In one example, the UE 104 may download models or MSs for one or more MLFNs or MLFs out of band, which may include the UE downloading models for new networks in conjunction with updating capabilities at the UE. In this example, in the method 500, at box 510, one or more models or MSs for each MLFN or MLF may be downloaded based on the updated capabilities. On the one hand, the model download component 354 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may download one or more models or MSs for each MLFN or MLF based on the updated capabilities (e.g., from the MR). As described, for example, the capability component 352 may update the capabilities of the UE 104 as long as the UE 104 can support or prefer or expect to use which models or MS IDs. In one example, the model download component 354 may attempt to download these models or MSs, for example, from the MR, which in some examples may also include downloading the associated PS.

[0081] In one example, when downloading these models or MSs at block 510, one or more models or MSs to be downloaded may be selected based on available resources at the UE, optionally at block 512. In one aspect, the model download component 354 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may select one or more models or MSs for download based on available resources at the UE. For example, the resources may include processing resources, storage or memory resources, hardware acceleration resources, etc. In one example, the model download component 354 may select one or more models or MSs for download based on resource capacity (e.g., the amount of resources configured at the UE 104) or capability (and the amount of available resources at the UE 104). For example, the capability component 352 may generate and / or prioritize a list of model or MS IDs for each MLFN or MLF based on the updated capabilities, and the model download component 354 may select the model or MS to be downloaded based on the generated or prioritized list (e.g., based on the list priority, until the available resources reserved for the model or MS are utilized). In one example, capability component 352 can obtain resource utilization information for models or MSs in the list when updating capabilities, and model download component 354 can use this information to determine which models or MSs can be selected for download to comply with available resources.

[0082] In method 600, at block 608, a request to download one or more models or MS IDs for each MLFN or MLF from the MR based on the list of supported models or MS IDs may be received. In one aspect, BS communication component 442 (e.g., in conjunction with processor 412, memory 416, transceiver 402, etc.) may receive a request to download one or more models or MS IDs for each MLFN or MLF from the MR based on the list of supported models or MS IDs (e.g., from UE 104). In one example, BS communication component 442 may forward the request to the MR of UE 104 so that UE 104 may download the one or more models or MSs.

[0083] In method 500, optionally at block 514, updated capabilities of the UE may be reported based on multiple models including the downloaded model or MS or one or more additional models or MS IDs available at the UE. In one aspect, capability component 352 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) may report (e.g., to a network node) updated capabilities of the UE based on multiple models including the downloaded model or MS or one or more additional models or MS IDs available at the UE. For example, capability component 352 may send an indication of the updated capabilities to the network node in a UCI or other PUCCH or PUSCH transmission.

[0084] In method 600, optionally at block 610, updated capabilities of the UE may be received. In one aspect, model indication component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) may receive (e.g., from UE 104) updated capabilities of the UE, which may include indications of models or MS IDs stored at UE 104, which may include recently downloaded models or MSs and / or other additional models or MSs available at the UE. For example, model indication component 454 may receive the indication of the updated capabilities in a UCI or other PUCCH or PUSCH transmission.

[0085] In method 600, optionally at box 612, a configuration of a subset of multiple models or MS IDs to be used for MLFN or MLF may be sent based on the updated capabilities. In one aspect, model selection component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) may send (e.g., to UE 104) a configuration of a subset of multiple models or MS IDs to be used for MLFN or MLF based on the updated capabilities. For example, model selection component 454 may send a configuration indicating which model or MS ID to use for each given MLFN or MLF. For example, model selection component 454 may select which model or MS to be used by UE 104 for a given MLFN or MLF based on one or more considerations, which may include a model priority indicated by UE 104, a preference of a network node for a certain model or MS (e.g., which may be based on resource utilization or other considerations at the network node), etc. For example, model selection component 454 can transmit the configuration using DCI, medium access control (MAC) control element (CE), or RRC signaling, among others.

[0086] In method 500, optionally at box 516, a configuration of a subset of multiple models or MS IDs to be used for MLFN or MLF may be received based on the updated capabilities. In one aspect, the model utilization component 356 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may receive a configuration of a subset of multiple models or MS IDs to be used for MLFN or MLF based on the updated capabilities (e.g., from a network node). In one example, the model utilization component 356 may configure the model or MS ID to be used for each MLFN or MLF accordingly, and the UE 104 may use these models when performing MLFN or MLF, as described. For example, the model selection component 454 may receive the configuration in a DCI, a medium access control (MAC) control element (CE), or RRC signaling, etc.

[0087] In another example, the UE 104 may download models or MSs to be used for one or more MLFNs or MLFs on demand, which may include the UE downloading models for new networks when the network configures the models to be used. In this example, in the method 500, at block 518, the updated capabilities of the UE may be reported based on multiple models or MS IDs including one or more additional models or MS IDs supported by the UE. In one aspect, the capability component 352 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may report (e.g., to a network node) the updated capabilities of the UE based on multiple models or MS IDs including one or more additional models or MS IDs supported by the UE. For example, the capability component 352 may update the capabilities based on a list of supported models or MS IDs as described above, and may report the updated capabilities to the network node, which may indicate support for multiple models, which may include one or more additional models or MS IDs based on the received list (e.g., they may not yet be in the initial capability information sent at block 504). For example, capability component 352 can send updated capabilities in UCI or other PUCCH or PUSCH transmissions.

[0088] In method 600, optionally at block 614, updated capabilities of the UE may be received based on a plurality of models or MS IDs including one or more additional models or MS IDs supported by the UE. In one aspect, model indication component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) may receive updated capabilities of the UE (e.g., from UE 104) based on a plurality of models or MS IDs including one or more additional models or MS IDs supported by the UE, which may include an indication of models or MS IDs stored at UE 104, which may include recently downloaded models or MSs and / or other additional models or MSs available at the UE. For example, model indication component 454 may receive an indication of the updated capabilities in a UCI or other PUCCH or PUSCH transmission.

[0089] In method 600, optionally at block 616, a configuration of a subset of multiple models or MS IDs including one or more models or MS IDs for each MLFN or MLF may be sent based on the updated capabilities. In one aspect, model selection component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) may send a configuration of a subset of multiple models or MS IDs including one or more models or MS IDs for each MLFN or MLF based on the updated capabilities (e.g., to UE 104). For example, model selection component 454 may send a configuration indicating which model or MS ID to use for each given MLFN or MLF. For example, model selection component 454 may select which model or MS to use for a given MLFN or MLF by UE 104 based on one or more considerations, which may include a model priority indicated by UE 104, a preference of a network node for a certain model or MS (e.g., which may be based on resource utilization or other considerations at the network node), etc.

[0090] In method 500, optionally at block 520, a configuration of a subset of multiple models or MS IDs including one or more models or MS IDs for each MLFN or MLF may be received based on the updated capabilities. In one aspect, model utilization component 356 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) may receive a configuration of a subset of multiple models or MS IDs including one or more models or MS IDs for each MLFN or MLF based on the updated capabilities (e.g., from a network node). In one example, model utilization component 356 may configure the model or MS ID to be used for each MLFN or MLF accordingly for on-demand downloading.

[0091] In method 500, at box 522, one or more models or MSs for each MLFN or MLF may be downloaded from the MR based on the updated capabilities. In one aspect, the model download component 354 (e.g., in conjunction with the processor 312, the memory 316, the transceiver 302, the UE communication component 342, etc.) may download one or more models or MSs for each MLFN or MLF from the MR based on the updated capabilities. For example, the model download component 354 may download one or more models or MSs indicated in the configuration received from the network node. In one example, as described in box 512, the download of the one or more models or MSs may also be based on the resource capacity or availability at the UE 104. For example, in the case where the configuration indicates multiple models or MS IDs (for each MLFN or MLF), the model download component 354 may download a subset of these models or MSs based on the resource availability at the UE, as described above.

[0092] In method 600, at block 618, a request to download one or more models or MS IDs for each MLFN or MLF from the MR based on the configuration may be received. In one aspect, the BS communication component 442 (e.g., in conjunction with the processor 412, the memory 416, the transceiver 402, etc.) may receive a request to download one or more models or MS IDs for each MLFN or MLF from the MR based on the configuration (e.g., from the UE 104). In one example, the BS communication component 442 may forward the request to the MR of the UE 104 so that the UE 104 may download the one or more models or MSs. The UE 104 may use one or more of the downloaded models or MSs for the corresponding MLFN or MLF, and / or the network node may use or determine parameter values ​​for the MLFN or MLF based on the downloaded models or MSs.

[0093] In method 500, optionally at block 524, a readiness indication that the one or more models or MSs are ready for use may be sent based on downloading the one or more models or MSs. In one aspect, model utilization component 356 (e.g., in conjunction with processor 312, memory 316, transceiver 302, UE communication component 342, etc.) may send a readiness indication that the one or more models or MSs are ready for use based on downloading the one or more models or MSs. For example, once the model or MS is downloaded, model utilization component 356 may send the indication, and model utilization component 356 may use the model or MS for the corresponding MLFN or MLF. For example, model utilization component 356 may send the readiness indication in UCI, MAC-CE, RRC signaling, etc.

[0094] In method 600, optionally at block 620, a readiness indication that the one or more models or MSs are ready for use may be received. In one aspect, model selection component 454 (e.g., in conjunction with processor 412, memory 416, transceiver 402, BS communication component 442, etc.) may receive a readiness indication that the one or more models or MSs are ready for use. For example, once UE 104 has downloaded, model selection component 454 may receive a readiness indication from UE 104 and may begin using the one or more models or MSs for a given MLFN or MLF. The network node may accordingly begin using the MLFN or MLF to receive or interpret parameters received from UE 104 as part of the corresponding MLFN or MLF. For example, model selection component 454 may receive a readiness indication in UCI, MAC-CE, RRC signaling, etc.

[0095] Figure 7An example of a system 700 for out-of-band model download and model update at a UE is illustrated. For example, the system 700 may include a UE 104, a base station 102, and a MR 702. The UE 104 may access the MR 702 via the base station 102. In this example, the UE 104 may optionally send UE capability information to the base station 102 at 704, which may indicate a list of UE supported models or MS IDs for each MLFN or MLF. At 706, the base station 102 may send a SIBx (e.g., a system information block with index x) or dedicated signaling to the UE 104, which may indicate a network list of models or MS IDs supported by each MLFN and / or may include priorities for these models or MS IDs. In one example, the network list may be filtered based on the initial UE capability information. In addition, as described, as part of the UE 104 performing registration or connection establishment with the base station 102, the UE capability information may be sent, and / or the network list may be received.

[0096] The UE 104 may update the UE capabilities locally based on the network list at 708, and may download the corresponding model or MS from the MR 702 using the updated capabilities at 710. In one example, the UE 104 may download the model or MS from the MR 702 based on available storage or other resources at the UE. Once the model or MS is downloaded, the UE 104 may update the UE capability information to the base station 102 at 712 to indicate the downloaded and otherwise locally stored models and MSs at the UE 104 for each MLFN or MLF. At 714, the base station 102 may select and configure one or more of the models or MSs for each MLFN or MLF for the UE 104, and at 716, the UE 104 may configure the one or more models or MSs accordingly and indicate to the base station 102 that the configuration is complete. The UE 104 and the base station 102 may use the one or more models or MSs accordingly to perform a specific MLFN or MLF.

[0097] Figure 8An example of a system 800 for on-demand model download and model update at a UE is illustrated. For example, the system 800 may include a UE 104, a base station 102, and a MR 702. The UE 104 may access the MR 702 via the base station 102. In this example, the UE 104 may optionally send UE capability information to the base station 102 at 704, which may indicate a list of UE supported models or MS IDs for each MLFN or MLF. At 704, the base station 102 may send a SIBx (e.g., a system information block with index x) or dedicated signaling to the UE 104, which may indicate a network list of models or MS IDs supported by each MLFN and / or may include priorities for these models or MS IDs. In one example, the network list may be filtered based on the initial UE capability information. In addition, as described, as part of the UE 104 performing registration or connection establishment with the base station 102, the UE capability information may be sent, and / or the network list may be received.

[0098] The UE 104 may update the UE capabilities locally based on the network list at 708, and may send the updated UE capability information to the base station 102 based on the network list at 802. At 804, the base station 102 may configure the model or MS ID for each MLFN or MLF reported by the UE 104. At 806, the UE 104 may download the configured model or MS from the MR 702, which may depend on the resource availability at the UE 104. At 808, the UE 104 may configure the one or more models or MSs accordingly and indicate the configuration completion to the base station 102. The UE 104 and the base station 102 may use the one or more models or MSs to perform a specific MLFN or MLF accordingly.

[0099] Fig. 9 An example of a system 900 for model downloading by a UE according to various aspects described herein is illustrated (such as Figure 5 Frames 510 and 522, Figure 7 Frame 710, Figure 8806 of the system 900). For example, the system 900 may include a UE 104 and a MR 702. The UE 104 may access the MR 702 via a base station and / or other network nodes (not shown). The network operator may prepare models at the MR 702 for download and / or use by one or more UEs. In one example, the models may optionally be hosted by a third party and accessed by the network operator via the third party. The MR 702 may store the models and parameter sets as executable files (e.g., a third party may convert the model for a particular UE) or as standardized descriptors (e.g., Open Neural Network Exchange (ONNX)) that the UE may interpret. As described, based on its own capabilities, the UE 104 may use a model identifier and / or a parameter set identifier as input to construct a resource locator (e.g., a universal resource locator (URL)) of the model and / or parameter set, which may be based on defined rules. In another example, the UE 104 may be configured with a policy for generating rules for the URL.

[0100] For example, the UE 104 may send a request (e.g., HTTP GET) for a model URL to the MR 702 at 902, and may receive a response (e.g., 200 OK) with the requested model at 904. The UE 104 may also send a request (e.g., HTTP GET) for a parameter set to the MR 702 at 906, and may receive a response (e.g., 200 OK) with the requested parameter set at 908. In one example, these requests may include secure hypertext transfer protocol (HTTP), stream control transmission protocol (SCTP), file transfer protocol (FTP), or similar user plane requests made by the UE 104. The UE 104 may cache frequently used models and / or parameter sets (e.g., similar to a SIB cache, where version tags and timers may be used to ensure freshness of cached parameter sets).

[0101] Fig.10 1 is a block diagram of a MIMO communication system 1000 including a base station 102 and a UE 104. The MIMO communication system 1000 may be exemplified with reference to Figure 1 The wireless communication access network 100 is described in detail. The base station 102 may be a reference Figure 1 Examples of various aspects of base station 102 are described. Base station 102 may be equipped with antenna 1034 and antenna 1035, and UE 104 may be equipped with antenna 1052 and antenna 1053. In MIMO communication system 1000, base station 102 may be able to transmit data over multiple communication links simultaneously. Each communication link may be referred to as a "layer", and the "rank" of a communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system in which base station 102 transmits two "layers", the rank of the communication link between base station 102 and UE 104 is two.

[0102] At the base station 102, a transmit (Tx) processor 1020 may receive data from a data source. The transmit processor 1020 may process the data. The transmit processor 1020 may also generate a control symbol or a reference symbol. The transmit MIMO processor 1030 may perform spatial processing (e.g., pre-coding) on ​​the data symbol, the control symbol, or the reference symbol (if applicable), and may provide an output symbol stream to the transmit modulator / demodulators 1032 and 1033. Each modulator / demodulator 1032 to 1033 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator / demodulator 1032 to 1033 may further process the output sample stream (e.g., convert the output sample stream to analog, amplify, filter, and up-convert) to obtain a DL signal. In one example, the DL signals from the modulator / demodulators 1032 and 1033 may be transmitted via antennas 1034 and 1035, respectively.

[0103] UE 104 may be a reference Figure 1 and Figure 3 Examples of various aspects of the UE 104 described herein. At the UE 104, the UE antenna 1052 and the antenna 1053 may receive DL signals from the base station 102 and may provide received signals to the modulators / demodulators 1054 and 1055, respectively. Each modulator / demodulator 1054 to 1055 may condition a corresponding received signal (e.g., filter, amplify, downconvert, and digitize the corresponding received signal) to obtain input samples. Each modulator / demodulator 1054 to 1055 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 1056 may obtain received symbols from the modulators / demodulators 1054 and 1055, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. The receive (Rx) processor 1058 may process (eg, demodulate, deinterleave, and decode) the detected symbols to provide decoded data for the UE 104 to a data output and to provide decoded control information to a processor 1080 or memory 1082 .

[0104] In some cases, processor 1080 may execute stored instructions to instantiate UE communication component 342 (see, e.g., Figure 1 and Figure 3 ).

[0105] On the uplink (UL), at the UE 104, a transmit processor 1064 may receive and process data from a data source. The transmit processor 1064 may also generate reference symbols for a reference signal. The symbols from the transmit processor 1064 may be pre-decoded by a transmit MIMO processor 1066 (if applicable), further processed by modulators / demodulators 1054 and 1055 (e.g., for single carrier FDMA, etc.), and transmitted to the base station 102 according to the communication parameters received from the base station 102. At the base station 102, the UL signal from the UE 104 may be received by antennas 1034 and 1035, processed by modulators / demodulators 1032 and 1033, detected by a MIMO detector 1036 (if applicable), and further processed by a receive processor 1038. The receive processor 1038 may provide decoded data to a data output and to the processor 1040 or memory 1042.

[0106] In some cases, processor 1040 may execute stored instructions to instantiate BS communication component 442 (see, e.g., Figure 1 and Figure 4 ).

[0107] The components of the UE 104 may be implemented individually or collectively using one or more ASICs, wherein the one or more ASICs are adapted to perform some or all of the applicable functions in hardware. Each of the modules indicated may be a component for performing one or more functions related to the operation of the MIMO communication system 1000. Similarly, the components of the base station 102 may be implemented individually or collectively using one or more application specific integrated circuits (ASICs), which are adapted to perform some or all of the applicable functions in hardware. Each of the components indicated may be a component for performing one or more functions related to the operation of the MIMO communication system 1000.

[0108] The following aspects are merely illustrative, and aspects thereof may be combined with aspects of other embodiments or teachings described herein without limitation.

[0109] Aspect 1 is a method for wireless communication at a UE, the method comprising: receiving a list of supported models or MS IDs for each MLFN or MLF at the network node from a network node; updating the capabilities at the UE to updated capabilities based on the list of supported models or MS IDs for each MLFN or MLF at the network node; and downloading one or more models or MSs for each MLFN or MLF at the UE and from a model repository based on the updated capabilities and available resources at the UE.

[0110] In aspect 2, the method according to aspect 1 includes: wherein the list of supported models or MS IDs for each MLFN or MLF received from the network node is based on sending capability information to the network node, the capability information including a list of UE supported models or MS IDs for each MLFN or MLF and a list of one or more newly developed models or MS IDs for each MLFN or MLF deployed or registered at the network.

[0111] In aspect 3, the method according to aspect 2 includes: wherein the one or more newly developed models or MS IDs of each MLFN or MLF deployed or registered at the network include one or more of a UE vendor-specific model or MS ID of each MLFN or MLF deployed or registered at the network, a network vendor-specific model or MS ID of each MLFN or MLF deployed or registered at the network, or a third-party model or MS ID of each MLFN or MLF deployed or registered at the network, wherein the network node is within the valid area of ​​the one or more models or MS IDs.

[0112] In aspect 4, the method according to any one of aspects 1 to 3 comprises establishing a connection for communicating with the network node, wherein receiving the list of supported models or MS IDs for each MLFN or MLF at the network node is part of establishing the connection.

[0113] In aspect 5, the method according to any one of aspects 1 to 4 includes reporting further updated capabilities of the UE to the network node based on multiple models, the multiple models including the one or more models or MSs downloaded from the model repository or additional models or MS IDs available at the UE.

[0114] In aspect 6, the method according to aspect 5 includes: receiving a configuration from the network node and based on the updated capabilities, the configuration configuring a subset of the multiple models or MS IDs per MLFN or MLF for use with the MLFN or MLF at the UE.

[0115] In aspect 7, the method according to aspect 6 includes wherein the configuration is received via RRC signaling.

[0116] In aspect 8, the method according to any one of aspects 1 to 7 comprises: reporting the updated capability of the UE to the network node based on the list of supported models or MS IDs for each MLFN or MLF at the network node.

[0117] In aspect 9, the method according to aspect 8 includes: receiving a configuration from the network node and based on the updated capabilities, the configuration configuring at least a subset of the one or more models or MS IDs of each MLFN or MLF for operation at the UE, wherein downloading the one or more models or MSs is based on the configuration.

[0118] In aspect 10, the method according to aspect 9 comprises: based on downloading the one or more models or MSs, sending a readiness indication that the one or more models or MSs are ready for use at the UE.

[0119] In aspect 11, the method according to aspect 10 includes wherein the readiness indication is sent using an RRC message, a MAC CE or a UCI.

[0120] In aspect 12, the method according to any one of aspects 1 to 11 includes: wherein receiving the list of supported models or MS IDs for each MLFN or MLF at the network node is via dedicated signaling for the UE, SI or using MBS.

[0121] In aspect 13, the method according to any one of aspects 1 to 12 comprises: wherein the list of supported models or MS IDs at the network node comprises a plurality of lists of supported models or MS IDs for each MLFN or MLF.

[0122] In aspect 14, the method according to any one of aspects 1 to 13 includes: wherein downloading the one or more models includes: constructing a resource locator for the one or more models or MSs and a parameter set for the one or more MSs based on the MS ID; sending a request for downloading the one or more models or MSs and the parameter set to the model repository; and receiving the one or more models or MSs and the parameter set from the model repository based on the request.

[0123] In aspect 15, the method according to aspect 14 includes wherein the request for downloading the model is sent over a user plane using secure HTTP, SCTP or FTP.

[0124] In aspect 16, the method according to any one of aspects 14 or 15 comprises caching the one or more models or the parameter sets at the UE.

[0125] Aspect 17 is a method for performing wireless communications at a network node, the method comprising: sending, to a UE, a list of supported models or MS IDs for each MLFN or MLF at the network node; and receiving, to the UE and based on the list of supported models or MS IDs, a request to download one or more models or MSs from a model repository based on the list of supported models or MS IDs at the network node.

[0126] In aspect 18, the method according to aspect 17 includes: wherein sending the list of supported models or MS IDs at the network node is based on receiving capability information from the UE, the capability information including a list of UE supported models or MS IDs and a list of one or more newly developed models or MS IDs for each MLFN or MFN deployed or registered at the network, wherein the network node is within a valid area of ​​the one or more newly developed models or MS IDs.

[0127] In aspect 19, the method according to aspect 18 includes: wherein the one or more newly developed models or MS IDs of each MLFN or MLF deployed or registered at the network include one or more of a UE vendor-specific model or MS ID of each MLFN or MLF deployed or registered at the network, a network vendor-specific model or MS ID of each MLFN or MLF deployed or registered at the network, or a third-party model or MS ID of each MLFN or MLF deployed or registered at the network, wherein the network node is within the valid area of ​​the one or more models or MS IDs.

[0128] In aspect 20, the method according to any one of aspects 17 to 19 comprises establishing a connection for communicating with the UE, wherein sending the list of supported models or MS IDs at the network node is part of establishing the connection.

[0129] In aspect 21, the method according to any one of aspects 17 to 20 includes: receiving a report of updated capabilities of the UE from the UE based on the one or more models or MSs downloaded from the model repository; and sending a configuration to the UE to configure a subset of the one or more models or MSs for operation based on the updated capabilities.

[0130] In aspect 22, the method according to any one of aspects 17 to 21 includes: receiving, from the UE and based on the list of supported models or MS IDs, a report of updated capabilities of the UE based on multiple models or MS IDs, wherein the multiple models or MS IDs include one or more additional models or MS IDs supported by the UE.

[0131] In aspect 23, the method according to aspect 22 includes: sending a configuration to the UE configuring a subset of the plurality of models or MS IDs based on the updated capabilities, wherein receiving the request to download the one or more models or MSs is based on the configuration.

[0132] In aspect 24, the method according to aspect 23 includes wherein the configuration is sent via RRC signaling.

[0133] In aspect 25, the method according to any one of aspects 22 to 24 comprises: receiving a readiness indication that the one or more models or MSs are ready for use at the UE based on downloading the one or more models or MSs.

[0134] In aspect 26, the method according to aspect 25 includes wherein the readiness indication is received using an RRC message, a MAC CE or a UCI.

[0135] In aspect 27, the method according to any one of aspects 17 to 26 includes: wherein sending the list of supported models or MSIDs is via dedicated signaling for the UE, SI or using MBS.

[0136] Aspect 28 is an apparatus for wireless communication, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and operable when executed by the processor to cause the apparatus to perform any of the methods described in aspects 1 to 27.

[0137] Aspect 29 is an apparatus for wireless communication, the apparatus comprising means for performing any of the methods according to aspects 1 to 27.

[0138] Aspect 30 is a computer-readable medium comprising code executable by one or more processors for wireless communication, the code comprising code for performing any of the methods according to aspects 1 to 27.

[0139] The above specific embodiments described above in conjunction with the accompanying drawings describe examples and do not represent the only examples that can be implemented or fall within the scope of the claims. The term "example" used in this specification means "used as an example, instance, or illustration", rather than "preferred" or "advantageous over other examples". The specific embodiments include specific details for providing an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0140] Information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer executable codes or instructions stored on a computer-readable medium, or any combination thereof.

[0141] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a specially programmed device, such as, but not limited to, a processor for performing the functions described herein, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. Although the specially programmed processor may be a microprocessor, in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The specially programmed processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0142] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented with software executed by a processor, the functions may be stored as one or more instructions or codes on a non-transient computer-readable medium or sent through it. Other examples and specific implementations fall within the scope and essence of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using hardware, firmware, hard wiring, software executed by a specially programmed processor, or a combination of any of these items. The features that implement the functions may also be physically located at different locations, including being distributed so that the parts of the functions are implemented at different physical locations. In addition, as used herein, including in the claims, the "or" used in the list of items starting with "at least one of" indicates a dispersed list, so that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0143] Computer-readable medium includes both computer storage medium and communication medium, including any medium that promotes computer program to be transferred from one place to another place. Storage medium can be any available medium that can be accessed by general or special-purpose computer. By way of example and not limitation, computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure. Moreover, any connection is appropriately referred to as computer-readable medium. For example, if software is to be sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer readable media.

[0144] The previous description of the present disclosure is provided to enable those skilled in the art to implement or use the present disclosure. It will be apparent to those of ordinary skill in the art that various modifications to the present disclosure will be apparent, and the general principles defined herein may be applied to other variations without departing from the essence or scope of the present disclosure. In addition, although the elements of the described aspects and / or embodiments are described or claimed in the singular, the plural form may also be envisioned unless explicitly stated to be limited to the singular. Additionally, unless otherwise stated, all or part of any aspect and / or embodiment may be used together with all or part of any other aspect and / or embodiment. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A device for wireless communication, the device comprising: processor; a memory coupled to the processor; and instructions stored in the memory and operable when executed by the processor to cause the apparatus to: receiving, from a network node, a list of supported models or model structure (MS) identifiers (IDs) for each machine learning function name (MLFN) or machine learning feature (MLF) at the network node; updating capabilities at the device to updated capabilities based on the list of supported models or MSIDs for each MLFN or MLF at the network node; as well as Based on the updated capabilities and available resources at the device, one or more models or MSs for each MLFN or MLF are downloaded from a model repository.

2. An apparatus according to claim 1, wherein the instructions, when executed by the processor, cause the apparatus to: receive the list of supported models or MSIDs for each MLFN or MLF from the network node based on sending capability information to the network node, the capability information comprising a list of UE supported models or MSIDs for each MLFN or MLF and a list of one or more newly developed models or MSIDs for each MLFN or MLF deployed or registered at the network.

3. An apparatus according to claim 2, wherein the one or more newly developed models or MSIDs of each MLFN or MLF deployed or registered at the network include one or more of a UE vendor-specific model or MS ID of each MLFN or MLF deployed or registered at the network, a network vendor-specific model or MS ID of each MLFN or MLF deployed or registered at the network, or a third-party model or MS ID of each MLFN or MLF deployed or registered at the network, wherein the network node is within a valid area of ​​the one or more models or MS IDs.

4. An apparatus according to claim 1, wherein the instructions, when executed by the processor, cause the apparatus to: establish a connection for communicating with the network node, wherein the instructions, when executed by the processor, cause the apparatus to: receive the list of supported models or MS IDs for each MLFN or MLF at the network node as part of establishing the connection.

5. The apparatus of claim 1 , wherein the instructions, when executed by the processor, cause the apparatus to: report to the network node further updated capabilities of the apparatus based on a plurality of models, the plurality of models comprising the one or more models or MSs downloaded from the model repository or additional models or MSIDs available at the apparatus.

6. An apparatus according to claim 5, wherein the instructions, when executed by the processor, cause the apparatus to: receive a configuration from the network node and based on the updated capabilities, the configuration configuring a subset of the multiple models or MS IDs for each MLFN or MLF for use with the MLFN or MLF at the apparatus.

7. The apparatus of claim 6, wherein the configuration is received via radio resource control (RRC) signaling.

8. The apparatus of claim 1, wherein the instructions, when executed by the processor, cause the apparatus to: report the updated capabilities of the apparatus to the network node based on the list of supported models or MS IDs for each MLFN or MLF at the network node.

9. An apparatus according to claim 8, wherein the instructions, when executed by the processor, cause the apparatus to: receive a configuration from the network node and based on the updated capabilities, the configuration configuring at least a subset of the one or more models or MSIDs of each MLFN or MLF for operation at the apparatus, wherein the instructions, when executed by the processor, cause the apparatus to: download the one or more models or MSs based on the configuration.

10. The apparatus of claim 9, wherein the instructions, when executed by the processor, cause the apparatus to: based on downloading the one or more models or MSs, send a readiness indication that the one or more models or MSs are ready for use at the apparatus.

11. The apparatus of claim 10, wherein the readiness indication is sent using a radio resource control (RRC) message, a medium access control (MAC) control element (CE), or downlink control information (UCI).

12. A device according to claim 1, wherein the instructions, when executed by the processor, cause the device to: receive the list of supported models or MS IDs for each MLFN or MLF at the network node via dedicated signaling for the device, system information (SI), or using multicast broadcast service (MBS).

13. The apparatus of claim 1, wherein the list of supported models or MSIDs at the network node comprises multiple lists of supported models or MS IDs for each MLFN or MLF.

14. The apparatus of claim 1, wherein the instructions, when executed by the processor, cause the apparatus to: download the one or more models at least in part by: constructing a resource locator for the one or more models or MSs and a parameter set for the one or more MSs based on the MSID; sending a request to the model repository for downloading one or more models or MSs and the parameter set; as well as Based on the request, the one or more models or MSs and the parameter set are received from the model repository.

15. The apparatus of claim 14, wherein the request for downloading the model is sent through a user plane using Secure Hypertext Transfer Protocol (HTTP), Stream Control Transmission Protocol (SCTP), or File Transfer Protocol (FTP).

16. The apparatus of claim 14, wherein the instructions, when executed by the processor, cause the apparatus to: cache the one or more models or the parameter sets at the apparatus.

17. An apparatus for wireless communication, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and operable when executed by the processor to cause the apparatus to: For a user equipment (UE), sending a list of supported models or model structure (MS) identifiers (IDs) for each machine learning function name (MLFN) or machine learning feature (MLF) at the device; as well as For the UE and based on the list of supported models or MSIDs, a request is received to download one or more models or MSs from a model repository based on the list of supported models or MSIDs at the device.

18. An apparatus according to claim 17, wherein the instructions, when executed by the processor, cause the apparatus to: send the list of supported models or MS IDs at the apparatus based on receiving capability information from the UE, the capability information comprising a list of UE supported models or MSIDs and a list of one or more newly developed models or MS IDs for each MLFN or MFN deployed or registered at the network, wherein the apparatus is within a valid area of ​​the one or more newly developed models or MS IDs.

19. An apparatus according to claim 18, wherein the one or more newly developed models or MS IDs for each MLFN or MLF deployed or registered at the network include one or more of a UE vendor-specific model or MSID for each MLFN or MLF deployed or registered at the network, a network vendor-specific model or MS ID for each MLFN or MLF deployed or registered at the network, or a third-party model or MS ID for each MLFN or MLF deployed or registered at the network, wherein the apparatus is within a valid area of ​​the one or more models or MS IDs.

20. The apparatus of claim 17, wherein the instructions, when executed by the processor, cause the apparatus to: establish a connection for communicating with the UE, wherein the instructions, when executed by the processor, cause the apparatus to: send the list of supported models or MSIDs at the apparatus as part of establishing the connection.

21. The apparatus of claim 17, wherein the instructions, when executed by the processor, cause the apparatus to: receiving, from the UE, a report of the updated capabilities of the UE based on the one or more models or MSs downloaded from the model repository; and Based on the updated capabilities, a configuration is sent to the UE configuring the one or more models or a subset of MSs for operation.

22. An apparatus according to claim 17, wherein the instructions, when executed by the processor, cause the apparatus to: receive from the UE and based on the list of supported models or MSIDs, a report of updated capabilities of the UE based on multiple models or MSIDs, the multiple models or MSIDs including one or more additional models or MSIDs supported by the UE.

23. An apparatus according to claim 22, wherein the instructions, when executed by the processor, cause the apparatus to: send a configuration configuring a subset of the multiple models or MS IDs to the UE and based on the updated capabilities, wherein the instructions, when executed by the processor, cause the apparatus to: receive the request to download the one or more models or MSs based on the configuration.

24. The apparatus of claim 23, wherein the configuration is sent via radio resource control (RRC) signaling.

25. The apparatus of claim 22, wherein the instructions, when executed by the processor, cause the apparatus to: receive a readiness indication that the one or more models or MSs are ready for use at the UE based on downloading the one or more models or MSs.

26. The apparatus of claim 25, wherein the readiness indication is received using a radio resource control (RRC) message, a medium access control (MAC) control element (CE), or downlink control information (UCI).

27. The apparatus of claim 17, wherein the instructions, when executed by the processor, cause the apparatus to: send the list of supported models or MS IDs via dedicated signaling for the UE, system information (SI), or using a multicast broadcast service (MBS).

28. A method for wireless communication at a user equipment (UE), the method comprising: receiving, from a network node, a list of supported models or model structure (MS) identifiers (IDs) for each machine learning function name (MLFN) or machine learning feature (MLF) at the network node; updating capabilities at the UE to updated capabilities based on the list of supported models or MS IDs for each MLFN or MLF at the network node; as well as Based on the updated capabilities and available resources at the UE, one or more models for each MLFN or MLF or MS are downloaded at the UE and from a model repository.

29. The method of claim 28, wherein receiving the list of supported models or MS IDs for each MLFN or MLF from the network node is based on sending capability information to the network node, the capability information comprising a list of UE supported models or MS IDs for each MLFN or MLF and a list of one or more newly developed models or MS IDs for each MLFN or MLF deployed or registered at the network.

30. A method for wireless communication at a network node, the method comprising: For a user equipment (UE), sending a list of supported models or model structure (MS) identifiers (IDs) for each machine learning function name (MLFN) or machine learning feature (MLF) at the network node; as well as For the UE and based on the list of supported models or MS IDs, a request is received to download one or more models or MSs from a model repository based on the list of supported models or MS IDs at the network node.

Images