Model selection and delivery

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a mobility management function (MMF) of a core network entity may obtain a trigger for transmitting meta-information associated with a model. The MMF may send an Access and Mobility Management Function (AMF) service invocation message to an AMF of a core network entity. The AMF may obtain an indication of one or more central network entities within the area. The AMF may send meta-information associated with the model to the one or more central network entities. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 484,879, filed on February 14, 2023, entitled “MODEL SELECTION AND DELIVERY,” and U.S. Non-Provisional Patent Application No. 18 / 409,457, filed on January 10, 2024, entitled “MODEL SELECTION AND DELIVERY,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for model selection and delivery. Background Art

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

[0005] Despite the tremendous technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Accordingly, there is a continuing desire to improve the technical performance of wireless communication systems, including, for example, improving the speed and data carrying capacity of communications, improving the efficiency of shared communication media usage, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, and increasing the number and types of wireless communication media available for use. Therefore, there is a need for further improvements in wireless communication systems to overcome the aforementioned technical challenges and others. Summary of the Invention

[0006] One aspect provides a method for wireless communication by a core network entity. The method includes: obtaining, by a model management function (MMF) of the core network entity, a trigger for sending meta-information associated with a model; sending, by the MMF, an AMF service invocation message to an access and mobility management function (AMF) of the core network entity; obtaining, by the AMF, an indication of one or more central network entities within a region; and sending, by the AMF, meta-information associated with the model to the one or more central network entities.

[0007] Another aspect provides a method for wireless communication by a central network entity. The method includes: sending a request for meta information associated with a model to an AMF of a core network entity; and receiving the meta information associated with the model from the AMF.

[0008] Another aspect provides a method for wireless communication by a user equipment (UE). The method includes: sending a model query to an AMF of a core network entity; receiving a model query response from the AMF; and selecting a model based at least in part on the model query response.

[0009] Another aspect provides a method for wireless communication by a core network entity. The method includes: receiving, by an AMF of the core network entity, a model query from a UE; sending, by the AMF, the model query to an MMF of the core network entity; selecting, by the MMF, a model; sending, by the MMF, a model query response to the AMF; and sending, by the AMF, the model query response.

[0010] Another aspect provides a method for wireless communication by a network entity. The method includes: selecting a model by a service management and orchestration (SMO) function of the network entity; and sending an indication of the model by the SMO function of the network entity.

[0011] Another aspect provides a method for wireless communication by a central network entity. The method includes: receiving UE capability information from a UE; selecting a model based at least in part on the UE capability information; sending a model delivery request message to a core network entity; and receiving a model delivery complete indication from the UE.

[0012] Another aspect provides a method for wireless communication by a core network entity. The method includes: receiving, by an Active Management Function (AMF) of the core network entity, a model delivery request message from a central network entity; and sending, by the AMF, a model delivery message including an indication of a model.

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

[0014] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, as well as the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0015] Although various aspects are described in this disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and compositions. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order that the above-described features of the present disclosure may be fully understood, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 An example of a wireless communication network according to the present disclosure is depicted.

[0018] Figure 2 Aspects of example base stations and user equipment (UEs) according to the present disclosure are depicted.

[0019] Figure 3 An example disaggregated base station architecture is depicted.

[0020] Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D Describes a method for use in wireless communication networks such as Figure 1 Various aspects of data structures of wireless communication networks).

[0021] Figure 5 is a diagram illustrating an example of providing meta information to a central network entity.

[0022] Figure 6 is a diagram illustrating an example of UE-triggered model and meta information download from the core network.

[0023] Figure 7 is a diagram illustrating an example of model downloading triggered by a central network entity.

[0024] Figure 8 is a diagram illustrating an example in which a core network function provides a model to a UE based at least in part on a request from a central network entity.

[0025] Figure 9 is a diagram illustrating an example of core network function initiated model delivery.

[0026] Figure 10 is a diagram illustrating an example of model transfer from a core network initiated by a central network entity.

[0027] Figure 11 is a diagram illustrating an example of model transfer from a core network initiated by a central network entity.

[0028] Figure 12 is a diagram illustrating an example of model delivery based at least in part on meta-information stored at a core network entity.

[0029] Figure 13 is a diagram illustrating an example of model transfer from a core network initiated by a central network entity.

[0030] Figure 14 A method for wireless communications by a core network entity is shown.

[0031] Figure 15 A method for wireless communication by a central network entity is shown.

[0032] Figure 16 A method for wireless communication by a UE is shown.

[0033] Figure 17 A method for wireless communications by a core network entity is shown.

[0034] Figure 18 A method for wireless communication by a network entity is shown.

[0035] Figure 19 A method for wireless communication by a central network entity is shown.

[0036] Figure 20 A method for wireless communication by a UE is shown.

[0037] Figure 21is a diagram illustrating an example of a specific implementation of code and circuitry for a communication device.

[0038] Figure 22 is a diagram illustrating an example of a specific implementation of code and circuitry for a communication device.

[0039] Figure 23 is a diagram illustrating an example of a specific implementation of code and circuitry for a communication device.

[0040] Figure 24 is a diagram illustrating an example of a specific implementation of code and circuitry for a communication device.

[0041] Figure 25 is a diagram illustrating an example of a specific implementation of code and circuitry for a communication device.

[0042] Figure 26 is a diagram illustrating an example of a specific implementation of code and circuitry for a communication device.

[0043] Figure 27 is a diagram illustrating an example of a specific implementation of code and circuitry for a communication device. DETAILED DESCRIPTION

[0044] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for model selection and delivery.

[0045] A model (such as an artificial intelligence (AI) or machine learning (ML) model) and / or information associated with the model can be communicated between a UE and one or more network entities (such as a central network entity and / or a core network entity). The information associated with the model can be meta-information that describes how the UE will use the model. For example, the meta-information can indicate a scenario, configuration, setting, or zone associated with the model. Additionally or alternatively, the meta-information can indicate information associated with the operation of the model, such as subcarrier spacing (SCS) information, antenna information, carrier information, or bandwidth part (BWP) information, etc.

[0046] Various delivery methods for models and / or meta-information can be considered. In one example, the model can be communicated between the UE and a central network entity. In another example, the model can be communicated between the UE and a core network entity. In another example, the model can be communicated between the UE and a location management function (LMF). In another example, the model can be communicated between the UE and a server. However, current network interfaces do not support these model delivery methods. For example, current network interfaces may not support communication of event triggering, model query or meta-information update, etc. for model selection and delivery. Therefore, it may be difficult or impossible to communicate models and / or meta-information between the UE, the central network entity, and the core network entity.

[0047] Techniques and apparatus for model selection and delivery are described herein. In some aspects, a core network entity may send a model and / or meta-information associated with the model to a UE. For example, a model management function (MMF) of the core network entity may receive an event trigger, and an access and mobility management function (AMF) of the core network entity may identify one or more central network entities within an area (e.g., a service area or a geographic area) of the UE. The AMF may command one or more central network entities to provide the model or meta-information to the UE. In some other aspects, the MMF may select a model to be used by the UE, and the AMF may send the model or meta-information to the UE. In some other aspects, the central network entity may send an indication of a model to be used by the UE, and the UE may request and receive the model from the AMF or MMF. In some other aspects, the UE may request and receive the model or meta-information from a service management and orchestration (SMO) function. Other example model selection and delivery methods are described herein.

[0048] Using the techniques and apparatus described herein, UEs, central network entities, and / or core network entities can communicate meta-information (or other model information, such as model identifiers) for AI / ML model delivery and updates. For example, the UEs, central network entities, and core network entities can communicate event triggers, model queries, or meta-information to be used for model selection and delivery, etc. This can enable the UE to receive the model or meta-information from the network entity and use the model according to the meta-information (such as according to a scenario, configuration, setting, or zone associated with the model).

[0049] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of protection of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice method. Furthermore, the scope of the present disclosure is intended to cover such apparatus or method that is practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claims.

[0050] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0051] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0052] Figure 1 An example of a wireless communication network 100 according to the present disclosure is depicted.

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

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

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

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

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

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

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

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

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

[0062] Communications using higher frequency bands may have higher path loss and shorter range than communications using lower frequencies. Accordingly, some base stations (e.g., Figure 1182 . BS 110b and UE 120 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS 110b may transmit beamformed signals to UE 120 in one or more transmit directions 182 ′. UE 120 may receive beamformed signals from BS 110b in one or more receive directions 182 ″. UE 120 may also transmit beamformed signals to BS 110b in one or more transmit directions 182 ″. BS 110b may also receive beamformed signals from UE 120 in one or more receive directions 182 ′. BS 110b and UE 120 may then perform beam training to determine optimal receive and transmit directions for each of BS 110b and UE 120. Notably, the transmit direction and receive direction of BS 110b may or may not be the same. Similarly, the transmit direction and receive direction of UE 120 may or may not be the same.

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

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

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

[0066] Generally, user Internet Protocol (IP) packets are delivered through a serving gateway 163, which is connected to a PDN gateway 166. The PDN gateway 166 provides UE IP address allocation and other functions. The PDN gateway 166 and the BM-SC 165 are connected to IP services 168, which may include, for example, the Internet, an intranet, an IP multimedia subsystem (IMS), packet switched (PS) streaming services, and / or other IP services.

[0067] BM-SC 165 can provide functionality for MBMS user service provisioning and delivery. BM-SC 165 can serve as the entry point for content providers' MBMS delivery, can be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or can be used to schedule MBMS delivery. MBMS Gateway 164 can distribute MBMS services to BSs 110 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a specific service, and / or can be responsible for session management (start / stop) and collecting eMBMS-related charging information.

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

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

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

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

[0072] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0073] Figure 2 Aspects of an example BS 110 and UE 120 according to the present disclosure are depicted.

[0074] Generally speaking, BS 110 includes various processors (e.g., 220, 230, 238, and 240), antennas 234a-234t (collectively 234), transceivers 232a-232t (collectively 232) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 212) and wireless reception of data (e.g., data sink 239). For example, BS 110 can transmit and receive data between BS 110 and UE 120. BS 110 includes a controller / processor 240 that can be configured to implement various functions described herein related to wireless communication.

[0075] Generally speaking, the UE 120 includes various processors (e.g., 258, 264, 266, and 280), antennas 252a-252r (collectively, 252), transceivers 254a-254r (collectively, 254) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 262) and wireless reception of data (e.g., provided to a data sink 260). The UE 120 includes a controller / processor 280 that can be configured to implement various functions described herein related to wireless communications.

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

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

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

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

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

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

[0082] At BS 110, uplink signals from UE 120 may be received by antennas 234a-234t, processed by demodulators in transceivers 232a-232t, detected by MIMO detector 236 where applicable, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. Memory 242 and memory 282 may store data and program codes (e.g., processor-executable instructions, computer-executable instructions) for BS 110 and UE 120, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0083] In various aspects, the BS 110 may be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as from a data source 212, a scheduler 244, a memory 242, a transmit processor 220, a controller / processor 240, a TX MIMO processor 230, transceivers 232a-232t, antennas 234a-234t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as from antennas 234a-234t, transceivers 232a-232t, an RX MIMO detector 236, a controller / processor 240, a receive processor 238, a scheduler 244, a memory 242, a network interface, and / or other aspects described herein.

[0084] In various aspects, the UE 120 may also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" may refer to various mechanisms for outputting data, such as from a data source 262, memory 282, transmit processor 264, controller / processor 280, TX MIMO processor 266, transceivers 254a-254t, antennas 252a-252t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as from antennas 252a-252t, transceivers 254a-254t, RX MIMO detector 256, controller / processor 280, receive processor 258, memory 282, and / or other aspects described herein.

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

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

