Functionality applicability determination and reporting

Abstract

A WTRU may send a WTRU capability report to the network indicating support for one or more AIML functionalities. The WTRU may receive a request from the network to report if one or more of the AIML functionalities that the WTRU has indicated in the WTRU capability report are currently applicable. The WTRU may be provided with one or more additional conditions / filters for performing the applicability determination. The WTRU may determine if the functionality is applicable for the indicated network side additional conditions, current WTRU conditions and configurations, and may send the applicability report that contains a list of applicable functionalities and / or a list of non-applicable functionalities, and may include a reason for non-applicability.

Description

FUNCTIONALITY APPLICABILITY DETERMINATION AND REPORTING CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of United States Provisional Patent Application No. 63 / 679,337, filed on August 5, 2024, the entire contents of which are incorporated herein by reference. BACKGROUND

[0002] Mechanisms and frameworks for using AI / ML based approaches at both the air interface level (e.g., CSI-feedback enhancements (e.g., CSI compression), beam management / prediction and WTRU positioning) and network level (e.g., network energy saving, load balancing and mobility) may be specified.

[0003] AI / ML operations are based on models (e.g., neural networks) that have been trained using a substantial amount of data under different scenarios / conditions. The conditions may be wireless transmit / receive unit (WTRU) side conditions (e.g., speed) or network side conditions (e.g., antenna pattern, load, etc.). These may be referred to as “WTRU side additional conditions” and “network side additional conditions,” respectively.

[0004] For a given artificial intelligence / machine learning (AIML) functionality, there may be several models (e.g., each trained / suitable for different network / WTRU side additional conditions).

[0005] Once a model is well trained, it may be deployed (e.g., in a test environment, e.g., test network) for performance testing. Model monitoring may need to be performed even after deployment in a real network, as the current network / WTRU conditions can be different from the scenarios / conditions in which the model was trained / tested. If the model monitoring is shown to provide undesirable WTRU / network performance, a decision may be made to switch to another model, or stop using AI / ML based operations for the concerned function, etc. The performance monitoring may (e.g., also) be used to determine whether a model needs to be retained with new sets of data.

[0006] Model training and monitoring may be performed at the WTRU, at the network, or in collaboration between the two.

[0007] Model training and monitoring may be performed offline or online. SUMMARY

[0008] A wireless transmit / receive unit (WTRU) may be configured to determine and report if an AIML functionality is applicable or not by considering several factors such as model availability,consistency between model training WTRU / network conditions and current WTRU / network conditions, and / or required performance level.

[0009] A WTRU may be configured to monitor and report when a non-applicable AIML functionality becomes applicable (or when an applicable AIML functionality becomes non- applicable), where the configuration may include one or more of: conditions to determine when a functionality becomes applicable or non-applicable (e.g., model availability, consistency between model training conditions and current conditions, and / or required performance level); how often or when the monitoring should be done; and / or when the applicability report is to be sent.

[0010] For example, the WTRU (e.g., a processor thereof) may send a capability report to a network. The capability report may include respective indicators that indicate whether the WTRU supports (e.g., each of) one or more artificial intelligence / machine learning (AIML) functionalities. The WTRU may receive a request to report to the network if at least one of the one or more AIML functionalities indicated in the capability report is (e.g., currently) applicable. The request may include one or more of: an indication of a minimum performance level, or an indication of one or more associated identifiers (IDs) corresponding to a network-side condition. The WTRU may determine, based on one or more conditions, whether a (e.g., each) AIML functionality indicated in the request is currently applicable. The one or more conditions may include a respective model availability associated with the AIML functionality, a respective consistency between model training WTRU conditions associated with the AIML functionality and current WTRU conditions, and / or a respective consistency between model training network conditions associated with the AIML functionality and the one or more network-side conditions. The minimum performance level may include a key performance indicator (KPI) threshold, and the WTRU may determine whether a (e.g., each) AIML functionality indicated in the request meets the KPI threshold.

[0011] The WTRU may send, to the network (e.g., via RRC, MAC CE, and / or UCI), a functionality applicability report that indicates at least one non-applicable AIML functionality and an indication of a reason for non-applicability associated with the at least one non-applicable AIML functionality. The functionality applicability report may include a bitmap. The functionality applicability report may include an indication of one or more applicable AIML functionalities, and / or a priority, a preference, or an expected performance level associated with a (e.g., each) applicable AIML functionality. The indication of the reason for non-applicability associated with the at least one non-applicable AIML functionality may be (e.g., include) one or more of: an indication that a model is not available, an indication that the model is not trained, an indicationthat the model is available and trained but not for a current network-side condition, an indication that the model is available and trained but not for a current WTRU condition, an indication that the a required WTRU configuration or WTRU input is lacking, or an indication that the model is not expected to provide an indicated performance level. The functionality applicability report may further include one or more of: one or more associated IDs corresponding to network-side conditions for which the at least one non-applicable AIML functionality will be applicable, one or more WTRU conditions for which the at least one non-applicable AIML functionality will be applicable, a configuration needed to perform inference with a model for the at least one non- applicable AIML functionality, and / or a performance level that can be achieved for the at least one non-applicable AIML functionality for current WTRU conditions. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG.1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.

[0013] FIG.1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG.1A according to an embodiment.

[0014] FIG.1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG.1A according to an embodiment.

[0015] FIG.1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG.1A according to an embodiment.

[0016] FIG.2 is a flowchart that illustrates an example of reactive applicability reporting. DETAILED DESCRIPTION

[0017] FIG.1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA(OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0018] As shown in FIG.1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a WTRU. Further, any description herein that is described with reference to a UE may be equally applicable to a WTRU (or vice versa). For example, a WTRU may be configured to perform any of the processes or procedures described herein as being performed by a UE (or vice versa).

[0019] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0020] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0021] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0022] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

[0023] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE- Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0024] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).

[0025] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., a eNB and a gNB).

[0026] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0027] The base station 114b in FIG.1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular- based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG.1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0028] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 may provide call control,billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG.1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing a NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0029] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0030] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG.1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0031] FIG.1B is a system diagram illustrating an example WTRU 102. As shown in FIG.1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0032] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller,Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG.1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0033] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0034] Although the transmit / receive element 122 is depicted in FIG.1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0035] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[0036] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0037] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0038] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0039] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0040] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous. The fullduplex radio may include an interference management unit 139 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).

[0041] FIG.1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0042] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0043] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown in FIG.1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0044] The CN 106 shown in FIG.1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0045] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0046] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packetsto / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0047] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0048] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[0049] Although the WTRU is described in FIGS.1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0050] In representative embodiments, the other network 112 may be a WLAN.

[0051] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

[0052] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0053] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0054] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0055] Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. The channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11n, and 802.11ac.802.11af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support Meter Type Control / Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0056] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0057] In the United States, the available frequency bands, which may be used by 802.11ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11ah is 6 MHz to 26 MHz depending on the country code.

[0058] FIG.1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0059] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement CoordinatedMulti-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0060] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0061] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

[0062] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG.1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0063] The CN 115 shown in FIG.1D may include at least one AMF 182a, 182b, at least one UPF 184a,184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part ofthe CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0064] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non- 3GPP access technologies such as WiFi.

[0065] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating WTRU IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

