System and method for parameter set configuration and downloading

Abstract

Example implementations include a method, an apparatus, and a computer readable medium for wireless communication by a user equipment (UE), including receiving parameter set configuration information from a network entity, the parameter set configuration information corresponding to a model structure employed in machine learning operations used by the UE for the wireless communication. These implementations also include activating a parameter set in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 17 / 891,974, filed on August 19, 2022, entitled “SYSTEMS AND METHODS OF PARAMETER SET CONFIGURATION AND DOWNLOAD,” which is expressly incorporated herein by reference in its entirety. Background Art Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to implementing processes for parameter set configuration and downloading. Background Art

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability, such as with the Internet of Things (IoT), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Summary of the invention

[0007] 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.

[0008] One example aspect includes a method of wireless communication by a user equipment (UE), the method comprising receiving parameter set configuration information from a network entity, the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communication by the UE. The method also includes activating the parameter set in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

[0009] Another example aspect includes a user equipment (UE) apparatus, the user equipment (UE) apparatus comprising a memory and a processor coupled to the memory. The processor is configured to receive parameter set configuration information from a network entity, the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communication by the UE. The processor is further configured to activate a parameter set in response to an activation condition, the parameter set being identified in the parameter set configuration information as being associated with the activation condition.

[0010] Another example aspect includes a user equipment (UE) apparatus including means for receiving parameter set configuration information from a network entity, the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communication by the UE. The apparatus also includes means for activating a parameter set in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

[0011] Another example aspect includes a computer-readable medium including stored instructions for wireless communications by a user equipment (UE), wherein the instructions are executable by a processor to receive parameter set configuration information from a network entity, the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communications by the UE. The instructions are further executable to activate a parameter set in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

[0012] One example aspect includes a method of wireless communications by a network entity, the method comprising sending parameter set configuration information to a user equipment (UE), the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communications by the UE. The method also includes causing activation of a parameter set in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

[0013] Another example aspect includes an apparatus for wireless communication by a network entity, the apparatus comprising a memory and a processor coupled to the memory. The processor is configured to send parameter set configuration information to a user equipment (UE), the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communication by the UE. The processor is further configured to cause activation of a parameter set in response to an activation condition, the parameter set being identified in the parameter set configuration information as being associated with the activation condition.

[0014] Another example aspect includes an apparatus for wireless communications by a network entity, the apparatus comprising means for sending parameter set configuration information to a user equipment (UE), the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communications by the UE. The apparatus further comprises means for causing activation of a parameter set in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

[0015] Another example aspect includes a computer-readable medium including stored instructions for wireless communication by a network entity, wherein the instructions are executable by a processor to send parameter set configuration information to a user equipment (UE), the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communication by the UE. The instructions are further executable to cause activation of a parameter set in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

[0016] 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

[0017] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided to illustrate and not to limit the disclosed aspects, wherein like designations represent like elements, wherein dashed lines may indicate optional elements, and wherein:

[0018] Figure 1 is a diagram illustrating an example of a wireless communication system and access network according to some aspects of the present disclosure.

[0019] Figure 2A is a diagram illustrating an example of a first 5G / NR frame according to some aspects of the present disclosure.

[0020] Figure 2Bis a diagram illustrating an example of DL channels within a 5G / NR subframe according to some aspects of the present disclosure.

[0021] Figure 2C is a diagram illustrating an example of a second 5G / NR frame according to some aspects of the present disclosure.

[0022] Figure 2D is a diagram illustrating an example of UL channels within a 5G / NR subframe according to some aspects of the present disclosure.

[0023] Figure 3 is a diagram illustrating an example of a base station and a UE in an access network according to some aspects of the present disclosure.

[0024] Figure 4 is a diagram illustrating an example of a decomposed base station architecture according to some aspects of the present disclosure.

[0025] Figure 5 is a diagram illustrating an example of communications of network entities and devices according to some aspects of the present disclosure.

[0026] Figure 6 is a diagram illustrating an example method of configuring parameter set information at a UE according to some aspects of the present disclosure.

[0027] Figure 7 is a diagram illustrating an example of reconfiguring parameter set information at a UE according to some aspects of the present disclosure.

[0028] Figure 8 is a diagram illustrating an example of obtaining additional parameter set information at a UE according to some aspects of the present disclosure.

[0029] Fig. 9 is a diagram illustrating an example of downloading parameter set information from a model repository according to some aspects of the present disclosure.

[0030] Fig.10 is a diagram illustrating an example storage structure for storing parameter set information at a model repository according to some aspects of the present disclosure.

[0031] Fig.11 is a diagram illustrating an example of a hardware implementation of a network entity employing a processing system according to some aspects of the present disclosure.

[0032] Fig.12 is a flow chart of an example of a method of a method for wireless communications by a network entity.

[0033] Fig.13 is a diagram illustrating an example of a hardware implementation of user equipment employing a processing system according to some aspects of the present disclosure.

[0034] Fig.14 is a flow chart of an example of a method for performing wireless communications by a UE. DETAILED DESCRIPTION

[0035] 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.

[0036] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it will be apparent to one of ordinary skill in the art that these concepts may be practiced without these specific details. In some instances, structures and components are shown in block diagram form in order to avoid diluting such concepts.

[0037] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0038] As an example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.

[0039] Accordingly, in one or more examples, the described functions may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media, which may be referred to as non-transitory computer-readable media. Non-transitory computer-readable media may not include transient signals. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0040] Various implementations as a whole relate to processes for implementing parameter set configuration, updating, switching, and downloading. In some aspects, a wireless device (e.g., UE) may employ a machine learning model to perform wireless communications. The machine learning model may be used to manage one or more device settings, perform different network layer (e.g., physical layer, MAC layer, RLC layer, PDCP layer, RRC layer, IP layer, transport layer, and application layer) processes, and manage the device configuration of the UE. For example, a machine learning model may be used to dynamically select device settings and configurations to manage battery performance, interference, beams, and antenna usage. In order to improve the performance of the machine learning model, the UE may employ different parameter sets for machine learning based on the state / condition of the UE or the network serving the UE. As used herein, in some aspects, a "parameter set" may refer to one or more coefficients or weights of a machine learning model. However, the device may incur significant signal overhead and utilize valuable storage space to manage different parameter sets for each machine learning model.