[0087] Although Figure 2 The blocks in FIG. 2 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0088] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0089] The deployment of a communication system such as a 5G NR system can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station or network equipment may be implemented in an aggregated architecture or a decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functions may be implemented as an aggregated base station (also known as an independent base station or a monolithic base station) or a decomposed base station. A “network entity” or a “network node” may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0090] A converged base station (e.g., a converged network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually spread across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among others.

[0091] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0092] Figure 3 An example decomposed base station 300 architecture is depicted. The decomposed base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with the SMO framework 305, or both. The CUs 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links, such as the F1 interface. The DUs 330 may communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. The RUs 340 may communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0093] Each of the units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or transmit 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 the unit, may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or transmit signals, or both, to one or more of the other units over a wireless transmission medium.

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

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

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

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

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

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

[0100] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0101] Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D Described is a method for wireless communication networks such as Figure 1 Various aspects of the data structure of the wireless communication network 100). Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D FIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0102] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single Carrier Frequency Division Multiplexing (SC-FDM) will (for example, Figure 4B and Figure 4D The system bandwidth (as depicted in FIG) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

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

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

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

[0106] like Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D As depicted in FIG, a resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending over, for example, 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.

[0107] like Figure 4AAs illustrated, some of the REs carry reference (pilot) signals (RSs) for a UE (e.g., UE 120). The RSs may include demodulation RSs (DMRSs) and / or channel state information reference signals (CSI-RSs) for channel estimation at the UE. The RSs may also include beamforming RSs (BRSs), beam refinement RSs (BRRSs), and / or phase tracking RSs (PT-RSs).

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

[0109] A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by a UE (eg, UE 120) to determine subframe / symbol timing and physical layer identification.

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

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

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

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

[0114] As indicated above, Figures 4A to 4D are provided as examples. Other examples can be found in the Figures 4A to 4D The examples described are different.

[0115] Models (such as AI / ML models) and / or information associated with the models can be communicated between the UE and one or more network entities (such as central network entities and / or core network entities). The information associated with the model can be meta-information that describes how the UE will use the model. For example, the meta-information can indicate a scenario, configuration, setting, or zone associated with the model. Additionally or alternatively, the meta-information can indicate information associated with the operation of the model, such as SCS information, antenna information, carrier information, or BWP information.

[0116] In some cases, multiple models or model structures may be defined for a Machine Learning Function Name (MLFN). In some cases, a single model structure may be associated with multiple parameter sets (e.g., each parameter set has different weights). During operation, the UE may use one or more models based at least in part on the scenario, configuration, setting, and / or zone associated with the model. Additionally or alternatively, the UE may use one or more models based at least in part on SCS information, antenna information, carrier information, or BWP information.

[0117] Various delivery methods for models and / or meta-information can be considered. In one example, the model can be communicated between the UE and a central network entity. In another example, the model can be communicated between the UE and a core network entity. In another example, the model can be communicated between the UE and an LMF. In another example, the model can be communicated between the UE and a server. However, current network interfaces do not support these model delivery methods. For example, current network interfaces may not support communication of event triggers for model selection and delivery, model queries, or meta-information updates, etc. Therefore, communicating models and / or meta-information between the UE, the central network entity, and the core network entity may be difficult or even impossible.

[0118] Techniques and apparatus for model selection and delivery are described herein. In some aspects, a core network entity may send a model and / or meta-information associated with the model to a UE. For example, the MMF of the core network entity may receive an event trigger, and the AMF of the core network entity may identify one or more central network entities within an area (e.g., a service area or a geographic area) of the UE. The AMF may command one or more central network entities to provide the model or meta-information to the UE. In some other aspects, the MMF may select a model to be used by the UE, and the AMF may send the model or meta-information to the UE. In some other aspects, the central network entity may send an indication of a model to be used by the UE, and the UE may request and receive the model from the AMF or MMF. In some other aspects, the UE may request and receive the model or meta-information from the SMO. Other example model selection and delivery methods are described herein.

[0119] Using the techniques and apparatus described herein, UEs, central network entities, and / or core network entities can communicate meta-information (or other model information, such as model identifiers) for AI / ML model delivery and updates. For example, the UE, central network entity, and core network entity can communicate event triggers, model queries, or meta-information to be used for model selection and delivery, among other things. This can enable the UE to receive a model or meta-information from a network entity and use the model based on the meta-information, such as based on a scenario, configuration, setting, or zone associated with the model. Some examples of meta-information availability, decision making, and model management are shown in Table 1 below.

[0120] Table 1

[0121]

[0122]

[0123] Figure 55 is a diagram illustrating an example 500 of providing meta-information to a central network entity according to the present disclosure. Central network entity 505 may communicate with AMF 510 and / or MMF 515. Central network entity 505 may be an NG-RAN node. AMF 510 and MMF 515 may be associated with a core network. For example, AMF 510 may be an AMF of the core network, and MMF 515 may be an MMF of the core network. In some aspects, AMF 510 and MMF 515 may be other entities associated with the core network. For example, AMF 510 may be a first core network entity, and MMF 515 may be a second core network entity.

[0124] The MMF 515 may obtain or detect an event trigger, as indicated by reference numeral 520. The event trigger may be associated with a request for meta-information associated with the model or an update to the meta-information associated with the model.

[0125] As shown in reference numeral 525, the MMF 515 may send an AMF service call message, and the AMF 510 may receive the AMF service call message. The MMF 515 may send the AMF service call message based at least in part on obtaining or detecting an event trigger. The AMF service call message may include, for example, a meta information update. The meta information update may include information such as a model identifier associated with the model, a model identifier list including an identifier associated with the model, meta information associated with the model, and / or a region indication (such as a service region indication or a geographic region indication).

[0126] As indicated by reference numeral 530, the AMF 510 may determine or identify one or more central network entities within an area (such as the area indicated in the AMF service invocation message). The AMF 510 may identify or determine the one or more central network entities, such as the central network entity 505, based at least in part on receiving the service invocation message.

[0127] As indicated by reference numeral 535, the AMF 510 may send the meta information and the central network entity 505 may receive the meta information. The AMF 510 may send the meta information based at least in part on determining or identifying one or more central network entities. In some aspects, the meta information may be associated with a meta information update and may include, for example, a model identifier associated with a model and / or a model identifier list including identifiers associated with a model.

[0128] As indicated by reference numeral 540, the central network entity 505 may send a meta information update request, and the core network (e.g., AMF 510 and / or MMF 515) may receive the meta information update request. The meta information update request may include a model identifier associated with the model to be updated and / or a model identifier list including a model identifier associated with the model to be updated.

[0129] As shown by reference numeral 545, the core network (e.g., AMF 510 and / or MMF 515) may send a meta information update response, and the central network entity 505 may receive the meta information update response. The core network may send the meta information update response based at least in part on receiving the meta information update request. The meta information update response may include, for example, meta information associated with the model indicated by the model identifier or the model identifier list.

[0130] In some aspects, the core network (e.g., MMF 515) may provide meta-information associated with a model to the central network entity 505 based at least in part on an event trigger (such as when meta-information associated with the model changes) or based at least in part on a request from the central network entity 505 (such as when the central network entity 505 requests to retrieve updated meta-information associated with the model).

[0131] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0132] Figure 6 is a diagram illustrating an example 600 of UE-triggered model and meta information download from a core network according to the present disclosure.

[0133] As shown in reference numeral 605, UE 120 may send a model query, and the core network (e.g., AMF 510 and / or MMF 515) may receive the model query. In some aspects, sending the model query may include sending an uplink non-access stratum (NAS) transport message, a category 1 NAS message, a category 2 NAS message, a category 1 message, or a category 2 message including the model query. The uplink NAS transport message, the category 1 NAS message, the category 2 NAS message, the category 1 message, or the category 2 message may include an MMF indication, information associated with the MMF, and / or the model query. The model query may include UE capability information and / or area information, among other things. In some aspects, the uplink NAS transport message, the category 1 NAS message, the category 2 NAS message, the category 1 message, or the category 2 message may include a payload. In some aspects, the area information may include service area information or geographic area information. The geographic area information may be associated with a registration area, such as a tracking area indication (TAI) or a tracking area code (TAC).

[0134] As indicated by reference numeral 610, the AMF 510 may select an MMF. The AMF 510 may select an MMF (e.g., MMF 515) based at least in part on receiving a model query (such as based at least in part on receiving an uplink NAS transport message, a Category 1 NAS message, a Category 2 NAS message, a Category 1 message, or a Category 2 message including a model query).

[0135] As indicated by reference numeral 615, the AMF 510 may send a model query, and the MMF 515 may receive the model query. The AMF 510 may send the model query to the MMF 515 based at least in part on selecting the MMF 515. In some aspects, the AMF 510 may forward the model query to the MMF 515 without processing the model query.

[0136] As indicated by reference numeral 620, the MMF 515 may send an additional information request, and the AMF 510 may receive the additional information request. The MMF 515 may send the additional information request based at least in part on receiving a model query (such as based at least in part on receiving an uplink NAS transport message, a Class 1 NAS message, a Class 2 NAS message, a Class 1 message, or a Class 2 message that includes a model query). The additional information request may be a request for additional information associated with a geographic area, for example, when the model is only valid in a certain TAI.

[0137] As indicated by reference numeral 625, the AMF 510 may send the additional information, and the MMF 515 may receive the additional information. The AMF 510 may send the additional information based at least in part on receiving the request for the additional information.

[0138] As indicated by reference numeral 630, the MMF 515 may perform model selection and / or determine model availability. The MMF 515 may select a model and / or determine model availability based at least in part on receiving a model query, such as based at least in part on receiving an uplink NAS transport message, a Class 1 NAS message, a Class 2 NAS message, a Class 1 message, or a Class 2 message that includes a model query. The MMF 515 may select a model and / or determine model availability based at least in part on information included in the model query, such as UE capability information and / or region information.

[0139] As shown in reference numeral 635, the core network (e.g., AMF 510 and / or MMF 515) may send a model query response, and the UE 120 may receive the model query response. The core network may send the model query response based at least in part on selecting a model or determining that a model is available. The model query response may be included in a registration accept message, a downlink NAS transport message, a category 1 NAS message, a category 2 NAS message, a category 1 message, or a category 2 message. The downlink NAS transport message, the category 1 NAS message, the category 2 NAS message, the category 1 message, or the category 2 message may include the model, meta information associated with the model, and / or an identifier associated with the model.

[0140] As indicated by reference numeral 640, UE 120 may perform model selection. UE 120 may select a model based at least in part on receiving a registration accept message, a downlink NAS transport message, a category 1 NAS message, a category 2 NAS message, a category 1 message, or a category 2 message. UE 120 may select a model based at least in part on meta information associated with the model and / or an identifier associated with the model.

[0141] As indicated by reference numeral 645, UE 120 may transmit UE capability information, and central network entity 505 may receive the UE capability information. UE 120 may transmit the UE capability information based at least in part on the selection model. The UE capability information may be updated UE capability information associated with the usage model. UE 120 may determine and transmit the updated UE capability information based at least in part on the meta-information.

[0142] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0143] Figure 7 is a diagram illustrating an example 700 of model downloading triggered by a central network entity according to the present disclosure.

[0144] As indicated by reference numeral 705, the UE 120 may transmit UE capability information, and the central network entity 505 may receive the UE capability information.

[0145] The central network entity 505 may perform model selection, as indicated by reference numeral 710. The central network entity 505 may select a model based at least in part on receiving UE capability information.

[0146] As indicated at reference numeral 715, the central network entity 505 may send a model download request, and the UE 120 may receive the model download request. The central network entity 505 may send the model download request based at least in part on selecting a model.

[0147] As indicated by reference numeral 720, the UE 120, the central network entity 505, the AMF 510, and / or the MMF 515 may perform UE-triggered download of the model and meta information from the core network. For example, the UE 120, the central network entity 505, the AMF 510, and the MMF 515 may perform one or more of the processes described above in conjunction with reference numerals 605, 610, 615, 620, 625, 630, 635, 640, and / or 645.