[0066] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0067] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112,which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0068] In view of Figures 1A-1D, and the corresponding description of Figures 1A-1D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0069] Mechanisms and frameworks for using AI / ML based approaches at both the air interface level (e.g., CSI-feedback enhancements (e.g., CSI compression), beam management / prediction and WTRU positioning) and network level (e.g., network energy saving, load balancing and mobility) may be specified.

[0070] AI / ML operations are based on models (e.g., neural networks) that have been trained using a substantial amount of data under different scenarios / conditions. The conditions may be wireless transmit / receive unit (WTRU) side conditions (e.g., speed) or network side conditions (e.g., antenna pattern, load, etc.). These may be referred to as “WTRU side additional conditions” and “network side additional conditions,” respectively.

[0071] For a given artificial intelligence / machine learning (AIML) functionality, there may be several models (e.g., each trained / suitable for different network / WTRU side additional conditions).

[0072] Once a model is well trained, it may be deployed (e.g., in a test environment, e.g., test network) for performance testing. Model monitoring may need to be performed even after deployment in a real network, as the current network / WTRU conditions can be different from the scenarios / conditions in which the model was trained / tested. If the model monitoring is shown to provide undesirable WTRU / network performance, a decision may be made to switch to another model, or stop using AI / ML based operations for the concerned function, etc. The performance monitoring may (e.g., also) be used to determine whether a model needs to be retained with new sets of data.

[0073] Model training and monitoring may be performed at the WTRU, at the network, or in collaboration between the two.

[0074] Model training and monitoring may be performed offline or online.

[0075] A WTRU may communicate its supported AIML functionalities to the network using a WTRU capability reporting. The WTRU capability framework may be used to report (semi)static capabilities of the WTRU that the WTRU may be expected to support (e.g., carriers supported, MIMO / antenna patterns, measurement capabilities, etc.) that are not expected to change frequently after deployment of the WTRU. In the case of AIML, the WTRU may not have all the AIML models it needs for all the functionalities ready upon deployment. That is, changes may happen after WTRU deployment such as the WTRU being provided with new AIML models (e.g., from the WTRU vendor), old models being retrained to support more scenarios / conditions, etc. Thus, the information that the WTRU indicates in the capability report in relation to supported AIML functionalities may inform the network that the WTRU has the hardware / software needed to run a model for such a functionality.

[0076] Thus, even if a WTRU has communicated that it supports a certain functionality, at a given time for that functionality, one of the following may be valid: the WTRU has no model available for that functionality; the WTRU has at least one model available for that functionality, but no model is yet to be trained (e.g., only model structure available and model has no parameters / weights yet); the WTRU has a model available and trained but not for the current WTRU conditions; the WTRU has a model available and trained but not for the current network- side conditions; the WTRU has a model available and trained that is suitable for the current WTRU and network conditions, but some input is missing to do the inference using the model (e.g., configuration for doing the required measurements to be used as an input to the model); and / or the WTRU has a model available and trained that is suitable for the current WTRU and network conditions and also has all the required input / configuration to stat using the model for inference.

[0077] If the network wants to enable the WTRU to use one of the AIML functionalities that the WTRU has indicated that it supports in the capability reporting, then further steps may be needed to determine if the concerned functionalities are applicable at the moment, considering all the aforementioned aspects (e.g., model availability, training level, WTRU / network conditions under which the model is trained, earlier performance, etc.).

[0078] Systems, methods, and instrumentalities are disclosed herein for a WTRU being configured / enabled to determine the applicability of AIML functionalities and signal applicability information / report to the network in an efficient / dynamic manner. One or more of the methods disclosed herein may be performed by a UE and / or a WTRU (e.g., via a processor thereof).

[0079] Reactive reporting of functionality applicability may be performed. A WTRU may be configured to determine and report if an AIML functionality is applicable or not by considering several factors such as model availability, consistency between model training WTRU / network conditions and current WTRU / network conditions and / or required performance level.

[0080] A WTRU may perform one or more of the following. The WTRU may send a WTRU capability report to the network indicating support for one or more AIML functionalities. The WTRU may receive a request from the network to report if one or more of the AIML functionalities that the WTRU has indicated in the WTRU capability report are currently applicable. The WTRU may be provided with one or more additional conditions / filters for performing the applicability determination, including but not limited to: an indication of the network side configuration / conditions (e.g., associated ID) in the request or before the request (e.g., one or more associated IDs), and / or a minimum performance level for the functionality to be considered applicable (e.g., a KPI threshold). The WTRU may determine if the functionality is applicable for the indicated network side additional conditions, current WTRU conditions and configurations, and may send a functionality applicability report that contains one or more of the following: a list of applicable functionalities (e.g., among the requested ones) and / or a list of non-applicable functionalities, and may include (e.g., an indication of) a reason for non- applicability. For example, the list of applicable functionalities may include a priority / preference (e.g., if there are multiple sub-functionalities or models with different complexity / requirements etc.) associated with each functionality. The list of applicable functionalities may include an expected performance associated with each functionality. The reason for non-applicability may include, for example, model not available; model not trained; model available and trained but not for the current network-side condition; model available and trained but not for the current WTRU conditions; model available and trained for the current WTRU and network conditions, but required WTRU configuration / input to do the inference using the model is lacking (e.g., Set A / B configuration for beam management); and / or model available and trained, and inference configuration available, but not expected to provide the indicated performance level. For example, the WTRU may include an indication that a model is not available, an indication that the model is not trained, an indication that the model is available and trained but not for a current network condition, an indication that the model is available and trained but not for a current WTRU condition, an indication that the a required WTRU configuration or WTRU input is lacking, and / or an indication that the model is not expected to provide an indicated performance level in the functionality applicability report.

[0081] Proactive reporting of functionality applicability may be performed. A WTRU may be configured to monitor and report when a non-applicable AIML functionality becomes applicable (or when an applicable AIML functionality becomes non-applicable), where the configuration includes one or more of: conditions to determine when a functionality becomes applicable or non-applicable (e.g., model availability, consistency between model training conditions and current conditions, and required performance level); how often or when the monitoring should be done; and / or when the applicability report is to be sent.

[0082] A WTRU may perform one or more of the following. The WTRU may send a WTRU capability report to the network indicating support for one or more AIML functionalities. The WTRU may receive a request from the network to monitor and report when / if one or more of AIML functionalities one or more AIML functionalities (e.g., previously indicated in a WTRU capability report, functionalities that are currently activated / configured, etc.) become applicable or non-applicable. The WTRU may be provided with additional conditions / filters, for example including an indication of the network side configuration / conditions (e.g., associated ID) in the request or before the request (e.g., one or more associated IDs); a minimum performance level for the functionality to be considered applicable (e.g., some KPI threshold); a monitoring / reporting periodicity (regular or some on / off pattern); and / or additional monitoring / reporting conditions / thresholds. The additional monitoring / reporting conditions / thresholds may include for example, WTRU conditions (e.g., monitor only when there is no data activity or data in the buffer, serving cell signal is below / above a threshold, throughput or some other KPI is below / above a threshold, etc.); network conditions (e.g., reception of a paging / SIB indication, detection of change of associated ID, etc.); time to trigger (e.g., duration of time the functionality is applicable or non-applicable continuously, number of instances the functionality is determined to be applicable or non-applicable within a given duration or consecutively, etc.); logging configuration (e.g., log time / location / measurements when a functionality becomes applicable / non-applicable rather than report immediately, and further conditions when to send the logged information, e.g., total time logged, number of records logged, size of log, etc.); and / or other conditions (e.g., when a certain number of functionalities become applicable / non-applicable, etc.). The WTRU may monitor the applicability / non- applicability of the indicated functionalities (based on the monitoring configuration). The WTRU may send an applicability / non-applicability report or log the report (based on the reporting configuration). The reported / logged information may contain details (e.g., as in the reactive case). If logging was configured, the logged info can be sent upon explicit network request orbased on further reporting conditions (e.g., total time logged, total number of records, log size, etc.).