[0041] Thus, in some aspects, the UE may be configured to efficiently configure and download parameter set information for machine learning models. As described in detail herein, the UE may receive parameter set information and activate parameter sets associated with the parameter set information based on conditions of the UE or a network serving the UE. In some aspects, the UE may download only parameter sets associated with detected conditions or incremental information corresponding to previously acquired parameter set information. Thus, in some aspects, the UE may be configured with multiple performance parameter sets for multiple machine learning models while reducing signaling overhead, minimizing air interface overhead, and preserving storage space within the device.

[0042] Figure 11 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)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0043] In one aspect, UE 104 may be an Internet of Things (IoT) device, such as (eMTC) or (NB-IoT). In addition, UE 104 may include a parameter set management component (PS MGMT component) 140, which is configured to receive and adopt parameter set configuration, update or switching information received from base station 102 / 180, and activate a parameter set associated with the parameter set configuration information based on detecting an activation condition related to the parameter. In addition, base station 102 / 180 may include a parameter set management component (PS MGMT component) 198, which is configured to send parameter set configuration, update or switching information to UE 104, and manage downloading and activation of parameter sets associated with the parameter set configuration information.

[0044] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: delivery 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 setup 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. The base stations 102 may communicate with each other directly or indirectly (eg, via the EPC 160 or the core network 190) over a third backhaul link 134 (eg, an X2 interface). The third backhaul link 134 may be wired or wireless.

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

[0046] 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.10 standards, LTE, or NR.

[0047] 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.

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

[0049] Whether a small cell 102a or a large cell (e.g., a macro base station), the base station 102 may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in one or more frequency bands within the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, frequency bands, channels, etc. based on frequency / wavelength. In 5GNR, two initial operating bands have been identified as frequency range names FR1 (416 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming issue sometimes arises with FR2, which is often referred to (interchangeably) as the “millimeter wave” band in various documents and articles, although it is different from the extremely high frequency (EHF) band (30GHz to 300GHz) that the International Telecommunication Union (ITU) has identified as the “millimeter wave” (mmW) band.

[0050] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, or can be within the EHF band. Communications using mmW radio frequency bands have extremely high path loss and short range. The mmW base station 180 can utilize beamforming 182 with the UE 104 to compensate for this path loss and short range. The base station 180 and the UE 104 can each include multiple antennas, such as antenna elements, antenna panels, or antenna arrays to facilitate beamforming.

[0051] The base station 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182a. The UE 104 may receive beamformed signals from the base station 180 in one or more receive directions 182b. The UE 104 may also transmit beamformed signals to the base station 180 in one or more transmit directions. The base station 180 may receive beamformed signals from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 180 / UE 104. The transmit direction and receive direction of the base station 180 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0052] 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, or other IP services. The BM-SC 170 may provide functions for MBMS user service configuration and delivery. 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. MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and may be responsible for session management (start / stop) and for collecting eMBMS related billing information.

[0053] The core network 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. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Generally speaking, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are passed through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, or other IP services.

[0054] A base station may include or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver, a wireless base station, a wireless transceiver, a transceiver functional unit, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other appropriate term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a satellite phone, a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, 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.

[0055] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0056] FIG. 2A to FIG. 2D Included are example diagrams 200, 230, 250, and 280 illustrating example structures that may be used for wireless communications by a base station 102 and a UE 104 (e.g., for 5G NR communications). Figure 2A200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G / NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2D 280 is a diagram illustrating an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure can be FDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to DL or UL, or can be TDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and X is flexible between DL / UL, and subframe 3 is configured with slot format 34 (most of which are UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the description presented herein also applies to the 5G / NR frame structure for TDD.

[0057] Other wireless communication technologies may have different frame structures or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots in a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 5 allow 1, 2, 4, 8, 16 and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4 and 8 slots per subframe, respectively. For slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2μ slots per subframe. The subcarrier spacing and symbol length / duration are a function of the parameter set. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 5. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=5 is 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=0 with 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is about 66.7 μs.

[0058] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0059] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (denoted as Rx for a particular configuration, where 100x is the port number, but other DM-RS configurations are also possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0060] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more CCEs, each CCE includes 9 RE groups (REGs), and each REG includes 4 consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine the subframe / symbol timing and the physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (SSB). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not sent through the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0061] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send DM-RS for a physical uplink control channel (PUCCH) and DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. Although not shown, the UE may send a sounding reference signal (SRS). The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

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

[0063] Figure 31 is a block diagram of a base station 102 / 180 in communication with a UE 104 in an access network. In the DL, IP packets from the EPC 160 may be provided to the controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (such as MIB, SIB), RRC connection control (such as RRC connection paging, RRC connection establishment, RRC connection modification and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification) and handover support functions; RLC layer functionality associated with transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling and logical channel prioritization.

[0064] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (such as binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimate may be derived from a reference signal or channel condition feedback sent by the UE 104. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0065] At the UE 104, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 104. If multiple spatial streams are destined for the UE 104, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely transmitted by the base station 102 / 180. These soft decisions can be based on channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 102 / 180 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0066] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.

[0067] Similar to the functionality described in conjunction with DL transmissions performed by base station 102 / 180, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0068] Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 102 / 180 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0069] UL transmissions are processed at the base station 102 / 180 in a manner similar to that described in conjunction with the receiver functionality at the UE 104. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0070] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 104. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.

[0071] In the UE 104, at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform the same Figure 1 In the base station 102 / 180, at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The parameter set management component 198 combines various aspects.

[0072] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or 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.

[0073] 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).

[0074] 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.

[0075] Figure 4 A diagram illustrating an example decomposed base station 400 architecture is shown. The decomposed base station 400 architecture may include one or more central units (CUs) 410 that may communicate directly with a core network 420 via a backhaul link, or indirectly with the core network 420 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 425 via an E2 link, or a non-real-time (non-RT) RIC 415 associated with a service management and orchestration (SMO) framework 405, or both. The CU 410 may communicate with one or more distributed units (DUs) 430 via respective midhaul links, such as an F1 interface. The DU 430 may communicate with one or more radio units (RUs) 440 via respective fronthaul links. The RU 440 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 440.

[0076] Each of the units (i.e., CU 410, DU 430, RU 440, and near-RT RIC 425, non-RT RIC 415, and SMO framework 405) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication 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.

[0077] In some aspects, CU 410 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 that is configured to communicate signals with other control functions hosted by CU 410. CU 410 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 410 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 410 may be implemented to communicate with DU 430 for network control and signaling.

[0078] DU 430 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 440. In some aspects, DU 430 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 430 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 430 or with control functions hosted by CU 410.