[0148] As indicated at reference numeral 725, the UE 120 may send a model download complete message and the central network entity 505 may receive the model download complete message. The UE 120 may send the model download complete message based at least in part on downloading the model from the core network.

[0149] In some aspects, the central network entity 505 may request the UE 120 to download one or more models from the core network by transmitting a message including a model download request to the UE 120. The model download request may include a model identifier associated with the model (if known) and / or may include assistance information for supporting model selection at the MMF 515. The assistance information may include, for example, carrier frequency information (e.g., FR1 or FR2), SCS information, BWP information, antenna tilt information, antenna pattern information, scenario information, configuration information, or zone information, among others.

[0150] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0151] Figure 8 is a diagram illustrating an example 800 of an OAM / SMO providing a model to a UE based at least in part on a request from a central network entity in accordance with the present disclosure. The UE 120 and / or the central network entity 505 may communicate with the OAM / SMO 805.

[0152] As indicated by reference numeral 810, the UE 120 may send a model delivery request, and the central network entity 505 may receive the model delivery request.

[0153] As indicated by reference numeral 815, the central network entity 505 may send a model delivery request, and the OAM / SMO 805 may receive the model delivery request. The central network entity 505 may send the model delivery request to the OAM / SMO 805 based at least in part on receiving the model delivery request from the UE 120. The model delivery request may include a model identifier associated with the model and / or may include UE assistance information. The central network entity 505 may send the model delivery request to the OAM / SMO 805 using a Class 1 message, a Class 2 message, or an RIC indication for a near real-time RAN intelligent controller (RIC), among others.

[0154] As shown by reference numeral 820, OAM / SMO 805 may send a model delivery message, and central network entity 505 may receive the model delivery message. The model delivery message may include the model and / or meta-information associated with the model. OAM / SMO 805 may send the model delivery message based at least in part on receiving the model delivery request. Model delivery may be performed using control plane signaling or user plane signaling.

[0155] As indicated by reference numeral 825, the central network entity 505 may send a model delivery message, and the UE 120 may receive the model delivery message. The central network entity 505 may send the model delivery message to the UE 120 based at least in part on receiving the model delivery message from the OAM / SMO 805.

[0156] In some aspects, the central network entity 505 may request the OAM / SMO 805 to deliver the model to the UE 120 by providing a model identifier associated with the model or by providing UE assistance information to facilitate model selection by the OAM / SMO 805 .

[0157] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0158] Figure 9 is a diagram illustrating an example 900 of OAM / SMO initiated model delivery according to the present disclosure.

[0159] As indicated by reference numeral 905, the UE 120 may transmit UE capability information, and the central network entity 505 may receive the UE capability information.

[0160] As indicated by reference numeral 910, the central network entity 505 may send UE capability information and the OAM / SMO 805 may receive the UE capability information. The central network entity 505 may send the UE capability information to the OAM / SMO 805 based at least in part on receiving the UE capability information from the UE 120.

[0161] As indicated by reference numeral 915, the central network entity 505 may send RAN information, and the OAM / SMO 805 may receive the RAN information. The central network entity 505 may send the RAN information based at least in part on the request for RAN information from the OAM / SMO 805. The RAN information may include, for example, UE context information and / or RAN configuration information, among other things.

[0162] The OAM / SMO 805 may determine to initiate an AI / ML based procedure, as indicated by reference numeral 920. The OAM / SMO 805 may determine to initiate an AI / ML based procedure based at least in part on receiving UE capability information and / or RAN information.

[0163] As shown at 925, the OAM / SMO 805 may send an assistance information request, and the central network entity 505 may receive the assistance information request. The OAM / SMO 805 may send the assistance information request based at least in part on determining to initiate an AI / ML-based process. The assistance information may be assistance information associated with execution model selection.

[0164] As indicated by reference numeral 930, the central network entity 505 may send the assistance information, and the OAM / SMO 805 may receive the assistance information. The central network entity 505 may send the assistance information to the OAM / SMO 805 based at least in part on receiving the assistance information request.

[0165] As indicated by reference numeral 935, the OAM / SMO 805 may initiate a signaling or management-based AI / ML operation. In some aspects, the OAM / SMO 805 may send an indication of the signaling or management-based AI / ML operation to the UE 120. Additionally or alternatively, the OAM / SMO 805 may send the indication of the signaling or management-based AI / ML operation to the central network entity 505, and the central network entity 505 may forward the indication of the signaling or management-based AI / ML operation to the UE 120.

[0166] In some aspects, the OAM / SMO 805 may determine to initiate an AI / ML-based procedure for a group of UEs, for example, by accessing RAN and UE information from a RIC database. Based on information available at the RIC database and / or UE assistance information, the OAM / SMO 805 may select a model and may deliver (e.g., send) the model to the UE 120. In some aspects, a signaling or management-based procedure may be used to initiate AI / ML-based operations and / or to provide the model to the UE 120 (and / or other UEs).

[0167] As indicated above, Figure 9 are provided as examples. Other examples can be found in the Figure 9 The examples described are different.

[0168] Figure 10 is a diagram illustrating an example 1000 of model transfer from a core network initiated by a central network entity according to the present disclosure.

[0169] As indicated by reference numeral 1005, the UE 120 may transmit UE capability information, and the central network entity 505 may receive the UE capability information.

[0170] The central network entity 505 may perform model selection, as indicated by reference numeral 1010. The central network entity 505 may select a model based at least in part on the UE capability information.

[0171] As indicated by reference numeral 1015, the central network entity 505 may send an indication of model delivery from the core network, and the UE 120 may receive the indication. For example, the central network entity 505 may send an indication to the UE 120 that the model is to be delivered to the UE 120 by the core network.

[0172] As indicated by reference numeral 1020, the central network entity 505 may send a model delivery request, and the AMF 510 may receive the model delivery request. The central network entity 505 may send the model delivery request based at least in part on the selection of a model. The model delivery request may include a model identifier associated with the selected model.

[0173] As indicated by reference numeral 1025, the AMF 510 may send a model delivery request, and the MMF 515 may receive the model delivery request. The AMF 510 may send the model delivery request to the MMF 515 based at least in part on receiving the model delivery request from the central network entity 505. The model delivery request may include a model identifier associated with the selected model.

[0174] As indicated by reference numeral 1030, the MMF 515 may send a model delivery message, and the AMF 510 may receive the model delivery message. The MMF 515 may send the model delivery message based at least in part on receiving the model delivery request. The model delivery message may include the requested model or an indication of the requested model.

[0175] As indicated by reference numeral 1035, the AMF 510 may send a model delivery message, and the UE 120 may receive the model delivery message. The AMF 510 may send the model delivery message to the UE 120 based at least in part on receiving the model delivery message from the MMF 515. In some aspects, sending the model delivery message may include sending a downlink NAS transfer message, a category 1 message, or a category 2 message including the model delivery message.

[0176] As indicated by reference numeral 1040, UE 120 may send a model delivery confirmation (ACK) message, and AMF 510 may receive the model delivery confirmation (ACK) message. UE 120 may send the model delivery ACK message based at least in part on receiving the model delivery message. In some aspects, sending the model delivery ACK message may include sending a NAS message including the model delivery ACK message.

[0177] As indicated by reference numeral 1045, the AMF 510 may send a Model Delivery ACK message, and the MMF 515 may receive the Model Delivery ACK message. The AMF 510 may send the Model Delivery ACK message to the MMF 515 based at least in part on receiving the Model Delivery ACK message from the UE 120.

[0178] As indicated by reference numeral 1050, UE 120 may send a model delivery complete message, and central network entity 505 may receive the model delivery complete message. The model delivery complete message may indicate to central network entity 505 that UE 120 has received the model. In some aspects, sending the model delivery complete message may include sending an RRC message or a MAC control element (MAC-CE) including the model delivery complete message.

[0179] In some aspects, the NG-RAN interface may be enhanced for indicating a model identifier associated with a model that requires delivery to the UE 120 using either a Class 1 message or a Class 2 message.

[0180] As indicated above, Figure 10 are provided as examples. Other examples can be found in the Figure 10 The examples described are different.

[0181] Figure 11is a diagram illustrating an example 1100 of model transfer from a core network initiated by a central network entity according to the present disclosure.

[0182] As indicated by reference numeral 1105, the UE 120 may transmit UE capability information, and the central network entity 505 may receive the UE capability information.

[0183] The central network entity 505 may perform model selection, as indicated by reference numeral 1110. The central network entity 505 may select a model based at least in part on the UE capability information.

[0184] As indicated by reference numeral 1115, the central network entity 505 may send a model delivery request, and the AMF 510 may receive the model delivery request. The central network entity 505 may send the model delivery request to the AMF 510 based at least in part on the selection of the model. The model delivery request may include a model identifier associated with the selected model.

[0185] As indicated by reference numeral 1120, the AMF 510 may send a model delivery request, and the MMF 515 may receive the model delivery request. The AMF 510 may send the model delivery request to the MMF 515 based at least in part on receiving the model delivery request from the central network entity 505. The model delivery request may include a model identifier associated with the selected model.

[0186] As indicated by reference numeral 1125, the MMF 515 may send a model delivery message, and the AMF 510 may receive the model delivery message. The MMF 515 may send the model delivery message based at least in part on receiving the model delivery request message. The model delivery message may include the requested model and / or may include an indication of the requested model.

[0187] As indicated by reference numeral 1130, the AMF 510 may send a model delivery message and the central network entity 505 may receive the model delivery message. The AMF 510 may send the model delivery message to the central network entity 505 based at least in part on receiving the model delivery message from the MMF 515.

[0188] As indicated by reference numeral 1135, the central network entity 505 may send a model delivery ACK message, and the AMF 510 may receive the model delivery ACK message. The central network entity 505 may send the model delivery ACK message based at least in part on receiving the model delivery message.

[0189] As indicated by reference numeral 1140, the AMF 510 may send a model delivery ACK message, and the MMF 515 may receive the model delivery ACK message. The AMF 510 may send the model delivery ACK message to the MMF 515 based at least in part on receiving the model delivery ACK message from the central network entity 505.

[0190] As indicated by reference numeral 1145, the central network entity 505 may send a model delivery message, and the UE 120 may receive the model delivery message. The model delivery message may include the model and / or may include an indication of the model. In some aspects, sending the model delivery message may include sending an RRC message including the model delivery message.

[0191] As indicated by reference numeral 1150, UE 120 may send a model delivery complete message, and central network entity 505 may receive the model delivery complete message. UE 120 may send the model delivery complete message based at least in part on receiving the model delivery complete message. In some aspects, sending the model delivery complete message may include sending an RRC message including the model delivery complete message.

[0192] In some aspects, the NG-RAN interface can be enhanced to indicate a model identifier associated with a model to be delivered to the UE 120 using a Class 1 message or a Class 2 message. The AMF 510 can transmit a model discovery and model delivery request message to the MMF 515. Additionally or alternatively, the NG-RAN interface can be enhanced to deliver the model from the core network to the NG-RAN. The NG-RAN can send the model to the UE 120 using an RRC message after receiving the model from the core network.

[0193] As indicated above, Figure 11 are provided as examples. Other examples can be found in the Figure 11 The examples described are different.

[0194] Figure 12 is a diagram illustrating an example 1200 of model delivery based at least in part on meta-information stored at a core network entity in accordance with the present disclosure.

[0195] As indicated by reference numeral 1205, the UE 120 may transmit UE capability information, and the central network entity 505 may receive the UE capability information.

[0196] As indicated by reference numeral 1210, the central network entity 505 may send an indication of model delivery from the core network, and the UE 120 may receive the indication. For example, the central network entity 505 may send an indication to the UE 120 that the model is to be delivered to the UE 120 by the core network.

