Managing artificial intelligence techniques in a distributed radio access network

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for managing AI techniques in a distributed network. For example, a DU (174) of a base station (106) receives (308, 314, 315, 324), from a CU (172) of the base station (106), a first message indicating that a UE (102) supports AI functionality. The DU (174) transmits (316), to the CU (172), a second message including a first configuration of the AI functionality for the UE (102). The DU (174) communicates (390, 391), with at least one of the CU (172) or the UE (102), based on the first configuration and the AI functionality.

Description

DockctNo.: G114380 10160WOMANAGING ARTIFICIAL INTELLIGENCE TECHNIQUES IN A DISTRIBUTED NETWORKCROSS REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 754,326. entitled “Managing Artificial Intelligence Techniques in a Distributed Network’7and filed on February 5, 2025, which is expressly incorporated by reference herein in its entirety.FIELD OF THE DISCLOSURE

[0002] This disclosure relates to wireless communications and, more particularly, to enabling and managing artificial intelligence (Al) techniques in a distributed network.BACKGROUND

[0003] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0004] The Third Generation Partnership Project (3GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR) (5G NR). An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), a user equipment (5G UE), etc. The 5G NR architecture seeks to provide increased data rates, decreased latency, and / or increased capacity compared to prior generation cellular communication systems.

[0005] Wireless communication systems, in general, provide various telecommunication services (e.g., telephony, video, data, messaging, etc.) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. 3GPP has studied to apply artificial intelligence / machine learning (AI / ML) techniques. The study results have been captured in 3GPP technical report (TR) 38.843 vl8.0.0. However, there are still some aspects that are missing in the study. Especially, it is not clear how to enable AI / ML for the 3GPP communication functions or features in a distributed network including a centralized unit (CU) and a distributed unit (DU).DockctNo.: G114380 10160WOSUMMARY

[0006] A network entity, such as a base station or a unit of a base station, may communicate with a user equipment (UE) and / or other network entities in an example distributed network. The application of artificial intelligence / machine learning (AI / ML) techniques to air-interfaces can be implemented for various use cases, such as channel state information (CSI) feedback enhancement, beam management, and / or positioning accuracy enhancements. CSI feedback enhancement includes spatial-frequency domain CSI compression using a two-sided Al model as well as time domain CSI prediction using a UE sided model. Beam management includes spatial-domain downlink beam prediction for a first set of beams based on measurement results of a second set of beams. Beam management may also include a temporal downlink beam prediction for the first set of beams based on historic measurement results of the second set of beams. Positioning accuracy enhancements include direct AI / ML positioning or AI / ML assisted positioning. However, certain aspects pertaining to enabling AI / ML for communication functions or features in a distributed network including a centralized unit (CU) and a distributed unit (DU) are undefined.

[0007] Thus, aspects of the present disclosure address the above-noted and other deficiencies by implementing a method for managing Al techniques in a distributed network. For example, the present disclosure describes a DU configuring an Al functionality for a UE. The present disclosure also describes a CU configuring an Al functionality for the UE. In further examples, the present disclosure describes a DU configuring an Al functionality applicability report for the UE. The present disclosure also describes a CU configuring an Al functionality applicability report for the UE.

[0008] According to some aspects, the DU of a base station receives, from the CU of the base station, a first message indicating that the UE supports AI / ML functionality. The DU transmits, to the CU, a second message including a first configuration of the Al functionality for the UE and communicates, with at least one of the CU or the UE, based on the first configuration and the Al functionality.

[0009] According to some aspects, the CU of a base station transmits, to the DU of the base station, a first message indicating that a UE supports AI / ML functionality. The CU receives, from the DU, a second message including a first configuration of the Al functionality for the UE and communicating, with at least one of the DU or the UE, in association with the first configuration and the Al functionality.BRIEF DESCRIPTION OF THE DRAWINGSDockctNo.: G114380 10160WO

[0010] FIG. 1A is a block diagram of an example system in which a radio access network (RAN) and a UE can implement the techniques of this disclosure for managing AI / ML techniques according to an embodiment.

[0011] FIG. IB is a block diagram of an example base station including a CU and a DU that can operate in the system of FIG. 1A according to an embodiment.

[0012] FIG. 2A is a block diagram of an example protocol stack according to which the UE of FIG. 1 A communicates with one or more base stations according to an embodiment.

[0013] FIG. 2B is a block diagram of an example protocol stack according to which the UE of Fig. 1A communicates with a CU and a DU according to an embodiment.

[0014] FIGs. 3A-3E are signaling diagrams illustrating communications between the UE, the CU, and the DU for configuring AI / ML functionality techniques according to an embodiment.

[0015] FIGs. 4A-4B are signaling diagrams illustrating communications between a UE, a CU, and a DU for deactivating an AI / ML functionality according to an embodiment.

[0016] FIGs. 5A-5B are signaling diagrams illustrating communications between a UE, a CU, and a DU for releasing an AI / ML functionality configuration according to an embodiment.

[0017] FIGs. 6A-6B are flowcharts of a method of wireless communication at a DU according to an embodiment.

[0018] FIG. 7 is a flowchart of a method of wireless communication at a DU according to an embodiment.

[0019] FIGs. 8A-8B are flowcharts of methods of wireless communication at a DU according to an embodiment.

[0020] FIG. 8 is a flowchart of a method of wireless communication at a network entity according to an embodiment.

[0021] FIG. 9 is a flowchart of a method of wireless communication at a CU according to an embodiment.

[0022] FIG. 10 is a flowchart of a method of wireless communication at a CU according to an embodiment.

[0023] FIGs. I IA-IIB are flowcharts of methods of wireless communication at a CU according to an embodiment.

[0024] FIGs. 12A-12D are flowcharts of methods of wireless communication at a CU according to an embodiment.

[0025] FIGs. 13A-13B are flowcharts of methods of wireless communication at aRAN node according to an embodiment.DockctNo.: G114380 10160WO

[0026] FIGs. 14A-14B are flowcharts of a method of wireless communication at a RAN node according to an embodiment.

[0027] FIGs. 15A-15D are flowcharts of methods of wireless communication at a UE according to an embodiment.

[0028] FIG. 16 is a flowchart of a method of wireless communication at a UE according to an embodiment.

[0029] FIG. 17 is a diagram illustrating a hardware implementation for an example UE apparatus according to an embodiment.

[0030] FIG. 18 is a diagram illustrating a hardware implementation for one or more example network entities according to an embodiment.DETAILED DESCRIPTION OF THE DRAWINGS

[0031] Fig. 1A depicts an example wireless communication system 100 in which communication devices can implement these techniques. The wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106 and a core network (CN) 110. The UE 102 initially connects to the BS 104. The BSs 104 and 106 can operate in a RAN 105 connected to the CN 110. The CN 110 may be or include an evolved packet core (EPC) 111, a fifth generation (5G) core (5GC) 160 and / or a sixth generation (6G) core (6GC) 170, for example. The base station 104 can be an eNB supporting an SI interface for communicating with the EPC 111. an ng-eNB supporting an NG interface for communicating with the 5GC 1 0, or a gNB that supports an NR radio interface as well as an NG interface for communicating with the 5GC 160. The base station 104 can also be an 6G base station (BS) supporting the NG interface, a new NG interface, or a 6G BS-to-CN (e.g., N6G) interface for communicating with the 5GC 160 or the 6GC 170. To directly exchange messages with each other during the scenarios discussed below, the base stations 104 and 106 can support an X2, Xn, new Xn, or 6G BS-to-BS (e.g., X6G) interface. Among other components, the EPC 111 can include a Serving Gateway (SGW) 112, a Mobility Management Entity7(MME) 114, and aPacket DataNetwork Gateway (PGW) 116. The SGW 112 is generally configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity7from the UE to one or more external packet data networks, e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network. The 5GC 160 includes a User Plane Function (UPF) 162 and an Access and Mobility Management (AMF) 164, and / or a Session Management Function (SMF) 166. The UPF 162DockctNo.: G114380 10160WOis generally configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF 164 is configured to manage authentication, registration, paging, and other related functions, and the SMF 166 is configured to manage PDU sessions. The 6GC 170 includes a 6G UPF 172 and a 6G AMF 174, and / or 6G SMF 176, similar to the UPF 162, the AMF 164 and the SMF 176 with enhanced functions respectively.

[0032] As illustrated in Fig. 1 A, the base station 104 supports cell 124, and the base station 106 supports cells 126A, 126B, and 126C. The cells 124, 126A, 126B. and / or 126C can operate on the same carrier frequency or different carrier frequencies. For example, the cells 126A, 126B and 126C operates on DL carrier frequencies fl, f2 and fl respectively. The cell 124 may operate on the DL carrier frequency fl. In cases where the cells 124, 126A, 126B, and / or 126C operate in a time division duplex (TDD) mode, the cells 124. 126A, 126B. and / or 126C operate in UL carrier frequencies same as the DL carrier frequencies. In cases where the cells 124, 126A, 126B, and / or 126C operate in a frequency division duplex (FDD) mode, the cells 124, 126 A, 126B, and / or 126C operate in UL carrier frequencies different from the DL carrier frequencies. The cells 124, 126A, 126B. and / or 126C can partially overlap to provide seamless service continuity. Thus, while the UE 102 may move among the cells 124, 126 A, 126B and 126C, the UE 102 still communicate with the CN 110 via these cells. In some other scenarios, the cells 126B and / or 126C may belong to one or more other base stations (e.g., the base station 104 and / or one or more additional base stations not shown in Fig. 1). In general, the wireless communication network 100 can include any suitable number of base stations supporting 6G cells, NR cells and / or EUTRA cells. More particularly, the EPC 111 can be connected to any suitable number of base stations supporting EUTRA cells, while the 5GC 160 and / or the 6GC 170 can be connected to any suitable number of base stations supporting 6G cells and / or NR cells. Although the examples below refer specifically to specific CN types (EPC, 5GC, 6GC) and RAT types (6G, 5GNR and EUTRA), in general the techniques of this disclosure also can apply to other suitable radio access and / or core network technologies such as seventh generation (7G) radio access and / or 7G core network.

[0033] With continued reference to Fig. 1A. the base station 104 is equipped with processing hardware 130 that includes one or more general-purpose processors (e.g., CPUs) and a non-transitory computer-readable memory (CRM) storing instructions that the one or more general-purpose processors execute. Additionally or alternatively, the processing hardware 130 may include special-purpose processing units. According to an embodiment illustrated in Fig. 1A, the processing hardware 130 includes a processor 132 to process data that the base station 104 transmits in the downlink direction, or data that the base station 104 receives in the uplinkDockctNo.: G114380 10160WOdirection. The processing hardware 130 also includes a receiver 134 configured to transmit data in the downlink direction and to receive data in the uplink direction. The processing hardware 130 also includes a protocol controller 136 configured to manage configurations for operating protocols (e.g., described for Figs. 2A and 2B). The processing hardware 130 further includes an AI / ML controller 138 configured to manage (e.g., configure, release, activate, deactivate, enable, or disable) AI / ML for communication with UEs. The CRM (not shown) stores executable codes for the processor 132 to perform methods according to embodiments described in this section. The base station 106 includes generally similar components. In particular, components 140, 142, 144, 146, and 148 of the base station 106 may be similar to the components 130, 132, 134. 136, and 138 respectively.

[0034] The UE 102 is equipped with processing hardware 150 that can include one or more general-purpose processors such as CPUs and non-transitory CRM storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. As schematically illustrated in Fig. 1A, the processing hardware 150 includes a processor 152 to prepare data that the UE 102 transmits in the uplink direction, or to process data that the UE 102 receives in the downlink direction. The processing hardware 150 also includes a transceiver 154 configured to transmit data in the uplink direction and to receive data in the downlink direction. The processing hardware 150 further includes a protocol controller 156 configured to manage configurations for operating protocols (e.g., described in Figs. 2A and 2B). The process hardware 150 additionally includes an AI / ML controller 158 configured to manage (e g., configure, release, activate, deactivate, enable, or disable) AI / ML for communication with a base station.