[0083] The terms “artificial intelligence / machine learning,” “AI / ML,” and “AIML” may be used interchangeably herein, where each may refer to artificial intelligence / machine learning.

[0084] The terms “data”, “measurements”, “report” and “results” may be used interchangeably herein.

[0085] The terms “starting conditions” and “validity conditions” may be used interchangeably herein.

[0086] The terms “indication,” “information,” and “message” may be used interchangeably herein.

[0087] The terms “AIML functionality applicability determination”, “functionality applicability determination,” and “applicability determination” may be used interchangeably herein.

[0088] Some of the AIML functionalities described herein, such as beam management and AIML based mobility, are just illustrative examples, and by no means limiting to the solutions described herein (e.g., the proposed applicability determination and reporting can be used for any AIML functionality to be defined / standardized in the future). The proposed solutions are also equally valid to any other form of functionality that uses prediction that is not based on AIML (e.g., time series forecasting, interpolation methods, etc.).

[0089] The solutions described herein may be agnostic to the kind of AIML model / technique used by the WTRU (e.g., the algorithm used, the mechanism such as neural network or what kind of neural network, e.g., depth and parameters / weights of the network, etc.), the origins of the model (e.g., WTRU vendor, operator, network vendor, etc.), and / or how / where the training of the model is done (e.g., the input data used for the training, where the training is performed, if the training is performed offline or online, etc.). The model may be trained based on historical observation of one or more WTRUs’ actual measurements in different WTRU and network conditions (e.g., during certain time durations of the day, during certain days of the week, at different locations, different WTRU mobility patterns / speeds, under different network conditions that are visible to the WTRU such as frequency / bandwidth, etc., under different network configurations, which may be visible to the WTRU just as a network configuration index that is provided by the network at the time of training or data collection for the training, etc.).

[0090] It may be assumed that there is some WTRU capability communication between the WTRU and the network about AIML capability (e.g., where the WTRU can indicate to the network the supported AIML models / functions, confidence level of predictions, time horizon of predictions (how far along in the future are the prediction being made), etc.).

[0091] It may be assumed that the WTRU may support several AIML models for a certain functionality (e.g., with different prediction time horizons, prediction confidence levels, processing requirements, trained under / for operation in different frequencies / cells / location / times of day, etc.).

[0092] It may be assumed that a given AIML model can operate in different modes (e.g., with different levels of prediction confidence levels at different prediction time horizons, at different locations, frequencies, WTRU mobility pattern / speed, etc.).

[0093] It may be assumed that the WTRU may choose the AIML model to use for a certain functionality (e.g., network decides for which functionalities the WTRU can use AIML based operation, and the WTRU chooses the AIML model to use) or the network may explicitly control this (e.g., WTRU provides details of AIML models and their capabilities, network determines which model to activate for a particular functionality).

[0094] It may be assumed that the AIML models can be available at the WTRU already trained, or the WTRU may be provided with an untrained AIML model and performs the training by itself.

[0095] It may be assumed that the AIML model is available at the WTRU already trained, and the WTRU may be enabled / configured to perform further training (e.g., for different conditions such as frequencies / cells / location / times of day, for the same conditions as the initial training but for increasing the level of confidence or / and the prediction time horizon, for different WTRU speeds, etc.).

[0096] It may be assumed that the AIML model is available at the WTRU but not trained at all or only trained for certain WTRU / network conditions, and WTRU may be configured to train the model (e.g. for the conditions that it is not trained for).

[0097] In some cases, the WTRU may require some configurations / inputs that it needs for performing the inference using an AIML model. For example, for beam management prediction, the WTRU may need to be configured with a certain number of beams to measure to predict other beams (this may be referred to as set A / B configuration, where A is the set of predicted beams and B is the set of measured beams). In some cases, the WTRU may communicate the required configuration / input as part of the capability information. In other cases, the required configuration / input may be communicated to the network after capability request (e.g., based on explicit network request, if the WTRU gets configured to do AIML based operations and it has determined that it is lacking the required configuration / input, etc.).

[0098] A given AIML functionality may be associated with a set of KPIs (Key Performance Indicators) or metrics. For example, this may include prediction accuracy, and / or average or mean square difference between measured and predicted values etc. (e.g., for the beamprediction, these could be the beam prediction accuracy or / and confidence level, L1 RSRP difference between the measured and predicted beam signal levels, etc.). A WTRU may have one or more AIML models for a given functionality, and a (e.g., each) model may have performance levels that meet different KPI thresholds (e.g., the WTRU may have 2 models, where one has an accuracy level of 90% and another one with an accuracy level of 95%, etc.) and it may inform the network during its capability reporting or after the capability reporting.

[0099] A given AIML model may be trained under certain WTRU and network conditions. For example, a WTRU condition could be the speed of the WTRU. On the other hand, network conditions could be something that may be related to some network configurations / settings that the WTRU may not be aware of but may impact the performance of the model. For example, an AIML beam management model may perform differently if it is trained when the network was using a certain antenna pattern, beam pattern, power levels, and so on. Also, there may be aspects related to network load, that may have an impact on the model performance. Since the WTRU doesn’t necessarily need to know all these (and network may also not want to expose some of these implementation), the network may hide these details by signaling to the WTRU a network configuration index or associated ID. For example, when data is being collected for training a model, tagging may be performed indicating under which network conditions the model is being trained. When a WTRU is being configured to perform an AIML operation, it may be configured to check the consistency between the conditions under which the AIML model is trained on and current conditions (e.g., current WTRU conditions, current associated ID signaled by the network indicating current network conditions / settings, etc.).