[0197] As indicated by reference numeral 1215, the central network entity 505 may send a model delivery request, and the AMF 510 may receive the model delivery request. The central network entity 505 may send the model delivery request to the AMF 510 based at least in part on receiving the UE capability information. In some aspects, the model delivery request may include UE assistance information.

[0198] As indicated by reference numeral 1220, the AMF 510 may send a model delivery request, and the MMF 515 may receive the model delivery request. The AMF 510 may send the model delivery request to the MMF 515 based at least in part on receiving the model delivery request from the central network entity 505. The model delivery request may include UE assistance information.

[0199] As indicated by reference numeral 1225, the MMF 515 may perform model selection and / or determine model availability. The MMF 515 may select a model or determine model availability based at least in part on the model delivery request, such as based at least in part on UE assistance information.

[0200] As shown in reference numeral 1230, the MMF 515 may send a model delivery message, and the AMF 510 may receive the model delivery message. The MMF 515 may send the model delivery message based at least in part on selecting a model or determining model availability. The model delivery message may include the selected model and / or may include an indication of the selected model.

[0201] As indicated by reference numeral 1235, the AMF 510 may send a model delivery message, and the UE 120 may receive the model delivery message. The AMF 510 may send the model delivery message to the UE 120 based at least in part on receiving the model delivery message from the MMF 515. In some aspects, sending the model delivery message may include sending a downlink NAS transfer message, a category 1 message, or a category 2 message including the model delivery message.

[0202] As indicated by reference numeral 1240, UE 120 may send a Model Delivery ACK message, and AMF 510 may receive the Model Delivery ACK message. UE 120 may send the Model Delivery ACK message based at least in part on receiving the Model Delivery ACK message. In some aspects, sending the Model Delivery ACK message may include sending a NAS message including the Model Delivery ACK message.

[0203] As indicated by reference numeral 1245, the AMF 510 may send a Model Delivery ACK message, and the MMF 515 may receive the Model Delivery ACK message. The AMF 510 may send the Model Delivery ACK message to the MMF 515 based at least in part on receiving the Model Delivery ACK message from the UE 120.

[0204] As indicated by reference numeral 1250, UE 120 may send a model delivery complete message, and central network entity 505 may receive the model delivery complete message. The model delivery complete message may indicate to central network entity 505 that UE 120 has received (and / or downloaded) the model. In some aspects, sending the model delivery complete message may include sending an RRC message or a MAC-CE including the model delivery complete message.

[0205] In some aspects, the NG-RAN interface may be enhanced to use a Class 1 message or a Class 2 message to provide UE assistance information for model selection at the MMF 515. The assistance information may include, for example, carrier frequency information (e.g., FR1 or FR2), SCS information, BWP information, antenna tilt information, antenna pattern information, scenario information, configuration information, or a zone identifier, etc. A flexible protocol may be used so that the assistance information can be extended.

[0206] As indicated above, Figure 12 are provided as examples. Other examples can be found in the Figure 12 The examples described are different.

[0207] Figure 13 is a diagram illustrating an example 1300 of model transfer from a core network initiated by a central network entity according to the present disclosure.

[0208] As indicated by reference numeral 1305, the UE 120 may transmit UE capability information, and the central network entity 505 may receive the UE capability information.

[0209] As indicated by reference numeral 1310, the central network entity 505 may send a model delivery request and the AMF 510 may receive the model delivery request. The central network entity 505 may send the model delivery request based at least in part on receiving the UE capability information. The model delivery request may include UE assistance information.

[0210] As indicated by reference numeral 1315, the AMF 510 may send a model delivery request, and the MMF 515 may receive the model delivery request. The AMF 510 may send the model delivery request to the MMF 515 based at least in part on receiving the model delivery request from the UE 120. The model delivery request may include a model identifier associated with the model.

[0211] As indicated by reference numeral 1320, the MMF 515 may perform model selection and / or determine model availability. The MMF 515 may select a model or determine model availability based at least in part on the model delivery request, such as based at least in part on UE assistance information or a model identifier.

[0212] As indicated by reference numeral 1325, the MMF 515 may send a model delivery message, and the AMF 510 may receive the model delivery message. The MMF 515 may send the model delivery message based at least in part on selecting a model or determining model availability. The model delivery message may include the selected model and / or may include an indication of the selected model.

[0213] As indicated by reference numeral 1330, the AMF 510 may send a model delivery message, and the central network entity 505 may receive the model delivery message. The AMF 510 may send the model delivery message to the central network entity 505 based at least in part on receiving the model delivery message from the MMF 515. The model delivery message may include the selected model and / or may include an indication of the selected model.

[0214] As indicated by reference numeral 1335, the central network entity 505 may send a model delivery ACK message, and the AMF 510 may receive the model delivery ACK message. The central network entity 505 may send the model delivery ACK message based at least in part on receiving the model delivery message.

[0215] As indicated by reference numeral 1340, the AMF 510 may send a model delivery ACK message, and the MMF 515 may receive the model delivery ACK message. The AMF 510 may send the model delivery ACK message to the MMF 515 based at least in part on receiving the model delivery ACK message from the central network entity 505.

[0216] As indicated by reference numeral 1345, the central network entity 505 may send a model delivery message, and the UE 120 may receive the model delivery message. The model delivery message may include the model and / or may include an indication of the model. In some aspects, sending the model delivery message may include sending an RRC message including the model delivery message.

[0217] As indicated by reference numeral 1350, UE 120 may send a model delivery complete message, and central network entity 505 may receive the model delivery complete message. UE 120 may send the model delivery complete message based at least in part on receiving the model delivery complete message. In some aspects, sending the model delivery complete message may include sending an RRC message including the model delivery complete message.

[0218] In some aspects, the NG-AP interface can be enhanced to use a Class 1 NG-AP message or a Class 2 NG-AP message to provide UE assistance information for model selection at the MMF 515. The NG-AP interface can be enhanced for delivering the model from the core network to the NG-RAN. The NG-RAN can transmit the model to the UE 120 (e.g., using an RRC message) based at least in part on receiving the model from the core network.

[0219] As indicated above, Figure 13 are provided as examples. Other examples can be found in the Figure 13 The examples described are different.

[0220] Figure 14 A method 1400 for wireless communications by a core network entity, such as the AMF 510 and / or the MMF 515, is shown.

[0221] The method 1400 begins at step 1410 , where an MMF of a core network entity obtains a trigger for sending meta-information associated with a model.

[0222] Then, method 1400 proceeds to step 1420, where the MMF sends an AMF service call message to the AMF of the core network entity.

[0223] The method 1400 then proceeds to step 1430, where the AMF obtains an indication of one or more central network entities within the area.

[0224] Then, the method 1400 proceeds to step 1440 where the AMF sends meta information associated with the model to one or more central network entities.

[0225] In one aspect, obtaining the trigger includes obtaining an update to meta-information associated with the model.

[0226] In one aspect, obtaining the trigger includes receiving a request for meta-information associated with the model from one or more central network entities.

[0227] In one aspect, sending the meta-information associated with the model includes sending at least one of a model identifier associated with the model or a list of model identifiers identifying the model.

[0228] In one aspect, obtaining an indication of one or more central network entities within the area includes obtaining an indication of multiple central network entities within the area; and the method also includes selecting, by the AMF, a central network entity from the multiple central network entities within the area, wherein sending meta-information associated with the model includes sending, by the AMF, meta-information associated with the model to the selected central network entity from the multiple central network entities.

[0229] In one aspect, sending the AMF service call message includes sending, by the MMF to the AMF, a meta information update indication including at least one of a model identifier associated with the model, a list of model identifiers identifying the model, meta information, or an indication of a region.

[0230] In one aspect, the indication of an area is an indication of a service area or an indication of a geographic area.

[0231] In one aspect, the method 1400 further includes: receiving, by at least one of the MMF or the AMF, a meta information update request; and sending, by at least one of the MMF or the AMF, a meta information update response.

[0232] In one aspect, the metainformation update request includes a model identifier associated with the model or a list of model identifiers identifying the model, and the metainformation update response includes metainformation associated with at least one of the model identifier associated with the model or the list of model identifiers identifying the model.

[0233] In one aspect, the meta-information indicates at least one of: a scenario associated with the model, a configuration associated with the model, a setting associated with the model, a zone identifier associated with the model, an SCS associated with the operation of the model, an antenna configuration associated with the operation of the model, carrier information associated with the operation of the model, or bandwidth portion information associated with the operation of the model.

[0234] In one aspect, method 1400 or any aspect related thereto may be performed by an apparatus such as Figure 21 The method 1400 is performed by a communication device 2100 comprising various components operable, configured, or adapted to perform the method 1400. The communication device 2100 is described in more detail below.

[0235] Please note that Figure 14 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in light of the present disclosure.

[0236] Figure 15 A method 1500 for wireless communications by a central network entity, such as central network entity 505, is shown.

[0237] Method 1500 begins at step 1510 by sending a request for meta-information associated with a model to an AMF of a core network entity.

[0238] Then, the method 1500 proceeds to step 1520 to receive meta information associated with the model from the AMF.

[0239] In one aspect, the request for meta-information associated with the model includes at least one of a model identifier associated with the model or a list of model identifiers identifying the model.

[0240] In one aspect, sending the request for metainformation associated with the model includes sending a request for updated metainformation associated with the model, and receiving the metainformation associated with the model includes receiving updated metainformation associated with the model.

[0241] In one aspect, the meta-information indicates at least one of: a scenario associated with the model, a configuration associated with the model, a setting associated with the model, a zone identifier associated with the model, an SCS associated with the operation of the model, an antenna configuration associated with the operation of the model, carrier information associated with the operation of the model, or bandwidth portion information associated with the operation of the model.

[0242] In one aspect, method 1500 or any aspect related thereto may be performed by an apparatus such as Figure 22 The method 1500 is performed by a communication device 2200 comprising various components operable, configured, or adapted to perform the method 1500. The communication device 2200 is described in more detail below.

[0243] Please note that Figure 15 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in light of the present disclosure.

[0244] Figure 16 A method 1600 for wireless communications by a UE, such as UE 120, is shown.

[0245] Method 1600 begins at step 1610 by sending a model query to the AMF of the core network entity.

[0246] Then, the method 1600 proceeds to step 1620 to receive a model query response from the AMF.

[0247] Method 1600 then proceeds to step 1630 where a model is selected based at least in part on the model query response.

[0248] In one aspect, method 1600 further includes sending UE capability information associated with the model to the central network entity.

[0249] In one aspect, the model query includes at least one of UE capability information or UE region information.

[0250] In one aspect, the UE area information is based at least in part on a registration area, wherein the registration area is based at least in part on a tracking area identification or tracking area code.

[0251] In one aspect, the model query response includes at least one of meta information associated with the model or a model identifier associated with the model.

[0252] In one aspect, the model query is included in an uplink NAS transport message, a Class 1 NAS message, a Class 2 NAS message, a Class 1 message, or a Class 2 message.

[0253] In one aspect, the method 1600 further includes sending the MMF information to the AMF.

[0254] In one aspect, the model query response is included in a registration accept message, a downlink NAS transport message, a class 1 NAS message, a class 2 NAS message, a class 1 message, or a class 2 message.

[0255] In one aspect, selecting a model based at least in part on the model query response includes selecting a model based at least in part on meta-information included in the model query response.

[0256] In one aspect, method 1600 further includes sending UE capability information to a central network entity; receiving a model download request including an indication of a model from the central network entity; and sending a model download complete message to the central network entity.

[0257] In one aspect, the model download request includes a model identifier or UE assistance information for supporting model selection at the MMF of the core network entity.

[0258] In one aspect, the UE assistance information includes at least one of: a carrier frequency indication, a subcarrier spacing indication, a bandwidth part indication, an antenna tilt indication, an antenna pattern indication, or a scenario, configuration, or zone identifier.