[0035] Fig. IB depicts an example, distributed or disaggregated implementation of any one or more of the BSs 104, 106. In this implementation, the BS 104, 106 includes a central unit (CU) 172 and one or more distributed units (DU)(s) 174. Each of the DU(s) can operate one or more cells. For example, the BS 104 includes a DU operating the cell 124.

[0036] In some implementations, the CU 172 can include a logical node centralized unitcontrol plane (CU-CP) 172A that hosts the control plane part of the PDCP protocol of the CU 172. The CU 172 can also include logical node(s) centralized unit-user plane (CU-UP) 172B that hosts the user plane part of the PDCP protocol and / or SDAP protocol of the CU 172. The CU-CP 172A can transmit control information (e.g., RRC messages, Fl application protocol messages), and the CU-UP 172B can transmit the data packets (e.g., SDAP PDUs or Internet Protocol packets).DockctNo.: G114380 10160WO

[0037] The CU-CP 172A can be connected to multiple CU-UP 172B through the El interface. The CU-CP 172A selects the appropriate CU-UP 172B for the requested services for the UE 102. In some implementations, a single CU-UP 172B can be connected to multiple CU-CP 172A through the El interface. The CU-CP 172A can be connected to one or more DUs 174 through an Fl-C or Wl-C interface. The CU-UP 172B can be connected to one or more DU 174 through a functional split-user plane (F 1 -U) or W 1 -U interface under the control of the same CU-CP 172A. In some implementations, one DU 174 can be connected to multiple CU-UP 172B under the control of the same CU-CP 172A. In such implementations, the connectivity between a CU-UP 172B and a DU 174 is established by the CU-CP 172A using Bearer Context Management functions.

[0038] Fig. 2A illustrates, in a simplified manner, an example protocol stack 200 according to which the UE 102 can communicate with a 6gNB 230 (i.e., a 6G RAN node) and / or a gNB 232 (e.g., one or more of the base stations 104, 106).

[0039] In the example stack 200, a NR PHY 202B provides transport channels to a NR MAC sublayer 204B. which in turn provides logical channels to a NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data transfer services to a NR PDCP sublayer 208B. The NR PDCP sublayer 208B in turn can provide data transfer sendees to a Service Data Adaptation Protocol (SDAP) 210B sublayer and / or a radio resource control (RRC) sublayer (not shown in Fig. 2A). Similarly, a physical layer (PHY) 202A of 6G provides transport channels to the 6G MAC sublayer 204A, which in turn provides logical channels to the 6G RLC sublayer 206A. The 6G RLC sublayer 20 A in turn provides RLC channels to a 6G PDCP sublayer 208 A. The 6G PDCP sublayer 208A in turn can provide data transfer sendees to a 6G Senice Data Adaptation Protocol (SDAP) sublayer 210A or a 6G radio resource control (RRC) sublayer (not shown in Fig. 2A). In some implementations, the 6G SDAP sublayer 210A can be omitted. In such cases, the PDCP sublayer 208A may support functionalities of the SDAP sublayer 210A. The UE 102, in some implementations, supports both the 6G and the NR stack as shown in Fig. 2A, to support handover between 6G and NR base stations and / or to support DC over 6G and NR interfaces.

[0040] The 6G PDCP sublayer 208A and the NR PDCP sublayer 208B receive packets (e.g., from an Internet Protocol (IP) layer, layered directly or indirectly over the PDCP layer 208A or 208B) that can be referred to as sen ice data units (SDUs), and output packets (e.g., to the RLC layer 206A or 206B) that can be referred to as protocol data units (PDUs). Except where the difference between SDUs and PDUs is relevant, this disclosure for simplicity refers to both SDUs and PDUs as “packets.”DockctNo.: G114380 10160WO

[0041] On a control plane, the 6G PDCP sublayer 208A and the NR PDCP sublayer 208B can provide signaling radio bearers (SRBs) or RRC sublayer (not shown in Fig. 2A) to exchange RRC messages or non-access-stratum (NAS) messages, for example. On a user plane, the 6G PDCP sublayer 208A and the NR PDCP sublayer 208B can provide Data Radio Bearers (DRBs) to support data exchange. Data exchanged on the 6G PDCP sublayer 208A and NR PDCP sublayer 208B can be SDAP PDUs, Internet Protocol (IP) packets or Ethernet packets.

[0042] Fig. 2B illustrates, in a simplified manner, an example protocol stack 250, which the UE 102 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally split as shown by the radio protocol stack 250 in Fig. 2B. The CU at any of the base stations 104 or 106 can hold all the control and upper layer functionalities (e.g., RRC 212, SDAP 210, PDCP 208), while the lower layer operations (e.g., RLC 206, MAC 204, and PHY 202) are delegated to the DU. To support connection to a core network (e.g., 5GC or 6GC), PDCP 208 provides DRBs to SDAP 210 and SRBs to RRC 212. In some implementations, the RRC 212, SDAP 210. and PDCP 208 are the 6G RRC 212A, 6G SDAP 210A, 6G PDCP 208A, respectively. In other implementations, the RRC 212, SDAP 210, and PDCP 208 are the NR RRC 212B, NR SDAP 210B, NR PDCP 208B, respectively.

[0043] Next, several example scenarios in which the base station operating in the system of Fig. 1A transmits a configuration to the UE 102 and later activates a configuration for communication between the UE 102 and base station. Generally speaking, events in Figs. SA-16 that are similar are labeled with similar reference numbers (e.g., event 302 of Figs. 3A-3E is similar to event 602 of Figs. 6A and 6B, event 902 of Figs. 9, event 318 of Figs. 3A-3E is similar to event 918 of Fig. 9, event 1218A of Figs. 12A and 12C, event 1218B of Figs. 12B and 12D. event 1518A of Figs. 15A and 15C, event 1518B of Figs. 15B and 15D, and event 1618 of Fig. 16), with differences discussed below where appropriate. With the exception of the differences shown in the figures and discussed below, any of the alternative implementations discussed with respect to a particular event (e.g., for messaging and processing) may apply to events labeled with similar reference numbers in other figures.

[0044] Referring first to Fig. 3 A, in a scenario 300A, the base station 106 includes a CU 172 and DU 174 and the DU 174 operates the cell 126A. The DU 174 initially may transmit 302, to the CU 172, a DU-to-CU message indicating support of Al functionalities 1, ... , M. Mis a positive integer (i.e., M> 0). In some implementations, the DU-to-CU message is a non-UE associated message. For example, the DU-to-CU message is a Fl Setup Request message or a DU Configuration Update message. In other implementations, the DU 174 transmits the DU-DockctNo.: G114380 10160WOto-CU message in response to a CU-to-DU message that the DU 174 received from the CU 172. For example, the CU-to-DU message and the DU-to-CU message are a CU Configuration Update message and a CU Configuration Update Acknowledge message, respectively.

[0045] In some implementations, the DU 174 communicates with the UE 102 on a first serving cell (e.g., the cell 126 A) using a first serving DU configuration, and the CU 172 communicates with the UE 102 via the DU 174 using a first serving CU configuration. The first serving DU configuration includes configuration parameters generated by the DU 174, and the serving CU configuration includes configuration parameters generated by the CU 172. In some implementations, the first serving DU configuration includes physical layer configuration parameters, MAC configuration parameters, and / or RLC configuration parameters. ). In some implementations, the first serving DU configuration is CellGroupConfig IE defined in 3GPP specification 38.331. In other implementations, the first serving DU configuration includes configuration parameters in the CellGroupConfig IE. In some implementations, the first serving CU configuration includes PDCP configuration parameters, measurement configuration parameters, and / or radio bearer configuration parameters. In some implementations, the first serving CU configuration includes a MeasConflg IE and / or a RadioBearerConfig IE defined in 3GPP specification 38.331 or includes configuration parameters in the MeasConflg IE and / or RadioBearerConfig IE. In some implementations, the radio configuration parameters or the RadioBearerConfig IE configures a SRB (e.g., SRB1).

[0046] While communicating with the base station 106, the UE 102 may transmit 304 a UE-to-BS message including UE capabilities to the CU 172 via the DU 174. The UE capabilities include Al functionality capabilities indicating support of Al functionalities 1, ... , N. V is a positive integer (i.e., N > 0). In some implementations, N may be larger than or equal to Al. In such cases, the Al functionalities 1, N include the Al functionalities 7 Al. In other implementations, N may be smaller than Al. In such cases, the Al functionalities 7, ... . M include Al functionalities 7, ... , N. In some implementations, the UE 102 transmits the UE-to-BS message in response to receiving a BS-to-UE message. For example, the BS-to-UE message and the UE-to-BS message are a UE Capability Enquiry message and a UE Capability Information message, respectively.

[0047] In some implementations, the UE capabilities include one or more Al applicability reporting capabilities indicating support of Al functionality applicability reporting for some or all of the Al functionalities 7, .. , N. In some implementations, the UE capabilities include a (single) Al applicability reporting capability indicating support of Al functionality applicability reporting for all of the Al functionalities supported by the UE 102. In other implementations,DockctNo.: G114380 10160WOthe UE capabilities include Al applicability reporting capabilities 1, , N indicating support of Al functionality applicability reporting for the Al functionalities 7 N respectively. In yet other implementations, the UE 102 may only support Al functionality applicability reporting for a subset of the Al functionalities 1, ... , N. For example, the UE capabilities include Al functionality applicability7reporting capabilities / . ... , K indicating support of Al functionality applicability reporting for the Al functionalities 1. ... , K respectively. 1 <K < N.

[0048] In other implementations, the CU 172 receives 306 the UE capabilities from a network node (e.g., the base station 104, or a CN node such as the AMF 164 or the 6G AMF 174) instead of the UE 102. In some implementations, the CU 172 receives 306 a CN-to-BS message including the UE capabilities from a CN node (e.g., a CN node such as the AMF 164 or the 6G AMF 174). In one implementation, the CN-to-BS message is an NG Application Protocol (NGAP) message. In another implementation, the CN-to-BS message is a 6G CN-to-BS interface (e.g., N6G) Application Protocol message. In some implementations, the CN-to-BS message is an Initial UE Context Setup Request message or a Handover Request message. In other implementations, the CU 172 receives 306 a BS-to-BS message including the UE capabilities from another base station (i.e., the base station 104), while the UE 102 communicates with the base station 104 and does not communicate with the base station 106. In one implementation, the BS-to-BS message is an Xn Application Protocol (XnAP) message. In another implementation, the BS-to-BS message is a 6G BS-to-BS interface (e.g., X6G) Application Protocol message. The BS-to-BS message may be a Handover Request message or a Retrieve UE Context Response message.

[0049] In some implementations, each Al functionality' refers to a 3GPP feature or feature group for which Al (e.g., an Al model) is enabled. In some implementations, the 3GPP features or feature groups includes one or more communication functions such as CSI feedback, beam management, and / or positioning. In some implementations, the Al functionalities 1, ..., N and / or 1, ..., M includes one or more of the following Al functionalities: Spatial-frequency domain CSI compression using Al; Time domain CSI prediction; Spatial-domain Downlink beam prediction for Set A of beams based on measurement results of Set B of beams; Temporal Downlink beam prediction for Set A of beams based on the historic measurement results of Set B of beams; Direct AI / ML positioning; AI / ML assisted positioning.