[0100] The term “life cycle management” (LCM) may be used to describe the overall management aspects of AI / ML models, which may include, for example: model training; functionality / model identification; model delivery / transfer; model inference operation; functionality / model selection, activation, deactivation, switching, and fallback operation (e.g., including: Decision by the network (either network initiated or WTRU-initiated and requested to the network), decision by the WTRU (event-triggered as configured by the network, WTRU’s decision reported to the network, or WTRU-autonomous either with WTRU’s decision reported to the network or without it); functionality / model monitoring; model update, WTRU capability; and / or data collection (e.g., for model training, monitoring, inference, etc.).

[0101] LCM may be functionality-based LCM or model-ID based LCM.

[0102] In functionality-based LCM, the network may indicate activation / deactivation / fallback / switching of AI / ML functionality via 3GPP signaling (e.g., RRC, MAC-CE, DCI, etc.). Models may not be identified at the network, and WTRU may performmodel-level LCM. The WTRU may have one AI / ML model for the functionality, or the WTRU may have multiple AI / ML models for the functionality.

[0103] In model-ID-based LCM, models may be identified at the network, and the network / WTRU may activate / deactivate / select / switch individual AI / ML models via model ID.

[0104] One or more of the solutions described herein may be focused on functionality-based applicability determination. However, one or more (e.g., all) of the solutions may be reused for model level applicability determination. For example, if model ID based LCM is being used, the WTRU may communicate model level details in the capability or subsequent assistance information after WTRU capability reporting. Similar to the functionality-based LCM, the network may request the WTRU for model ID based applicability determination, and the WTRU may provide a detailed report of applicability or non-applicability at model level.

[0105] A WTRU may indicate an AIML capability. For example, a WTRU may indicate to the network that it is capable of AIML operations.

[0106] The granularity of the capability indication may be at a use case or functionality level (e.g., beam management, positioning, mobility, etc.), a sub-use or sub-functionality level (e.g., spatial beam management, WTRU assisted positioning, RRM measurement prediction, etc.), and / or at a model level. For example, the WTRU can indicate that it has a certain number of models for a given AIML functionality, or it may even include detailed information about each model (e.g., model identities, model capabilities, model inference configuration requirements, etc.).

[0107] The WTRU may indicate the functionalities at a higher granular level (e.g., beam management).

[0108] The WTRU may indicate the supported functionalities in more detail in the capability information. For example, for beam management / prediction, the capability may include one or more of the following: a beam prediction type, which may be a temporal prediction (e.g., prediction of the signal level of a beam at a future time instance based on, e.g., current and historical signal levels of the beam) and / or a spatial prediction (e.g., prediction of the signal level of one beam based on the signal level of another beam, e.g., beam of the same cell, beam of a different cell, etc.); a number of beams that can be predicted; a number of beams that need to be measured to do the predictions; a confidence level of the predictions; and / or conditions under which the AIML functionality / models can operate at (e.g., the models / functionality were trained under the indicated conditions, where the performance of the models / functionality has been tested and shown to work properly, etc.), where the conditions may include WTRU and / ornetwork conditions (e.g., WTRU mobility state, WTRU location, cells / frequencies, time of day, network configuration index, etc.).

[0109] The capability may be provided at a functionality level (e.g., WTRU not explicitly indicating the number / identity of the models it is using, but simply providing the overall capability of the one or more models for the beam prediction capability), and / or it may be at a model level (e.g., WTRU providing explicit information about each model it has for the beam prediction functionality and associated capability information for each model).

[0110] The capability information may be provided autonomously by the WTRU (e.g., upon connection setup / resume, upon handover, upon detecting that the WTRU has entered a new cell / region / RAT where the capability regarding beam prediction is different from previously reported capability, etc.) or based on an explicit request from the network.

[0111] If capability information is requested from the network, the request may be a generic request (e.g., in which case WTRU may provide all its capabilities), or it may be a more granular request. For example, the WTRU may receive a request from the network if it supports beam prediction at a certain frequency layer, and the WTRU may respond with one or more of the following: an indication that it does not support beam prediction at a certain frequency layer; and / or an indication that it supports beam prediction at a certain frequency layer and / or detailed information about the capability regarding prediction of beam at the frequency layer (e.g., summarized information at functionality level, detailed information for each AIML model that supported beam prediction at that frequency layer, etc.).

[0112] One or more of the solutions provided herein may be applicable to both reactive and proactive applicability reporting. FIG.2 is a flowchart that illustrates an example of reactive applicability reporting.

[0113] As shown in FIG.2, at 202, a WTRU may transmit a capability report to a network. The capability report may include indicator(s) that indicate whether the WTRU supports one or more AIML functionalities. At 204, the network may send, and the WTRU may receive, a request regarding the applicability of an (e.g., one or more) AIML functionality (e.g., at least one AIML functionality indicated in the capability report).

[0114] The request may be an immediate request (e.g., WTRU determines the applicability, as described herein, and sends a report). Herein, this may be referred to as “reactive applicability determination / reporting.”

[0115] The request may be a proactive / monitoring request (e.g., the WTRU may monitor the applicability, as described herein, and may send a report when / if a functionality becomes applicable or not). Herein, this is referred to as “proactive applicability determination / reporting.”

[0116] The request may be a combination of reactive and proactive applicability determination / reporting. The WTRU may check immediately if a functionality is applicable and, if so, reports immediately. Otherwise, it may start monitoring the applicability and reports when / if the functionality becomes applicable.

[0117] The request may be a dedicated message to the WTRU (e.g., an RRC message, MAC CE, DCI, etc.), a broadcast message (e.g., an information element in a system information block (SIB)), a groupcast message to a subset of WTRUs, and / or a paging message to one or more WTRUs (e.g., a paging RNTI, a group paging RNTI, etc.).

[0118] The request may be regarding one or more (e.g., all) AIML functionalities (e.g., all the AIML functionalities that a WTRU has previously indicated in a capability report). For example, the request may include the list of AIML functionalities to be considered in the applicability determination by the WTRU. In another example, the request may include the list of AIML functionalities that should not be considered in the applicability determination by the WTRU (e.g., all other functionalities that are not included will be considered).

[0119] The request may indicate a set of functionalities regarding which the WTRU should (e.g., must) perform reactive reporting and a set of functionalities for which the WTRU should (e.g., must) perform proactive reporting (e.g., one single message to configure reactive reporting for some functionalities and proactive reporting for others).

[0120] If an AIML functionality has sub-functionalities, the inclusion of the functionality in the request may implicitly indicate to the WTRU that the request is concerning one or more (e.g., all) of the sub-functionalities under the functionality. For example, if beam management was indicated, the WTRU may consider the request to be concerning beam management functionalities such as spatial beam management, temporal beam management, etc.

[0121] The AIML functionalities whose applicability is to be checked may be signaled to the WTRU prior to the applicability request message (e.g., separate dedicated message, a broadcast / groupcast message, etc.).

[0122] The AIML functionalities whose applicability is to be checked may be functionalities that the WTRU previously has indicated as non-applicable (e.g., as a response to a previous applicability request from the network).

[0123] The AIML functionalities whose applicability is to be checked may be functionalities that the WTRU previously has indicated as non-applicable (e.g., as a response to a previous applicability request from the network) and / or functionalities that the WTRU previously has indicated as applicable (e.g., as a response to a previous applicability request from the network).

[0124] Network-side additional conditions to be considered during the applicability determination by the WTRU may be disclosed herein.

[0125] The functionality applicability request from the network may include one or more associated IDs related to network configuration that the WTRU should (e.g., needs to) consider in the applicability determination.

[0126] The associated IDs may be included in the request message and / or in a separate message prior to the request message.

[0127] The associated IDs may be common for one or more (e.g., all) functionalities.

[0128] The associated IDs may be specific to a (e.g., each) functionality or a subset of the functionalities. For example, the request (e.g., or the prior message that signalled the associated IDs to the WTRU) may indicate an (e.g., one) associated ID for beam management functionality and another associated ID for positioning, etc.

[0129] The associated IDs for some of the functionalities may be provided in a prior message to the applicability request, while the associated IDs for other functionalities may be provided in the request message.

[0130] Performance-related information may be included in a request. The request for functionality applicability determination may include information related to one or more performance levels / thresholds to be met for a KPI by the AIML functionalities that the WTRU is being requested to determine the applicability.

[0131] The performance level criteria may be regarding a common KPI for all the AIML functionalities that the WTRU needs to check the applicability (e.g., the KPI is prediction accuracy for all the AIML functionalities). The threshold for the KPIs may be the same for one or more (e.g., all) functionalities (e.g., threshold of x% indicated and only functionalities that are expected to provide a performance above x% prediction accuracy to be considered applicable). Different thresholds may be configured for different functionalities (e.g., prediction accuracy of 95% required for positioning functionality but only 90% accuracy sufficient for beam management, etc.).

[0132] The KPI and / or the thresholds (e.g., both) may be different for a (e.g., each) AIML functionality for which the WTRU needs to check the applicability (e.g., the KPI may be prediction accuracy for positioning, while for the beam management functionality, it may be an L1 RSRP difference between measured and predicted beams, etc.).

[0133] More than one KPI and associated threshold may be configured for a given functionality. For example, for the beam management functionality, the WTRU may be provided with thisconfiguration: KPI 1 – beam prediction accuracy, threshold 1; KPI2 – L1-RSRP difference between measured and predicted beams, threshold 2; etc.

[0134] The performance level(s) to be checked may be signalled to the WTRU prior to the applicability determination request (e.g., in a separate dedicated or broadcasted message, a minimum requirement for a functionality to be considered applicable, etc.).

[0135] If the performance levels(s) are included in the request message and also have been configured prior to the reception of the request message, the WTRU may be configured to consider (e.g., only) the ones in the request message (e.g., the information in the request message overrides the previous ones the WTRU has been provided with).

[0136] If the performance levels(s) are included in the request message and also have been configured prior to the reception of the request message, the WTRU may be configured to consider a union of the two, assuming they are not referring to the same metric (e.g., if, in the request message, performance level related to beam accuracy is provided while in the previous message performance level related to L1 RSRP difference was provided, the WTRU may consider both).

[0137] The WTRU may perform one or more actions upon the reception of a functionality applicability request. For example, as shown in FIG.2 at 206, the WTRU, upon the reception of a request for AIML functionality applicability determination / reporting according to any of the solutions described herein, may determine if the concerned functionalities are currently applicable or not. For example, the WTRU may determine whether an AIML functionality (e.g., each functionality indicated in the request received from the network) is currently applicable based on one or more conditions.

[0138] The WTRU may determine that a functionality is applicable if one or more of the following conditions are fulfilled: there is at least one AIML model for the functionality; and / or there is at least one model that fulfills one or more of the following: the model has been trained for the current WTRU conditions (e.g., WTRU speed); the model has been trained for the indicated network conditions (e.g., the indicated associated ID(s)); and / or the model is expected to perform to the indicated level (according to the one or more indicated performance level thresholds).

[0139] The WTRU may consider a functionality applicable (e.g., only) if all the above criteria are fulfilled, or if (e.g., only) one of the above conditions is fulfilled.

[0140] If the associated IDs are provided prior to the request message and also in the request message, the WTRU may consider the union of the two (e.g., if associated IDs a and b were signaled to the WTRU before the request message, and associated IDs c and d are included inthe request message, WTRU may consider associated IDs a, b, c and d in the applicability determination).

[0141] Alternatively, the associated IDs (e.g., only the associated IDs) that are provided in the request message may be considered in the applicability determination by the WTRU (e.g., even if the WTRU was previously provided with other associated IDs). For example, if associated IDs a and b were signaled to the WTRU before the request message, and associated IDs c and d are included in the request message the WTRU will consider (e.g., only) associated IDs c and d in the applicability determination.

[0142] Upon the reception of a functionality applicability request from the network, the WTRU may acquire the associated ID related information (e.g., the WTRU may acquire the information from a system information block). For example, if the WTRU was not able to find the associated ID information (e.g., network may have temporarily paused the transmission of the information, e.g., for energy saving purposes), the WTRU may trigger the on-demand transmission of the needed system information.

[0143] If more than one associated ID is signalled, the WTRU may consider a given functionality applicable if the functionality is applicable for one or more (e.g., all) of the associated IDs.

[0144] If more than one associated ID is signalled, the WTRU may perform the functionality applicability determination separately for an (e.g., each) associated ID. For example, if associated IDs a, b, and c were signalled and the concerned functionality is beam management, the WTRU may determine if the beam management functionality is applicable for a, b or c separately.

[0145] If more than one KPI is configured for a functionality, the WTRU may consider the functionality applicable if the functionality is expected to deliver performance at a level equal to or better than the indicated performance level thresholds for one or more of (e.g., all) the KPIs.

[0146] If more than one KPI is configured for a functionality, the WTRU may consider the functionality applicable if the functionality fulfills at least one of the configured KPIs.

[0147] If more than one KPI is configured for a functionality, the WTRU may consider the functionality applicable if the functionality fulfills a certain number of, or a certain percentage of, the KPIs.

[0148] An applicability report (e.g., a functionality applicability report) may be used. At 208, after the WTRU performs the applicability determination of the one or more indicated functionalities, it may send an applicability report to the network. The applicability report may indicate at least one non-applicable functionality and / or a reason for non-applicability associated with the non-applicable functionality. The applicability report may additionally indicate at least one applicable functionality.

[0149] The applicability report may be (e.g., part of) an RRC message (e.g., a new RRC message, additional information elements included in an existing RRC message such as RRC Reconfiguration Complete message, etc.), a MAC CE, and / or a UCI.

[0150] The applicability report may be (or include) a bitmap (e.g., a 0 indicating non- applicability, a 1 indicating applicability, or vice versa). For example, the ordering of the bitmap may correspond to the order in which the functionalities were signalled in the request. For example, if the network has signalled to the WTRU to check the applicability of functionalities a, b, c, d, e, and f, and the WTRU has determined that a, b and f are applicable, but c, d and e are not, the bitmap included in the report may be [1,1,0,0,0,1]. Padding 0s or 1s may be included in the bitmap if the bitmap is to be byte aligned.

[0151] The applicability report may include identities of the functionalities that are applicable. For example, the different functionalities may be assigned a local or global ID (e.g., an integer value) (e.g., this may be in the request message or prior to the request message), and the WTRU may include a list of the IDs of the functionalities that are applicable.

[0152] The applicability report may include the identities of the functionalities that are not applicable.

[0153] The identities of both the applicable and non-applicable functionalities may be included. For example, the report may include two lists, one for the applicable and one for the non- applicable ones. Alternatively, the identities of (e.g., only) non-applicable functionalities may be included (e.g., with indication(s) of reason(s) for non-applicability).

[0154] The applicability request message may include an indication whether the WTRU is to report applicable functionalities, non-applicable functionalities, or both.

[0155] If applicable functionalities are to be indicated in the report, and the WTRU has determined that it has more than one sub-functionality that may be applicable for the current WTRU conditions, associated IDs, and indicated performance levels, the WTRU may be configured to include information regarding these sub-functionalities and the WTRU’s preference. For example, if the WTRU was requested to check the applicability of a beam management functionality, and it has determined that it has a spatial beam management model and a temporal beam management model that is currently applicable, it may include that both are applicable, and whether it prefers one or the other (e.g., due to complexity and current WTRU processing levels). For example, the WTRU may be configured to indicate the sub-functionalities using an identity that has been further configured by the network for the different sub-functionalities.

[0156] If an applicable functionality has a performance level better than the threshold indicated in the request (e.g., or prior to the request) by more than a certain configured level, the WTRU may be configured to include that information the applicability report. For example, if the performance level threshold is 75% accuracy and WTRU has determined it has a model for that functionality that can deliver 90% accuracy for the current conditions, the WTRU may indicate that in the report (e.g., the delta from the threshold level, the actual performance level, etc.).

[0157] If non-applicable functionalities are to be indicated in the report, the WTRU may include (e.g., indicate) one or more of the following reasons (e.g., cause values) for non-applicability along with the identity of the functionality: a) no model available for the functionality; b) there is no trained model available for the functionality (e.g., Model structure available, but not trained); c) there is a model available for the functionality and it is trained, but not for the indicated associated ID(s); d) there is a model available for the functionality and it is trained, but not for the current WTRU conditions; e) there is a model available for the functionality and it is trained for the indicated associated ID(s) and current WTRU conditions, but WTRU doesn’t have the required configuration that it needs for using the model for inference (e.g., Set A / B configuration for beam management); and / or f) there is a model available for the functionality and it is trained for the indicated associated ID(s) and current WTRU conditions, and WTRU has the required configuration that it needs for using the model for inference, but the model is not expected to provide the indicated performance level. Other reasons for non-applicability may be included and / or indicated in the functionality applicability report.