[0259] In one aspect, method 1600 or any aspect related thereto may be performed by an apparatus such as Figure 23 The method 1600 is performed by a communication device 2300 comprising various components operable, configured, or adapted to perform the method 1600. The communication device 2300 is described in more detail below.

[0260] Please note that Figure 16 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in light of the present disclosure.

[0261] Figure 17 A method 1700 for wireless communications by a core network entity, such as the AMF 510 and / or the MMF 515, is shown.

[0262] Method 1700 begins at step 1710, where the AMF of the core network entity receives a model query from the UE.

[0263] Then, method 1700 proceeds to step 1720, where the AMF sends a model query to the MMF of the core network entity.

[0264] Then, the method 1700 proceeds to step 1730 where the MMF selects a model.

[0265] Then, method 1700 proceeds to step 1740, where the MMF sends a model query response to the AMF.

[0266] Then, the method 1700 proceeds to step 1750, where the AMF sends a model query response.

[0267] In one aspect, the model query includes at least one of UE capability information or UE region information.

[0268] In one aspect, the UE area information is based at least in part on a registration area, wherein the registration area is based at least in part on a tracking area identification or tracking area code.

[0269] In one aspect, the model query response includes at least one of meta information associated with the model or a model identifier associated with the model.

[0270] In one aspect, receiving the model query comprises receiving, by the AMF from the UE, an uplink NAS transport message, a category 1 NAS message, a category 2 NAS message, a category 1 message, or a category 2 message.

[0271] In one aspect, sending the model query response includes sending a Registration Accept message, a Downlink NAS Transport message, a Category 1 NAS message, a Category 2 NAS message, a Category 1 message, or a Category 2 message from the AMF to the UE.

[0272] In one aspect, method 1700 or any aspect related thereto may be performed by an apparatus such as Figure 24 The method 1700 is performed by a communication device 2400 comprising various components operable, configured, or adapted to perform the method 1700. The communication device 2400 is described in more detail below.

[0273] Please note that Figure 17 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in light of the present disclosure.

[0274] Figure 18 A method 1800 for wireless communications by a network entity, such as an OAM / SMO 805, is shown.

[0275] Method 1800 begins at step 1810 by selecting a model by a service management and orchestration (SMO) function of a network entity.

[0276] Then, the method 1800 proceeds to step 1820 where the SMO function of the network entity sends an indication of the model.

[0277] In one aspect, the method 1800 further includes receiving a model delivery request message from the central network entity, wherein sending the indication of the model includes sending, by an SMO function of the network entity, the indication of the model to the central network entity.

[0278] In one aspect, the model delivery request message includes a model identifier or UE assistance information associated with the model.

[0279] In one aspect, receiving the model delivery request message includes receiving a radio access network intelligent controller indication message, a category 1 message, or a category 2 message.

[0280] In one aspect, method 1800 further includes: receiving UE capability information from a central network entity; determining to initiate an AI or ML process; and sending information associated with the AI ​​or ML process.

[0281] In one aspect, method 1800 further includes receiving UE context information or radio access network information from a central network entity.

[0282] In one aspect, method 1800 further includes requesting UE assistance information from the central network entity.

[0283] In one aspect, sending the information associated with the AI ​​or ML process includes sending the information associated with the AI ​​or ML process to a central network entity.

[0284] In one aspect, sending the information associated with the AI ​​or ML process includes sending the information associated with the AI ​​or ML process to the UE.

[0285] In one aspect, the information associated with the AI ​​or ML process is associated with a signaling or management based process for initializing the AI ​​or ML process or for providing a model to the UE.

[0286] In one aspect, method 1800 or any aspect related thereto may be performed by an apparatus such as Figure 25 The method 1800 is performed by a communication device 2500 comprising various components operable, configured, or adapted to perform the method 1800. The communication device 2500 is described in more detail below.

[0287] Please note that Figure 18This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in light of the present disclosure.

[0288] Figure 19 A method 1900 for wireless communications by a central network entity, such as central network entity 505, is shown.

[0289] Method 1900 begins at step 1910 by receiving UE capability information from a UE.

[0290] Method 1900 then proceeds to step 1920 where a model is selected based at least in part on the UE capability information.

[0291] Then, the method 1900 proceeds to step 1930 to send a model delivery request message to the core network entity.

[0292] Then, the method 1900 proceeds to step 1940 to receive a model delivery completion indication from the UE.

[0293] In one aspect, the model delivery request message includes an indication of a model identifier associated with the model.

[0294] In one aspect, sending the model delivery request message includes sending a category 1 message or a category 2 message including the model delivery request message to the core network entity.

[0295] In one aspect, sending the model delivery request message includes sending the model delivery request message to an access and mobility management function.

[0296] In one aspect, method 1900 further includes sending a radio resource control message or a medium access control message to the UE indicating that the model is to be received from the core network entity.

[0297] In one aspect, method 1900 or any aspect related thereto may be performed by an apparatus such as Figure 26 The method 1900 is performed by a communication device 2600 comprising various components operable, configured, or adapted to perform the method 1900. The communication device 2600 is described in more detail below.

[0298] Please note that Figure 19 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in light of the present disclosure.

[0299] Figure 20 A method 2000 for wireless communications by a UE, such as UE 120, is shown.

[0300] Method 2000 begins at step 2010, where the AMF of the core network entity receives a model delivery request message from the central network entity.

[0301] Then, the method 2000 proceeds to step 2020, where the AMF sends a model delivery message including an indication of the model.

[0302] In one aspect, the model delivery request message includes an indication of a model identifier associated with the model.

[0303] In one aspect, the method 2000 further includes: sending, by the AMF, a model delivery request message to the MMF of the core network entity; and receiving, by the AMF, a model delivery message including an indication of the model from the MMF.

[0304] In one aspect, sending the model delivery message includes sending, by the AMF to the UE, a downlink NAS message, a category 1 message, or a category 2 message including the model delivery message.

[0305] In one aspect, the method 2000 also includes receiving, by the AMF, a Model Delivery Confirm message from the UE.

[0306] In one aspect, the method 2000 further includes sending, by the AMF, a model delivery confirmation message to the mobility management function.

[0307] In one aspect, method 2000 or any aspect related thereto may be performed by an apparatus such as Figure 27 The method 2000 is performed by a communication device 2700 comprising various components operable, configured, or adapted to perform the method 2000. The communication device 2700 is described in more detail below.

[0308] Please note that Figure 20 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in light of the present disclosure.

[0309] Figure 21 2 is a diagram illustrating an example of a specific implementation of codes and circuits for a communication device 2100 according to the present disclosure. The communication device 2100 may be a core network entity (such as BS 110 or a related Figure 3 The described decomposed base station), or a core network entity may include the communication device 2100.

[0310] The communication device 2100 includes a processing system 2102 coupled to a transceiver 2108 (e.g., a transmitter and / or receiver). The transceiver 2108 is configured to transmit and receive signals for the communication device 2100, such as the various signals described herein, via an antenna 2110. The network interface 2112 is configured to communicate with the communication device 2100 via a communication link (such as those described herein). Figure 3 The processing system 2102 may be configured to perform processing functions for the communication device 2100, including processing signals received by the communication device 2100 and / or to be transmitted by the communication device 2100.

[0311] The processing system 2102 includes one or more processors 2120. In various aspects, the one or more processors 2120 may represent Figure 2 One or more of the receive processor 238, transmit processor 220, TX MIMO processor 230, and / or controller / processor 240 are described. The one or more processors 2120 are coupled to the computer-readable medium / memory 2130 via the bus 2106. In various aspects, the computer-readable medium / memory 2130 may represent a processor as described with respect to FIG. Figure 2 The computer readable medium / memory 2130 is configured to store instructions (e.g., computer executable code, processor executable code) that, when executed by the one or more processors 2120, cause the one or more processors 2120 to perform operations related to the computer readable medium / memory 2130. Figure 14 The method 1400 or any aspect related thereto is described. Note that reference to a processor performing a function of the communication device 2100 may include one or more processors performing that function of the communication device 2100.

[0312] like Figure 21 As shown, the communication device 2100 may include circuitry (circuitry 2135 ) for obtaining, by the MMF of the core network entity, a trigger for sending meta-information associated with the model.

[0313] like Figure 21 As shown, the communication device 2100 may include code (code 2140) stored in the computer-readable medium / memory 2130 for obtaining, by the MMF of the core network entity, a trigger for transmitting meta-information associated with the model.

[0314] like Figure 21 As shown, the communication device 2100 may include a circuit (circuit 2145) for sending an AMF service call message from the MMF to the AMF of the core network entity.

[0315] like Figure 21 As shown, the communication device 2100 may include code (code 2150) stored in the computer-readable medium / memory 2130 for sending an AMF service call message from the MMF to the AMF of the core network entity.

[0316] like Figure 21As shown, the communication device 2100 may include circuitry (circuitry 2155) for obtaining, by the AMF, an indication of one or more central network entities within a region.

[0317] like Figure 21 As shown, the communication device 2100 may include code (code 2160) stored in the computer-readable medium / memory 2130 for obtaining, by the AMF, an indication of one or more central network entities within a region.

[0318] like Figure 21 As shown, the communication device 2100 may include circuitry (circuitry 2165) for sending, by the AMF, meta-information associated with the model to one or more central network entities.

[0319] like Figure 21 As shown, the communication device 2100 may include code (code 2170) stored in the computer-readable medium / memory 2130 for sending, by the AMF, meta-information associated with the model to one or more central network entities.

[0320] The various components of the communication device 2100 may provide for performing Figure 14 Means for transmitting, conveying, or outputting for transmission may include the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 21 The transceiver 2108 and antenna 2110 of the communication device 2100 in the embodiment of the present invention may be used to receive or obtain the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 21 The transceiver 2108 and antenna 2110 of the communication device 2100 in FIG.

[0321] Figure 21 is provided as an example. Other examples can be combined with Figure 21 The examples described are different.

[0322] Figure 22 is a diagram illustrating an example of a specific implementation of code and circuits for a communication device 2200 according to the present disclosure. The communication device 2200 may be a central network entity (such as BS 110 or a Figure 3 The described decomposed base station), or a central network entity may include the communication device 2200.

[0323] The communication device 2200 includes a processing system 2202 coupled to a transceiver 2208 (e.g., a transmitter and / or receiver). The transceiver 2208 is configured to transmit and receive signals for the communication device 2200, such as the various signals described herein, via an antenna 2210. The network interface 2212 is configured to communicate with the communication device 2200 via a communication link (such as those described herein). Figure 3 The processing system 2202 may be configured to perform processing functions for the communication device 2200, including processing signals received by the communication device 2200 and / or to be transmitted by the communication device 2200.

[0324] The processing system 2202 includes one or more processors 2220. In various aspects, the one or more processors 2220 may represent Figure 2 One or more of the receive processor 238, transmit processor 220, TX MIMO processor 230, and / or controller / processor 240 are described. The one or more processors 2220 are coupled to a computer-readable medium / memory 2230 via a bus 2206. In various aspects, the computer-readable medium / memory 2230 may represent a processor such as a processor 2200. Figure 2 The computer readable medium / memory 2230 is configured to store instructions (e.g., computer executable code, processor executable code) that, when executed by the one or more processors 2220, cause the one or more processors 2220 to perform operations related to the computer readable medium / memory 2230. Figure 15 The described method 1500 or any aspect related thereto. Note that reference to a processor performing a function of the communication device 2200 may include one or more processors performing that function of the communication device 2200.

[0325] like Figure 22 As shown, the communication device 2200 may include circuitry (circuitry 2235) for sending a request for meta-information associated with the model to the AMF of the core network entity.