[0050] The CU 172 then may transmit 308 the UE capabilities to the DU 174. In some implementations, after receiving the UE capabilities, the CU 172 transmits a first CU-to-DU message to the DU 174 to request the DU 174 to configure radio resources for the UE 102. The CU 172 may include the UE capabilities in the first CU-to-DU message. Alternatively, the CUDockctNo.: G114380 10160WO172 transmits a second CU-to-DU message including the UE capabilities to the DU 174. In response to the first CU-to-DU message, the DU 174 generates a second serving DU configuration and transmits a first DU-to-CU message including the second serving DU configuration to the CU 172. In some implementations, the DU 174 generates the second serving DU configuration based on information in the first CU-to-DU message and / or the UE capabilities. The information may include SRB information and / or DRB information. The UE capabilities may include non- Al capabilities and the DU 174 may generate the configuration parameters in the second serving DU configuration based on the non-AI capabilities. The CU 172 generates a first message including the second serving DU configuration and transmits the first message to the UE 102, e.g., via the DU 174 or a RAN node (e g., another DU or the base station 104). For example, the first message is an RRC reconfiguration message. In some implementations, the CU 172 generates a second serving CU configuration for the UE 102 and includes the second serving CU configuration in the first message. After transmitting the second serving DU configuration to the UE 102 via the CU 172, the DU 174 communicates with the UE 102 using the second serving DU configuration. After transmitting the second serving CU configuration to the UE 102. the CU 172 communicates with the UE 102 using the second serving CU configuration. In some implementations, the first CU-to-DU message and the first DU-to-CU message are Fl Application Protocol (F1AP) messages. In some implementations, the first CU-to-DU message and the first DU-to-CU message are a UE Context Modification Request message and a UE Context Modification Response message, respectively. In other implementations, the first CU-to-DU message and the first DU-to-CU message are a UE Context Setup Request message and a UE Context Setup Response message, respectively.

[0051] In some implementations, the second serving DU configuration includes configuration parameters configuring one or more additional serving cell(s) (e.g., the cell(s) 126B and / or 126C). In some implementations, the second serving DU configuration includes at least one first configuration for beam management for the first and / or additional serving cell(s). In some implementations, the second serving DU configuration includes at least one TCI state configuration for the first and / or additional serving cell(s). In some implementations, the second serving DU configuration includes a CSI-MeasConfig IE or configuration parameters for channel state information (CSI) measurement and reporting. In other implementations, the serving CU configuration includes a CSI-MeasConfig IE or configuration parameters for CSI measurement and reporting. In some implementations, the second serving CU configuration includes PDCP configuration parameters, measurement configurationDockctNo.: G114380 10160WOparameters, and / or radio bearer configuration parameters. In some implementations, the second serving CU configuration includes aMeasConftg IE and / or a RadioBear erConfig IE defined in 3GPP specification 38.331 or includes configuration parameters in the MeasConflg IE and / or RadioBear erConfig IE. In some implementations, the radio configuration parameters or the RadioBearerConfig IE configures a SRB (e.g., SRB2) or one or more DRBs.

[0052] While communicating with the UE 102, after receiving the UE capabilities, or receiving the first CU-to-DU message, the DU 174 determines to request 309 to configure Al functionality applicability reporting. In response to the determination 309, the DU 174 transmits 312 a DU-to-CU message to the CU 172, indicating or requesting to configure Al functionality applicability reporting. In some implementations, the DU 174 indicates or requests to configure Al functionality applicability reporting specific only for the Al functionality 1 in the DU-to-CU message 312. In such cases, the DU 174 may include identification information of the Al functionality' 1 in the DU-to-CU message. The identification information may be an identity' or identifier (ID) 1 or a name (e.g., an enumeration value) of the Al functionality 1. The DU 174 may or may not indicate or request to configure Al functionality applicability reporting for some or all of Al functionalities 2. ... , N in the DU-to-CU message 312. In some implementations, the DU-to-CU message 312 and the first DU-to-CU message are combined into the same message (i.e., same instance). In other implementations, the DU-to-CU message 312 and the first DU-to-CU message are different messages or instances of messages.

[0053] In some implementations, the DU-to-CU message 312 is a Fl AP message. In other implementations, the DU-to-CU message 312 is a UE Context Modification Required message. In yet other implementations, the DU 174 transmits 312 the DU-to-CU message in response to the first CU-to-DU message. In some implementations, the first CU-to-DU message and the DU-to-CU message 312 may be a UE Context Setup Request message and a UE Context Setup Response message, respectively. In other implementations, the first CU-to-DU message and the DU-to-CU message 312 may be a UE Context Modification Request message and a UE Context Modification Response message, respectively. In some implementations, the first CU-to-DU message is the CU-to-DU message 308 (i.e.. the same instance). In other implementations, the first CU-to-DU message is different from the CU-to-DU message 308.

[0054] In some implementations, the DU 174 makes the determination 309 because the UE 102 supports the Al functionality' 1 and / or the condition(s) 1 is / are met as described above. In other implementations, the DU 174 makes the determination 309 because the UE 102 supportsDockctNo.: G114380 10160WOthe Al functionality applicability reporting and / or the condition(s) 1 is / are met as described above.

[0055] In some implementations, the CU 172 may transmit 314 a CU-to-DU message to the DU 174 in response to the DU-to-CU message 312. In some implementations, the DU-to-CU message 312 may indicate the Al functionality 1. For example, the DU-to-CU message 312 includes identification information of the Al functionality 1 to indicate the Al functionality 1. The DU-to-CU message 312 may or may not indicate some or all of the Al functionalities 2, , N. For example, the DU-to-CU message 312 may or may not include identification information of some or all of the Al functionalities 2, ... A. In other implementations, the DU-to-CU message 312 indicates no (specific) Al functionality'. In such cases, the DU 174 may request configuration of Al functionality applicability reporting generally for Al functionalities supported by the UE 102 and / or associated with 3GPP features or feature groups configured in the first serving DU configuration and / or the second serving DU configuration.

[0056] In some implementations, the CU 172 may determine whether to accept the request of configuring Al functionality applicability reporting. In some implementations, the CU 172 makes the determination based on whether (1) the CU 172 supports configuration of the Al functionality applicability reporting (e.g., for the Al functionality 1 or generally), (2) the UE 102 supports the Al functionality 1 and / or the Al functionality applicability reporting (e.g., for the Al functionality 1 or generally), (3) the UE 102 has a valid Al model for the Al functionality 1, and / or (4) the condition(s) for configuring the Al functionality 1 is / are met (as described below). If the CU 172 accepts the request of configuring Al functionality applicability reporting, the CU-to-DU message 314 indicates that the CU 172 accepts the request of configuring Al functionality applicability reporting. In some implementations, the CU 172 accepts the request because (1) the CU 172 supports configuration of the Al functionality applicability reporting (e.g., for the Al functionality 1 or generally), (2) the UE 102 supports the Al functionality 1 and / or the Al functionality' applicability' reporting (e.g., for the Al functionality 1 or generally), (3) the UE 102 has a valid Al model for the Al functionality 1, and / or (4) the condition(s) for configuring the Al functionality 1 is / are met (as described below). If the CU 172 accepts the request, the CU 172 generates an Al functionality applicability reporting configuration for the UE 102 in response to the request in the DU-to-CU message 312. In some implementations, the Al functionality applicability reporting configuration configures Al functionality applicability reporting specifically for the Al functionality 1. In such cases, the Al functionality applicability reporting configuration indicates the Al functionality 1. For example, the Al functionality applicability reportingDockctNo.: G114380 10160WOconfiguration includes identification information of the Al functionality' 1 as described above. The Al functionality applicability reporting configuration may or may not indicate some or all of other Al functionalities 2. ...N. For example, the Al functionality applicability reporting configuration may or may not include identification information of some or all of the Al functionalities 2, ... , TV as described above. In some implementations, if the DU-to-CU message 312 indicates an Al functionality (e.g., the Al functionality 1), the CU 172 indicates the Al functionality in the Al functionality applicability reporting configuration. Otherwise, if the DU-to-CU message 312 does not indicate an Al functionality, the CU 172 does not indicate the Al functionality in the Al functionality applicability reporting configuration.

[0057] In other implementations, the Al functionality' applicability reporting configuration does not indicate which Al functionality’. In some implementations, the CU 172 may indicate no (specific) Al functionality in the Al functionality applicability reporting configuration, because the DU-to-CU message 312 indicates no (specific) Al functionality.

[0058] Otherwise, if the CU 172 rejects the request of configuring Al functionality applicability reporting, the CU-to-DU message 314 indicates that the CU 172 rejects the request of configuring Al functionality applicability reporting. In some implementations, the CU 172 rejects the request because (1) the CU 172 does not support configuration of the Al functionality’ applicability reporting (e.g., for the Al functionality 1 or generally), (2) the UE 102 does not support the Al functionality 1 or the Al functionality applicability reporting (e.g., for the Al functionality’ 1 or generally), (3) the UE 102 does not have a valid Al model for the Al functionality 1, and / or (4) the condition(s) for configuring the Al functionality 1 is / are not met.

[0059] While communicating with the UE 102, after receiving the UE capabilities, receiving the first CU-to-DU message, or receiving the CU-to-DU message 314, the DU 174 determines 310 to configure the Al functionality 1. In response to the determination 310, the DU 174 generates a first configuration configuring the Al functionality 1 and transmits 316 a DU-to-CU message including the first configuration to the CU 172. In some implementations, the first configuration includes the identification information for the UE 102 to determine the first configuration for the Al functionality 1. In some implementations, the DU 174 indicates, in the first configuration, “inactive” or “deactivated” for the Al functionality 1. For example, the DU 174 includes an indication indicating “inactive” or “deactivated” for the Al functionality 1 in the first configuration. In other implementations, the DU 174 does not indicate whether the Al functionality 1 is inactive or deactivated in the first configuration. In such cases, the UE 102 and the DU 174 determine that the Al functionality 1 is inactive or deactivated before the UEDockctNo.: G114380 10160WO102 receives an activation command activating the Al functionality 1. In some implementations, the DU 174 indicates the Al functionality 1 in the DU-to-CU message 316 as described for the DU-to-CU message 312. Examples and implementations for the DU-to-CU message 312 can apply to the DU-to-CU message 31 . In some implementations, the DU 174 makes the determination 310 in response to receiving the CU-to-DU message 314. In other implementations, the DU 174 makes the determination 310 based on the Al functionality capabilities. In some implementations, event 309 can be omitted and the DU 174 transmits 312 the DU-to-CU message to the CU 172 in response to the determination 310. In some implementations, the DU-to-CU message 316 and the DU-to-CU message 312 are combined into a single DU-to-CU message. In other implementations, the DU-to-CU message 316 and the DU-to-CU message 312 are different messages or instances of messages. In some implementations, the DU-to-CU message 316 and the first DU-to-CU message are combined into the same message (i.e., same instance). In one implementation, the DU 174 may include the first configuration in the second serving DU configuration. In another implementation, the DU 174 includes the first configuration and the second serving DU configuration in a first IE and a second IE in the DU-to-CU message 316 respectively. In other implementations, the DU-to-CU message 316 and the first DU-to-CU message are different messages or instances of messages. In such cases, the DU 174 in one implementation may generate a third serving DU configuration (e.g., a CellGroupConfig information element (IE)) including the first configuration and includes the third serving DU configuration in the DU-to-CU message 316.