[0158] For example, if the WTRU was requested to determine the applicability of three functionalities, with identities 1, 2 and 3, and it has determined that 1 is applicable, but 2 and 3 are not applicable (e.g., #2 due to no model available for the functionality, and #3 due to the WTRU lacking the required configuration that it needs for using the model for inference), the WTRU may include the following in the report: Applicable: {1}; Non-Applicable {[2, a], [3, e]}, where “a” and “e” may indicate the reasons why the functionalities are not applicable. Alternatively, the WTRU may include (e.g., indicate) the following in the report: [2, a], [3, e], where “a” and “e” may indicate the reasons why the functionalities are not applicable.

[0159] An integer value may be assigned to a (e.g., each) cause value, and WTRU may indicate that in the report (e.g., instead of the alphabetical values described herein).

[0160] If a functionality is not applicable, the WTRU may indicate information regarding what may make it applicable. For example, the WTRU may include one or more of the informationcorresponding to each functionality that is being indicated as non-applicable: associated ID(s) for which the functionality will be applicable; WTRU condition(s) for which the functionality will be applicable; a configuration needed to perform the inference with a model for that functionality (e.g., set A / B configuration); and / or performance level that can be achieved for that functionality for the current WTRU conditions and indicated associated ID(s) in the request. The information may be interrelated. For example, the associated ID(s) and WTRU conditions may be provided in pairs (e.g., for associated ID x and WTRU conditions a, b, c, OR associated ID y and WTRU conditions, d, e, and so on).

[0161] If the WTRU was provided with multiple associated IDs, and it was configured to report / determine the applicability separately for each associated ID, it may include multiple entries of applicability and non-applicability corresponding to a (e.g., each) associated ID. For example, if the WTRU was requested to determine and report applicability for functionality #1 and #2 for associated IDs, X, Y and Z, and the WTRU has determined that functionality #2 is applicable for all associated IDs, while functionality #1 is applicable for X but not for Y and Z, and the reason for non-applicability for Y is due to model being not trained for the current WTRU conditions, but for Z, it was due to the performance level being below the threshold, the applicability report the WTRU provides may contain the following information: Associated ID =X a) Applicable: {1, 2} b) Non-applicable: {} Associated ID =Y a) Applicable: {2} b) Non-applicable: {[1,d]} Associated ID =Z a) Applicable: {2} b) Non-applicable: {[1,e]}

[0162] Proactive reporting may be performed.

[0163] As disclosed herein, the WTRU may be configured to do the functionality applicability determination and reporting in a reactive or / and proactive manner. Aspects specific to the proactive reporting configuration and WTRU behavior are described herein.

[0164] Applicability monitoring / reporting periodicity may be described herein.

[0165] The WTRU may be provided with a proactive monitoring periodicity (e.g., X seconds), and the WTRU may perform the applicability determination accordingly (e.g., every X seconds).

[0166] The periodicity may be the same for one or more (e.g., all) of the functionalities for which the WTRU is configured to check the applicability.

[0167] Different periodicities may be configured for different functionalities.

[0168] The WTRU may be provided with a proactive reporting periodicity (e.g., X seconds), and the WTRU may perform the applicability reporting accordingly (e.g., every X seconds). For example, the reporting periodicity may be the same as the monitoring periodicity (e.g., WTRU may do the monitoring every X seconds and if the applicability has changed, it will trigger the report). In another example, the reporting periodicity may be different from the monitoring periodicity. Like the monitoring periodicity, different reporting configurations may be configured for different functionalities.

[0169] WTRU conditions for disabling / relaxing monitoring are disclosed herein.

[0170] The WTRU may be configured with WTRU-related conditions, which may indicate that the WTRU is required to perform proactive applicability determination. The WTRU-related conditions may include one or more of the following: UL or / and DL data activity level (e.g., WTRU configured to check functionality applicability only if the data activity is above / below a certain throughput threshold); UL or / and DL buffer level (e.g., WTRU configured to check functionality applicability only if the UL / DL buffer level is above / below a certain buffer threshold); radio conditions (e.g., WTRU configured to check functionality applicability only if the DL RSRP with one or more of the serving cells is above / below a certain RSRP threshold); and / or any other WTRU conditions (e.g., power headroom level, overheating level, WTRU speed, etc.).

[0171] The configuration related to the WTRU-related conditions and associated thresholds may be the same for one or more (e.g., all) functionalities.

[0172] The WTRU-related conditions to be considered may be the same for one or more (e.g., all) of the functionalities. The thresholds may be the same or different for a (e.g., each) functionality (e.g., perform applicability determination for functionality x if throughput is below y, perform applicability determination of functionality z if throughput is above a, etc.).

[0173] The WTRU-related conditions to be considered may be different for different functionalities (e.g., perform applicability determination for functionality x if throughput is below y, perform applicability determination of functionality z if serving cell radio signal level is above a, etc.).

[0174] The WTRU may be configured with different periodicities for the functionality determination / monitoring depending on one or more of the WTRU conditions described herein (e.g., instead of not performing the applicability determination at all). This may be considered as applicability determination relaxation. For example, WTRU may be configured to do functionalitydetermination every 5 seconds when the UL throughput is below 1Mbps but do it every 10 seconds otherwise. This relaxation configuration may be for one or more (e.g., all) functionalities or specific functionalities. Also, different relaxation configurations may be configured for different functionalities and / or WTRU conditions that are associated with the relaxation (e.g., for functionality x and y, if UL throughput is below 1Mbps, perform the applicability determination every 5 seconds, otherwise, do the functionality determination every 10 seconds for functionality x and every 15 seconds for functionality y, and so on).

[0175] The WTRU may be configured to perform proactive applicability determination / reporting upon detecting a change in WTRU conditions (e.g., WTRU speed). For example, the WTRU may have previously determined / reported that a certain functionality is not applicable and at that time the WTRU speed was X kph, and if the WTRU later detects that that the WTRU speed is Y kph, the WTRU may trigger the applicability determination / reporting. In another example, the WTRU may have previously determined / reported that a certain functionality is applicable and at that time the WTRU speed was X kph, and if later the WTRU detects that that the WTRU speed has changed to Y kph, the WTRU may trigger the applicability determination / reporting. The change in the WTRU conditions may also be configured as a delta (e.g., trigger the applicability determination / reporting if the WTRU buffer level has changed by more than a certain percentage or amount from the last time the WTRU has sent applicability or non-applicability report).

[0176] Network-side additional conditions may be disclosed herein.

[0177] The WTRU may be configured to perform proactive applicability determination / reporting upon detecting a change in associated ID (e.g., as detected by the reception of a dedicated or broadcast message). For example, the WTRU may have previously determined / reported that a certain functionality is not applicable and at that time the associated ID was x, and if the WTRU later detects that the associated ID has changed to y, the WTRU may trigger the applicability determination / reporting. The WTRU may have previously determined / reported that a certain functionality is applicable and at that time the associated ID was x, and if later the WTRU detects that that associated ID has changed to y, the WTRU may trigger the applicability determination / reporting.

[0178] The WTRU may be configured to perform proactive applicability determination / reporting upon detecting certain associated ID(s) (e.g., as detected by the reception of a dedicated or broadcast message). For example, the WTRU may have been configured to trigger the proactive applicability determination / reporting for one or more functionalities if the associated ID becomes one of a set of associated IDs, and upon determining that the current associated ID isnow one of these configured IDs, it may trigger the functionality applicability determination / reporting.

[0179] A time to trigger (TTT) may be considered.

[0180] The WTRU may be configured to consider a time to trigger (TTT), during which a functionality may need to be applicable continuously, before determining that the functionality is applicable. For example, if a TTT value of 10 seconds is configured for a given functionality, the WTRU, upon determining the functionality has become applicable, may monitor the applicability of this functionality for the next 10 seconds and may consider the functionality to be applicable (e.g., only) if the applicability conditions are still fulfilled after that period.

[0181] Different TTT values may be configured for different functionalities, or the same TTT may be configured to be used for all (e.g., or a group of) functionalities.

[0182] The TTT may also be configured to be used to determine if a functionality has become non-applicable. For example, a functionality that has been previously determined to be applicable may be considered non-applicable if the WTRU determines that the applicability conditions were not met for the TTT duration configured for determining non-applicability. The TTT to determine applicability and the TTT to determine non-applicability may be configured to have the same or different values (e.g., if they are different values, they may be configured to be associated with each other, e.g., one being a multiple of the other).

[0183] Instead of or in addition to the TTT value, other parameters may be configured to determine when a functionality is determined to be applicable or non-applicable. Several example solutions are described herein.

[0184] A WTRU may be configured with a threshold (e.g., N1) corresponding to the number of instances that the functionality must be applicable in sequence before it can be considered as applicable for applicable reporting. For example, if the WTRU was configured with applicability determination periodicity of X seconds, then the WTRU may consider the functionality applicable if it has determined that the functionality it was applicable for the next N1*X seconds (e.g., checking N1 times every X seconds). A similar configuration may be made for detecting non-applicability (e.g., N2 consecutive instances, which may have the same or different value from N1) to determine non-applicability.

[0185] A WTRU may be configured with a threshold (e.g., N3) corresponding to the number of instances (e.g., not necessarily consecutive) within a given time duration (T1) that the functionality may (e.g., must) be determined to be applicable before it can be reported as applicable. For example, if the WTRU was configured with applicability determination periodicity of X seconds, then the WTRU may consider the functionality applicable if it has determined thatthe functionality was applicable at least N3 times within the T1 duration (i.e., checking T1 / X times every X seconds, there were at least N3 instances where the functionality was applicable). A similar configuration may be made for detecting non-applicability (e.g., N4 instances of non-applicability, which may have the same or different value from N3, within a given time duration T2, which can be the same or different from T1).

[0186] A WTRU may be configured with one or more (e.g., two) thresholds (e.g., N4, N5) and a (e.g., one) timer value (e.g., T3). When the WTRU determines N4 consecutive instances of non- applicability for a functionality, it may start a timer with a value of T3. If the timer expires before N5 consecutive instances of applicability were detected for the functionality, the functionality may be reported as non-applicable. A similar configuration may be made for detecting applicability (e.g., a certain number of consecutive applicability instances are detected, WTRU will start a timer and unless a certain number of consecutive non-applicability instances are detected in that time, the functionality can be reported as applicable).

[0187] A WTRU may be configured with one or more (e.g., two) thresholds (e.g., N6, N7) and one or more (e.g., two) timer values (e.g., T4, T5). When the WTRU determines N6 instances of non-applicability for a functionality (not necessarily consecutive) within a time duration of T4, the WTRU may start a timer with a value of T5. If the timer expires before N7 (e.g., not necessarily consecutive) instances of applicability were detected for the functionality, the functionality may be reported as non-applicable. A similar configuration may be made for detecting applicability (e.g., a certain number of applicability instances are detected (not necessarily consecutive), the WTRU will start a timer and unless a certain number of non-applicability instances are detected in that time, the functionality can be reported as applicable).

[0188] A logging configuration may be used.

[0189] The WTRU may be configured to keep a log of the applicability determination (e.g., instead of sending an applicability report).

[0190] The WTRU may be configured to make an entry in the log periodically (e.g., every Y seconds). For example, the WTRU may be configured with the same logging periodicity as the applicability determination periodicity (e.g., log every result of the applicability determination). In another example, the WTRU may be configured to log the applicability determination results every Nthdetermination / monitoring period.

[0191] The WTRU may be configured to include additional information such as the time of the day, WTRU location, etc. in the logging report for each entry (e.g., in addition to the indication of applicability / non-applicability, and reason for non-applicability, etc. that are included in the applicability report as disclosed herein).

[0192] The WTRU may be configured to send the logged information upon explicit request from the network.

[0193] The WTRU is configured to send an indication that it has logged information. This, for example, may be triggered due to one or more of the following: when the size of the logged information becomes above a certain threshold (e.g., more than a certain number of logged entries, more than a certain size, e.g., in MBs, etc.); when the WTRU has performed some mobility related action (e.g., after a handover); when the total time the logging has been performed is above a certain time threshold; and / or when the WTRU has traversed more than a certain distance (e.g., in km, in number of cells traversed, in leaving a certain configured RAN area, etc.).

[0194] The WTRU may be configured to send the logged information every applicability reporting periodicity (e.g., WTRU configured to log every X second and to send report every Y seconds, where Y may be a multiple of X).

[0195] The WTRU may be configured to compress / summarize the logged information to be reported instead of sending the raw report. For example, the WTRU maybe configured to report the number of times a functionality has been found to be applicable or non-applicable during the logging duration (e.g., instead of including the details of each logged record).

[0196] Interactions between reactive and proactive applicability reporting may be disclosed herein.

[0197] If the WTRU has reported a functionality to be applicable (via immediate / reactive reporting), it may start monitoring the conditions for the functionality to be considered non- applicable according to any of the solutions described herein. This behaviour may be configured for one or more (e.g., all) functionalities or for specific functionalities.

[0198] If the WTRU has reported a functionality to be non-applicable, it may start monitoring the conditions for the functionality to be considered applicable again according to any of the solutions described herein. This behaviour may be configured for one or more (e.g., all) functionalities or for specific functionalities.

[0199] The proactive applicability determination / reporting configuration may be valid until the WTRU receives a message / indication indicating the release / disabling of the configuration. For example, the WTRU may continue to do the applicability determination and reporting / logging according to the configuration until it receives an indication to release / disable this. This behavior / configuration may be the same for all functionalities or configured (e.g., only) for certain functionalities.

[0200] The WTRU may be provided with a time duration (e.g. Tx) value along with the proactive applicability determination / reporting configuration, which may indicate that the configuration may be valid (e.g., only) for that duration. For example, the WTRU may continue to do the applicability determination and reporting / logging according to the configuration until that time duration has elapsed, but may stop doing so afterwards. This behavior / configuration may be the same for all functionalities or configured (e.g., only) for certain functionalities. Also, if configured for certain functionalities, the time duration value may be different for the different functionalities.

[0201] The WTRU may be provided with a threshold value of the number of times an applicability report should (e.g., must) be sent along with the proactive applicability determination / reporting configuration. For example, if the threshold was set to 2, the WTRU may stop doing the applicability determination / reporting after the WTRU has sent 2 applicability reports that were triggered due to this proactive applicability determination / reporting configuration. This behavior / configuration may be the same for one or more (e.g., all) functionalities or configured (e.g., only) for certain functionalities. Also, if the behavior / configuration is configured for certain functionalities, the threshold value for the maximum number of reporting may be different for the different functionalities.

[0202] The WTRU may be configured with a prohibit timer, indicating the minimum time duration between sending two applicability or non-applicability reports.

[0203] The WTRU may be configured with a maximum number of applicability or non- applicability reports that the WTRU sends in relation to one proactive applicability determination / reporting configuration / request.

[0204] The WTRU may be configured with a maximum time duration for which the proactive applicability determination / reporting configuration / request is considered valid (after the reception of the configuration / request). After that time has elapsed, WTRU may consider the request to be invalid / deactivated, or it may release / delete the configuration.

[0205] The WTRU may be configured to continue performing the proactive applicability determination / reporting until an explicit message is received from the network disabling / releasing the configuration / request.

Claims

CLAIMS:

1. A wireless transmit / receive unit (WTRU) comprising a processor configured to: send, to a network, a capability report, wherein the capability report comprises respective indicators that indicate whether the WTRU supports each of one or more artificial intelligence / machine learning (AIML) functionalities; receive, from the network, a request to report if at least one of the one or more AIML functionalities indicated in the capability report is currently applicable; determine, for each AIML functionality of the at least one of the one or more AIML functionalities, whether the AIML functionality is currently applicable based on one or more conditions; and send, to the network, a functionality applicability report based on the determination, wherein the functionality applicability report indicates at least one non-applicable AIML functionality and an indication of a reason for non-applicability associated with the at least one non-applicable AIML functionality.

2. The WTRU of claim 1, wherein the request received from the network comprises one or more of an indication of a minimum performance level or an indication of one or more associated identifiers (IDs) corresponding to a network-side condition.

3. The WTRU of claim 2, wherein the one or more conditions comprise one or more of: a respective model availability associated with the AIML functionality, a respective consistency between model training WTRU conditions associated with the AIML functionality and current WTRU conditions, or a respective consistency between model training network conditions associated with the AIML functionality and the one or more network-side conditions.

4. The WTRU of claim 3, wherein the minimum performance level comprises a key performance indicator (KPI) threshold, and wherein the processor being configured to determine whether each AIML functionality of the at least one of the one or more AIML functionalities is currently applicable comprises the processor being configured to determine whether each AIML functionality of the at least one of the one or more AIML functionalities meets the KPI threshold.

5. The WTRU of claim 1, wherein the functionality applicability report further comprises an indication of one or more applicable AIML functionalities.

6. The WTRU of claim 5, wherein the functionality applicability report further comprises, for each applicable AIML functionality, one or more of a priority associated with the applicable AIML functionality, a preference associated with the applicable AIML functionality, or an expected performance level associated with the applicable AIML functionality.

7. The WTRU of claim 1, wherein the indication of the reason for non-applicability associated with the at least one non-applicable AIML functionality comprises one or more of: an indication that a model is not available, an indication that the model is not trained, an indication that the model is available and trained but not for a current network-side condition, an indication that the model is available and trained but not for a current WTRU condition, an indication that a required WTRU configuration or WTRU input is lacking, or an indication that the model is not expected to provide an indicated performance level.

8. The WTRU of claim 1, wherein the functionality applicability report is transmitted via one or more of: a radio resource control (RRC) message, a medium access control (MAC) control element (CE), or uplink control information (UCI).

9. The WTRU of claim 1, wherein the functionality applicability report comprises a bitmap.

10. The WTRU of claim 1, wherein the functionality applicability report further comprises one or more of: one or more associated IDs corresponding to network-side conditions for which the at least one non-applicable AIML functionality will be applicable, one or more WTRU conditions for which the at least one non-applicable AIML functionality will be applicable, a configuration needed to perform inference with a model for the at least one non-applicable AIML functionality, or a performance level that can be achieved for the at least one non-applicable AIML functionality for current WTRU conditions.

11. A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: sending, to a network, a capability report, wherein the capability report comprises respective indicators that indicate whether the WTRU supports each of one or more artificial intelligence / machine learning (AIML) functionalities;receiving, from the network, a request to report if at least one of the one or more AIML functionalities indicated in the capability report is currently applicable; determining, for each AIML functionality of the at least one of the one or more AIML functionalities, whether the AIML functionality is currently applicable based on one or more conditions; and sending, to the network, a functionality applicability report based on the determination, wherein the functionality applicability report indicates at least one non-applicable AIML functionality and an indication of a reason for non-applicability associated with the at least one non-applicable AIML functionality.

12. The method of claim 11, wherein the request received from the network comprises one or more of an indication of a minimum performance level or an indication of one or more associated identifiers (IDs) corresponding to a network-side condition.

13. The method of claim 12, wherein the one or more conditions comprise one or more of: a respective model availability associated with the AIML functionality, a respective consistency between model training WTRU conditions associated with the AIML functionality and current WTRU conditions, or a respective consistency between model training network conditions associated with the AIML functionality and the one or more network-side conditions.

14. The method of claim 13, wherein the minimum performance level comprises a key performance indicator (KPI) threshold, and wherein determining whether each AIML functionality of the at least one of the one or more AIML functionalities is currently applicable comprises determining whether each AIML functionality of the at least one of the one or more AIML functionalities meets the KPI threshold.

15. The WTRU of claim 11, wherein the functionality applicability report further comprises an indication of one or more applicable AIML functionalities.

16. The WTRU of claim 15, wherein the functionality applicability report further comprises, for each applicable AIML functionality, one or more of a priority associated with the applicable AIML functionality, a preference associated with the applicable AIML functionality, or an expected performance level associated with the applicable AIML functionality.

17. The method of claim 11, wherein the indication of the reason for non-applicability associated with the at least one non-applicable AIML functionality comprises one or more of: an indication that a model is not available, an indication that the model is not trained, an indication that the model is available and trained but not for a current network-side condition, an indication that the model is available and trained but not for a current WTRU condition, an indication that a required WTRU configuration or WTRU input is lacking, or an indication that the model is not expected to provide an indicated performance level.

18. The method of claim 11, wherein the functionality applicability report is transmitted via one or more of: a radio resource control (RRC) message, a medium access control (MAC) control element (CE), or uplink control information (UCI).

19. The method of claim 11, wherein the functionality applicability report comprises a bitmap.

20. The method of claim 11, wherein the functionality applicability report further comprises one or more of: one or more associated IDs corresponding to network-side conditions for which the at least one non-applicable AIML functionality will be applicable, one or more WTRU conditions for which the at least one non-applicable AIML functionality will be applicable, a configuration needed to perform inference with a model for the at least one non-applicable AIML functionality, or a performance level that can be achieved for the at least one non-applicable AIML functionality for current WTRU conditions.

Images