[0326] like Figure 22 As shown, the communication device 2200 may include code (code 2240) stored in the computer-readable medium / memory 2230 for sending a request for meta-information associated with the model to the AMF of the core network entity.

[0327] like Figure 22 As shown, the communication device 2200 may include circuitry (circuitry 2245) for receiving meta-information associated with the model from the AMF.

[0328] like Figure 22As shown, the communication device 2200 may include code (code 2250) stored in the computer-readable medium / memory 2230 for receiving meta information associated with the model from the AMF.

[0329] The various components of the communication device 2200 may provide for performing Figure 15 Means for transmitting, conveying, or outputting for transmission may include the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 22 The transceiver 2208 and antenna 2210 of the communication device 2200 in the embodiment of the present invention may be used to receive or obtain the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 22 The transceiver 2208 and antenna 2210 of the communication device 2200 in FIG.

[0330] Figure 22 is provided as an example. Other examples can be combined with Figure 22 The examples described are different.

[0331] Figure 23 2 is a diagram illustrating an example of a specific implementation of codes and circuits for a communication device 2300 according to the present disclosure. The communication device 2300 may be a UE, or a UE may include the communication device 2300.

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

[0333] The processing system 2302 includes one or more processors 2320. In various aspects, the one or more processors 2320 may represent Figure 2 One or more of the receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280 are described. The one or more processors 2320 are coupled to the computer-readable medium / memory 2330 via the bus 2306. In various aspects, the computer-readable medium / memory 2330 may represent a processor as described with respect to FIG. Figure 2The computer readable medium / memory 2330 is configured to store instructions (e.g., computer executable code, processor executable code) that, when executed by the one or more processors 2320, cause the one or more processors 2320 to perform operations related to the computer readable medium / memory 2330. Figure 16 The described method 1600 or any aspect related thereto. Note that reference to a processor performing a function of the communication device 2300 may include one or more processors performing that function of the communication device 2300.

[0334] like Figure 23 As shown, the communication device 2300 may include circuitry (circuitry 2335) for sending a model query to the AMF of the core network entity.

[0335] like Figure 23 As shown, the communication device 2300 may include code (code 2340) stored in the computer-readable medium / memory 2330 for sending a model query to the AMF of the core network entity.

[0336] like Figure 23 As shown, the communication device 2300 may include circuitry (circuitry 2345) for receiving a model query response from the AMF.

[0337] like Figure 23 As shown, the communication device 2300 may include code (code 2350) stored in the computer-readable medium / memory 2330 for receiving a model query response from the AMF.

[0338] like Figure 23 As shown, the communication device 2300 may include circuitry for selecting a model based at least in part on the model query response (circuitry 2355).

[0339] like Figure 23 As shown, communication device 2300 may include code (code 2360 ) stored in computer-readable medium / memory 2330 for selecting a model based at least in part on a model query response.

[0340] The various components of the communication device 2300 may provide for performing Figure 16 Means for transmitting, conveying, or outputting for transmission may include the transceiver 254 and / or antenna 252 of the UE 120, and / or any aspect thereof. Figure 23 The transceiver 2308 and antenna 2310 of the communication device 2300 in FIG. The means for receiving or obtaining may include the transceiver 254 and / or antenna 252 of the UE 120, and / or Figure 23The transceiver 2308 and antenna 2310 of the communication device 2300 in FIG.

[0341] Figure 23 is provided as an example. Other examples can be combined with Figure 23 The examples described are different.

[0342] Figure 24 2 is a diagram illustrating an example of a specific implementation of codes and circuits for a communication device 2400 according to the present disclosure. The communication device 2400 may be a core network entity (such as BS 110 or a Figure 3 The described decomposed base station), or a core network entity may include the communication device 2400.

[0343] The communication device 2400 includes a processing system 2402 coupled to a transceiver 2408 (e.g., a transmitter and / or receiver). The transceiver 2408 is configured to transmit and receive signals for the communication device 2400, such as the various signals described herein, via an antenna 2410. The network interface 2412 is configured to communicate with the communication device 2400 via a communication link (such as those described herein). Figure 3 The processing system 2402 may be configured to perform processing functions for the communication device 2400, including processing signals received by the communication device 2400 and / or to be transmitted by the communication device 2400.

[0344] The processing system 2402 includes one or more processors 2420. In various aspects, the one or more processors 2420 may represent Figure 2 One or more of the receive processor 238, transmit processor 220, TX MIMO processor 230, and / or controller / processor 240 are described. The one or more processors 2420 are coupled to a computer-readable medium / memory 2430 via a bus 2406. In various aspects, the computer-readable medium / memory 2430 may represent a processor as described with respect to FIG. Figure 2 The computer readable medium / memory 2430 is configured to store instructions (e.g., computer executable code, processor executable code) that, when executed by the one or more processors 2420, cause the one or more processors 2420 to perform operations related to the computer readable medium / memory 2430. Figure 17 The described method 1700 or any aspect related thereto. Note that reference to a processor performing a function of the communication device 2400 may include one or more processors performing that function of the communication device 2400.

[0345] like Figure 24As shown, the communication device 2400 may include a circuit (circuit 2435) for receiving a model query from the UE by the AMF of the core network entity.

[0346] like Figure 24 As shown, the communication device 2400 may include code (code 2440) stored in the computer-readable medium / memory 2430 for receiving, by the AMF of the core network entity, a model query from the UE.

[0347] like Figure 24 As shown, the communication device 2400 may include circuitry (circuitry 2445) for selecting a model by the MMF.

[0348] like Figure 24 As shown, communication device 2400 may include code (code 2450 ) stored in computer-readable medium / memory 2430 for selecting a model by an MMF.

[0349] like Figure 24 As shown, the communication device 2400 may include a circuit (circuit 2455) for sending a model query response from the MMF to the AMF.

[0350] like Figure 24 As shown, the communication device 2400 may include code (code 2460) stored in the computer-readable medium / memory 2430 for sending a model query response from the MMF to the AMF.

[0351] like Figure 24 As shown, the communication device 2400 may include circuitry (circuitry 2465) for sending a model query response by the AMF.

[0352] like Figure 24 As shown, the communication device 2400 may include code (code 2470) stored in the computer-readable medium / memory 2430 for sending a model query response by the AMF.

[0353] The various components of the communication device 2400 may provide for performing Figure 17 Means for transmitting, conveying, or outputting for transmission may include the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 24 The transceiver 2408 and antenna 2410 of the communication device 2400 in the embodiment of the present invention may be used to receive or obtain the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 24 The transceiver 2408 and antenna 2410 of the communication device 2400 in FIG.

[0354] Figure 24is provided as an example. Other examples can be combined with Figure 24 The examples described are different.

[0355] Figure 25 2 is a diagram illustrating an example of a specific implementation of codes and circuits for a communication device 2500 according to the present disclosure. The communication device 2500 may be a network entity (such as BS 110 or a network entity related to Figure 3 The described decomposed base station), or a network entity may include the communication device 2500.

[0356] The communication device 2500 includes a processing system 2502 coupled to a transceiver 2508 (e.g., a transmitter and / or receiver). The transceiver 2508 is configured to transmit and receive signals for the communication device 2500, such as the various signals described herein, via an antenna 2510. The network interface 2512 is configured to communicate with the communication device 2500 via a communication link (such as those described herein). Figure 3 The processing system 2502 may be configured to perform processing functions for the communication device 2500, including processing signals received by the communication device 2500 and / or to be transmitted by the communication device 2500.

[0357] The processing system 2502 includes one or more processors 2520. In various aspects, the one or more processors 2520 may represent Figure 2 One or more of the receive processor 238, transmit processor 220, TX MIMO processor 230, and / or controller / processor 240 are described. The one or more processors 2520 are coupled to the computer-readable medium / memory 2530 via bus 2506. In various aspects, the computer-readable medium / memory 2530 may represent a processor as described with respect to FIG. Figure 2 The computer readable medium / memory 2530 is configured to store instructions (e.g., computer executable code, processor executable code) that, when executed by the one or more processors 2520, cause the one or more processors 2520 to perform operations related to the computer readable medium / memory 2530. Figure 18 The described method 1800 or any aspect related thereto. Note that reference to a processor performing a function of the communication device 2500 may include one or more processors performing that function of the communication device 2500.

[0358] like Figure 25 As shown, the communication device 2500 may include circuitry (circuitry 2535) for selecting a model by an SMO function of a network entity.

[0359] like Figure 25As shown, the communication device 2500 may include code (code 2540) stored in the computer-readable medium / memory 2530 for selecting a model by a SMO function of a network entity.

[0360] like Figure 25 As shown, the communications device 2500 may include circuitry (circuitry 2545) for sending, by the SMO function of the network entity, an indication of the model.

[0361] like Figure 25 As shown, communications device 2500 may include code (code 2550) stored in computer-readable medium / memory 2530 for sending, by a SMO function of a network entity, an indication of a model.

[0362] like Figure 25 As shown, the communication device 2500 may include circuitry (circuitry 2555) for relaying an indication of the model.

[0363] like Figure 25 As shown, communication device 2500 may include code (code 2560 ) stored in computer-readable medium / memory 2530 for relaying an indication of a model.

[0364] The various components of the communication device 2500 may provide for performing Figure 18 Means for transmitting, conveying, or outputting for transmission may include the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 25 The transceiver 2508 and antenna 2510 of the communication device 2500 in the embodiment of the present invention may be used to receive or obtain the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 25 The transceiver 2508 and antenna 2510 of the communication device 2500 in FIG.

[0365] Figure 25 is provided as an example. Other examples can be combined with Figure 25 The examples described are different.

[0366] Figure 26 is a diagram illustrating an example of a specific implementation of code and circuits for a communication device 2600 according to the present disclosure. The communication device 2600 may be a central network entity (such as BS 110 or a Figure 3 The described decomposed base station), or a central network entity may include the communication device 2600.

[0367] The communication device 2600 includes a processing system 2602 coupled to a transceiver 2608 (e.g., a transmitter and / or receiver). The transceiver 2608 is configured to transmit and receive signals for the communication device 2600, such as the various signals described herein, via an antenna 2610. The network interface 2612 is configured to communicate with the communication device 2600 via a communication link (such as those described herein). Figure 3 The processing system 2602 may be configured to perform processing functions for the communication device 2600, including processing signals received by the communication device 2600 and / or to be transmitted by the communication device 2600.

[0368] The processing system 2602 includes one or more processors 2620. In various aspects, the one or more processors 2620 may represent Figure 2 One or more of the receive processor 238, transmit processor 220, TX MIMO processor 230, and / or controller / processor 240 are described. The one or more processors 2620 are coupled to the computer-readable medium / memory 2630 via the bus 2606. In various aspects, the computer-readable medium / memory 2630 may represent a computer program product as described with respect to FIG. Figure 2 The computer readable medium / memory 2630 is configured to store instructions (e.g., computer executable code, processor executable code) that, when executed by the one or more processors 2620, cause the one or more processors 2620 to perform operations related to the computer readable medium / memory 2630. Figure 19 The described method 1900 or any aspect related thereto. Note that reference to a processor performing a function of the communication device 2600 may include one or more processors performing that function of the communication device 2600.

[0369] like Figure 26 As shown, the communications device 2600 may include circuitry for receiving UE capability information from the UE (circuitry 2635 ).

[0370] like Figure 26 As shown, communications device 2600 may include code (code 2640 ) stored in computer-readable medium / memory 2630 for receiving UE capability information from a UE.

[0371] like Figure 26 As shown, the communications device 2600 may include circuitry for selecting a model based at least in part on UE capability information (circuitry 2645).

[0372] like Figure 26As shown, communications device 2600 may include code (code 2650) stored in computer-readable medium / memory 2630 for selecting a model based at least in part on UE capability information.

[0373] like Figure 26 As shown, the communications device 2600 may include circuitry (circuitry 2655) for sending a model delivery request message to a core network entity.