[0060] In some implementations, the UE capabilities or the Al functionality capabilities include or indicate condition(s) 1, . . , N for configuration of the Al functionalities 7, ... , N, respectively. For example, the DU 174 determines to configure or configures the Al functionality X when determining that the condition(s) X is met, where 1 <X < N. In some implementations, the condition(s) X is an area configuration indicating an area. If the serving cell(s) is within the area, the DU 174 determines to configure the Al functionality X. In event 310, the DU 174 may determine to configure the Al functionality 1 because the serving cell(s) is within an area indicated by an area configuration for the Al functionality 1. In one implementation, the area consists of one or more cells and the area configuration includes one or more cell identities each identifying a corresponding cell in the one or more cells. In addition to the one or more cell identities, the area configuration may include a tracking area code and / or a public land mobile network (PLMN) identity where the one or more cells belongs. In another implementation, the area consists of one or more tracking areas and the area configuration includes one or more tracking area codes each identifying a corresponding tracking area. InDockctNo.: G114380 10160WOaddition to the one or more tracking area codes, the area configuration may include a PLMN identity where the one or more tracking areas belongs.

[0061] The CU 172 then transmits 318 the Al functionality applicability reporting configuration and the first configuration to the UE 102, e.g., via the DU 174 or the RAN node. In some implementations, the CU 172 generates a second message including the Al functionality applicability reporting configuration and transmits the second message to the UE 102 via the DU 174 or the RAN node. In one implementation, the CU 172 includes the first configuration in the second message. In another implementation, the CU 172 generates a third message including the first configuration and transmits the third message to the UE 102 via the DU 174 or the RAN node. In other implementations, if the second serving DU configuration includes the first configuration as described above, the UE 102 receives the first configuration in the first message. In some implementations, the CU 172 includes the Al functionality applicability reporting configuration in the first message.

[0062] After receiving 318 the Al functionality applicability reporting configuration and / or first configuration, the UE 102 evaluates 320 whether the Al functionality 1 is applicable. If the Al functionality 1 is applicable based on the evaluation of the UE 102, the UE 102 transmits 322 an Al functionality applicability report to the CU 172, e.g., via the DU 174 or the RAN node. The UE 102 indicates the Al functionality' 1 is applicable in the Al functionality' applicability report. After receiving 322 the Al functionality applicability report, the CU 172 transmits 324 the Al functionality applicability report to the DU 174. In some implementations, the UE 102 in event 322 transmits a UL message including the Al functionality applicability report to the CU 172, e.g., via the DU 174 or the RAN node. In some implementations, the UE 102 initiates transmission of the UL message. In such cases, the UL message is aUE Assistance Information message. In other implementations, the UE 102 transmits the UL message in response to receiving a DL message from the CU 172 or the RAN node. In one implementation, the DL message and the UL message are an RRC reconfiguration message and an RRC reconfiguration complete message, respectively. In another implementation, the DL message and the UL message are an RRC resume message and an RRC resume complete message, respectively. In some implementations, the CU 172 retrieves the Al functionality applicability report from the UL message and transmits the Al functionality applicability report to the DU 174. In other implementations, the CU 172 transmits the UL message to the DU 174 and the DU 174 retrieves the Al functionality applicability' report from the UL message.

[0063] In some implementations, if the Al functionality applicability reporting configuration indicates some or all of the Al functionalities 2, .... N, the UE 102 evaluates whether the someDockctNo.: G114380 10160WOor all of the Al functionalities 2, N are applicable. In some implementations, if the Al functionality applicability reporting configuration indicates no specific Al functionality, the UE 102 evaluates whether the some or all of the Al functionalities 2 A are applicable. If Al functional K in the some or all of the Al functionalities 2, ... , N is applicable based on the evaluation, the UE 102 transmitting an additional Al functionality applicability report to the CU 172 via the DU 174 or the RAN node, indicating the Al functionality K is applicable, as described for event 322. In some implementations, the UE 102 includes the additional Al functionality applicability report in the UL message (i.e., a first UE message). In other implementations, the UE 102 transmits a second UL message including the additional Al functionality applicability report to the CU 172 via the DU 174 or the RAN node. In some alternative implementations, the UE 102 indicates the Al functionality K is applicable in the Al applicability report 322.

[0064] After transmitting the first configuration to the UE 102 (e.g., events 316 and / or 318), the DU 174 may determine 326 to activate the Al functionality 1. In some implementations, the DU 174 makes the determination 326 based on the indication of the Al functionality 1 applicable 324. In other implementations, the DU 174 makes the determination 326 based on the Al functionality capabilities. In response to the determination 326, the DU 174 transmits 328 an activation command to the UE 102, indicating to activate the Al functionality 1. In some implementations, the activation command includes the identification information of the Al functionality 1. In other implementations, the activation command includes a field indicating the Al functionality 1. The UE 102 activates 330 the Al functionality 1 in response to the indication of activating the Al functionality 1 that the UE 102 received at event 328. The UE 102 then performs 332 communication with the DU 174 using the Al functionality 1. In some implementations, the activation command is a MAC control element. In other implementations, the activation command is a DL control information (DCI). In some implementations, the UE 102 activates a first Al model for the Al functionality 1 in response to activating the Al functionality 1. In some implementations, after (e.g., in response to) activating the Al functionality 1 or the first Al model, the UE 102 starts to use or uses the first Al mode to perform inference for the Al functionality 1. In some implementations, the Al functionality I uses two-sided Al model. In such cases, after transmitting (e.g., in response to) the activation command, the DU 174 activates a second Al model or starts using the second Al model to communicate with the UE 102 in event 332. In some implementations, after (e.g., in response to) activating the Al functionality 1 or the second Al model for the UE 102 or starting usingDockctNo.: G114380 10160WOthe second Al model for the UE 102, the DU 174 uses the second Al model to perform inference for the Al functionality’ 1 in communicating with UE 102.

[0065] In some implementations, in response to the determination 326 or transmission of the activation command, the DU 174 transmits 334 aDU-to-CU message to the CU 172, indicating the Al functionality 1 is activated. Thus, the CU 172 knows that the Al functionality' 1 is activated for the UE 102. In some implementations, the DU-to-CU message 334 is a UE Context Modification Required message. In other implementations, the DU-to-CU message 334 is an interface message or a Fl AP message specific for Al operation.

[0066] The events 320, 324, 326, 328, 334, 330, and 332 are collectively referred to in Fig.3A as an Al functionality' applicability reporting and / or activation procedure 390.

[0067] In some implementations, the DU 174 indicates the Al functionality 1 is active or activated in the first configuration. In such cases, the UE 102 activates 330 the Al functionality 1 in response to receiving the first configuration. After activating the Al functionality 1, the UE 102 performs communication with the DU 174 using the Al functionality 1.

[0068] In some implementations, the Al functionality 1 is a beam prediction for beam management. In such cases, the Al functionality 2 and / or the Al function 3 can be CSI compression for CSI feedback and / or CSI prediction for CSI feedback. In other implementations, the Al functionality' 1 is a CSI compression for CSI feedback. In such cases, the Al functionality 2 and / or the Al function 3 can be beam prediction for beam management and / or CSI prediction for CSI feedback. In yet other implementations, the Al functionality 1 is a CSI prediction for CSI feedback. In such cases, the Al functionality 2 and / or the Al function 3 can be CSI compression for CSI feedback and / or beam prediction for beam management.

[0069] Referring next to Fig. 3B depicting a scenario 300B similar to Fig. 3A. The differences between Fig. 3A and Fig. 3B are described below. In the scenario 300B, the CU 172 determines 317 to configure Al functionality applicability reporting instead of receiving a request of configuring Al functionality' applicability' reporting. The CU makes the determination 317 in response to receiving 316 the DU-to-CU message. In some implementations, the DU 174 may indicate the Al functionality 1 (is applicable) in the DU-to-CU message 316, as described for Fig. 3 A. In some implementations, the indication of the Al functionality 1 (is applicable) is an IE included in the DU-to-CU message 316. Based on the indication of the Al functionality' 1 (is applicable) in the DU-to-CU message 316, the CU 172 indicates the Al functionality in the Al functionality applicability' reporting configuration. In other implementations, the DU 174 includes an indication in the DU-to-CU message 316, generally indicating an Al functionality is applicable. In response to the indication of anDockctNo.: G114380 10160WO(unspecific) Al functionality is applicable, the CU 172 may indicate no (specific) Al functionality in the Al functionality applicability reporting configuration, as described for Fig.3A.

[0070] Referring next to Fig. 3C depicting a scenario 300C similar to Figs. 3 A and 3B. The differences between Fig. 3C and Figs. 3A and 3B are described below. In the scenario 300B, the CU 172 determines 311 to configure the Al functionality 1 for the UE 102 after receiving the UE capabilities (e.g., event 304 or 306). In response to the determination 311, the CU 172 transmits 315 a CU-to-DU message to the DU 174, indicating or requesting to configure the Al functionality 1. In some implementations, the CU 172 makes the determination 311 based on the Al functionality capability for the Al functionality 1. In other implementations, the CU 172 makes the determination 311 based on that the UE 102 supports the Al functionality 1. (2) the UE 102 has a valid Al model for the Al functionality 1, and / or (3) the condition(s) for configuring the Al functionality' 1 is / are met (as described above). If the UE 102 does not support the Al functionality' 1, the UE 102 does not have a valid Al model for the Al functionality 1. and / or the condition(s) for configuring the Al functionality 1 is / are not met (as described above), the CU 172 determines not to configure the Al functionality 1 for the UE 102.

[0071] In response to the CU-to-DU message, the DU 174 transmits 316 the DU-to-CU message to the CU 172 as described for Fig. 3 A and Fig. 3B. In some implementations, the DU 174 may determine whether to accept the request of configuring the Al functionality 1. In some implementations, the DU 174 makes the determination based on whether (1) the DU 174 supports configuration of the Al functionality 1, (2) the UE 102 supports the Al functionality 1, (3) the UE 102 has a valid Al model for the Al functionality 1, and / or (4) the condition(s) for configuring the Al functionality 1 is / are met (as described below). If the DU 174 accepts the request of configuring Al functionality 1, the DU 174 transmits 316 the DU-to-CU message. In some implementations, the DU 174 accepts the request because (1) the DU 174 supports configuration of the Al functionality 1, (2) the UE 102 supports the Al functionality 1, (3) the UE 102 has a valid Al model for the Al functionality 1, and / or (4) the condition(s) for configuring the Al functionality 1 is / are met (as described above). If the DU 174 accepts the request, the DU 174 generates the first configuration for the UE 102 in response to the request in the CU-to-DU message 315.

[0072] Otherwise, if the DU 174 rejects the request of configuring Al functionality 1, the DU 174 transmits another DU-to-CU message to the CU instead of the DU-to-CU message, indicating that the DU 174 rejects the request of configuring Al functionality 1. In someDockctNo.: G114380 10160WOimplementations, the DU 174 rejects the request because (1) the DU 174 does not support configuration of the Al functionality 1, (2) the UE 102 does not support the Al functionality 1, (3) the UE 102 does not have a valid Al model for the Al functionality 1, and / or (4) the condition(s) for configuring the Al functionality 1 is / are not met.

[0073] Referring next to Fig. 3D depicting a scenario 300D similar to Figs. 3A-3C. The differences between Fig. 3D and Figs. 3A-3C are described below. In the scenario 300D, the CU 172 determines 325 to activate Al functionality 1 instead of the DU 174. In some implementations, the CU 172 makes the determination 325 based on the indication 322 indicating that the Al functionality 1 is applicable. In response to the determination 325, the CU 172 transmits 327 a CU-to-DU message to the DU 174, indicating to activate the Al functionality 1 for the UE 102. In response to the CU-to-DU message 327 or the indication of activating the Al functionality 1, the DU 174 transmits 328 the activation command to the UE 102. In some implementations, the CU-to-DU message 327 is a F1AP message. For example, the CU-to-DU message 327 is a UE Context Modification Request message. The DU 174 may transmit a UE Context Modification Response message in response to the UE Context Modification Request message. In other implementations, the CU-to-DU message 327 is an interface message or F1AP message specific for Al operation.