[0079] The lower layer functionality may be implemented by one or more RUs 440. In some deployments, a RU 440 controlled by a DU 430 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 440 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 control plane and user plane communications with the RU 440 may be controlled by the corresponding DU 430. In some scenarios, this configuration may enable the implementation of the DU 430 and the CU 410 in a cloud-based RAN architecture (such as a vRAN architecture).

[0080] The SMO framework 405 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 405 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 405 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 490) 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 410, DU 430, RU 440, and near-RT RIC 425. In some specific implementations, the SMO framework 405 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 410) via the O1 interface. Additionally, in some specific implementations, the SMO framework 405 may communicate directly with one or more RUs 440 via the O1 interface. The SMO framework 405 may also include a non-RT RIC 415 configured to support the functionality of the SMO framework 405 .

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

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

[0083] Reference Figures 5 to 14 In one non-limiting aspect, according to some aspects of the present disclosure, system 500 is configured to implement a process for implementing parameter set configuration and downloading.

[0084] Figure 5 is a diagram illustrating example communications and components of network entities and devices. Figure 5 As illustrated, system 500 may include one or more network entities 502(1)-(n) (e.g., base station 102 / 180), one or more UEs 504(1)-(n) (e.g., UE 104), and one or more model repositories 506. Further, in some aspects, network entity 502(1)-(n) may serve UE 504(1)-(n).

[0085] like Figure 5 As illustrated, UE 504(1) may include one or more machine learning models 508(1)-(n), a parameter set management component 510, and parameter set information 512. As described herein, in some aspects, UE 504(1) may employ one or more machine learning (ML) models 508(1)-(n) to perform wireless communications with network entities 502(1)-(n) and / or other UEs 504(2)-(n). For example, UE 504(1) may employ one or more ML models 508(1)-(n) to exchange wireless communications with network entities 502(1)-(n) and other UEs 504(2)-(n) to infer settings and / or configuration parameters for operations performed by UE 504(1) for sending and receiving wireless data. Parameter set management component 510 may manage parameter set information 512(1)-(n) used by one or more ML models 508(1)-(n). Additionally, parameter set information 512(1)-(n) may include parameter sets 514(1)-(n) for one or more ML models 514(1)-(n), identifiers for each of parameter sets 508(1)-(n), and one or more activation conditions identifying when each of the parameter sets should be employed within a corresponding ML model 508 of parameter set 514. In some aspects, parameter set information 512 may include identifiers of parameter sets 514 and corresponding activated conditions, but not parameter sets 514.

[0086] Additionally, in some aspects, parameter set management component 510 can receive parameter set information 512(1)-(n) from network entities 502(1)-(n) and / or model repositories 506(1)-(n). Additionally, parameter set information 512 can be used to enable configuration, updating, switching, and downloading of parameter sets 514(1)-(n). For example, parameter set management component 510 can receive parameter set configuration information 516(1)-(n) and / or parameter sets 514(1)-(n) including parameter set information 512(1)-(n) from network entities 502(1)-(n), and / or parameter sets 514(1)-(n) including parameter set information 512(1)-(n) from model repositories 506(1)-(n). Additionally, parameter set management component 510 can receive updates to parameter set information 512(1)-(n) from network entities 502(1)-(n) and / or model repositories 506(1)-(n). Additionally, parameter set management component 510 can activate parameter sets within parameter set information 512(1)-(n) for UE 504(1).

[0087] like Figure 5 As illustrated, parameter set management component 510 (e.g., parameter set management component 140) can include monitoring component 518, reporting component 520, and activation component 522. Monitoring component 518 can determine a condition of UE 504(1) and / or system 500. For example, monitoring component 518 can determine whether a current condition of UE 504(1) corresponds to an activation condition listed in parameter set information 512(1)-(n). In some aspects, monitoring component 518 can determine whether there has been a change in a monitored performance attribute of UE 504(1) or an associated network entity 502 (e.g., performance degradation of UE 504(1) or network entity 502), a modification to the configuration of UE 504(1) or a network serving UE 504(1), a handover or mobility event associated with UE 504(1), or a state change (e.g., activation, modification, or release) of a service (e.g., network slice, QoS flow, DNN, or PDU session) associated with UE 504(1) or a network serving UE 504(1).

[0088] Reporting component 516 can report conditions of UE 504(1) to network entity 502. For example, reporting component 520 can send condition information to network entity 502. In some aspects, reporting component 520 can send parameter set requests 524(1)-(n) to network entities 502(1)-(n) and model repositories 506(1)-(n). Parameter set requests 524 can identify current conditions of UE 504(1) and / or parameter set identifiers of parameter sets associated with current conditions but not available at UE 504(1). In some aspects, reporting component 520 can send condition reports 526(1)-(n) to network entities 502(1)-(n). Condition reports 526 can identify one or more conditions detected by monitoring component 518. Further, in some aspects, reporting component 516 can report activation of parameter set 514 at UE 504(1). For example, reporting component 516 may transmit activation reports 528(1)-(n) to network entities 502(1)-(n). Activation reports 528 may identify parameter sets 514 activated at UE 504(1). In some aspects, activation reports 528 may be sent using L1 (uplink control information - UCI) / L2 (MAC CE) / or radio resource control (RRC) signaling.

[0089] Activation component 522 may activate parameter sets 514(1)-(n) at UE 504(1). In some aspects, activation component 522 may activate parameter sets 514 in response to monitoring component 518 detecting a condition associated with parameter sets 514. In some other aspects, activation component 522 may activate parameter sets 514 in response to parameter set activations 530(1)-(n) received from network entities 502(1)-(n). For example, UE 504(1) may activate parameter set 514(1) in response to parameter set activation 530(1) identifying parameter set 514(1).