[0374] like Figure 26 As shown, communications device 2600 may include code (code 2660) stored in computer-readable medium / memory 2630 for sending a model delivery request message to a core network entity.

[0375] like Figure 26 As shown, the communications device 2600 may include circuitry for receiving a model delivery completion indication from the UE (circuitry 2665).

[0376] like Figure 26 As shown, communications device 2600 may include code (code 2670 ) stored in computer-readable medium / memory 2630 for receiving a model delivery complete indication from a UE.

[0377] The various components of the communication device 2600 may provide for performing Figure 19 Means for transmitting, conveying, or outputting for transmission may include the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 26 The transceiver 2608 and antenna 2610 of the communication device 2600 in the embodiment of the present invention may be used to receive or obtain the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 26 The transceiver 2608 and antenna 2610 of the communication device 2600 in FIG.

[0378] Figure 26 is provided as an example. Other examples can be combined with Figure 26 The examples described are different.

[0379] Figure 27 2 is a diagram illustrating an example of a specific implementation of codes and circuits for a communication device 2700 according to the present disclosure. The communication device 2700 may be a core network entity (such as BS 110 or a related Figure 3 The described decomposed base station), or a core network entity may include the communication device 2700.

[0380] The communication device 2700 includes a processing system 2702 coupled to a transceiver 2708 (e.g., a transmitter and / or receiver). The transceiver 2708 is configured to transmit and receive signals for the communication device 2700, such as the various signals described herein, via an antenna 2710. The network interface 2712 is configured to communicate with the communication device 2700 via a communication link (such as those described herein). Figure 3 The processing system 2702 may be configured to perform processing functions for the communication device 2700, including processing signals received by the communication device 2700 and / or to be transmitted by the communication device 2700.

[0381] The processing system 2702 includes one or more processors 2720. In various aspects, the one or more processors 2720 may represent Figure 2 One or more of the receive processor 238, transmit processor 220, TX MIMO processor 230, and / or controller / processor 240 are described. The one or more processors 2720 are coupled to a computer-readable medium / memory 2730 via a bus 2706. In various aspects, the computer-readable medium / memory 2730 may represent a processor such as a processor 2720 that is configured to receive and transmit data from a processor 2720. Figure 2 The computer readable medium / memory 2730 is configured to store instructions (e.g., computer executable code, processor executable code) that, when executed by the one or more processors 2720, cause the one or more processors 2720 to perform operations related to the computer readable medium / memory 2730. Figure 20 The method 2000 described herein or any aspect related thereto. Note that reference to a processor performing a function of the communication device 2700 may include one or more processors performing that function of the communication device 2700.

[0382] like Figure 27 As shown, the communication device 2700 may include a circuit (circuit 2735) for receiving, by the AMF of the core network entity, a model delivery request message from the central network entity.

[0383] like Figure 27 As shown, the communication device 2700 may include code (code 2740) stored in the computer-readable medium / memory 2730 for receiving, by the AMF of the core network entity, a model delivery request message from the central network entity.

[0384] like Figure 27 As shown, the communication device 2700 may include circuitry (circuitry 2745) for sending, by the AMF, a model delivery message including an indication of the model.

[0385] like Figure 27As shown, the communication device 2700 may include code (code 2750) stored in the computer-readable medium / memory 2730 for sending, by the AMF, a model delivery message including an indication of the model.

[0386] The various components of the communication device 2700 may provide for performing Figure 20 Components of the described method 2000 or any aspect thereof. For example, components for sending, transmitting, or outputting for transmission may include the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 27 The transceiver 2708 and antenna 2710 of the communication device 2700 in the embodiment of the present invention may be used to receive or obtain the transceiver 232 and / or antenna 234 of the BS 110, and / or Figure 27 The transceiver 2708 and antenna 2710 of the communication device 2700 in FIG.

[0387] Figure 27 is provided as an example. Other examples can be combined with Figure 27 The examples described are different.

[0388] The following provides an overview of some aspects of the disclosure:

[0389] Aspect 1: A method of wireless communication performed by a core network entity, the method comprising: obtaining, by a model management function (MMF) of the core network entity, a trigger for sending meta-information associated with a model; sending, by the MMF, an AMF service call message to an access and mobility management function (AMF) of the core network entity; obtaining, by the AMF, an indication of one or more central network entities within an area; and sending, by the AMF, meta-information associated with the model to the one or more central network entities.

[0390] Aspect 2: The method according to aspect 1, wherein obtaining the trigger comprises obtaining an update to the meta-information associated with the model.

[0391] Aspect 3: The method according to any one of aspects 1 to 2, wherein obtaining the trigger comprises receiving a request for the meta-information associated with the model from the one or more central network entities.

[0392] Aspect 4: The method according to any one of aspects 1 to 3, wherein sending the meta information associated with the model comprises sending at least one of a model identifier associated with the model or a list of model identifiers identifying the model.

[0393] Aspect 5: A method according to any one of Aspects 1 to 4, wherein: obtaining the indication of the one or more central network entities within the area includes obtaining an indication of multiple central network entities within the area; and the method also includes selecting, by the AMF, a central network entity from the multiple central network entities within the area, wherein sending the meta-information associated with the model includes sending, by the AMF, the meta-information associated with the model to the selected central network entity from the multiple central network entities.

[0394] Aspect 6: A method according to any one of Aspects 1 to 5, wherein sending the AMF service call message includes sending a meta information update indication by the MMF to the AMF, the meta information update indication including at least one of a model identifier associated with the model, a model identifier list identifying the model, the meta information, or an indication of the area.

[0395] Aspect 7: The method according to aspect 6, wherein the indication of the area is an indication of a service area or an indication of a geographical area.

[0396] Aspect 8: According to the method according to any one of Aspects 1 to 7, the method further includes: receiving a meta information update request by at least one of the MMF or the AMF; and sending a meta information update response by at least one of the MMF or the AMF.

[0397] Aspect 9: The method according to Aspect 8, wherein the metainformation update request includes a model identifier associated with the model or a list of model identifiers identifying the model, and the metainformation update response includes metainformation associated with at least one of the model identifier associated with the model or the list of model identifiers identifying the model.

[0398] Aspect 10: A method according to any one of Aspects 1 to 9, wherein the meta-information indicates at least one of the following: a scenario associated with the model, a configuration associated with the model, a setting associated with the model, a zone identifier associated with the model, a subcarrier spacing (SCS) associated with the operation of the model, an antenna configuration associated with the operation of the model, carrier information associated with the operation of the model, or bandwidth portion information associated with the operation of the model.

[0399] Aspect 11: A method of wireless communication performed by a central network entity, the method comprising: sending a request for meta-information associated with a model to an access and mobility management function (AMF) of a core network entity; and receiving the meta-information associated with the model from the AMF.

[0400] Aspect 12: The method of aspect 11, wherein the request for the meta-information associated with the model includes at least one of a model identifier associated with the model or a list of model identifiers identifying the model.

[0401] Aspect 13: A method according to any one of Aspects 11 to 12, wherein sending the request for the meta-information associated with the model includes sending a request for updated meta-information associated with the model, and receiving the meta-information associated with the model includes receiving updated meta-information associated with the model.

[0402] Aspect 14: A method according to any one of Aspects 11 to 13, wherein the meta-information indicates at least one of the following: a scenario associated with the model, a configuration associated with the model, a setting associated with the model, a zone identifier associated with the model, a subcarrier spacing (SCS) associated with the operation of the model, an antenna configuration associated with the operation of the model, carrier information associated with the operation of the model, or bandwidth portion information associated with the operation of the model.

[0403] Aspect 15: A method of wireless communication performed by a user equipment (UE), the method comprising: sending a model query to an access and mobility management function (AMF) of a core network entity; receiving a model query response from the AMF; and selecting a model based at least in part on the model query response.

[0404] Aspect 16: The method according to aspect 15, further comprising sending UE capability information associated with the model to a central network entity.

[0405] Aspect 17: The method according to any one of aspects 15 to 16, wherein the model query includes at least one of UE capability information or UE area information.

[0406] Aspect 18: The method of aspect 17, wherein the UE area information is based at least in part on a registration area, wherein the registration area is based at least in part on a tracking area identity or a tracking area code.

[0407] Aspect 19: The method according to any one of aspects 15 to 18, wherein the model query response includes at least one of meta information associated with the model or a model identifier associated with the model.

[0408] Aspect 20: The method according to any one of aspects 15 to 19, wherein the model query is included in an uplink non-access stratum (NAS) transport message, a category 1 NAS message, a category 2 NAS message, a category 1 message or a category 2 message.

[0409] Aspect 21: According to the method according to any one of aspects 15 to 20, the method further includes sending model management function (MMF) information to the AMF.

[0410] Aspect 22: A method according to any one of aspects 15 to 21, wherein the model query response is included in a registration accept message, a downlink non-access stratum (NAS) transport message, a category 1 NAS message, a category 2 NAS message, a category 1 message or a category 2 message.

[0411] Aspect 23: The method of any one of Aspects 15 to 22, wherein selecting the model based at least in part on the model query response comprises selecting the model based at least in part on meta-information included in the model query response.

[0412] Aspect 24: The method according to any one of aspects 15 to 23 further comprises: sending UE capability information to a central network entity; receiving a model download request including an indication of a model from the central network entity; and sending a model download completion message to the central network entity.

[0413] Aspect 25: The method according to aspect 24, wherein the model download request includes a model identifier or UE assistance information for supporting model selection at a model management function (MMF) of the core network entity.

[0414] Aspect 26: The method according to aspect 25, wherein the UE assistance information includes at least one of the following: a carrier frequency indication, a subcarrier spacing indication, a bandwidth part indication, an antenna tilt indication, an antenna pattern indication, or a scene, configuration or zone identifier.

[0415] Aspect 27: A method of wireless communication performed by a core network entity, the method comprising: receiving a model query from a user equipment (UE) by an access and mobility management function (AMF) of the core network entity, sending the model query to a model management function (MMF) of the core network entity by the AMF; selecting a model by the MMF; sending a model query response by the MMF to the AMF; and sending the model query response by the AMF.

[0416] Aspect 28: The method according to aspect 27, wherein the model query includes at least one of UE capability information or UE area information.

[0417] Aspect 29: The method of aspect 28, wherein the UE area information is based at least in part on a registration area, wherein the registration area is based at least in part on a tracking area identity or a tracking area code.

[0418] Aspect 30: The method according to any one of aspects 27 to 29, wherein the model query response includes at least one of meta information associated with the model or a model identifier associated with the model.

[0419] Aspect 31: A method according to any one of aspects 27 to 30, wherein receiving the model query includes receiving, by the AMF from the UE, an uplink non-access stratum (NAS) transport message, a category 1 NAS message, a category 2 NAS message, a category 1 message, or a category 2 message.

[0420] Aspect 32: A method according to any one of aspects 27 to 31, wherein sending the model query response includes sending a registration accept message, a downlink non-access stratum (NAS) transport message, a category 1 NAS message, a category 2 NAS message, a category 1 message or a category 2 message from the AMF to the UE.

[0421] Aspect 33: A method of wireless communication performed by a network entity, the method comprising: selecting a model by a service management and orchestration (SMO) function of the network entity; and sending an indication of the model by the SMO function of the network entity.

[0422] Aspect 34: The method according to Aspect 33 further comprises receiving a model delivery request message from a central network entity, wherein sending the indication of the model comprises sending the indication of the model by the SMO function of the network entity to the central network entity.

[0423] Aspect 35: The method according to aspect 34, wherein the model delivery request message includes a model identifier or user equipment (UE) assistance information associated with the model.

[0424] Aspect 36: The method according to aspect 34, wherein receiving the model delivery request message comprises receiving a radio access network intelligent controller indication message, a category 1 message, or a category 2 message.