[0074] The events 320, 324, 326, 328, 327, 330, and 332 are collectively referred to in Fig.3A as Al functionality applicability reporting and / or activation procedure 391.

[0075] Referring next to Fig. 3E depicting a scenario 300E similar to Figs. 3A-3D. The differences between Fig. 3E and Figs. 3A-3D are described below. In the scenario 300E, in response to the determination 317, the CU 172 transmits 313 the Al functionality applicability reporting configuration to the UE 102, e.g., via the DU 174 or the RAN node. The UE 102 evaluates 320 whether the Al functionality 1 is applicable in response to receiving the Al functionality applicability reporting configuration. Later in time, the CU 172 receives 316 the DU-to-CU message including the first configuration and transmits 319 the first configuration to the UE 102. Examples and implementations described for event 318 of Fig. 3A can apply to events 313 and 319.

[0076] Now referring to Fig. 4A, in a scenario 400A, the base station 106 includes a CU 172 and DU 174. Initially, the UE 102 and the base station 106 communicates with each other and the UE 102 activates the Al functionality 1 in communication with the DU 174 as described in the scenario 300A, 300B, 300C, 300D or 300E. While performing communication with the DU 174 using the Al functionality 1, the UE 102 may determine that the Al functionality 1 is not applicable. In response to the determination that the Al functionality 1 is not applicable, theDockctNo.: G114380 10160WOUE 102 may transmit 436 an Al functionality applicability' report indicating the Al functionality 1 is not applicable to the CU 172 via the DU 174 or the RAN node. The CU 172 then transmits 438 the Al functionality applicability' report to the DU 174. Examples and implementations described for events 322 and 324 may apply to events 436 and 438.

[0077] While performing communication with the DU 174 using the Al functionality71, the DU 174 determines 440 to deactivate the Al functionality 1 for the UE 102. In some implementations, the DU 174 makes the determination 440 because the condition(s) for the Al functionality 1 is / are no longer met. In other implementations, the DU 174 makes the determination 440 in response to the indication 438 indicating that the Al functionality 1 is not applicable. In response to the determination 440 or the indication 438. the DU 174 transmits 442 a deactivation command to the UE 102. commanding to deactivate the Al functionality 1. In response to the deactivation command, the UE 102 deactivates 444 the Al functionality 1. In some implementations, the deactivation command includes the identification information of the Al functionality' 1. In other implementations, the deactivation command includes a field indicating the Al functionality' 1. In some implementations, the deactivation command is a MAC CE or a DCI. The UE 102 then performs communication with the DU 174 without using the Al functionality 1. In some implementations, in response to the determination 440 or transmission of the deactivation command, the DU 174 transmits 448 a DU-to-CU message to the CU 172, indicating the Al functionality 1 is deactivated. Thus, the CU 172 knows that the Al functionality 1 is deactivated for the UE 102. Later in time, the UE 102 and the base station 106 may perform 490 an Al functionality7applicability reporting and / or activation procedure similar to the procedure 390. Alternatively, the UE 102 and the base station 106 may perform 491 an Al functionality applicability reporting and / or activation procedure similar to the procedure 391. In other implementations, the DU-to-CU message 448 is an interface message or Fl AP message, e.g., specific for Al operation.

[0078] In some implementations, the UE 102 deactivates the first Al model for the Al functionality 1 in response to deactivating the Al functionality71. In some implementations, after (e g., in response to) deactivating the Al functionality 1 or the first Al model, the UE 102 stops using the first Al model to performing inference for the Al functionality 1. In some implementations, the Al functionality 1 uses two-sided Al model. In such cases, the DU 174 deactivates the second Al model or stops using the second Al model to communicate with the UE 102 after (e.g., in response to) transmitting the deactivation command. In some implementations, after (e.g.. in response to) deactivating the Al functionality 1 or the second Al model for the UE 102 or stops using the second Al model for the UE 102, the DU 174 stopsDockctNo.: G114380 10160WOusing the second Al model to perform inference for the Al functionality 1 in communication with the UE 102.

[0079] Referring next to Fig. 4B depicting a scenario 400B similar to Fig. 4A. The differences between Fig. 4B and Fig. 4A are described below. In the scenario 400B, while communicating with the UE 102, the CU 172 determines 439 to deactivate the Al functionality 1 for the UE 102 instead of the DU 174. In some implementations, the CU 172 makes the determination 439 because the condition(s) for the Al functionality 1 is / are no longer met. In other implementations, the CU 172 makes the determination 439 in response to the indication 436 indicating that the Al functionality 1 is not applicable. In response to the determination 439 or the indication 436. the CU 172 transmits 441 a CU-to-DU message to the DU 174, indicating to deactivate the Al functionality 1. In some implementations, the CU-to-DU message 441 is a F1AP message. For example, the CU-to-DU message 441 is a UE Context Modification Request message. The DU 174 may transmit a UE Context Modification Response message in response to the UE Context Modification Request message. In other implementations, the CU-to-DU message 441 is an interface message or F1AP message, e.g., specific for Al operation. The DU 174 may transmit a DU-to-CU message to the CU 172 in response to the CU-to-DU message 441.

[0080] Now referring to Fig. 5 A, in a scenario 500A, the base station 106 includes a CU 172 and DU 174. Initially, the UE 102 and the base station 106 communicates with each other and the UE 102 activates the Al functionality 1 in communication with the DU 174 as described in the scenario 300A, 300B, 300C, 300D or 300E. While performing communication with the DU 174 using the Al functionality’ 1, the UE 102 transmit 436 the Al functionality7applicability report indicating the Al functionality 1 is not applicable to the CU 172 via the DU 174 or the RAN node, as described for Fig. 4A. The CU 172 then transmits 438 the Al functionality applicability report to the DU 174.

[0081] While performing communication with the DU 174 using the Al functionality 1, the DU 174 determines 550 to release the Al functionality71 for the UE 102 (i.e., release the first configuration). In some implementations, the DU 174 makes the determination 550 because the condition(s) for the Al functionality 1 is / are no longer met. In other implementations, the DU 174 makes the determination 550 in response to the indication 438 indicating that the Al functionality 1 is not applicable. In response to the determination 550 or the indication 438, the DU 174 may transmit 552 a DU-to-CU message to the CU 172, indicating (e.g., requesting or commanding) to release the Al functionality applicability reporting. In response, the CU 172 may transmit 554 a CU-to-DU message to the DU 174. In some implementations, the CU-to-DockctNo.: G114380 10160WODU message acknowledges the reception of the DU-to-CU message 552 or accepts the request of releasing the Al functionality applicability reporting.

[0082] In response to the determination 550, the DU 174 transmits 556 a DU-to-CU message to the CU 172, including a first release configuration releasing the Al functionality 1. In some implementations, the DU 174 indicates to release the Al functionality 1 in the DU-to-CU message. The CU 172 transmits 560 the first release configuration to the UE 102 via the DU 174 or the RAN node. In some implementations, the DU 174 generates a fourth serving DU configuration including the first release configuration and includes the fourth serving DU configuration (e.g., a CellGroupConfig IE) in the DU-to-CU message 556. Examples and implementations described for events 312, 314, and 316 may apply to events 552, 554, and 556, respectively. In some implementations, the first release configuration includes the identification information for the UE 102 to determine the first release configuration for the Al functionality 1.

[0083] In some implementations, the CU 172 may determine 558 to release or may release 558 the Al functionality applicability reporting configuration in response to receiving 556 the DU-to-CU message or the indication of releasing the Al functionality 1. In other implementations, the CU 172 172 may determine 558 to release or may release 558 the Al functionality7applicability reporting configuration in response to receiving 552 the DU-to-CU message or the indication of the releasing the Al functionality applicability reporting. In response to the determination or releasing 558, the CU 172 transmits 560 an indication of releasing the Al functionality applicability reporting configuration via the DU 174 or the RAN node.

[0084] In some implementations, the CU 172 generates a first message including the first release configuration and transmits the first message to the UE 102. In some implementations, the CU 172 includes the indication of releasing the Al functionality applicability reporting configuration in the first message. In other implementations, the CU 172 generates a second message including the indication of releasing the Al functionality applicability reporting configuration and transmits the second message to the UE 102. In some implementations, the first message and the second message are RRC reconfiguration message.

[0085] In some alternative implementations, the CU 172 determines to keep or maintain the Al functionality applicability reporting configuration when releasing the first configuration configuring the Al functionality 1. In response to the determination of keeping or maintaining the Al functionality applicability reporting configuration, the CU 172 refrains fromDockctNo.: G114380 10160WOtransmitting the indication of releasing the Al functionality applicability reporting configuration to the UE 102.

[0086] In response to (receiving) the first release configuration, the UE 102 stops 562 using the Al functionality 1 and releases the first configuration. In some implementations, the UE 102 stops 564 evaluating whether the Al functionality 1 is applicable in response to (receiving the indication of) releasing the first configuration. In some implementations, if the UE 102 does not receive the indication of releasing the Al functionality applicability reporting configuration, the UE 102 keeps or retains the Al functionality’ applicability reporting configuration. In such cases, the UE 102 stops 564 evaluating whether the Al functionality 1 is applicable in response to receiving the first release configuration. Alternatively, the UE 102 continues evaluating whether the Al functionality 1 is applicable in response to receiving the first release configuration. If the UE 102 receives the indication of releasing the Al functionality applicability reporting configuration, the UE 102 releases the Al functionality applicability reporting configuration in response to the indication of releasing the Al functionality applicability reporting configuration.

[0087] After or in response to stopping 562 using the Al functionality 1 in communication with the DU 174, the UE 102 performs 446 communication with the DU 174 without using the Al functionality 1. In some implementations, the stopping using the Al functionality 1 includes stopping or deactivating using the first Al model to perform inference for the Al functionality 1. In some implementations, the Al functionality’ 1 uses two-sided Al model. In such cases, the DU 174 deactivates the second Al model or stops using the second Al model to communicate with the UE 102 after (e.g., in response to) transmitting the first release configuration. In some implementations, after (e.g., in response to) deactivating the second Al model or stopping using the second Al model, the DU 174 stops using the second Al model to perform inference for the Al functionality 1 in communication with the UE 102.

[0088] Referring next to Fig. 5B depicting a scenario 500B similar to Fig. 5A. The differences between Fig. 5B and Fig. 5A are described below. In the scenario 500B, while communicating with the UE 102, the CU 172 determines 551 to release the Al functionality 1 for the UE 102 (i.e., release the first configuration) instead of the DU 174. In some implementations, the CU 172 makes the determination 551 because the condition(s) for the Al functionality 1 is / are no longer met. In other implementations, the CU 172 makes the determination 551 in response to the indication 436 indicating that the Al functionality 1 is not applicable. In response to the determination 551 or the indication 436, the CU 172 transmits 555 a CU-to-DU message to the DU 174, indicating to releasing the Al functionality’ 1. In someDockctNo.: G114380 10160WOimplementations, the CU-to-DU message 555 is a F 1 AP message. For example, the CU-to-DU message 555 is a UE Context Modification Request message. The DU 174 may transmit a UE Context Modification Response message in response to the UE Context Modification Request message. In other implementations, the CU-to-DU message 555 is a message specific for Al operation.

[0089] In response to the indication of releasing the Al functionality, the DU 174 generates the first release configuration releasing the Al functionality I. The DU 174 then transmits 556 the DU-to-CU message including the first release configuration to the CU 172 in response the CU-to-DU message 555.