[0090] In addition, UE 504(1) may include a receiver component 532 and a transmitter component 534. Receiver component 532 may include, for example, an RF receiver for receiving signals as described herein. Transmitter component 534 may be configured to generate signals for transmission operations, as described herein. Transmitter component 534 may include, for example, an RF transmitter for transmitting signals as described herein. In one aspect, receiver component 520 and transmitter component 534 may be co-located in a transceiver (e.g., Fig.13 In the transceiver 1310 shown.

[0091] like Figure 5As illustrated, network entity 502 may include parameter set management component 536 (e.g., parameter set management component 198) and parameter set information 538. Parameter set management component 536 may manage parameter set information 512(1)-(n) used by one or more ML models 508(1)-(n) of UE 504(1)-(n). For example, parameter set management component 510 may send parameter set configuration information 516(1) to UE 504(1) and activate parameter sets 514 identified or included in parameter set configuration information 516.

[0092] Parameter set management component 536 (e.g., parameter set management component 198) can include monitoring component 540 and activation component 542. In some aspects, monitoring component 540 can determine conditions of UE 504 and system 500. For example, monitoring component 540 can determine whether a current condition of UE 504(1) corresponds to an activation condition having an associated parameter set 514 (e.g., a parameter set 514 associated with a condition within parameter set configuration information 516(1)-(n)). In some aspects, monitoring component 540 can determine whether there has been a change in a monitored performance attribute of UE 504 or network entity 502(1), a modification to a configuration of UE 504 or system 500, a handover or mobility event associated with UE 504, or a state change (e.g., activation, modification, or release) of a service (e.g., network slice, QoS flow, DNN, or PDU session) associated with UE 504 or system 500. Activation component 542 may activate parameter sets 514(1)-(n) at UE 504(1)-(n). In some aspects, activation component 542 may activate parameter sets 514 at UE in response to determining that current conditions of UE 504 are associated with parameter sets 514. For example, in some aspects, activation component 542 may send parameter set activation 530 to activate parameter sets 514 at UE 504 in response to monitoring component 540 determining that conditions of UE 504 correspond to parameter sets 514. In some other aspects, activation component 542 may send parameter set activation 530 to activate parameter sets 514 at UE 504 in response to receiving a parameter set request 524 or condition report 526 identifying current conditions of UE 504 associated with parameter sets 514. In some aspects, parameter set activation 530 may be sent using L1 (downlink control information - DCI) / L2 (MAC CE) signaling.

[0093] In addition, network entity 502 may include a receiver component 544 and a transmitter component 546. Receiver component 544 may include, for example, a radio frequency (RF) receiver for receiving the signals described herein. Transmitter component 546 may include, for example, an RF transmitter for transmitting the signals described herein. In one aspect, receiver component 544 and transmitter component 546 may be co-located in a transceiver (e.g., Fig.11 In the transceiver 1110 shown.

[0094] like Figure 5 As shown, model repositories 506(1)-(n) may include parameter set information 548(1)-(n). In addition, model repositories 506(1)-(n) may include receiver component 550 and transmitter component 552. Receiver component 550 may include, for example, a radio frequency (RF) receiver for receiving signals as described herein. Transmitter component 552 may include, for example, an RF transmitter for transmitting signals as described herein. In one aspect, receiver component 550 and transmitter component 552 may be co-located in a transceiver.

[0095] Figure 6 6 is a diagram illustrating an example method of configuring parameter set information at a UE according to some aspects of the present disclosure. In some aspects, the network entity 502 and the UE 504 may employ a control plane (C-plane) process 602 or a user plane (U-plane) process 604 for parameter set configuration and updating. For example, in the C-plane process 602, at step 606, the network entity 502 may send ML configuration information (e.g., parameter set configuration information 516) to the UE 504. At step 608, the UE 504 may activate the parameter set (e.g., the parameter set 514 included in the parameter set information 512).

[0096] In some other examples, in the u-plane process 604, at step 610, the network entity 502 may send ML configuration information (e.g., parameter set configuration information 516) to the UE 504. In addition, the ML configuration information may include parameter set identifiers and activation conditions for activating each parameter set corresponding to one of the parameter set identifiers. At step 612, if one or more parameter sets are not available at the UE 504, the UE 504 may download one or more parameter sets (e.g., parameter set 514) from the model repository 506. At step 614, the UE may send an indication to the network entity 502 identifying the parameter sets (e.g., parameter set information 512) available at the UE 504. At step 608, the UE 504 may activate the parameter set (e.g., the parameter set 514 included in the parameter set information 512).

[0097] Figure 75 is a diagram illustrating an example of reconfiguring parameter set information at a UE according to some aspects of the present disclosure. At step 702, the network entity 502 may send ML configuration information (e.g., parameter set configuration information 516(1)) to the UE 504. In addition, the ML configuration information may include parameter set identifiers and activation conditions for activating each parameter set corresponding to one of the parameter set identifiers. At step 704, if the parameter sets (e.g., parameter sets 514) are not available at the UE 504, the UE 504 may retrieve the parameter sets from the model repository 506. At step 706, the UE 504 may receive an ML activation (e.g., parameter set activation 530(1)) from the network entity 502. At step 708, the UE 504 may activate the parameter set (e.g., parameter set 514 included in the parameter set information 512 or downloaded from the model repository 506) in response to the ML activation. At step 710, the UE 504 may receive updated ML configuration information (e.g., parameter set configuration information 516(2)) from the network entity 502. At step 712, if the parameter set or delta information is not available at the UE 504, the UE 504 may retrieve the parameter set or delta information from the model repository 506. In some aspects, the parameter set configuration information 516 and / or the parameter set 514 may provide one or more parameter sets 514 as delta information. As used herein, in some aspects, "delta information" (δ) may refer to the difference between a reference parameter set and a parameter set. Further, in some aspects, the UE 504 may receive a generated parameter set by combining a reference parameter set and delta information corresponding to the parameter set to reduce storage and bandwidth usage. At step 706, the UE may receive an ML activation (e.g., parameter set activation 530(2)) from the network entity 502.

[0098] Figure 8 5 is a diagram illustrating an example of obtaining additional parameter set information at a UE according to some aspects of the present disclosure. In some aspects, each parameter set may not be currently available at the UE 504. For example, the UE 504 may receive parameter set configuration information including a parameter set identifier and corresponding activation conditions for one or more parameter sets. For another example, the UE 504 may receive only a subset of the parameter sets used within the system 500.

[0099] Thus, at step 802 of the C-plane process 804, the UE 504 may send UE assistance information (e.g., condition report 526(1)) to the network entity 502. In some aspects, the UE assistance information may include a condition detected by the UE 504 and / or one or more parameter set identifiers. The parameter set identifier may identify a parameter set available at the UE. Additionally or alternatively, the parameter set identifier may identify a parameter set that is not available at the UE 504 but is required in view of the condition detected at the UE 504. At step 806, the UE 504 may receive a parameter set corresponding to the condition identified within the UE assistance information, or a parameter set identifier of a reference parameter and delta information that may be used to generate a parameter set corresponding to the condition identified within the UE assistance information.

[0100] Thus, at step 802 of the C-plane process 804, the UE 504 may send UE assistance information (e.g., condition report 526(1)) to the network entity 502. In some aspects, the UE assistance information may include a condition detected by the UE 504 and / or one or more parameter set identifiers. The parameter set identifier may identify a parameter set available at the UE. Additionally or alternatively, the parameter set identifier may identify a parameter set that is not available at the UE 504 but is required in view of the condition detected at the UE 504. At step 806, the UE 504 may receive a parameter set corresponding to the condition identified within the UE assistance information, or a parameter set identifier of a reference parameter and delta information that may be used to generate a parameter set corresponding to the condition identified within the UE assistance information.

[0101] In some aspects, the UE 504 may know the parameter set identifier required for the detected condition associated with the UE 504. For example, the UE 504 may be able to determine the parameter set identifier based on the parameter set configuration information 516 received from the network entity 502. Therefore, at step 808 of the first c-plane process 810 between the UE 504 and the model repository 506, when the parameter set is not available at the UE 504, the UE 504 may use the parameter set identifier (e.g., via the parameter set request 524) to retrieve the parameter set associated with the detected condition, or use the parameter set identifier (e.g., via the parameter set request 524) to retrieve a reference master set and delta information used to generate the parameter set associated with the detected condition.

[0102] In some other aspects, the UE 504 may not know the parameter set identifier required for the detected condition associated with the UE 504. Thus, at step 808 of the second c-plane process 810, the UE 504 may send UE assistance information (e.g., condition report 526(2)) to the network entity 502. In some aspects, the UE assistance information may include the condition detected by the UE 504 and / or one or more parameter set identifiers. The parameter set identifier may identify a parameter set available at the UE. At step 812, the UE 504 may receive an ML configuration (e.g., parameter set configuration information 516, parameter set 514) from the network entity 502. At step 814, when the parameter set is not available at the UE 504, the UE 504 may use the parameter set identifier (e.g., via the parameter set request 524) to retrieve the parameter set associated with the detected condition, or use the parameter set identifier (e.g., via the parameter set request 524) to retrieve a reference master set and delta information for generating the parameter set associated with the detected condition.

[0103] Fig. 9 9 is a diagram illustrating an example of downloading parameter set information from a model repository according to some aspects of the present disclosure. At step 902, the UE 504 may construct a uniform resource locator (URL) based on parameter set configuration information 516 received from the network entity 502. At step 904, the UE 504 may send a request (e.g., a Hypertext Transfer Protocol Secure (HTTPS) GET) to the model repository 506 to obtain a URL for a parameter set or incremental information corresponding to the parameter set. At step 906, the UE 504 may receive the parameter set or incremental information from the model repository.

[0104] Fig.10 is a diagram illustrating an example storage structure for storing parameter set information at a model repository according to some aspects of the present disclosure. Fig.10As illustrated, a parameter set identifier 1004 identifying a parameter set 1002 may be at a root level of the storage structure 1000. At a second level, the storage structure 1000 may include the parameter set 1002. Additionally, the second level may include a plurality of reference parameter set identifiers 1004(1)-(n). At a third level, each of the plurality of reference parameter set identifiers may have corresponding delta information 1006(n). For example, the reference parameter set identifier 1004(1) at the second level may be mapped to delta information 1006(1) between the parameter set 1002 and a reference parameter set identified by the reference parameter set identifier 1004(1), the reference parameter set identifier 1004(n) at the second level may be mapped to delta information 1006(n) between the parameter set 1002 and a reference parameter set identified by the reference parameter set identifier 1004(n), and so on. Additionally, in some aspects, the UE 504 may utilize the storage structure to generate a URL for accessing the parameter set or delta information. For example, the UE 504 may generate a URL including a level of a storage structure of parameter sets for accessing parameter sets or delta information that may be used to generate parameter sets (e.g., www.modelrepository.com / required_PS_ID for accessing parameter sets or www.modelrepository.com / required_PS_ID / reference_PS_ID for accessing delta information of parameter sets and reference parameter sets). In addition, the network entity 502 may utilize the storage structure when determining which primary reference and delta information to use. For example, the network entity may use the storage structure of parameter sets to determine a reference parameter set that is closest to a required parameter set based on a detected condition.

[0105] Fig.11 1 is a diagram 1100 illustrating an example of a hardware implementation for a network entity 1102 employing a processing system 1114. The processing system 1114 may be implemented using a bus architecture generally represented by a bus 1124. The bus 1124 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1114 and the overall design constraints. The bus 1124 connects together various circuits including one or more processors and / or hardware components represented by the processor 1104, the parameter set management component 198 / 540, and the computer readable medium / memory 1106. The bus 1124 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0106] The processing system 1114 may be coupled to the transceiver 1110. The transceiver 1110 is coupled to one or more antennas 1120. The transceiver 1110 provides components for communicating with various other devices over a transmission medium. The transceiver 1110 receives signals from the one or more antennas 1120, extracts information from the received signals, and provides the extracted information to the processing system 1114 (specifically, the receiver component 544). The receiver component 544 may receive parameter set requests 524, condition reports 526, and activation reports 528. In addition, the transceiver 1110 receives information from the processing system 1114 (specifically, the transmitter component 546) and generates signals to be applied to the one or more antennas 1120 based on the received information. In addition, the transmitter component 546 may transmit parameter set configuration information 516, parameter sets 514, and parameter set activation 530.

[0107] The processing system 1114 includes a processor 1104 coupled to a computer-readable medium / memory 1106 (e.g., a non-transitory computer-readable medium). The processor 1104 is responsible for general processing, including executing software stored on the computer-readable medium / memory 1106. The software, when executed by the processor 1104, causes the processing system 1114 to perform the various functions described above for any particular device. The computer-readable medium / memory 1106 can also be used to store data manipulated by the processor 1104 when executing the software. The processing system 1114 also includes a parameter set management component 198 / 540. The aforementioned components can be software components running in the processor 1104, resident / stored in the computer-readable medium / memory 1106, one or more hardware components coupled to the processor 1104, or some combination thereof. The processing system 1114 can be a component of the base station 310 and can include a memory 376 and / or at least one of the TX processor 316, the RX processor 370, and the controller / processor 375. Alternatively, the processing system 1114 may be an entire base station (see, for example, Figure 3 of 310, Figure 5 network entity 502).

[0108] The aforementioned means may be one or more of the aforementioned components of the network entity 1102 and / or the processing system 1114 of the network entity 1102 configured to perform the functions recited by the aforementioned means. As described above, the processing system 1114 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Therefore, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0109] Reference Fig.11 and Fig.12In operation, the network entity 1100 may perform the method 1200 of wireless communications by, for example, executing the parameter set management component 198 / 540 via the processor 1104, the computer-readable medium / memory 1106, the TX processor 316, the RX processor 370, and the controller / processor 375.