[0425] Aspect 37: The method according to Aspect 34 further includes: receiving user equipment (UE) capability information from a central network entity; determining to initiate an artificial intelligence (AI) or machine learning (ML) process; and sending information associated with the AI ​​or ML process.

[0426] Aspect 38: The method according to aspect 37, further comprising receiving UE context information or radio access network information from the central network entity.

[0427] Aspect 39: The method according to aspect 37, further comprising requesting UE assistance information from the central network entity.

[0428] Aspect 40: The method of aspect 37, wherein sending the information associated with the AI ​​or ML process comprises sending the information associated with the AI ​​or ML process to the central network entity.

[0429] Aspect 41: The method of aspect 37, wherein sending the information associated with the AI ​​or ML process comprises sending the information associated with the AI ​​or ML process to a UE.

[0430] Aspect 42: The method according to aspect 37, wherein the information associated with the AI ​​or ML process is associated with a signaling or management-based procedure for initializing the AI ​​or ML process or for providing the model to the UE.

[0431] Aspect 43: A method of wireless communication performed by a central network entity, the method comprising: receiving UE capability information from a user equipment (UE); selecting a model based at least in part on the UE capability information; sending a model delivery request message to a core network entity; and receiving a model delivery completion indication from the UE.

[0432] Aspect 44: The method of aspect 43, wherein the model delivery request message includes an indication of a model identifier associated with the model.

[0433] Aspect 45: The method according to any one of aspects 43 to 44, wherein sending the model delivery request message comprises sending a category 1 message or a category 2 message including the model delivery request message to the core network entity.

[0434] Aspect 46: The method according to any one of aspects 43 to 45, wherein sending the model delivery request message comprises sending the model delivery request message to an access and mobility management function.

[0435] Aspect 47: The method according to any one of aspects 43 to 46, further comprising sending a radio resource control message or a medium access control message to the UE indicating that the model is to be received from the core network entity.

[0436] Aspect 48: A method of wireless communication performed by a core network entity, the method comprising: receiving, by an access and mobility management function (AMF) of the core network entity, a model delivery request message from a central network entity; and sending, by the AMF, a model delivery message including an indication of a model.

[0437] Aspect 49: The method of aspect 48, wherein the model delivery request message includes an indication of a model identifier associated with the model.

[0438] Aspect 50: According to the method described in any one of Aspects 48 to 49, the method further includes: the AMF sending the model delivery request message to the model management function (MMF) of the core network entity; and the AMF receiving the model delivery message including the indication of the model from the MMF.

[0439] Aspect 51: A method according to any one of aspects 48 to 50, wherein sending the model delivery message includes sending, by the AMF, a downlink non-access stratum (NAS) message, a category 1 message, or a category 2 message including the model delivery message to a user equipment (UE).

[0440] Aspect 52: The method according to aspect 51 further includes receiving, by the AMF, a model delivery confirmation message from the UE.

[0441] Aspect 53: The method according to Aspect 52 further includes sending, by the AMF, the model delivery confirmation message to the mobility management function.

[0442] Aspect 54: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 53.

[0443] Aspect 55: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 53.

[0444] Aspect 56: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 53.

[0445] Aspect 57: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 53.

[0446] Aspect 58: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 53.

[0447] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0448] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of different forms of hardware and / or hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0449] As used herein, "satisfying a threshold" may mean a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0450] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways that are not specifically described in the claims and / or disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (including a single member). As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other arrangement of a, b, and c).

[0451] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only want to refer to a project, then use the phrase "only one" or similar terms. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

[0452] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the functions and arrangements of the elements discussed may be changed without departing from the scope of this disclosure. Various examples may omit, replace or add various processes or components as appropriate. For example, the methods described may be performed in an order different from the order described, and various actions may be added, omitted or combined. In addition, the features described with respect to some examples may be combined in some other examples. For example, a device or method of practice may be implemented using any number of aspects set forth herein. In addition, the scope of this disclosure is intended to cover such devices or methods practiced using other structures, functionalities, or structures and functionalities that supplement or replace the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claims.

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

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

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

[0456] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless specifically stated otherwise, reference to an element in the singular is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. No claim element is to be interpreted under the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "parts for...". All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or will later be 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 explicitly stated in the claims.

Claims

1. An apparatus configured for wireless communication, the apparatus comprising: one or more memories comprising processor-executable instructions; and one or more processors configured to execute the processor-executable instructions and cause the apparatus to: Obtaining, by a mobility management function (MMF) of a core network entity, a trigger for sending meta-information associated with the model; The MMF sends an AMF service invocation message to the access and mobility management function (AMF) of the core network entity; Obtaining, by the AMF, an indication of one or more central network entities within the area; as well as Meta information associated with the model is sent by the AMF to the one or more central network entities. 2 . The apparatus of claim 1 , wherein, in order for the MMF to obtain the trigger, the one or more processors are configured to cause the MMF to obtain an update to the meta-information associated with the model. 3 . The apparatus of claim 1 , wherein, in order for the MMF to obtain the trigger, the one or more processors are configured to cause the MMF to receive a request for the meta-information associated with the model from the one or more central network entities.

4. The apparatus of claim 1 , wherein, in order for the AMF to send the meta-information associated with the model, the one or more processors are configured to cause the AMF to send at least one of a model identifier associated with the model or a model identifier list identifying the model.

5. The apparatus of claim 1 , wherein in order for the AMF to obtain the indication of the one or more central network entities within the area, the one or more processors are configured to cause the AMF to obtain an indication of a plurality of central network entities within the area, wherein the one or more processors are configured to cause the AMF to select a central network entity among the plurality of central network entities within the area, and wherein in order for the AMF to send the meta-information associated with the model, the one or more processors are configured to cause the AMF to send the meta-information associated with the model to the selected central network entity among the plurality of central network entities.

6. The apparatus according to claim 1, wherein, in order to cause the MMF to send the AMF service call message, the one or more processors are configured to cause the MMF to send a meta information update indication to the AMF, the meta information update indication including at least one of a model identifier associated with the model, a model identifier list identifying the model, the meta information, or an indication of the area.

7. The apparatus according to claim 1, wherein the one or more processors are configured to cause at least one of the MMF or the AMF to receive a meta information update request and send a meta information update response, wherein the meta information update request includes a model identifier associated with the model or a list of model identifiers identifying the model, and the meta information update response includes meta information associated with at least one of the model identifier associated with the model or the list of model identifiers identifying the model.

8. The apparatus of claim 1 , wherein the meta-information indicates at least one of: a scenario associated with the model, a configuration associated with the model, a setting associated with the model, a zone identifier associated with the model, a subcarrier spacing (SCS) associated with operation of the model, an antenna configuration associated with operation of the model, carrier information associated with operation of the model, or bandwidth portion information associated with operation of the model.

9. An apparatus configured for wireless communication, the apparatus comprising: one or more memories comprising processor-executable instructions; and one or more processors configured to execute the processor-executable instructions and cause the apparatus to: Sending a model query to the Access and Mobility Management Function (AMF) of the core network entity; receiving a model query response from the AMF; and A model is selected based at least in part on the model query response.

10. The apparatus of claim 9, wherein the one or more processors are configured to cause the apparatus to send UE capability information associated with the model to a central network entity.

11. The apparatus of claim 9, wherein the model query comprises at least one of user equipment (UE) capability information or UE area information. 12 . The apparatus of claim 9 , wherein the model query response comprises at least one of meta information associated with the model or a model identifier associated with the model.

13. The apparatus of claim 9, wherein the model query is included in an uplink non-access stratum (NAS) transport message, a class 1 NAS message, a class 2 NAS message, a class 1 message, or a class 2 message.

14. The apparatus of claim 9, wherein the one or more processors are configured to cause the apparatus to send model management function (MMF) information to the AMF.

15. The apparatus of claim 9, wherein the model query response is included in a registration accept message, a downlink non-access stratum (NAS) transport message, a class 1 NAS message, a class 2 NAS message, a class 1 message, or a class 2 message.

16. The apparatus of claim 9, wherein in order for the apparatus to select the model based at least in part on the model query response, the one or more processors are configured to cause the apparatus to select the model based at least in part on meta-information included in the model query response.

17. The apparatus of claim 9, wherein the one or more processors are configured to cause the apparatus to: Sending user equipment (UE) capability information to a central network entity; receiving a model download request including an indication of a model from the central network entity; and Sending a model download completion message to the central network entity.

18. The apparatus of claim 17, wherein the model download request comprises a model identifier or UE assistance information for supporting model selection at a model management function (MMF) of the core network entity, wherein the UE assistance information comprises at least one of: a carrier frequency indication, a subcarrier spacing indication, a bandwidth part indication, an antenna tilt indication, an antenna pattern indication, or a scenario, configuration, or zone identifier.

19. An apparatus configured for wireless communication, the apparatus comprising: one or more memories comprising processor-executable instructions; and one or more processors configured to execute the processor-executable instructions and cause the apparatus to: The access and mobility management function (AMF) of the core network entity receives a model query from the user equipment (UE), The AMF sends the model query to the mobility management function (MMF) of the core network entity; Selecting a model from the MMF; The MMF sends a model query response to the AMF; as well as The AMF sends the model query response to the UE.

20. The apparatus of claim 19, wherein the model query comprises at least one of UE capability information or UE area information.

21. The apparatus of claim 19, wherein the model query response comprises at least one of meta-information associated with the model or a model identifier associated with the model.

22. The apparatus of claim 19, wherein in order for the AMF to receive the model query, the one or more processors are configured to cause the AMF to receive an uplink non-access stratum (NAS) transport message, a category 1 NAS message, a category 2 NAS message, a category 1 message, or a category 2 message from the UE, and wherein in order for the AMF to send the model query response, the one or more processors are configured to cause the AMF to send a registration accept message, a downlink NAS transport message, the category 1 NAS message, the category 2 NAS message, the category 1 message, or the category 2 message to the UE.

23. An apparatus configured for wireless communication, the apparatus comprising: one or more memories comprising processor-executable instructions; and one or more processors configured to execute the processor-executable instructions and cause the apparatus to: Service Management and Orchestration (SMO) functionality selection model by network entities; and An indication of the model is sent by the SMO function of the network entity.

24. An apparatus according to claim 23, wherein the one or more processors are configured to cause the SMO function of the network entity to receive a model delivery request message from a central network entity, wherein in order for the SMO function of the network entity to send the indication of the model, the one or more processors are configured to cause the SMO function of the network entity to send the indication of the model to the central network entity.

25. The apparatus of claim 24, wherein the model delivery request message includes a model identifier or user equipment (UE) assistance information associated with the model.

26. The apparatus of claim 24, wherein in order to cause the SMO function of the network entity to receive the model delivery request message, the one or more processors are configured to cause the SMO function of the network entity to receive a radio access network intelligent controller indication message, a category 1 message, or a category 2 message.

27. The apparatus of claim 24, wherein the one or more processors are configured to cause the SMO function of the network entity to: receiving, by the SMO function of the network entity, user equipment (UE) capability information from a central network entity; determining, by the SMO function of the network entity, to initiate an artificial intelligence (AI) or machine learning (ML) process; and Information associated with the AI ​​or ML process is sent by the SMO function of the network entity.

28. The apparatus of claim 27, wherein the one or more processors are configured to cause the SMO function of the network entity to receive UE context information or radio access network information from the central network entity.

29. The apparatus of claim 27, wherein the one or more processors are configured to cause the SMO function of the network entity to request UE assistance information from the central network entity.

30. The apparatus of claim 27, wherein, in order to cause the SMO function of the network entity to send the information associated with the AI ​​or ML process, the one or more processors are configured to cause the SMO function of the network entity to send the information associated with the AI ​​or ML process to at least one of the central network entity or the UE.

Images