[0090] Next, several example methods, which can be implemented in a RAN node (e.g., a base station, a CU, or a DU described above) or a UE (e.g., the UE 102), are discussed next with reference to Figs. 6A-16. Descriptions and example implementations described for Figs.3A-5B can apply to Figs. 6A-16.

[0091] Fig. 6A illustrates an example method 600A, which can be implemented by a DU. The method 600A begins at block 602, where the DU transmits a DU-to-CU message to a CU, indicating that the DU supports Al functionalities 1. ... , M. AT is an integer larger than zero. At block 608, the DU receives a CU-to-DU message from the CU, indicating a UE supports Al functionalities 1, .. , N. / V is a positive integer and N >M. At block 610, the DU determines to configure the Al functionality 1 for the UE. At block 616, the DU transmits a DU-to-CU message including a first configuration to the CU. where the first configuration configures the Al functionality 1. At block 612, the DU transmits a DU-to-CU message to the CU, causing the CU to transmit an Al functionality applicability reporting configuration to the UE. The flow proceeds to block 624 or block 626. At block 624, the DU receives an Al functionality applicability report from the CU. indicating that the Al functionality 1 is applicable for the UE. At block 626, the DU determines to activate the Al functionality 1. At block 628, the DU transmits an activation command to the UE, indicating the UE to activate the Al functionality 1. At block 634, the DU transmits a DU-to-CU message to the CU, indicating the Al functionality 1 is activated. At block 632, the DU communicates with the UE based on the first configuration.

[0092] In some implementations, the DU includes an indication in the DU-to-CU message 612, indicating to configure the UE to transmit Al functionality applicability report(s). In response to the DU-to-CU message 612, the CU generates the Al functionality applicability reporting configuration and transmits the Al functionality applicability reporting configuration to the UE. In one implementation, the DU includes an indication of the Al functionality 1 inDockctNo.: G114380 10160WOthe DU-to-CU message 612. Thus, the CU includes, in the Al functionality applicability reporting configuration, an indication of the Al functionality 1 (e.g., identification information or an ID of the Al functionality 1).

[0093] In other implementations, the DU transmits includes the Al functionality applicability reporting configuration in the DU-to-CU message 612. In turn, the CU retrieves the Al functionality applicability reporting configuration from the DU-to-CU message 612 and transmits the Al functionality applicability reporting configuration to the UE. In one implementation, the DU includes, in the Al functionality applicability' reporting configuration, an indication of the Al functionality 1 (e.g., identification information or an ID of the Al functionality 1).

[0094] Fig.6B is a flow diagram of an example method 600B similar to the method 600A, except that the method 600B includes block 615 instead of block 610. At block 615, the DU receives a CU-to-DU message from the CU, requesting to configure Al functionality 1 for the UE.

[0095] Fig. 7 illustrates an example method 700, which can be implemented by a DU. The method 700 begins at block 712, where the DU transmits a DU-to-CU message to a CU, requesting to configure Al functionality applicability reporting for a UE or configure Al functionality' 1 for the UE. At block 714, the DU receives a CU-to-DU message from the CU, rejecting to configure Al functionality applicability reporting for the UE or configure the Al functionality 1 for the UE.

[0096] In some implementations, the CU rejects to configure Al functionality applicability reporting for the UE because the CU does not support Al functionality applicability reporting configuration or the Al functionality 1. In other implementations, the CU rejects to configure Al functionality applicability reporting for the UE because the UE does not support the Al functionality applicability reporting or the Al functionality 1. In some implementations, the CU rejects to configure the Al functionality 1 for the UE because the UE does not support the Al functionality 1.

[0097] Fig. 8A illustrates an example method 800A, which can be implemented by a DU. The method 800A begins at block 815, where the DU receives a CU-to-DU message from a CU, requesting to configure Al functionality’ 1 for a UE. At block 868, the DU transmits a DU-to-CU message to the CU, rejecting to configure the Al functionality 1 for the UE.

[0098] Fig.8B is a flow diagram of an example method 800B similar to the method 800A, except that the method 800B includes blocks 866 and 616. At block 866, the DU determines whether the DU supports configuring the Al functionality 1. If the DU supports configuringDockctNo.: G114380 10160WOthe Al functionality 1 (“Yes” branch of block 866), the flow proceeds to block 616 described for Fig. 6A. Otherwise, if the DU does not support configuring the Al functionality 1 (“No” branch of block 866), the flow proceeds to block 868.

[0099] Fig. 9 illustrates an example method 900, which can be implemented by a CU. The method 900 begins at block 902, where the CU receives a DU-to-CU message from a DU, indicating that the DU supports Al functionalities 1, ... , M. M is an integer larger than zero. The flow proceeds to block 904 or block 906. At block 904, the CU receives UE capabilities of a UE from a network node, indicating a UE supports Al functionalities 1. . N. N is a positive integer and N >M. At block 906, the CU receives UE capabilities of a UE from a network node, indicating a UE supports Al functionalities 1, ... , N. At block 908, the CU transmits a CU-to-DU message to the DU. including the UE capabilities indicating the UE supports Al functionalities 1 N. At block 915, the CU transmits a CU-to-DU message to the DU, requesting to configure the Al functionality 1 for a UE. At block 916, the CU receives a DU-to-CU message including a first configuration from the DU, where the first configuration configures the Al functionality 1. At block 912, the CU receives a DU-to-CU message from the DU, causing the CU to transmit an Al functionality applicability reporting configuration to the UE. At block 918, the CU transmits the first configuration and / or the Al functionality applicability reporting configuration to the UE. At block 922, the CU receives a first Al functionality applicability report from the UE, indicating that the Al functionality 1 is applicable for the UE. The flow proceeds to block 924 or block 927. At block 924, the CU transmits a CU-to-DU message to the DU, including the first Al functionality applicability report. At block 927, the CU transmits a CU-to-DU message to the DU, indicating to activate the Al functionality 1. At block 934, the CU receives a DU-to-CU message from the DU, indicating the Al functionality 1 is activated.

[0100] Fig. 10 illustrates an example method 1012, which can be implemented by a CU. The method 1000 begins at block 1012, where the CU receives a DU-to-CU message from a DU, requesting to configure Al functionality applicability reporting for a UE or configure Al functionality 1 for the UE. At block 1014, the CU transmits a CU-to-DU message to the DU, rejecting to configure Al functionality applicability reporting for the UE or configure the Al functionality 1 for the UE.

[0101] Fig. 11 A illustrates an example method 1100A, which can be implemented by a CU. The method 1100A begins at block 1115, where the CU transmits a CU-to-DU message to a DU, requesting to configure Al functionality 1 for a UE. At block 1168. the CU receives a DU-to-CU message from the DU, rejecting to configure the Al functionality 1 for the UE.DockctNo.: G114380 10160WO

[0102] Fig.1 IB illustrates an example method 1100B, which can be implemented by a CU.The method 1100B begins at block 1105, where the CU receives UE capabilities of a UE. At block 1180, the CU determines whether the UE capabilities indicate that the UE supports Al functionality 1. If the UE capabilities indicate that the UE supports Al functionality 1 ("Yes" branch of block 1180), the flow proceeds to block 1115. At block 1115, the CU transmits a CU-to-DU message to a DU, requesting to configure the Al functionality 1 for a UE. Otherwise, if the UE capabilities do not indicate that the UE supports Al functionality 1 (“No branch of block 1180), the flow proceeds to block 1170, where the flow ends.

[0103] In some implementations, the CU receives a DU-to-CU message in response to the CU-to-DU message. In one implementation, the DU-to-CU message is as described for block 1168. In another implementations, the DU-to-CU message includes a first configuration configuring the Al functionality 1 as described for event 316.

[0104] Fig. 12A illustrates an example method 1200A, which can be implemented by a CU. The method 1200A begins at block 1218 A, where the CU transmits, toaUE, a first DL message configuring the UE to report whether a first Al functionality is applicable. At block 1222 A, the CU receives, from the UE, a first Al functionality applicability report, where the first Al functionality applicability report indicates the first Al functionality' is applicable. At block 1224, the CU transmits the first Al functionality applicability report to a DU. At block 1236, the CU receives, from the UE, a second Al functionality applicability report, where the second Al functionality applicability report indicates the first Al functionality is not applicable. At block 1248, the CU transmits the second Al functionality applicability report to the DU.

[0105] In some implementations, the CU receives a first UL message including the first Al functionality applicability' report from the UE. In one implementation, the CU retrieves the first Al functionality applicability report from the first UL message and transmits the first Al functionality applicability report to the DU. In another implementation, the CU transmits the first UL message to the DU and the DU retrieves the first Al functionality applicability report from the first UL message. In some implementations, the CU receives a second UL message including the second Al functionality’ applicability report from the UE. In one implementation, the CU retrieves the second Al functionality applicability report from the second UL message and transmits the second Al functionality applicability report to the DU. In another implementation, the CU transmits the second UL message to the DU and the DU retrieves the second Al functionality applicability report from the second UL message.

[0106] Fig.l2B is a flow diagram of an example method 1200B similar to the method 1200A, except that the method 1200B includes blocks 1218B and 1222B instead of blocks 1218A andDockctNo.: G114380 10160WO1222A. At block 1218B, the CU transmits, to a UE, a first DL message configuring the UE to report whether any Al functionality is applicable. At block 1222B. the CU receives, from the UE, a first Al functionality applicability report, where the first Al functionality applicability report indicates a first Al functionality is applicable.

[0107] Fig.12C is a flow diagram of an example method 1200C similar to the method 1200A, except that the method 1200C includes blocks 1227 and 1241 instead of blocks 1224 and 1248. At block 1227, the CU transmits a CU-to-DU message to a DU, requesting or indicating to activate the first Al functionality. At block 1241, the CU transmits a CU-to-DU message to the DU, requesting or indicating to deactivate the first Al functionality.

[0108] Fig.l2D is a flow diagram of an example method 1200D similar to the methods 1200A-1200C. except that the method 1200D includes blocks 1227 and 1241 instead of blocks 1224 and 1248.

[0109] Fig. 13 A illustrates an example method 1300 A, which can be implemented by an RAN node (e.g., a DU, CU, or base station). The method 1300 A begins at block 1322, where the RAN node receives a first Al functionality applicability report, where the first Al functionality applicability report indicates a first Al functionality’ is applicable for a UE (e.g. event 322 or 324). At block 1376, the RAN node determines whether the UE is configured with the first Al functionality7. If the UE is configured with the first Al functionality (“Yes” branch of block 1376), the flow proceeds to block 1328. At block 1328. the RAN node transmits an activation command to the UE, activating the first Al functionality. Otherwise, if the UE is not configured with the first Al functionality (“No branch of block 1376), the flow proceeds to block 1378. At block 1378, the RAN node discards the first Al functionality applicability report.

[0110] Fig.l3B is a flow diagram of an example method 1300B similar to the method 1300A, except that the method 1300B includes block 1316 instead of block 1328. If the UE is configured with the first Al functionality (“Yes” branch of block 1376), the flow proceeds to block 1316. At block 1316, the RAN node transmits a first configuration configuring the first Al functionality.