[0110] At block 1202, method 1200 includes sending, by a network to a user equipment (UE), parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communication by the UE. For example, in an aspect, network entity 1100, processor 1104, computer-readable medium / memory 1106, parameter set management component 198 / 540, and / or receiver component 544 may be configured to receive parameter set configuration information from a network entity or may include means for receiving parameter set configuration information from a network entity, the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communication by the UE. For example, network entity 1102 may send parameter set configuration information 516 to UE 504.

[0111] At block 1204, the method 1200 includes causing activation of a parameter set in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition. For example, in an aspect, the network entity 1100, the processor 1104, the computer-readable medium / memory 1106, the parameter set management component 198 / 540, and / or the activation component 1125 may be configured to activate the parameter set in response to the activation condition or may include means for activating the parameter set in response to the activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition. For example, the network entity 1102 may send the parameter set 514 and / or the parameter set activation 530 to the UE 504. Further, the UE 504 may activate the parameter set of the parameter set information 512 within the ML model 508 based on receiving the parameter set 514 and / or the parameter set activation 530. As described herein, the network entity 1302 may send the parameter set 514 and / or the parameter set activation 530 in response to an activation condition detected by the UE 504 or the network entity 1302. Thus, the network entity 1102 may cause the UE 504 to employ a parameter set that is most appropriate for the ML model used by the UE 504 for wireless communication based on the condition detected by the UE 1302 or a network serving the UE 504.

[0112] Fig.131300 is a diagram illustrating an example of a hardware implementation of a UE 1302 (e.g., UE 104, UE 504, etc.) employing a processing system 1314. The processing system 1314 may be implemented using a bus architecture generally represented by a bus 1324. The bus 1324 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1314 and the overall design constraints. The bus 1324 links various circuits together, including one or more processors and / or hardware components (represented by the processor 1304, the parameter set management component 140 / 510, and the computer-readable medium (e.g., non-transitory computer-readable medium) / memory 1306). The bus 1324 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0113] The processing system 1314 may be coupled to the transceiver 1310. The transceiver 1310 may be coupled to one or more antennas 1320. The transceiver 1310 provides components for communicating with various other devices over a transmission medium. The transceiver 1310 receives signals from the one or more antennas, extracts information from the received signals, and provides the extracted information to the processing system 1314 (specifically, the receiver component 532). The receiver component 532 may receive parameter set configuration information 516, parameter sets 514, and parameter set activation 530. In addition, the transceiver 1310 receives information from the processing system 1314 (specifically, the transmitter component 534) and generates a signal to be applied to the one or more antennas based on the received information. In addition, the transmitter component 534 may transmit a parameter set request 524, a condition report 526, and an activation report 528.

[0114] The processing system 1314 includes a processor 1304 coupled to a computer-readable medium / memory 1306 (e.g., a non-transitory computer-readable medium). The processor 1304 is responsible for general processing, including executing software stored on the computer-readable medium / memory 1306. The software, when executed by the processor 1304, causes the processing system 1314 to perform the various functions described above for any particular device. The computer-readable medium / memory 1306 can also be used to store data manipulated by the processor 1304 when executing the software. The processing system 1314 also includes a parameter set management component 140 / 510. The aforementioned components can be software components running in the processor 1304, resident / stored in the computer-readable medium / memory 1306, one or more hardware components coupled to the processor 1304, or some combination thereof. The processing system 1314 can be a component of the UE 1302 and can include at least one of the memory 360 and / or the TX processor 368, the RX processor 356, and the controller / processor 359. Alternatively, the processing system 1314 may be the entire UE (see, for example, Figure 3 350 Figure 5 UE 504).

[0115] The aforementioned means may be one or more of the aforementioned components of the UE 1302 and / or the processing system 1314 of the UE 1302 configured to perform the functions recited by the aforementioned means. As described above, the processing system 1314 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Therefore, in one configuration, the aforementioned components may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned components.

[0116] Reference Fig.13 and Fig.14 In operation, the UE 1302 may perform method 1400 of wireless communications by, for example, execution of the parameter set management component 140 / 510 via the processor 1304, the computer-readable medium / memory 1306, the TX processor 368, the RX processor 356, and / or the controller / processor 359.

[0117] At block 1402, method 1400 includes receiving parameter set configuration information from a network entity, the parameter set configuration information corresponding to a model structure employed in a machine learning operation used by a UE for wireless communication. For example, in an aspect, UE 504, processor 1304, computer readable medium / memory 1306, parameter set management component 140 / 510, monitoring component 518, and / or receiver component 534 may be configured to send parameter set configuration information by a network to a user equipment (UE) or may include means for sending parameter set configuration information by a network to a user equipment (UE), the parameter set configuration information corresponding to a model structure employed in a machine learning operation used by a UE for wireless communication. For example, UE 1302 may receive parameter set configuration information 516 from network entity 502. In some aspects, as described in detail herein, parameter set configuration information 516 may include parameter set identifiers and / or delta information rather than complete parameter sets to minimize storage usage and / or bandwidth usage.

[0118] At block 1404, method 1400 includes activating a parameter set in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition. For example, in an aspect, UE 1302, UE 504, parameter set management component 140 / 510, processor 1304, computer-readable medium / memory 1306, parameter set management component 140 / 510, monitoring component 518, reporting component 520, activation component 522, receiver component 532, and / or transmitter component 534 may be configured to cause activation of a parameter set in response to an activation condition or may include means for causing activation of a parameter set in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition. For example, UE 1302 may activate a parameter set of parameter set information 512 within ML model 508 based on the activation condition detected by network entity 502 or UE 1302. Thus, the UE 1302 may employ a set of parameters that is most appropriate for the ML model used by the UE 1302 for wireless communications based on conditions detected by the UE 1302 or a network serving the UE 1302 .

[0119] The previous description is provided to enable any person of ordinary skill in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those of ordinary skill in the art, and the universal principles defined in this article can be applied to other aspects. The claims are not intended to be limited to the aspects shown in this article, but should be granted the full scope consistent with the claims in language, wherein the singular reference of the elements is not intended to represent "there is and only one", but "one or more", unless otherwise stated. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B or C, and may include multiples of A, multiples of B or multiples of C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are or will later become known to one of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recited in the claims. Words such as "module," "mechanism," "element," "device," etc. cannot replace the word "component." Therefore, no claim element will be understood to be a component plus function unless the element is expressly recited using the phrase "component for..."

[0120] Sample Clauses

[0121] The following example clauses describe various aspects of the disclosure.