[0111] Fig. 14A illustrates an example method 1400 A, which can be implemented by an RAN node (e.g., a DU, CU, or base station). The method 1400 A begins at block 1438, where the RAN node receives a first Al functionality applicability report, where the first Al functionality applicability report indicates a first Al functionality is not applicable for a UE (e.g., event 436 or 438). At block 1376. the RAN node determines whether the UEis configured with the first Al functionality. If the UE is configured with the first Al functionality (“Yes”DockctNo.: G114380 10160WObranch of block 1376), the flow proceeds to block 1442. At block 1442, the RAN node transmits a deactivation command to the UE, deactivating the first Al functionality. Otherwise, if the UE is not configured with the first Al functionality (‘"No” branch of block 1376), the flow proceeds to block 1378.

[0112] Fig.14B is a flow diagram of an example method 1400B similar to the method 1400A, except that the method 1400B includes block 1456 instead of block 1442. If the UE is configured with the first Al functionality ("Yes” branch of block 1376), the flow proceeds to block 1456. At block 1456, the RAN node transmits a first release configuration configuring the UE to release the first Al functionality.

[0113] Fig. 15A illustrates an example method 1500 A, which can be implemented by a UE. The method 1500A begins at block 1518A, where the UE receives, from a RAN, a first DL message configuring the UE to report whether a first Al functionality is applicable. At block 1520A, the UE evaluates whether the first Al functionality is applicable. At block 1522A, the UE transmits, to the RAN, a first Al functionality7applicability7report, where the first Al functionality applicability report indicates the first Al functionality is applicable. At block 1536, the UE transmits, to the RAN, a second Al functionality applicability report, where the second Al functionality applicability report indicates the first Al functionality is not applicable. At block 1560 A, the UE receives, from the RAN, a second DL message configuring the UE to stop reporting whether the first Al functionality is applicable. At block 1564A, the UE stops evaluating whether the first Al functionality is applicable.

[0114] Fig. 15B is a flow diagram of an example method 1500B similar to the method 1500A, except that the method 1500B includes block 1518B, 1520B, 1522B, 1560B, and 1564B instead of blocks 1518A, 1520A, 1522A, 1560A, and 1564A. At block 1518B, the UE receives, from a RAN, a first DL message configuring the UE to report whether any Al functionality is applicable. At block 1520B, the UE evaluates whether any Al functionality supported by7the UE is applicable. At block 1522B, the UE transmits, to the RAN, a first Al functionality applicability7report, where the first Al functionality7applicability7report indicates a first Al functionality is applicable. At block 1560B, the UE receives, from a RAN, a second DL message configuring the UE to stop reporting whether any Al functionality is applicable. At block 1564B, the UE stops evaluating whether any7Al functionality supported by the UE is applicable.

[0115] Fig. 15C is a flow diagram of an example method 1500C similar to the method 1500A. except that the method 1500C includes blocks 1518C and 1560C instead of block 1560A. At block 1518C, the UE receives, from a RAN, a third DL message configuring theDockctNo.: G114380 10160WOfirst Al functionality. At block 1560C, the UE receives, from a RAN, a second DL message configuring the UE to release the first Al functionality’.

[0116] Fig. 15D is a flow diagram of an example method 1500D similar to the methods 1500A-1500C.

[0117] Fig. 16 illustrates an example method 1600, which can be implemented by a UE. The method 1600 begins at block 1618, where the UE receives, from a RAN, a first DE message including an Al functionality applicability reporting configuration configuring the UE to report whether a first Al functionality is applicable. At block 1676, the UE determines whether the UE is configured with the first Al functionality. If the UE is configured with the first Al functionality ("Yes" branch of block 1676), the flow proceeds to blocks 1520A and 1522A and may proceed to block 1536. Otherwise, if the UE is not configured with the first Al functionality ’No” branch of block 1676), the flow proceeds to block 1678. At block 1678, the UE ignores or discards the Al functionality applicability reporting configuration.

[0118] AUE apparatus 1702, as described in FIG. 17, may perform the method of flowcharts as depicted in Figs. 15A, 15B, 15C. 15D. and 16. The one or more network entities 104, as described in FIG. 18, may perform the method of flowcharts as depicted in Figs. 6A, 6B, 7, 8A, 8B, 9, 10, 11 A, 11B, 12A, 12B, 12C, 12D, 13A, 13B, 14A, and 14B.

[0119] FIG. 17 is a diagram 1700 illustrating an example of a hardware implementation for a UE apparatus 1702. The UE apparatus 1702 may be the UE 102, a component of the UE 102, or may implement UE functionality’. The UE apparatus 1702 may include an application processor 1706, which may have on-chip memory 1706’. In examples, the application processor 1706 may be coupled to a secure digital (SD) card 1708 and / or a display 1710. The application processor 1706 may also be coupled to a sensor(s) module 1712, a power supply 1714, an additional module of memory’ 1716, a camera 1718, and / or other related components.

[0120] The UE apparatus 1702 may further include a wireless baseband processor 1726, which may be referred to as a modem. The yvireless baseband processor 1726 may have on-chip memory 1726'. Along with, and similar to, the application processor 1706, the wireless baseband processor 1726 may also be coupled to the sensor(s) module 1712, the power supply 1714, the additional module of memory 1716, the camera 1718, and / or other related components. The wireless baseband processor 1726 may be additionally coupled to one or more subscriber identity module (SIM) card(s) 1720 and / or one or more transceivers 1730 (e.g., wireless RF transceivers).

[0121] Within the one or more transceivers 1730. the UE apparatus 1702 may include a Bluetooth module 1732, a WLAN module 1734, an SPS module 1736 (e.g., GNSS module),DockctNo.: G114380 10160WOand / or a cellular module 1738. The Bluetooth module 1732, the WLAN module 1734, the SPS module 1736, and the cellular module 1738 may each include an on-chip transceiver (TRX), or in some cases, just a transmitter (TX) or just a receiver (RX). The Bluetooth module 1732, the WLAN module 1734, the SPS module 1736, and the cellular module 1738 may each include dedicated antennas and / or utilize antennas 1740 for communication with one or more other nodes. For example, the UE apparatus 1702 can communicate through the transceiver(s) 1730 via the antennas 1740 with another UE (e.g., sidelink communication) and / or with a network entity 104 (e.g., uplink / downlink communication), where the network entity 104 may correspond to a base station or a unit of the base station, such as the radio unit (RU) 178, the DU 174, or the CU 172.

[0122] The wireless baseband processor 1726 and the application processor 1706 may each include a computer-readable medium / memory 1726’, 1706’, respectively. The additional module of memory 1716 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory71726’, 1706’, 1716 may be non-transitory. The wireless baseband processor 1726 and the application processor 1706 may each be responsible for general processing, including execution of software stored on the computer-readable medium / memory 1726’, 1706’, 1716. The software, when executed by the wireless baseband processor 1726 / application processor 1706, causes the wireless baseband processor 1726 / application processor 1706 to perform the various functions described herein. The computer-readable medium / memory may also be used for storing data that is manipulated by the wireless baseband processor 1726 / application processor 1706 when executing the software. The wireless baseband processor 1726 / application processor 1706 may be a component of the UE 102. The UE apparatus 1702 may be a processor chip (e.g., modem and / or application) and include just the wireless baseband processor 1726 and / or the application processor 1706. In other examples, the UE apparatus 1702 may be the entire UE 102 and include the additional modules of the apparatus 1702.

[0123] As discussed, and implemented with respect to Figs. 15A, 15B, 15C, 15D, and 16, the Al functionality component 141 is configured to report whether an Al functionality’ is applicable. The Al functionality component 141 may be within the application processor 1706 (e.g., at 141a), the wireless baseband processor 1726 (e.g., at 140b), or both the application processor 1706 and the wireless baseband processor 1726. The Al functionality’ component 141 a- 141b may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform theDockctNo.: G114380 10160WOstated processes / algorithm, stored within a computer-readable medium for implementation by the one or more processors, or a combination thereof.

[0124] FIG. 18 is a diagram 1800 illustrating an example of a hardware implementation for one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include, or may correspond to, at least one of the RU 178, the DU, 108, or the CU 172. The CU 172 may include a CU processor 1846, which may have on-chip memory 1846’. In some aspects, the CU 172 may further include an additional module of memory 1856 and / or a communications interface 1848, both of which may be coupled to the CU processor 1846. The CU 172 can communicate with the DU 174 through a midhaul link 192, such as an Fl interface between the communications interface 1848 of the CU 172 and a communications interface 1828 of the DU 174.

[0125] The DU 174 may include a DU processor 1826, which may have on-chip memory 1826’ . In some aspects, the DU 174 may further include an additional module of memory 1836 and / or the communications interface 1828, both of which may be coupled to the DU processor 1826. The DU 174 can communicate with the RU 178 through a fronthaul link 190 between the communications interface 1828 of the DU 174 and a communications interface 1808 of the RU 178.

[0126] The RU 178 may include an RU processor 1806, which may have on-chip memory 1806’. In some aspects, the RU 178 may further include an additional module of memory 181 , the communications interface 1808, and one or more transceivers 1830, all of which may be coupled to the RU processor 1806. The RU 178 may further include antennas 1840, which may be coupled to the one or more transceivers 1830, such that the RU 178 can communicate through the one or more transceivers 1830 via the antennas 1840 with the UE 102.

[0127] The on-chip memory 1806’, 1826’, 1846’ and the additional modules of memory 1816, 1836, 1856 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 1806, 1826, 1846 is responsible for general processing, including execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor(s) 1806, 1826, 1846 causes the processor(s) 1806, 1826, 1846 to perform the various functions described herein. The computer-readable medium / memory' may also be used for storing data that is manipulated by the processor(s) 1806, 1826, 1846 when executing the software. In examples, the functionality configuration component 151 may sit at any of the one or more network entities 104, such as at the CU 172; both the CU 172 and the DU 174;DockctNo.: G114380 10160WOeach of the CU 172, the DU 174, and the RU 178; the DU 174; both the DU 174 and the RU 178; orthe RU 178.

[0128] As discussed, and implemented with respect to Figs. 6A, 6B, 7, 8 A, 8B, 9, 10, 11A, 1 IB, 12A, 12B, 12C, 12D, 13A, 13B, 14A, and 14B, the functionality configuration component 151 is configured, in some examples, to: receive, from a CU of a base station, a first message indicating that a UE supports Al functionality; transmit, to the CU, a second message including a first configuration of the Al functionality for the UE; and communicate, with at least one of the CU or the UE, based on the first configuration and the Al functionality. In further examples, the functionality configuration component is configured to: transmit, to a DU of a base station, a first message indicating that a UE supports Al functionality; receive, from the DU, a second message including a first configuration of the Al functionality for the UE; and communicate, with at least one of the DU or the UE, in association with the first configuration and the Al functionality.

[0129] The functionality configuration component 151 may be within one or more processors of the one or more network entities 104, such as the RU processor 1806 (e.g., at 151a), the DU processor 1826 (e.g., at 151b), and / or the CU processor 1846 (e.g., at 151c). The functionality configuration component 151a- 151c may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors 1806, 1826, 1846 configured to perform the stated processes / algorithm. stored within a computer-readable medium for implementation by the one or more processors 1806, 1826, 1846, or a combination thereof.

[0130] The descriptions and example implementations described in an earlier figure can apply to a later figure or vice versa, if applicable.

[0131] The following description may be applied to the description above.

[0132] Generally speaking, description for one of the above figures can apply to another of the above figures. Examples, implementations and methods described above can be combined, if there is no conflict. An event or block described above can be optional or omitted. For example, an event or block with dashed lines in the figures can be optional. The description described from the perspective of the receiving node also applies to the sending node. For example, a description that a receiving node (e.g., DU) receives a message from a sending node (e.g., CU) may be replaced by the sending node sending a message to the receiving node. Similarly, a description that a receiving node (e.g., CU) receives a message from a sending node (e.g., DU) may be replaced by the sending node sending a message to the receiving node.DockctNo.: G114380 10160WO

[0133] In some implementations, “message” is used and can be replaced by “information element (IE)”, and vice versa. In some implementations, “IE” is used and can be replaced by “field”, and vice versa. In some implementations, “configuration” can be replaced by “configurations” or “configuration parameters”, and vice versa. In some implementations, “configures” or “configuring” can be replaced by “enables” or “enabling”. In some implementations, “requests” or “requesting” can be replaced by “indicates” or “indicating”. In some implementations, “indicates” or “indicating” can be replaced by “commands” or “commanding”. In some implementations, the “Al functionality” or “Al functionalities” can be replaced by “AI / ML functionality” or “AI / ML functionalities”. In some implementations, “functionalities” can be replaced by “functionality”.

[0134] A user device in which the techniques of this disclosure can be implemented (e.g, the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an intemet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer- readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0135] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may can be software modules (e.g, code, or machine-readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry7or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logic or circuitry' (e.g, as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g. configured by software) may be driven by cost and time considerations.DockctNo.: G114380 10160WO

[0136] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more special-purpose processors.

[0137] Upon reading this disclosure, those of skill in the art will appreciate still additional and alternative structural and functional designs for handling mobility between base stations through the principles disclosed herein. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the disclosed embodiments are not limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those of ordinary skill in the art, may be made in the arrangement, operation and details of the method and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims.

[0138] The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation.

[0139] Example 1 is a method of wireless communication at a DU of a base station including: receiving, from a CU of the base station, a first message indicating that a UE supports Al functionality; transmitting, to the CU, a second message including a first configuration of the Al functionality for the UE; and communicating, with at least one of the CU or the UE, based on the first configuration and the Al functionality.

[0140] Example 2 may be combined with Example 1 and further includes transmitting, to the CU, a first indication that the DU supports the Al functionality.

[0141] Example 3 may be combined with any of Examples 1-2 and further includes determining a second configuration associated with Al functionality applicability reporting for the UE; and transmitting, to the CU, a third message to configure the Al functionality applicability reporting for the UE.

[0142] Example 4 may be combined with any of Examples 1-3 and further includes determining to configure the first configuration of the Al functionality for the UE.

[0143] Example 5 may be combined with any of Examples 1-4 and further includes receiving, from the CU, a first Al functionality applicability report indicating that the first configuration of the Al functionality is applicable to the UE.

[0144] Example 6 may be combined with any of Examples 1-5 and further includes determining to activate the Al functionality at the UE; and transmitting, to the UE, an activation command that activates the Al functionality.DockctNo.: G114380 10160WO

[0145] Example 7 may be combined with Example 6 and further includes transmitting, to the CU, a fourth message indicating an activation of the Al functionality at the UE.

[0146] Example 8 may be combined with any of Examples 1-2 or 5-7 and further includes receiving, from the CU, a request to configure the first configuration of the Al functionality for the UE, the second message being transmitted, to the CU, based on the request.

[0147] Example 9 may be combined with Example 8 and further includes receiving, from the CU, a fifth message including an activation indication for the Al functionality of the UE; and transmitting, to the UE based on the activation indication, the activation command that activates the Al functionality'.

[0148] Example 10 may be combined with Example 8 and includes that the transmitting the second message and the communicating with the at least one of the CU or the UE is based on the DU accepting the request, and further including: transmitting, to the CU, a rejection to the request to configure the first configuration of the Al functionality for the UE.

[0149] Example 11 may be combined with Example 10 and further includes determining whether the DU supports the first configuration of the Al functionality; and transmitting, to the CU, the rejection to the request when the DU does not support the first configuration of the Al functionality.

[0150] Example 12 may be combined with any of Examples 1-11 and further includes determining to at least one of deactivate or release the first configuration of the Al functionality; and transmitting at least one of: a deactivation command, to the UE. to deactivate the first configuration of the Al functionality, a deactivation indication, to the CU, indicating that the first configuration of the Al functionality for the UE is deactivated, a release request, to the CU, for the Al functionality' applicability reporting for the UE, or a release configuration, to the CU, to release the Al functionality applicability reporting for the UE.

[0151] Example 13 may be combined with Example 12 and further includes receiving, from the CU, a second Al functionality applicability report indicating that the first configuration of the Al functionality is not supported by the UE, and includes that the determining to at least one of deactivate or release the first configuration of the Al functionality is based on the second Al functionality applicability report.

[0152] Example 14 may be combined with any of Examples 1-11 and further includes receiving, from the CU, a deactivation indication to deactivate the first configuration of the Al functionality; and transmitting, to the UE, a deactivation command that deactivates the first configuration.DockctNo.: G114380 10160WO

[0153] Example 15 may be combined with any of Examples 1-11 and further includes receiving, from the CU. a release indication that indicates a release of the Al functionality applicability reporting for the UE; and transmitting, to the CU, a release configuration to release the Al functionality applicability reporting for the UE based on the release indication.

[0154] Example 16 is a method of wireless communication at a CU of a base station including: transmitting, to a DU of the base station, a first message indicating that a UE supports Al functionality; receiving, from the DU, a second message including a first configuration of the Al functionality for the UE; and communicating, with at least one of the DU or the UE, in association with the first configuration and the Al functionality.

[0155] Example 17 may be combined with Example 16 and further includes receiving at least one of a first indication that the DU supports the Al functionality or a second indication that the UE supports the Al functionality.

[0156] Example 18 may be combined with any of Examples 16-17 and further includes receiving, from the DU, a third message to configure Al functionality applicability reporting for the UE.

[0157] Example 19 may be combined with any of Examples 16-18 and further includes transmitting, to the DU, a first Al functionality applicability report indicating that the first configuration of the Al functionality7is applicable to the UE; and receiving, from the DU, a fourth message indicating an activation of the Al functionality at the UE.

[0158] Example 20 may be combined with any of Examples 16- 17 or 19 and further includes transmitting, to the DU, a request to configure the first configuration of the Al functionality for the UE, the second message being received, from the DU, based on the request.

[0159] Example 21 may be combined with any of Examples 16-17 or 19-20 and further includes determining to configure at least one of: the first configuration of the Al functionality for the UE or a second configuration associated with Al functionality applicability reporting for the UE.

[0160] Example 22 may be combined with any of Examples 16-17 or 20-21 and further includes determining to activate the first configuration of the Al functionality7for the UE; and transmitting, to the DU based on the determination, a fifth message including an activation indication for the Al functionality.

[0161] Example 23 may be combined with any of Examples 16-22 and further includes transmitting, to the UE, at least one of the first configuration or the second configuration; and receiving, from the UE, a second Al functionality applicability report indicating whether theDockctNo.: G114380 10160WOfirst configuration of the Al functionality is at least one of: supported by the UE or applicable to the UE.

[0162] Example 24 is an apparatus for wireless communication for implementing a method as in any of Examples 1-23.

[0163] Example 25 is an apparatus for wireless communication including means for implementing a method as in any of Examples 1-23.

[0164] Example 26 is a non-transitory computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of Examples 1-23.

[0165] Example 27 is a computer program product for implementing a method as in any of Examples 1-23.

Claims

DockctNo.: G114380 10160WOCLAIMS WHAT IS CLAIMED IS:

1. A method of wireless communication at a distributed unit, DU, (174) of a base station (106) comprising:receiving (308, 314, 315, 324), from a centralized unit, CU, (172) of the base station (106), a first message indicating that a user equipment, UE, (102) supports artificial intelligence. Al, functionality;transmitting (316), to the CU (172), a second message including a first configuration of the Al functionality for the UE (102); andcommunicating (390. 391). with at least one of the CU (172) or the UE (102), based on the first configuration and the Al functionality.

2. The method of claim 1, further comprising:transmitting (302), to the CU (172), a first indication that the DU (174) supports the Al functionality.

3. The method of any of claims 1-2, further comprising:determining (309) a second configuration associated with Al functionality applicability7reporting for the UE (102); andtransmitting (312). to the CU (172). a third message to configure the Al functionality applicability reporting for the UE (102).

4. The method of any of claims 1-3, further comprising:determining (310) to configure the first configuration of the Al functionality for the UE (102).

5. The method of any of claims 1-4, further comprising:receiving (324), from the CU (172), a first Al functionality applicability report indicating that the first configuration of the Al functionality is applicable to the UE (102).

6. The method of any of claims 1-5, further comprising:determining (326) to activate the Al functionality at the UE (102); and transmitting (328). to the UE (102), an activation command that activates the Al functionality.DockctNo.: G114380 10160WO7. The method of claim 6. further comprising:transmitting (334), to the CU (172), a fourth message indicating an activation of the Al functionality at the UE (102).

8. The method of any of claims 1-2 or 5-7, further comprising:receiving (315), from the CU (172), a request to configure the first configuration of the Al functionality for the UE (102), the second message being transmitted (316), to the CU (172), based on the request.

9. The method of claim 8. further comprising:receiving (327), from the CU (172), a fifth message including an activation indication for the Al functionality' of the UE (102); andtransmitting (328), to the UE (102) based on the activation indication, the activation command that activates the Al functionality.

10. The method of claim 8, wherein the transmitting (316) the second message and the communicating (390, 391) with the at least one of the CU (172) or the UE (102) is based on the DU (174) accepting the request, further comprising:transmitting (868). to the CU (172), a rejection to the request to configure the first configuration of the Al functionality' for the UE (102).

11. The method of claim 10, further comprising:determining (866) whether the DU (174) supports the first configuration of the Al functionality; andtransmitting (868), to the CU (172), the rejection to the request when the DU (174) does not support the first configuration of the Al functionality7.

12. The method of any of claims 1-11, further comprising:determining (440, 550) to at least one of deactivate or release the first configuration of the Al functionality'; andtransmitting at least one of:a deactivation command (442), to the UE (102), to deactivate the first configuration of the Al functionality.DockctNo.: G114380 10160WOa deactivation indication (448), to the CU (172), indicating that the first configuration of the Al functionality for the UE (102) is deactivated,a release request (552), to the CU (172), for the Al functionality applicability reporting for the UE (102), ora release configuration (556), to the CU (172), to release the Al functionality applicability reporting for the UE (102).

13. The method of claim 12, further comprising:receiving (438), from the CU (172), a second Al functionality applicability' report indicating that the first configuration of the Al functionality is not supported by the UE (102), wherein the determining (440, 550) to at least one of deactivate or release the first configuration of the Al functionality is based on the second Al functionality applicability report.

14. The method of any of claims 1-11, further comprising:receiving (441), from the CU (172), a deactivation indication to deactivate the first configuration of the Al functionality; andtransmitting (442), to the UE (102), a deactivation command that deactivates the first configuration.

15. The method of any of claims 1-11, further comprising:receiving (555), from the CU (172), a release indication that indicates a release of the Al functionality applicability reporting for the UE (102); andtransmitting (556), to the CU (172), a release configuration to release the Al functionality applicability reporting for the UE based on the release indication.

16. A method of wireless communication at a centralized unit, CU, (172) of a base station (106) comprising:transmitting (308, 314. 315, 324), to a distributed unit, DU, (174) of the base station ( 106), a first message indicating that a user equipment, UE, ( 102) supports artificial intelligence. Al, functionality;receiving (316), from the DU (174), a second message including a first configuration of the Al functionality for the UE (102); andcommunicating (390, 391), with at least one of the DU (174) or the UE (102), in association with the first configuration and the Al functionality.DockctNo.: G114380 10160WO17. The method of claim 16, further comprising:receiving (302, 304, 306) at least one of a first indication that the DU (174) supports the Al functionality or a second indication that the UE (102) supports the Al functionality.

18. The method of any of claims 16-17, further comprising:receiving (312), from the DU (174), a third message to configure Al functionality applicability reporting for the UE (102).

19. The method of any of claims 16-18, further comprising:transmitting (324), to the DU (174), a first Al functionality applicability report indicating that the first configuration of the Al functionality is applicable to the UE (102); and receiving (334), from the DU (174), a fourth message indicating an activation of the Al functionality at the UE (102).

20. An apparatus for wireless communication comprising a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of claims 1-19.

Images