[0122] A. A method for wireless communication by a UE, the method comprising: receiving parameter set configuration information from a network entity, the parameter set configuration information corresponding to a model structure adopted in a machine learning operation used by the UE for wireless communication; and activating a parameter set in response to an activation condition, the parameter set being identified in the parameter set configuration information as being associated with the activation condition.

[0123] B. The method of clause A, wherein the parameter set configuration information comprises the parameter set.

[0124] C. A method according to clause A, wherein the parameter set configuration information includes a parameter set identifier that identifies the parameter set, and further includes sending a request for the parameter set to a repository, the request including the parameter set identifier; and receiving the parameter set in response to the request from the repository.

[0125] D. The method of clause C, further comprising determining that the parameter set is not currently stored at the UE; and wherein sending the request comprises sending the request in response to the parameter set not currently stored at the UE.

[0126] E. A method according to any one of clauses A to D, the method further comprising: detecting the activation condition; identifying the parameter set associated with the activation condition; and wherein activating the parameter set comprises sending a notification to the network entity that the parameter set has been activated.

[0127] F. A method according to any one of clauses A to D, the method further comprising detecting the activation condition; identifying the parameter set associated with the activation condition; sending a request to the network entity to activate the parameter set; and wherein activating the parameter set comprises receiving an indication to activate the parameter set in response to the request.

[0128] G. A method according to any one of clauses A to F, the method further comprising receiving an indication to activate the parameter set in response to the network entity detecting the activation condition; and wherein activating the parameter set comprises activating the parameter set in response to receipt of the indication.

[0129] H. A method according to any one of clauses A to G, wherein the parameter set is an activated parameter set, the parameter set configuration information includes a reference parameter set and incremental information, and

[0130] The method further includes determining the activated parameter set based on the reference parameter set and the delta information.

[0131] I. A method according to any one of clauses A to G, wherein the parameter set is an activated parameter set, the parameter set configuration information includes a reference parameter set identifier and incremental information, and the method further includes identifying a reference parameter set corresponding to the reference parameter set identifier; and determining the activated parameter set based on the reference parameter set and the incremental information.

[0132] J. A method according to any one of clauses A to G, wherein the parameter set is an activated parameter set, the parameter set configuration information includes a reference parameter set identifier and an activated parameter set identifier, and the method further includes sending a request for incremental information to a repository, the request including the reference parameter set identifier and the activated parameter set identifier; receiving the incremental information in response to the request from the repository; and determining the activated parameter set based on the reference parameter set and the incremental information.

[0133] K. A method according to any one of clauses A to J, wherein the parameter set configuration information is updated parameter set configuration information, the parameter set is an updated parameter set, and the activation condition is a current activation condition; and the method also includes activating the updated parameter set in response to the current activation condition, including being configured to switch from an older parameter set associated with a previous parameter set configuration information to the parameter set associated with the updated parameter set configuration information, the older parameter set being associated with the previous activation condition.

[0134] L. A method according to any one of clauses A to K, the method further comprising sending parameter request information including the activation condition and one or more reference candidates to the network entity; and wherein activating the parameter set comprises receiving the parameter set configuration information based on the parameter request information.

[0135] M. A method according to any one of clauses A to D, wherein the activation condition includes at least one of: a change in a monitored performance attribute; a modification to the configuration of the UE or the network serving the UE; a handover or mobility event associated with the UE; or a change in the state of a service associated with the UE or the network serving the UE.

[0136] N. One or more non-transitory computer-readable media encoded with instructions that, when executed by one or more processors, configure a computing device to perform a computer-implemented method as recited in any of clauses A to M.

[0137] O. A device comprising one or more processors and one or more computer-readable media encoded with instructions that, when executed by the one or more processors, configure a computer to perform a computer-implemented method as described in any one of clauses A to M.

[0138] P. An apparatus comprising means for performing a method according to any one of clauses A to M.

[0139] Q. A method for wireless communications by a network entity, the method comprising: sending parameter set configuration information to a user equipment (UE), the parameter set configuration information corresponding to a model structure adopted in a machine learning operation used by the UE for wireless communications; and causing activation of a parameter set in response to an activation condition, the parameter set being identified in the parameter set configuration information as being associated with the activation condition.

[0140] R. A method according to clause Q, wherein the parameter set configuration information includes the parameter set.

[0141] S. The method of clause Q, wherein the parameter set configuration information includes a parameter set identifier that identifies the parameter set.

[0142] T. A method according to clause Q, wherein the parameter set configuration information includes a reference parameter set and increment information configured to be used by the UE to generate the parameter set.

[0143] U. A method according to any one of clauses Q to T, the method further comprising detecting the activation condition; identifying the parameter set associated with the activation condition; and wherein activation of the parameter set in response to the activation condition comprises sending a parameter set identifier to the UE, the parameter set identifier identifying the parameter.

[0144] V. A method according to any one of clauses Q to U, the method further comprising receiving parameter request information including the activation condition and one or more reference candidates from the UE; and wherein causing activation of the parameter set comprises sending the parameter set configuration information based on the parameter request information.

[0145] W. A method according to any one of clauses Q to V, wherein the activation condition includes at least one of: a change in a monitored performance attribute; a modification to the configuration of the UE or the network serving the UE; a handover or mobility event associated with the UE; or a change in the state of a service associated with the UE or the network serving the UE.

[0146] X. One or more non-transitory computer-readable media encoded with instructions that, when executed by one or more processors, configure a computing device to perform a computer-implemented method as recited in any of clauses Q to W.

[0147] Y. A device comprising one or more processors and one or more computer-readable media encoded with instructions that, when executed by the one or more processors, configure a computer to perform a computer-implemented method as described in any one of clauses Q to W.

[0148] Z. An apparatus comprising means for performing a method according to any one of clauses Q to W.

Claims

1. A user equipment (UE) device, the user equipment (UE) device comprising: Memory; and a processor coupled to the memory and configured to: receiving parameter set configuration information from a network entity, the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communication by the UE; as well as A parameter set is activated in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

2. The apparatus according to claim 1, wherein the parameter set configuration information comprises the parameter set.

3. The apparatus of claim 1 , wherein the parameter set configuration information comprises a parameter set identifier identifying the parameter set, and wherein the processor is further configured to: sending a request for the parameter set to a repository, the request including the parameter set identifier; and The set of parameters is received from the repository in response to the request.

4. The apparatus of claim 3, wherein the processor is further configured to: determining that the parameter set is not currently stored at the UE; and Wherein being configured to send the request comprises being configured to send the request in response to the parameter set not currently being stored at the UE.

5. The apparatus of claim 1, wherein the processor is further configured to: detecting the activation condition; identifying the parameter set associated with the activation condition; and Wherein being configured to activate the parameter set includes being configured to send a notification to the network entity that the parameter set has been activated.

6. The apparatus of claim 1, wherein the processor is further configured to: detecting the activation condition; identifying the set of parameters associated with the activation condition; sending a request to the network entity to activate the parameter set; and Wherein being configured to activate the parameter set comprises being configured to receive an indication to activate the parameter set in response to the request.

7. The apparatus of claim 1, wherein the processor is further configured to: In response to the network entity detecting the activation condition, receiving an indication to activate the parameter set; and Wherein being configured to activate the parameter set comprises being configured to activate the parameter set in response to receipt of the indication.

8. The apparatus according to claim 1, wherein the parameter set is an activated parameter set, the parameter set configuration information comprises a reference parameter set and incremental information, and wherein the processor is further configured to: The activated parameter set is determined based on the reference parameter set and the delta information.

9. The apparatus of claim 1 , wherein the parameter set is an activated parameter set, the parameter set configuration information comprises a reference parameter set identifier and increment information, and wherein the processor is further configured to: identifying a reference parameter set corresponding to the reference parameter set identifier; and The activated parameter set is determined based on the reference parameter set and the delta information.

10. The apparatus of claim 1, wherein the parameter set is an activated parameter set, the parameter set configuration information comprises a reference parameter set identifier and an activated parameter set identifier, and wherein the processor is further configured to: sending a request for delta information to a repository, the request including the reference parameter set identifier and the activated parameter set identifier; receiving the incremental information in response to the request from a repository; as well as The activated parameter set is determined based on the reference parameter set and the delta information.

11. The apparatus according to claim 1, wherein the parameter set configuration information is updated parameter set configuration information, the parameter set is an updated parameter set, and the activation condition is a current activation condition; and Wherein being configured to activate the updated parameter set in response to the current activation condition comprises being configured to switch from an older parameter set associated with previous parameter set configuration information to the parameter set associated with the updated parameter set configuration information, the older parameter set being associated with the previous activation condition.

12. The apparatus of claim 1, wherein the processor is further configured to: sending a parameter request message including the activation condition and one or more reference candidates to the network entity; and Wherein being configured to activate the parameter set includes being configured to receive the parameter set configuration information based on the parameter request information.

13. The apparatus of claim 1, wherein the activation condition comprises at least one of the following: Changes in monitored performance attributes; modification of the configuration of the UE or a network serving the UE; a handover or mobility event associated with the UE; or A status change of a service associated with the UE or the network serving the UE.

14. A method for wireless communication by a user equipment (UE), the method comprising: receiving parameter set configuration information from a network entity, the parameter set configuration information corresponding to a model structure employed in a machine learning operation used by the UE for the wireless communication; as well as A parameter set is activated in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

15. The method according to claim 14, wherein the parameter set configuration information comprises a parameter set identifier identifying the parameter set, and further comprising: sending a request for the parameter set to a repository, the request including the parameter set identifier; as well as The set of parameters is received from the repository in response to the request.

16. The method according to claim 14, further comprising: detecting the activation condition; identifying the set of parameters associated with the activation condition; and The activating the parameter set includes sending a notification to the network entity that the parameter set has been activated.

17. The method according to claim 14, further comprising: detecting the activation condition; identifying the set of parameters associated with the activation condition; sending a request to the network entity to activate the parameter set; and Wherein activating the parameter set comprises receiving an indication to activate the parameter set in response to the request.

18. The method according to claim 14, further comprising: receiving, in response to the network entity detecting the activation condition, an indication to activate the parameter set; and Wherein activating the parameter set comprises activating the parameter set in response to receipt of the indication.

19. The method according to claim 14, wherein the parameter set is an activated parameter set, the parameter set configuration information includes a reference parameter set and incremental information, and the method further comprises: The activated parameter set is determined based on the reference parameter set and the delta information.

20. The method according to claim 14, wherein the parameter set is an activated parameter set, the parameter set configuration information comprises a reference parameter set identifier and increment information, and the method further comprises: identifying a reference parameter set corresponding to the reference parameter set identifier; as well as The activated parameter set is determined based on the reference parameter set and the delta information.

21. The method according to claim 14, wherein the parameter set is an activated parameter set, the parameter set configuration information comprises a reference parameter set identifier and an activated parameter set identifier, and the method further comprises: sending a request for delta information to a repository, the request including the reference parameter set identifier and the activated parameter set identifier; receiving the incremental information in response to the request from a repository; as well as The activated parameter set is determined based on the reference parameter set and the delta information.

22. A method for wireless communication by a network entity, the method comprising: sending parameter set configuration information to a user equipment (UE), the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communication by the UE; as well as The activation of a parameter set is caused in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

23. The method of claim 22, wherein the parameter set configuration information comprises the parameter set.

24. The method of claim 22, wherein the parameter set configuration information comprises a parameter set identifier identifying the parameter set.

25. The method of claim 22, wherein the parameter set configuration information comprises a reference parameter set and increment information configured to be used by the UE to generate the parameter set.

26. The method according to claim 22, further comprising: detecting the activation condition; identifying the set of parameters associated with the activation condition; and Wherein causing activation of the parameter set in response to the activation condition comprises sending a parameter set identifier to the UE, the parameter set identifier identifying the parameter.

27. The method according to claim 22, further comprising: receiving, from the UE, parameter request information including the activation condition and one or more reference candidates; and Wherein causing activation of the parameter set comprises sending the parameter set configuration information based on the parameter request information.

28. The method of claim 22, wherein the activation condition comprises at least one of the following: Changes in monitored performance attributes; modification of the configuration of the UE or a network serving the UE; a handover or mobility event associated with the UE; or A status change of a service associated with the UE or the network serving the UE.

29. An apparatus for wireless communication by a network entity, the apparatus comprising: Memory; and a processor coupled to the memory and configured to: sending parameter set configuration information to a user equipment (UE), the parameter set configuration information corresponding to a model structure employed in a machine learning operation for wireless communication by the UE; as well as Activation of a parameter set is caused in response to an activation condition, the parameter set being identified within the parameter set configuration information as being associated with the activation condition.

30. The apparatus of claim 29, wherein the processor is further configured to: detecting the activation condition; identifying the parameter set associated with the activation condition; and Wherein being configured to cause activation of the parameter set in response to the activation condition comprises being configured to send a parameter set identifier to the UE, the parameter set identifier identifying the parameter.

Images