Methods, architectures, apparatuses and systems for handover of a wireless transmit-receive unit from a source cell to a target cell

Abstract

Procedures, methods, architectures, apparatuses, systems, devices, and computer program products for handover of a wireless transmit-receive unit, WTRU, from a source network node to a target network node in a network, are described. The WTRU may receive configuration information related to handover of the WTRU from the source network node to the target network node, and determine that reference signal received power with the source network node is greater than a configured reference signal received power value or range. The WTRU may determine that artificial intelligence / machine learning, AI / ML, operation of the WTRU for one or more AI / ML functionalities cannot be supported by the WTRU at the target network node, and may send an indication to the source network node indicating that the WTRU declines the handover to the target network node.

Description

METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS FOR HANDOVER OF A WIRELESS TRANSMIT-RECEIVE UNIT FROM A SOURCE CELL TO A TARGET CELL CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of US Provisional Patent Application No.63 / 540,458 filed September 26, 2023, which is incorporated by reference herein int its entirety. BACKGROUND

[0002] The present disclosure is generally directed to the fields of communications, software and encoding, including, for example, to methods, architectures, apparatuses, systems related to Artificial Intelligence / Machine Learning (AI / ML) operations for wireless transmit-receive units (WTRUs) in wireless networks. It is desirable to resolve some of the challenges facing the support of AI / ML in wireless networks. SUMMARY

[0003] In the following, there are defined and described methods and apparatuses for improvement of support for handover and for AI / ML functionality for wireless transmit-receive units and base stations and that are claimed according to the appended claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the FIGs. indicate like elements, and wherein:

[0005] FIG.1A is a system diagram illustrating an example communications system;

[0006] 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;

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

[0008] 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;

[0009] FIG. 2 is a sequence chart illustrating legacy capability reporting by a WTRU in a network;

[0010] FIG.3 is a sequence chart for a handover of a WTRU in a network from a source network node to a target network node according to an embodiment;

[0011] FIG.4 is a sequence chart for a handover of a WTRU in a network from a source network node to a target network node according to an embodiment;

[0012] FIG.5 is a flow chart of a method according to an embodiment;

[0013] FIG.6 is a flow chart of a method according to an embodiment; and

[0014] FIG.7 is a flow chart of a method according to an embodiment. DETAILED DESCRIPTION

[0015] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and / or inherently (collectively "provided") herein. Although various embodiments are described and / or claimed herein in which an apparatus, system, device, etc. and / or any element thereof carries out an operation, process, algorithm, function, etc. and / or any portion thereof, it is to be understood that any embodiments described and / or claimed herein assume that any apparatus, system, device, etc. and / or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and / or any portion thereof.

[0016] Abbreviations and Acronyms ACK Acknowledgement AI Artificial Intelligence BLER Block Error Rate BM Beam Management BWP Bandwidth Part CQI Channel Quality Indicator C-RNTI Cell-RNTI CSI Channel State Information DL Downlink; Deep Learning DNN Deep Neural Network HIT Handover Interruption Time HO Handover LPP Long-Term Evolution (LTE) Positioning ProtocolLTE Long Term Evolution e.g. from 3GPP LTE R8 and up L1-RSRP Layer1-RSRP MAC CE MAC control element ML Machine Learning NACK Negative ACK NR New Radio NW Network PDU Packet Data Unit PMI Precoding Matrix Indicator PRS Positioning Reference Signal RACH Random Access Channel (or procedure) RI Rank Indicator RNTI Radio Network Temporary Identifier RRC Radio Resource Control RS Reference Signal RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality RSSI Received Signal Strength Indicator SINR Signal-to-Interference-plus-Noise Ratio UE User Equipment (WTRU) UL Uplink

[0017] Example Communications System

[0018] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and / or be adapted and / or configured for the methods, apparatuses and systems provided herein.

[0019] FIG. 1A is a system 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 (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block- filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0020] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113,a core network (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 (or be) 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 UE.

[0021] 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, e.g., to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the networks 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), 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.

[0022] 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 an 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 or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

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

[0024] 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 116 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 Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (HSUPA).

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

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

[0027] 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., an eNB and a gNB).

[0028] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), 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.

[0029] 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 an 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 an 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 any of a small cell, 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.

[0030] 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 an NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0031] 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 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), userdatagram 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 / 114 or a different RAT.

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

[0033] 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 elements / 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.

[0034] 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, e.g., in an electronic package or chip.

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

[0036] 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. For example, the WTRU 102 may employ MIMO technology. Thus, in an 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.

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

[0038] 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 storage device. 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).

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

[0040] 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., basestations 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.

[0041] The processor 118 may further be coupled to other elements / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality and / or wired or wireless connectivity. For example, the elements / peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., 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 elements / 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.

[0042] 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 uplink (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit 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 WTRU 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 uplink (e.g., for transmission) or the downlink (e.g., for reception)).

[0043] 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, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0044] 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 an 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 receive wireless signals from, the WTRU 102a.

[0045] Each of the eNode-Bs 160a, 160b, and 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 uplink (UL) and / or downlink (DL), and the like. As shown in FIG.1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0046] 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 (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the CN operator.

[0047] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c 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.

[0048] 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 packets to / 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.

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

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

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

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

[0053] 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 into 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.

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

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

[0056] Very high throughput (VHT) STAs may support 20 MHz, 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 a medium access control (MAC) layer, entity, etc.

[0057] 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 (MTC), 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).

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

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

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

[0061] 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 an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRUs 102a, 102b, 102c. 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 Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0062] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, 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., including a varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0063] 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 amobility 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.

[0064] 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 functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG.1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0065] 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 at least one Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the 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.

[0066] 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 protocol data unit (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, e.g., 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 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 radiotechnologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as Wi- Fi.

[0067] 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 UE 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.

[0068] 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, e.g., 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.

[0069] 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 an 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.

[0070] In view of FIGs.1A-1D, and the corresponding description of FIGs.1A-1D, one or more, or all, of the functions described herein with regard to any of: WTRUs 102a-d, base stations 114a- b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, and / or any other element(s) / device(s) described herein, may be performed by one or more emulation elements / 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.

[0071] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or moreemulation devices may perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and / or may performing testing using over-the-air wireless communications.

[0072] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0073] Introduction / Terminology

[0074] ‘baseline’ AI / ML (sub)functionality(ies) and / or (sub) use case(s) may correspond to any one or more of the below:

[0075] an AI / ML (sub)functionality and / or (sub) use case where the legacy operation is not configured in the WTRU;

[0076] an AI / ML (sub)functionality and / or (sub) use case where the legacy operation is configured in the WTRU but may involve a lot of overhead (e.g., CSI-RS for CSI / beam management, PRS for positioning);

[0077] an AI / ML (sub)functionality and / or (sub) use case where the legacy operation is configured in the WTRU with the understanding that it is only used as a backup option when the corresponding AI / ML (sub)functionality and / or (sub) use case is unavailable, e.g., during handover, immediately after handover, when handing over to a target cell (target network node, destination network node / cell) that does not support the same set of AI / ML (sub)functionality(ies) and / or (sub) use case(s), etc.;

[0078] an AI / ML (sub)functionality and / or (sub) use case where the legacy operation is configured in the WTRU but the AI / ML model operation is much more efficient, e.g., in terms of overhead, accuracy, latency, etc. for e.g., when the best beam predicted by an AI / ML model is the actual ‘best’ beam (with highest RSRP) compared to the best beam found via conventional methods of beam sweeping.

[0079] ‘baseline’ AI / ML functionality may be understood as AI / ML functionality that is to be present to support a given desired AI / ML model implementation.

[0080] Source ‘cell’ is used interchangeably with source ‘network node’ / ‘gNB’ or simply ‘source’.

[0081] Target ‘cell’ is used interchangeably with target ‘network node / ‘gNB’ or simply ‘target’.

[0082] ‘Legacy’ mechanism / procedure / operation is used to refer to non-AIML based mechanisms used as a possible substitute to their AI / ML counterpart.

[0083] An AIML related / based action refers to any action taken by the WTRU or / and associated WTRU behavior that is impacted by a prediction of one or more metrics (e.g., radio link quality, buffer levels, etc.,) that was made by an AIML model / functionality. For example, this could be a handover execution, where the handover action was triggered due to the fulfilment of the conditions of an event associated with the handover action, and the event conditions are related to thresholds that were compared to one or more measured and / or predicted values (e.g., measured / predicted RSRP measurements).

[0084] Artificial Intelligence (AI). Artificial intelligence may be broadly defined as the behavior exhibited by machines that mimic cognitive functions to sense, reason, adapt and act.

[0085] Machine Learning (ML): General Principles, notions of Deep Learning, Autoencoder, and AI / ML Model.

[0086] ML, General Principles: Machine learning may refer to type of algorithms that solve a problem based on learning through experience (‘data’), without explicitly being programmed (‘configuring set of rules’). Machine learning can be considered as a subset of AI. Different machine learning paradigms may be envisioned based in the nature of data or feedback available to the learning algorithm. For example, a supervised learning approach may involve learning a function that maps input to an output based on labeled training example, wherein each training example may be a pair consisting of input and the corresponding output. For example, an unsupervised learning approach may involve detecting patterns in the data with no pre-existing labels. For example, reinforcement learning approach may involve performing sequence of actions in an environment in order to maximize the cumulative reward. In some solutions, it is possible to apply machine learning algorithms using a combination or interpolation of the above-mentioned approaches. For example, semi-supervised learning approach may use a combination of a small amount of labeled data with a large amount of unlabeled data during training. In this regard semi- supervised learning falls between unsupervised learning (with no labeled training data) and supervised learning (with only labeled training data).

[0087] ML, Deep Learning: Deep learning refers to a class of machine learning algorithms that employ artificial neural networks (specifically DNNs) which were loosely inspired from biological systems. The Deep Neural Networks (DNNs) are a special class of machine learning models inspired by the human brain wherein the input is linearly transformed and pass-through non-linear activation function multiple times. DNNs typically consists of multiple layers where each layer consists of linear transformation and a given non-linear activation functions. The DNNs can be trained using the training data via back-propagation algorithm. Recently, DNNs have shown state- of-the-art performance in a variety of domains, e.g., speech, vision, natural language etc. and for various machine learning settings supervised, un-supervised, and semi-supervised.

[0088] ML, Autoencoder: Auto-encoders are specific class of DNNs that arise in context of un- supervised machine learning setting wherein the high-dimensional data is non-linearly transformed to a lower dimensional latent vector using the DNN based encoder and the lower dimensional latent vector is then used to re-produce the high-dimensional data using a non-linear decoder. The encoder is represented as ^^^ ^^; ^^^^where x is the high-dimensional data and ^^^represents the parameters of the encoder. The decoder is represented as ^^^ ^^; ^^ௗ^ where z is the low-dimensional latent representation and ^^ௗrepresents the parameters of the encoder. Further, using training data ^ ^^^,⋯ , ^^ே^ the auto-encoder can be trained by solving the following optimization problem:

[0089] ^ ^^^௧^, ^^ௗ௧^^ ൌ arg^m ^,i^n ∑ே^^ୀ^|| ^^^െ ^^^ ^^^ ^^^; ^^^^; ^^ௗ^ ||ଶଶ .

[0090] The above problem can be approximately solved using a backpropagation algorithm. The trained encoder ^^^ ^^; ^^^௧^^ can be used to compress the high-dimensional data and trained decoder ^^^ ^^; ^^ௗ௧^^ can is used to decompress the latent representation.

[0091] The terms Artificial Intelligence (AI), Machine Learning (ML), Deep Learning (DL), DNNs may be used interchangeably. Methods described herein are exemplified based on learning in wireless communication systems. The methods are not limited to such scenarios, systems and services and may be applicable to any type of transmissions and / or services etc.

[0092] ML: AI / ML model. Throughout this disclosure, “AIML model”, “AI / ML model”, “ML model”, “model” are used interchangeably to refer to an Artificial Intelligence / Machine Learning model that emulates logical decision-making based on available / collected / requested data.

[0093] Principles and observations

[0094] A WTRU determining applicability of AI / ML operation may be one or more of the following:

[0095] the AIML functionalities / models that were being used / activated at the source cell;

[0096] the AIML functionalities / models that were possible to be used / activated at the source cell but not activated (but now the target cell is trying to activate them);

[0097] any AIML functionalities / models that the target cell is trying to activate;

[0098] the WTRU may have been configured some indication / flag for AIML functionalities / models that it has to check for applicability in the target during HO stage (e.g., in the HO command, even before the HO command in a previous RRC reconfiguration, etc.,);

[0099] How activation of AI / ML for one functionality impacts AI / ML capability / operation of another functionality;

[0100] How model switching or fallback to legacy for one functionality impacts AI / ML capability / operation of another functionality;

[0101] How to define mandatory vs optional capabilities and how it impacts WTRU behavior;

[0102] How to indicate dynamic capabilities when the model becomes applicable (e.g., appropriate channel conditions / NW configuration, etc), or usage of model become possible (e.g., availability of processing capability);

[0103] the WTRU receives activation indication for a WTRU-sided model from a third party that has no knowledge of UL and DL traffic. Transmission of model inference output requires resources over the Uu link.

[0104] Embodiment components

[0105] [‘baseline’ AI / ML (sub)functionality(ies) and / or (sub) use case(s)]

[0106] According to an embodiment, the WTRU may be pre-configured with what is considered an ‘baseline’ AI / ML (sub)functionality and / or (sub) use case such that the list of ‘baseline’ AI / ML (sub)functionality(ies) and / or (sub) use case(s) does not change. According to another embodiment, the WTRU may be configured with what is considered an ‘baseline’ AI / ML (sub)functionality and / or (sub) use case during RRC (re)configuration. According to an embodiment, the WTRU may receive updates (e.g., from the NW) if there is an update on what is considered an ‘baseline’ AI / ML (sub)functionality and / or (sub) use case by the NW. For example, following a high performing AI / ML model download (e.g., from the NW) for CSI prediction, the NW may consider AI / ML based CSI prediction as an ‘baseline’ (sub)functionality and / or (sub) use case and send an updated list if it was not previously considered as ‘baseline’.

[0107] [WTRU may receive activation indication]

[0108] The WTRU may receive from the NW / third party / gNB an activation indication for any one or more of the following A)-B):

[0109] A) AI / ML model(s), A1-A3):

[0110] A1) for example, a WTRU may receive an indication to activate an AI / ML model for CSI prediction;

[0111] A2) for example, a WTRU may receive an indication to activate AI / ML enabled CSI prediction. This may or may not be accompanied with an identification of the relevant model to activate. In the case where the indication is not accompanied with an identification of the relevant model to activate, it may be up to the WTRU to activate any AI / ML model that it has for CSI prediction. The WTRU may indicate to the NW / gNB the AI / ML that it has selected for the CSI prediction. The model that the WTRU chooses to activate may also be subject to WTRU capability (e.g., available processing power at WTRU, WTRU storage, etc.);

[0112] A3) in the case where the indication is accompanied with an identification of the relevant model to activate, the WTRU may simply activate the relevant model, provided WTRU is able to do so (subject to WTRU capability, e.g., WTRU storage / processing capability).

[0113] B) AI / ML (sub)functionality(ies) and / or (sub) use case(s), B1)-B3):

[0114] B1) for example, a WTRU may receive an indication to activate AI / ML enabled beam prediction;

[0115] B2) for example, a WTRU may receive an indication to activate AI / ML enabled temporal beam prediction;

[0116] B3) for example, a WTRU may receive an indication to activate AI / ML enabled CSI prediction.

[0117] In response to the activation indication from the NW, the WTRU may do any one or more of the following, A)-E):

[0118] A) activate relevant AI / ML (sub)functionality(ies) and / or AI / ML (sub) use case(s) and / or AI / ML model(s);

[0119] B) determine whether it can activate relevant AI / ML (sub)functionality(ies) and / or AI / ML (sub) use case(s) and / or AI / ML model(s), e.g., based on WTRU capability (e.g., WTRU processing capability, WTRU storage etc.);

[0120] C) send an ACK to the NW to confirm that it can activate relevant AI / ML (sub)functionality(ies) and / or AI / ML (sub) use case(s) and / or AI / ML model(s);

[0121] D) send a list to NW on a set of AI / ML (sub)functionality(ies) and / or AI / ML (sub) use case(s) and / or AI / ML model(s) that the WTRU can activate. The set may be a subset of the list of AI / ML (sub)functionality(ies) and / or AI / ML (sub) use case(s) and / or AI / ML model(s) indicated by the NW in the activation request. The set may include one or more AI / ML (sub)functionality(ies) and / or AI / ML (sub) use case(s) and / or AI / ML model(s) that were not part of the initial request by the NW but that the WTRU may have determined that it can activate based on, for e.g., WTRU capability;

[0122] E) Negotiate with the NW E1)-E2):

[0123] E1) the WTRU may send an indication to the NW that it is not able to activate all the AI / ML (sub)functionality(ies) and / or AI / ML (sub) use case(s) and / or AI / ML model(s) as indicated by the NW, but may be able to do so at a later time;

[0124] E2) the WTRU may send an indication to the NW that it is not able to activate all the AI / ML (sub)functionality(ies) and / or AI / ML (sub) use case(s) and / or AI / ML model(s) as indicated by the NW, but may be able to do so if it deactivates a currently supported feature (e.g., XR feature / ability to process PDU set in the AS layer functionality).

[0125] Overview

[0126] See FIG.2. A WTRU (20) may report its capabilities to the network / to a network node (gNB) (21) via the WTRU capability Information message (201) in RRC, in response to the WTRU Capability enquiry (200) from the NW (21).

[0127] Capability reporting is conventionally done in a semi-static way. Since the WTRU’s AI / ML capability may be a function of dynamic parameters such as WTRU computation resources and storage one-time capability reporting may not be sufficient for AI / ML. As baseline, RAN2 (RAN2 is responsible for the development of specifications dealing with Evolved UTRA, NR radio access (NR) and beyond) can start with the RRC and LPP capability frameworks and as part of the study consider whether dynamic capability reporting is needed for AI / ML.

[0128] RAN1#112 has agreed that for functionality identification, WTRU capability reporting will be considered as a starting point.

[0129] Since the current RRC capability framework does not include any AI / ML specific indication, some enhancements are needed to the RRC capability framework.

[0130] Enhancements to the UECapabilityInformation message may be desirable, to include AI / ML capability.

[0131] WTRU reporting whether or not the WTRU is AI / ML capable may be sufficient in cases where AI / ML capability only applies to one functionality / feature or WTRU only has one AI / ML model. However, a simple capability indication does not provide information on the functionality / feature where the capability is applicable. It may therefore be desirable to include, in the capability indication, information on the applicable functionality / feature.

[0132] Functionality / feature-specific capability indication may help for support of multi-AI / ML functionality / feature capability.

[0133] During handover, capability information is sent as part of WTRU context from source gNB to target gNB. If a target gNB does not support a functionality, this may result in RRCReconfiguration Failure. For AI / ML, there are several instances where the AI / ML functionalities supported by one gNB may not match those supported by another gNB. To avoidthis leading to reconfiguration failure, the WTRU may perform some actions; AI / ML capability may be cell-specific.

[0134] Reporting all the possible combinations of supported functionalities / models, their inter- dependencies, the network / WTRU conditions where they are applicable etc., will create too much overhead for the WTRU and / or the network. It is not feasible / realistic to send a complete AI / ML WTRU capability to the network that captures all the aspects (validity conditions, inter- dependency, etc.,), and so we may assume only a limited WTRU capability is sent to the network at the start, resulting in several problems, e.g., mismatch during handover, network trying to activate models / functionalities that are not compatible at the same time, etc.

[0135] Handover: Source gNB releases WTRU after sending Handover command: Summary

[0136] The following is a summary of WTRU-network node behavior according to embodiments. Details of these embodiments are found in the related section.

[0137] There may be many AI / ML capabilities corresponding to different use cases / functionalities / features, etc. It is possible that an AIML model / function at the WTRU that was applicable / valid at the source cell / node may not be applicable at the target cell during a handover (e.g., the AIML function / model is not trained for the target cell’s frequency, BWP, the target cell / gNB does not provide the required input, e.g., reference signals, for the AIML model operation, etc.,) Had the WTRU communicated all the possible combinations of AIML model / functionality capability, then from the WTRU context / capability that is forwarded from source to the target, the target will have figured out what AIML functionality to configure / activate at the WTRU after the HO. However, communicating all the combinations of AIML capabilities is undesirable as the capability to be exchanged at once from the WTRU to the network (e.g., during connection setup) will become very large.

[0138] According to some applicable scenarios:

[0139] a target cell does not support some functionalities supported by source cell.

[0140] an AI / ML model is not trained for the target cell.

[0141] It may then be investigated how to prevent reconfiguration failure, and subsequent re- establishment, when handing over a WTRU where an AIML functionality / model that was being used (or was possible to be used) at the source cannot be used at the target gNB / cell.

[0142] Summary of a embodiment embodiment: During a HO, if a WTRU receives a configuration that enables / activates an AI / ML operation that it cannot apply at the target, instead of considering this a reconfiguration failure and triggering re-establishment, WTRU falls back tolegacy operation for that functionality and sends indication to target cell (e.g., in the HO complete message)

[0143] According to an embodiment, see FIG.3:

[0144] a WTRU (30) receives from network (e.g., source gNB (31)) configuration information related to / for handover (HO command) (e.g., in RRC Reconfiguration message, (300)). The configuration may contain info to access target cell (32): at least target cell ID, new C-RNTI, target gNB security algorithm IDs, etc., AI / ML related information (including basic functionalities, e.g., CSI, BM, etc.);

[0145] the WTRU determines (301) applicability of AI / ML operation at the target node for one or more functionalities / models implicitly (e.g., based on target cell frequency, BWP, reference signals from the target cell, etc.,) or explicitly (e.g., based on the AIML information included in HO command):

[0146] if AI / ML operation is applicable for the concerned functionalities / models, WTRU executes the handover command;

[0147] if AI / ML operation is not applicable for one or more of the concerned functionalities / models, then the WTRU falls back to non-AIML operation for said functionality or functionality associated to the model, or the WTRU falls back to model / functionality applicable at target (model / (sub)functionality switching (type));

[0148] the WTRU sends a HO complete (e.g., RRCReconfigurationComplete) message to the target cell (32). If the WTRU has fallen back to legacy operation for the one or more AIML functionalities, WTRU indicates this (302) to the target cell (32) (e.g., in the HO complete message, or subsequent RRC message).

[0149] Handover: Source gNB releases WTRU after sending Handover command: Detailed Operation

[0150] The following is a description of the detailed operation of WTRU-network node behavior according to embodiments.

[0151] [WTRU receives configuration for handover]

[0152] A WTRU may receive, e.g., from the source gNB, configuration for handover, e.g., in RRC (re)configuration, which may contain any one or more of the following information to access the target cell A)-E):

[0153] A) cell ID of at least one target cell;

[0154] B) C-RNTI of at least one target cell;

[0155] C) security algorithm IDs of at least one target cell;

[0156] D) AI / ML related information (including basic functionalities) of at least one target cell, for e.g., support for AI / ML enabled CSI prediction / CSI compression / Beam management / positioning, etc.;

[0157] E) time delay when the WTRU may expect to be able to activate one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s) E1)-E2):

[0158] E1) as a first example of time delay when the WTRU may expect to be able to activate one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s), prior to the handover, it is possible that there were no UEs being served by the target cell that had some AI / ML (sub)functionality(ies) and / or (sub) use case(s) activated such that the target cell did not register these AI / ML (sub)functionality(ies) and / or (sub) use case(s) as ‘available’ at the target cell. The target cell may send a delay information of when it should be able to activate one or more such AI / ML (sub)functionality(ies) and / or (sub) use case(s) to the source gNB which may then forward this information to the WTRU as part of the handover configuration

[0159] E2) as a second example of time delay when the WTRU may expect to be able to activate one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s), this may consist of one delay information for the activation of all AI / ML (sub)functionality(ies) and / or (sub) use case(s) that are served by the source cell, or it may consist of different delay interval for when the target cell expects to be able to activate each of the AI / ML (sub)functionality(ies) and / or (sub) use case(s) that are currently deactivated and / or may still be deactivated after handover is complete for the WTRU.

[0160] The configuration for handover may have been generated by the target cell but forwarded to the WTRU by the source cell on behalf of the target cell. In one embodiment, the source cell may forward the information pertaining to the best candidate target cell (i.e., target cell with highest RSRP). In another embodiment, the source cell may forward information pertaining to the best two or more candidate target cell. In one embodiment, the network may determine the best candidate target cell based not only on the target cell with the highest RSRP (as in legacy) but also considering AI / ML applicability, i.e., in the case where more there may be more than one candidate target cell, the network may select the one best candidate target cell based on the AI / ML operation supported by the target cell. This may consist of the list of AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the target cell and / or the intersection of the AI / ML operation between the currently serving source cell and the candidate cell. In that case, the network may select the best candidate cell based on the target cell that has the largest intersection with the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the source cell.

[0161] [WTRU determines applicability of AI / ML operation]

[0162] A WTRU may determine the applicability of the AI / ML operation which may include determining whether the one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the source cell are supported by the target cell. According to an embodiment, such determination may be based on implicit information that may be shared as part of the handover configuration, e.g., based on target cell frequency, bandwidth part, reference signals from the target cell, etc. According to another embodiment, such determination based be based on explicit information which may include any AI / ML related information that may be included in the handover (re)configuration.

[0163] According to an embodiment, the WTRU may determine the applicability of the AI / ML operation for all AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the WTRU. According to another embodiment, the WTRU may only determine the applicability of the AI / ML operation for AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the currently serving source gNB. According to another embodiment, the WTRU may assume that the list of AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the currently serving source gNB will be supported by the target gNB selected by the network for handover and only determine AI / ML applicability for AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the WTRU but not supported by the currently serving source gNB.

[0164] According to another embodiment, the WTRU may be configured with a list of AI / ML (sub)functionality(ies) and / or (sub) use case(s) for which to check AI / ML applicability. For example, the WTRU may be configured with a list of ‘baseline’ versus ‘optional’ AI / ML (sub)functionality(ies) and / or (sub) use case(s) and the WTRU may be configured to only determine the applicability of the ‘baseline’ AI / ML (sub)functionality(ies) and / or (sub) use case(s). For example, an ‘baseline’ AI / ML (sub)functionality and / or (sub) use case may be one where the legacy non-AI / ML (sub)functionality and / or (sub) use case is not configured. In one example, it may be mandatory for the WTRU to check the applicability of the baseline AI / ML (sub)functionality(ies) and / or (sub) use case(s) and only check the applicability of any other AI / ML (sub)functionality(ies) and / or (sub) use case(s) in an opportunistic way, e.g., if after checking applicability of the baseline AI / ML (sub)functionality(ies) and / or (sub) use case(s) there is still some remaining time in the Handover Interruption Time (HIT) or if the remaining timer in the HIT is above a preconfigured threshold, the WTRU may determine the applicability of non- baseline AI / ML (sub)functionality(ies) and / or (sub) use case(s).

[0165] According to an embodiment, the WTRU may receive an indication from the network to assist the WTRU in determining applicability of the AI / ML operation. Such indication may include at least one of A)-D):

[0166] A) indication to inform the WTRU that the set of AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the target cell matches the set of AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the source cell;

[0167] B) flag / indication to only check a subset of AI / ML (sub)functionality(ies) and / or (sub) use case(s) that may be enabled at the WTRU, for e.g., that subset may correspond to the list of ‘baseline’ AI / ML (sub)functionality(ies) and / or (sub) use case(s);

[0168] C) list of AI / ML (sub)functionality(ies) and / or (sub) use case(s) to check for applicability;

[0169] D) the granularity of such indication may vary, for e.g., it may be at feature group (FG) level and / or feature level and / or functionality level and / or sub-functionality level and / or use case level and / or sub use case level and / or type of any of the aforementioned levels. See D1)-D2):

[0170] D1) for beam management, the indication may be at any one or more of the following granularities for example D1a)-D1c):

[0171] D1a) beam management level;

[0172] D1b) spatial domain beam prediction level, temporal domain beam prediction level;

[0173] D1c) spatial domain beam prediction option 1 level, Spatial domain beam prediction option 2 level D1c1-D1c2):

[0174] D1c1) e.g., Option 1: Select the best beam within Set A of beams based on the measurement of all RS resources or all possible beams of beam Set A (exhaustive beam sweeping);

[0175] D1c2) e.g., Option 2: Select the best beam within Set A of beams based on the measurement of RS resources from Set B of beams.

[0176] D2) according to an embodiment, the NW may indicate the granularity level to the WTRU. For example, (1,0,0) may signify indication at FG level; (0,1,0) may signify indication at feature level; (0,0,1) may signify indication at functionality level. In one embodiment, functionality may be defined the granularity of Spatial domain beam prediction level or temporal domain beam prediction level. In another embodiment, functionality may be defined the granularity of Option 1 vs Option 2 spatial domain beam prediction.

[0177] [WTRU action based on applicability of AI / ML operation determination]

[0178] If the AI / ML operation is applicable for all the AI / ML (sub)functionality(ies) and / or (sub) use case(s), the WTRU may execute the handover command to the target cell. If a subset of the AI / ML (sub)functionality(ies) and / or (sub) use case(s) are applicable for the target cell whereby the subset includes all the ‘baseline’ AI / ML (sub)functionality(ies) and / or (sub) use case(s), the WTRU may execute the handover command. If the AI / ML operation is not applicable for one or more of the concerned (sub)functionalities / (sub)use cases / models at the target cell, the WTRU may fall back to legacy procedures for the concerned (sub)functionalities / (sub)use cases / models.

[0179] The WTRU may send a handover complete message (e.g., RRCReconfigurationComplete) message to the target gNB to indicate completion of handover. If the WTRU has fallen back to legacy operation for the one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s), the WTRU may indicate this to the target gNB, e.g., in the HO complete message, or subsequent RRC message(s), e.g., in RRCReconfigurationComplete message(s). Such indication may include any one or more of the following A)-I):

[0180] A) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the source cell but not supported by the target cell;

[0181] B) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) not supported by the source cell but supported by the target cell;

[0182] C) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the WTRU;

[0183] D) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the WTRU but will be activated at later time. Indication may also optionally include expected time when AI / ML (sub)functionality(ies) and / or (sub) use case(s) will be activated;

[0184] E) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) currently not activated and / or supported by the target cell for which the WTRU is using legacy mechanism as a substitute;

[0185] F) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) that were not activated and / or supported by the source cell for which the WTRU was using legacy mechanism as a substitute;

[0186] G) any of the aforementioned AI / ML (sub)functionality(ies) and / or (sub) use case(s) may be indicated, for e.g., in terms of AI / ML (sub)functionality(ies) IDs and / or (sub) use case(s) IDs;

[0187] H) associated criticality of being unable to activate the aforementioned list of AI / ML (sub)functionality(ies) and / or (sub) use case(s), for e.g., each (sub)functionality and / or (sub) use case could have a criticality number attached to it;

[0188] I) time delay when the WTRU expects to be able to activate any of the aforementioned list of AI / ML (sub)functionality(ies) and / or (sub) use case(s) I1)-I3):

[0189] I1) for e.g., prior to the handover, it is possible that there were no UEs being served by the target cell that had some AI / ML (sub)functionality(ies) and / or (sub) use case(s) activated such that the target cell did not register these AI / ML (sub)functionality(ies) and / or (sub) use case(s) as ‘available’ at the target cell;

[0190] I2) for e.g., the WTRU may send the delay information to the target cell to inform the target cell that activation of these AI / ML (sub)functionality(ies) and / or (sub) use case(s) is expected at a given time. This may consist of one delay information for all the AI / ML (sub)functionality(ies) and / or (sub) use case(s) currently deactivated at the target cell but that wereactivated at the source cell or different delay information for each respective AI / ML (sub)functionality and / or (sub) use case.

[0191] I3) according to an embodiment, the WTRU may have been preconfigured with the delay information, e.g., for functionality X, allow for t1 ms interval for activation in a target cell following completion of handover; for functionality Y, allow for t2 ms interval for activation in a target cell following completion of handover. In another embodiment, the WTRU may have received such information from the source cell before the handover.

[0192] According to an embodiment, following the completion of handover, the WTRU may receive from the target cell time delay information on when the target cell may be able to activate some AI / ML (sub)functionality(ies) and / or (sub) use case(s) that may currently be deactivated A)- B):

[0193] A) the WTRU may use legacy functionality during that time if needed as a workaround for example;

[0194] B) in another example, the WTRU may extend the prediction time window for the relevant AI / ML (sub)functionality and / or (sub) use case while still being served by the source cell, for e.g., if the WTRU is using AI / ML for temporal domain beam prediction, while being served by the source cell, it may extend the prediction window to also include the Handover Interruption Timer (e.g., extend prediction window by 50ms) to account for the fact that the temporal beam prediction capability may not be activated at the target cell immediately upon handover.

[0195] [WTRU receives RRCReconfiguration with multiple sub-configurations, selects configurations to apply based on conditions, performs actions based on selected sub- configurations, indicates selected sub-configurations]

[0196] According to an embodiment, the WTRU may receive a RRCReconfiguration with a first sub-configuration, a second sub-configuration and a third sub-configuration. For example, the first sub-configuration may correspond to a full configuration, whereas the second and third sub- configuration may correspond to a delta configuration. For example, the first sub-configuration may correspond to non-AIML / legacy configuration and the second and third sub-configuration may correspond to AIML configuration(s). For example, the second and third sub-configuration may have different combinations and / or number of AIML functionalities, use cases and / or AIML model configurations.

[0197] According to an embodiment, each sub-configuration may be associated with a priority. For example, the WTRU may select the sub-configuration to apply based on priority. For example, the WTRU may check if it can apply the highest priority sub-configuration. If it cannot complywith the highest priority sub-configuration, then the WTRU checks if it can comply with the next highest priority sub-configuration.

[0198] According to an embodiment, each sub-configuration may be associated with a flag to indicate if the sub-configuration is mandatory or optional. For example, if the WTRU cannot comply with mandatory sub-configuration, it may declare RRCReconfiguration failure. For example, if the WTRU cannot comply with optional sub-configuration, it can ignore the sub- configuration and continue processing / applying rest of the sub-configurations if applicable. According to an embodiment, the sub-configuration corresponding to full configuration may be considered mandatory by default.

[0199] The embodiments may be extended to plurality of AIML sub-configurations, for example, more than two AIML sub-configurations with different combinations of AIML functionalities, use cases and / or AIML model configurations. Herein each target cell may be associated with set of sub-configurations.

[0200] The WTRU may be configured with a logical ID associated with each sub-configuration. According to an embodiment, the WTRU may be configured to indicate the status of sub- configurations via RRCReconfiguration complete. For example, the WTRU may indicate the logical ID(s) of sub-configurations that it has applied. For example, the WTRU may indicate the logical ID(s) of sub-configurations that it cannot comply.

[0201] According to an embodiment, the WTRU may be configured with RACH resources – wherein each RACH resource may be associated with a sub-configuration (or combination of sub- configuration(s)). The WTRU may implicitly indicate the applicable sub-configuration(s) by selection of RACH resource associated with the applicable sub-configuration(s) and transmitting a preamble on the selected resource.

[0202] According to a first embodiment, upon receiving the RRCconfiguration with sync including one or more sub-configurations, the WTRU may determine the applicable sub- configurations based on one or more conditions described herein. The WTRU may apply the selected sub-configuration(s), trigger a random access to target cell (e.g., possibly according to selected sub-configurations), upon successful random access in target cell, the WTRU may indicate the applicable sub-configurations in RRC reconfiguration complete message.

[0203] According to a second embodiment, upon receiving the RRCconfiguration with sync including one or more sub-configurations, the WTRU may determine the applicable sub- configurations based on one or more conditions described herein. The WTRU may apply a first sub-configuration (e.g., associated with legacy / non-AIML configuration), trigger a random access to target cell, upon successful random access in target cell, the WTRU may indicate in RRCreconfiguration complete message, a set of sub-configurations that the WTRU can potentially activate in the target cell. In other words, the WTRU may transmit an indication of sub- configurations that the WTRU can activate in the future based on subsequent command from the target cell. The WTRU may receive MAC CE from the target cell carrying an indication (e.g., logical ID associated with the sub-configurations) of the sub-configurations that the WTRU should activate.

[0204] Handover: Source gNB does not release WTRU after sending Handover command: Summary

[0205] The following is a summary of WTRU-network node behavior according to embodiments. Details of these embodiments are found in the related section.

[0206] It is desirable for a source gNB to minimize reconfiguration failure when handing a WTRU over to another gNB that supports a different set of AI / ML capabilities.

[0207] Therefore, a source gNB may not release the WTRU immediately after sending HO command. The source gNB may only release the WTRU after receiving a confirmation from WTRU that handover is possible. The WTRU may only send this confirmation when it determines that AI / ML operation for one or more of the functionalities is applicable in the target cell.

[0208] In summary, see FIG.4:

[0209] A) a WTRU (40) receives from the network (e.g., from the source gNB (41)) a configuration (configuration information relative to handover, HO command) for handover (e.g., in an RRC Reconfiguration message (400)), e.g., a first configuration part and a second configuration part A1)-A2):

[0210] A1) the first configuration part contains info to access target cell (42): at least target cell ID, new C-RNTI, target gNB security algorithm IDs, etc. (e.g., generated by target);

[0211] A2) the second configuration part contains configuration information relative to, for example, an RSRP threshold (configured threshold), a time window to determine applicability for the HO.

[0212] B) the WTRU may determine applicability (401) of AI / ML operation for a function at target node, implicitly (e.g., based on frequency, BWP) or explicitly (e.g., based on info included in HO command), B1)-B2):

[0213] B1) if AI / ML operation is applicable (402), the WTRU may complete the handover by sending RRCReconfigurationComplete message to the target cell. The WTRU may send a confirmation (403) to source gNB (41) that it can execute the HO (e.g., allowing source to release WTRU; conventionally, the WTRU would just send a RRCReconfigurationComplete message tothe target cell (42). In this case, it is also sending a message (403) to the source cell (41) so that the source cell can release the WTRU.

[0214] B2) if AI / ML operation for a function is not applicable at the target node (e.g., because the WTRU cannot support functionality), see B2a), B2b):

[0215] B2a) if RSRP with the source cell (41) is greater than a configured RSRP threshold (404):

[0216] the WTRU may send an indication (405) to source cell (41) that it cannot transfer to target (e.g., decline to transfer or handover without support for some functionalities (switch model etc.);

[0217] B2b) if RSRP with the source cell (41) is less than configured RSRP threshold (406), see B2b1), B2b2):

[0218] B2b1) the WTRU may complete the HO (407) with the target cell (42) (e.g., if the WTRU can fallback to legacy (non-AIML) operation for the function), and if the WTRU has fallen back to legacy operation for the one or more AIML functionalities, the WTRU may indicate this to the target (42) (e.g., in the HO complete message (407), or in a subsequent RRC message);

[0219] B2b2) or, the WTRU declares a reconfiguration failure.

[0220] Note that the RSRP level is verified as discussed previously, because, if the RSRP level with the source cell (41) is good, (e.g., RSRP > Th) it may be preferable to keep the WTRU in the source cell (41) to keep the AI / ML functions alive, as the WTRU, if it would be HO to the target cell (42), cannot.

[0221] However, if RSRP with the source cell (41) is not good (e.g. RSRP < Th), handover seems preferable, and as the AI / ML functions are likely to be not supportable in the source cell (41) because of the low RSRP in the source cell (41) and as the HO seems preferable because of the low RSRP, the HO is done anyway even if the WTRU will fall back to non-AIML operation in the target cell (42).

[0222] Handover: Source gNB does not release WTRU after sending Handover command: Detailed Operation

[0223] The following is a description of the detailed operation of WTRU-network node behavior according to embodiments.

[0224] [WTRU receives configuration for handover (e.g., generated by target gNB)]

[0225] A WTRU may receive, e.g., from the source gNB, a configuration (configuration information) for handover, e.g., in an RRC (re)configuration, which may contain any one or more of the following information to access the target cell, A)-F):

[0226] A) cell ID of at least one target cell;

[0227] B) C-RNTI of at least one target cell;

[0228] C) security algorithm IDs of at least one target cell;

[0229] D) AI / ML related information (including basic functionalities) of at least one target cell, for e.g., support for AI / ML enabled CSI prediction / CSI compression / Beam management / positioning, etc.;

[0230] E) time delay when the WTRU may expect to be able to activate one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s) e.g., E1), E2):

[0231] E1) for e.g., prior to the handover, it is possible that there were no UEs being served by the target cell that had some AI / ML (sub)functionality(ies) and / or (sub) use case(s) activated such that the target cell did not register these AI / ML (sub)functionality(ies) and / or (sub) use case(s) as ‘available’ at the target cell. The target cell may send a delay information of when it should be able to activate one or more such AI / ML (sub)functionality(ies) and / or (sub) use case(s) to the source gNB which may then forward this information to the WTRU as part of the handover configuration.

[0232] E2) for e.g., this may consist of one delay information for the activation of all AI / ML f(sub)functionality(ies) and / or (sub) use case(s) that are served by the source cell, or it may consist of different delay interval for when the target cell expects to be avle to activate each of the AI / ML (sub)functionality(ies) and / or (sub) use case(s) that are currently deactivated and / or may still be deactivated after handover is complete for the WTRU.

[0233] F) reference signals, for e.g., the target cell may generate reference signals (e.g., CSI-RS, PRS) which may be forwarded to the WTRU by the source cell. The WTRU may use the reference signals to make measurements (e.g., measure CSI parameters, measure WTRU position).

[0234] The configuration for handover may have been generated by the target cell but forwarded to the WTRU by the source cell on behalf of the target cell. In one embodiment, the source cell may forward the information pertaining to the best candidate target cell (i.e., target cell with highest RSRP). In another embodiment, the source cell may forward information pertaining to the best two or more candidate target cells. In one embodiment, the network may determine the best candidate target cell based not only on the target cell with the highest RSRP (as in legacy) but also considering AI / ML applicability, i.e., in the case where there may be more than one candidate target cell, the network may select the one best candidate target cell based on the AI / ML operation supported by the target cell. This may consist of the list of AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the target cell and / or the intersection of the AI / ML operation between the currently serving source cell and the candidate cell. In that case, the network may select the best candidate cell based on the target cell that has the largest intersection with the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the source cell.

[0235] [WTRU receives configuration for AI / ML support during handover (e.g., generated by source gNB)]

[0236] In addition to the information typically generated by target gNB and forwarded to the WTRU by the source gNB, the WTRU may receive information generated from the source gNB. This may include any one or more of the following A)-C):

[0237] A) configurations regarding any conditions which when met will enable / trigger the handover A1)-A4):

[0238] A1) e.g., RSRP threshold w.r.t. source cell A1a)-A1b):

[0239] A1a) e.g., when the threshold is met / exceeded, the WTRU may have the flexibility to not handover to the target cell if the target cell does not support all or a subset of AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the source cell.

[0240] A1b) the WTRU may be configured whether or not to handover to the target cell based on all or a subset of AI / ML (sub)functionality(ies) and / or (sub) use case(s) based on, for e.g., criticality of being unable to activate the concerned AI / ML (sub)functionality(ies) and / or (sub) use case(s) A1b1)-A1b2):

[0241] A1b1) for e.g., a (sub)functionality and / or (sub) use case for which legacy procedures are not configured may have a high criticality score versus one where legacy is configured in addition to the AI / ML-enabled function;

[0242] A1b2) for e.g., each (sub)functionality and / or (sub) use case may have a criticality number attached to it.

[0243] A2) e.g., thresholds corresponding to CSI parameters (e.g., CQI, PMI, RI) for Uu link with source cell A2a)-A2b):

[0244] A2a) for example, if any of the CSI parameters (e.g., CQI) for Uu link with source cell is above a preconfigured threshold, the WTRU may be configured to delay the handover to the target cell if the target cell cannot immediately activate all the AI / ML (sub)functionality(ies) and / or (sub) use case(s) that are activated at the source cell.

[0245] A2b) for example, if CQI for Uu link with source cell is above a preconfigured threshold, the WTRU may be configured to delay the handover to the target cell if the target cell cannot immediately activate all the ‘baseline’ AI / ML (sub)functionality(ies) and / or (sub) use case(s) that are activated at the source cell. The WTRU may be configured with what is considered an ‘baseline’ AI / ML (sub)functionality and / or (sub) use case.

[0246] A3) e.g., RSRP threshold w.r.t. target cell, for e.g., if RSRP threshold w.r.t. target cell falls below a preconfigured threshold which is relatively low but still above the RSRP threshold that triggers handover to the target cell, the WTRU may only complete handover if all or a subsetof AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the source cell are also supported at the target cell;

[0247] A4) e.g., WTRU location / position threshold w.r.t. target cell, e.g., if WTRU location / position / distance is relatively far away to the target cell, i.e., within a certain distance larger than a preconfigured threshold, the WTRU may be configured to delay the handover to the target cell if the target cell cannot immediately activate all the AI / ML (sub)functionality(ies) and / or (sub) use case(s) that are activated at the source cell.

[0248] B) Time window to determine applicability, for e.g., the WTRU may receive from the NW a time window (e.g., of X ms) to determine applicability of the AI / ML operation at the target cell. If within the time window, the WTRU is not able to assess if all or a subset of AI / ML (sub)functionality(ies) and / or (sub) use case(s) that are activated at the source cell are also supported at the target and / or are supported at the target cell immediately upon handover, the WTRU may delay handover, e.g., to give the target cell time to activate the one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s). In another embodiment, the WTRU may only do this if the RSRP with the source cell is above a preconfigured threshold.

[0249] C) configurations regarding any condition that may be relaxed to delay the handover C1)- C2):

[0250] C1) e.g., time window by which to delay handover C1a)-C1b):

[0251] C1a) for e.g., if all or a subset of AI / ML (sub)functionality(ies) and / or (sub) use case(s) that are supported by the source cell are not supported by the target cell, the NW may send to the WTRU information on the time delay that can be tolerated for handover (even if the RSRP with the target cell currently meets the threshold for handover)

[0252] C1b) for e.g., if the time it takes the target cell to activate some AI / ML functionality is longer than a preconfigured threshold, the network may delay handover of the WTRU to the target cell (even if the RSRP with the target cell currently meets the threshold for handover)

[0253] C2) e.g., if expected Handover Interruption time > t ms, the WTRU may be configured to delay handover to the target cell until a later time if RSRP with the source cell is above a threshold.

[0254] [WTRU determines applicability of AI / ML operation]

[0255] A WTRU may determine the applicability of the AI / ML operation which may include determining whether the one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the source cell are supported by the target cell. In one embodiment, such determination may be based on implicit information that may be shared as part of the handover configuration, e.g., based on target cell frequency, bandwidth part, reference signals from the targetcell, etc. In another embodiment, such determination based be based on explicit information which may include any AI / ML related information that may be included in the handover (re)configuration.

[0256] According to an embodiment, the WTRU may determine the applicability of the AI / ML operation for all AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the WTRU. In another embodiment, the WTRU may only determine the applicability of the AI / ML operation for AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the currently serving source gNB. In another embodiment, the WTRU may assume that the list of AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the currently serving source gNB will be supported by the target gNB selected by the network for handover and only determine AI / ML applicability for AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the WTRU but not supported by the currently serving source gNB.

[0257] According to another embodiment, the WTRU may be configured with a list of AI / ML (sub)functionality(ies) and / or (sub) use case(s) for which to check for AI / ML applicability. For example, the WTRU may be configured with a list of ‘baseline’ versus ‘optional’ AI / ML (sub)functionality(ies) and / or (sub) use case(s) and the WTRU may be configured to only determine the applicability of the ‘baseline’ AI / ML (sub)functionality(ies) and / or (sub) use case(s). For example, an ‘baseline’ AI / ML (sub)functionality and / or (sub) use case may be one where the legacy non-AI / ML (sub)functionality and / or (sub) use case is not configured. In one example, it may be mandatory for the WTRU to check the applicability of the baseline AI / ML (sub)functionality(ies) and / or (sub) use case(s) and only check the applicability of any other AI / ML (sub)functionality(ies) and / or (sub) use case(s) in an opportunistic way, e.g., if after checking applicability of the baseline AI / ML (sub)functionality(ies) and / or (sub) use case(s) there is still some remaining time in the Handover Interruption Time (HIT) or if the remaining timer in the HIT is above a preconfigured threshold, the WTRU may determine the applicability of non- baseline AI / ML (sub)functionality(ies) and / or (sub) use case(s).

[0258] According to any embodiment, the WTRU may receive an indication from the network to assist the WTRU in determining applicability of the AI / ML operation. Such indication may include any one or more of:

[0259] indication to inform the WTRU that the set of AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the target cell matches the set of AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the source cell;

[0260] flag / indication to only check a subset of AI / ML (sub)functionality(ies) and / or (sub) use case(s) that may be enabled at the WTRU, for e.g., that subset may correspond to the list of ‘baseline’ AI / ML (sub)functionality(ies) and / or (sub) use case(s);

[0261] list of AI / ML (sub)functionality(ies) and / or (sub) use case(s) to check for applicability;

[0262] the granularity of such indication may vary, for e.g., it may be at feature group (FG) level and / or feature level and / or functionality level and / or sub-functionality level and / or use case level and / or sub use case level and / or type of any of the aforementioned levels.

[0263] [WTRU action based on applicability of AI / ML operation determination]

[0264] If the AI / ML operation is applicable, i.e., all or a subset of the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported at the source cell are also supported at the target cell, the WTRU may send a confirmation message to the source gNB to indicate that it can execute the handover. Such a confirmation message may trigger the source cell to release the WTRU. In one embodiment, the source cell may not release the WTRU until reception of the confirmation message from the WTRU:

[0265] for e.g., the subset of AI / ML (sub)functionality(ies) and / or (sub) use case(s) that needs to be supported in order for the WTRU to send the confirmation message may correspond to the ‘baseline’ AI / ML (sub)functionality(ies) and / or (sub) use case(s);

[0266] for e.g., the subset of AI / ML (sub)functionality(ies) and / or (sub) use case(s) that needs to be supported in order for the WTRU to send the confirmation message may be configured in the WTRU and / or sent to the WTRU from the source cell as part of the handover command.

[0267] The WTRU may complete the handover process by sending the RRCReconfigurationComplete message to target cell. The WTRU may send additional information to the target cell as part of the handover complete message, for e.g., in the case where handover is executed with only a subset of AI / ML (sub)functionality(ies) and / or (sub) use case(s) since only that subset is also applicable to the target cell. The WTRU may optionally also indicate one or more of the following to the target cell A)-I):

[0268] A) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the source cell but not supported by the target cell;

[0269] B) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) not supported by the source cell but supported by the target cell;

[0270] C) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the WTRU;

[0271] D) The AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the WTRU but will be activated at later time. Indication may also optionally include expected time when AI / ML (sub)functionality(ies) and / or (sub) use case(s) will be activated;

[0272] E) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) currently not activated and / or supported by the target cell for which the WTRU is using legacy mechanism as a substitute;

[0273] F) the AI / ML (sub)functionality(ies) and / or (sub) use case(s) that were not activated and / or supported by the source cell for which the WTRU was using legacy mechanism as a substitute

[0274] G) any of the aforementioned AI / ML (sub)functionality(ies) and / or (sub) use case(s) may be indicated, for e.g., in terms of AI / ML (sub)functionality(ies) IDs and / or (sub) use case(s) IDs.;

[0275] H) associated criticality of being unable to activate the aforementioned list of AI / ML (sub)functionality(ies) and / or (sub) use case(s), for e.g., each (sub)functionality and / or (sub) use case could have a criticality number attached to it;

[0276] I) Time delay when the WTRU expects to be able to activate any of the aforementioned list of AI / ML (sub)functionality(ies) and / or (sub) use case(s) I1)-I3):

[0277] I1) for e.g., prior to the handover, it is possible that there were no UEs being served by the target cell that had some AI / ML (sub)functionality(ies) and / or (sub) use case(s) activated such that the target cell did not register these AI / ML (sub)functionality(ies) and / or (sub) use case(s) as ‘available’ at the target cell;

[0278] I2) for e.g., the WTRU may send the delay information to the target cell to inform the target cell that activation of these AI / ML (sub)functionality(ies) and / or (sub) use case(s) is expected at a given time. This may consist of one delay information for all the AI / ML (sub)functionality(ies) and / or (sub) use case(s) currently deactivated at the target cell but that were activated at the source cell or different delay information for each respective AI / ML (sub)functionality and / or (sub) use case;

[0279] I3) according to an embodiment, the WTRU may have been preconfigured with the delay information, e.g., for functionality X, allow for t1 ms interval for activation in a target cell following completion of handover; for functionality Y, allow for t2 ms interval for activation in a target cell following completion of handover. In another embodiment, the WTRU may have received such information from the source cell before the handover.

[0280] If the AI / ML operation is not applicable at the target cell, i.e., at least one of the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported at the source cell is not supported at the target cell, the WTRU may be configured with conditions on whether or not to execute handover to the target cell. Such conditions may, for e.g., be the RSRP w.r.t. the source cell. For example, if the RSRP with the source cell is above a preconfigured threshold, the WTRU may determine to not execute handover or delay handover for a preconfigured time period (provided the RSRP with the source cell remains above the preconfigured threshold throughout the time period). If theWTRU determines to delay and / or cancel handover execution to the target cell, the WTRU may send an indication to the source cell to indicate that it cannot transfer to the target cell. Such an indication may, for e.g., be a decline to transfer or handover to the target cell without support for some AI / ML (sub)functionality(ies) and / or (sub) use case(s). In one embodiment, the WTRU may request for a AI / ML model switch and / or model download from the source cell to replace the unavailable AI / ML (sub)functionality(ies) at the target cell. Until the new AI / ML model is received, the WTRU may not execute handover to the target cell.

[0281] If the AI / ML operation is not applicable at the target cell but the measured RSRP with the source cell is below a preconfigured threshold, the WTRU may not be allowed to delay and / or decline handover command from the network. The WTRU may have to complete the handover command regardless of the lack of support for the at least one AI / ML (sub)functionality(ies) and / or (sub) use case(s). In such a case, the WTRU may fall back to legacy procedures for the concerned AI / ML (sub)functionality(ies) and / or (sub) use case(s). In one embodiment, the WTRU may be configured with a time window during which to execute handover. If the AI / ML operation is not applicable at the target cell and the measured RSRP with the source cell is below a preconfigured threshold but expected to exceed the threshold for handover at a future time instant within the preconfigured time window, the WTRU may delay handover and send an indication of the delay window to the source cell. In another embodiment, if the AI / ML operation is not applicable at the target cell and the measured RSRP with the source cell is below a preconfigured threshold and expected to remain below the handover threshold throughout the preconfigured time window, the WTRU may execute handover to the target cell and fall back to legacy procedures for the unsupported AI / ML (sub)functionality(ies) and / or (sub) use case(s) by the target cell.

[0282] According to an embodiment, if the AI / ML operation is not applicable at the target cell but the measured RSRP with the source cell is below a preconfigured threshold and / or expected to remain below such threshold though the preconfigured window to execute the handover, the WTRU may declare a reconfiguration failure.

[0283] Handover: Dynamic Capability Indication: Summary

[0284] First exemplary embodiment

[0285] The following is a summary of WTRU-network node behavior related to dynamic capability indication according to first exemplary embodiments. Details of these embodiments are found in the related section.

[0286] A WTRU may not be able to support AI / ML operations across different features / functionalities at once. Activation of AI / ML operation for one feature / functionality mayresult in deactivation of another feature / functionality. From a procedure perspective, it is interesting to understand:

[0287] How activation of AI for one functionality impacts AI / ML capability / operation of another functionality;

[0288] How model switching or fallback to legacy for one functionality impacts AI / ML capability / operation of another functionality;

[0289] How to define mandatory vs optional capabilities and how it impacts WTRU behavior;

[0290] How to indicate dynamic capabilities when the model becomes applicable (e.g., appropriate channel conditions / NW configuration, etc), or usage of model become possible (e.g., availability of processing capability);

[0291] WTRU receives activation indication for a WTRU-sided model from a third party that has no knowledge of UL and DL traffic. Transmission of model inference output requires resources over the Uu link.

[0292] Therefore, according to embodiments described in detail in the dedicated section, AI / ML capability is dynamic, e.g., a function of available processing capability and storage which changes dynamically (even with the same set of supported functionalities / models). A WTRU is configured with priorities for functionalities to activate and / or rules to select the functionalities to activate. Includes all variable conditions (WTRU processing capability, storage, radio conditions).

[0293] According to an embodiment, a WTRU, A)-G):

[0294] A) the WTRU receives from network / third party configuration including priority of AI / ML functionality to support. (e.g., BM Case 1 = priority #1, CSI compression = priority #2, etc.) and minimum periodicity / duration of assessment (e.g., timer / slots / periodicities) and reporting configuration (e.g., reporting content + triggers); E.g., WTRU only reports to network if it cannot activate first priority functionality as determined by network;

[0295] B) the WTRU receives activation indication from NW / third party for functionalities / models;

[0296] C) the WTRU determines the functionality(ies) it can support, e.g., based on priority and / or applicable channel conditions or available processing capability or storage. E.g., Processing capability is less than threshold;

[0297] D) the WTRU activates AI / ML functionality(ies) for the determined functionality(ies) among the activated functionalities from the network.

[0298] E) the WTRU sends indication to NW if it cannot activate entire set of functionalities / models as requested by NW. For example, includes the list of activated AI / ML functionalities.

[0299] F) the WTRU at configured periodic instances (e.g., determined from configured duration of assessment or based on periodicity), the WTRU performs assessment of supported AI / ML functionalities F1)-F2):

[0300] F1) e.g., given the current computational resources and / or storage, WTRU determines whether it can update the currently activated AI / ML functionalities;

[0301] F2) the WTRU activates / deactivates functionality and / or model in increasing / decreasing priority level (e.g., stepwise degradation) based on F2a)-F2b):

[0302] F2a) accuracy of the model; or

[0303] F2b) priority of the AI / ML functionality.

[0304] G) the WTRU sends indication to NW of updated list of activated AI / ML functionalities.

[0305] Second exemplary embodiment

[0306] The following is a summary of WTRU-network node behavior related to dynamic capability indication according to second exemplary embodiments. Details of these embodiments are found in the related section.

[0307] It is noted that the list of WTRU capabilities gets longer with every release of the related 3GPP specifications. When the set of features that the WTRU has to report on gets too large, this may result in the WTRU failing to generate the UECapabilityInformation message in the right structure. It may also result in the NW failing to properly decode the lengthy capability indication from the WTRU (lengthy messages have a higher probability to become corrupted at reception).

[0308] Summary of embodiment: WTRU does not report on all possible combinations of what it can support.

[0309] Therefore, a WTRU may A)-E):

[0310] A) the WTRU may report to network capability including AI / ML related capability (initial high level capability);

[0311] B) the WTRU may receive activation for functionality / model, e.g., model #m1, functionality #f1, etc. (e.g., from network or third party);

[0312] C) the WTRU may activate functionality / model, e.g., model #m1, functionality #f1;

[0313] D) the WTRU may receive activation for functionality / model, e.g., model #m2, functionality #f2. (e.g., from network or third party);

[0314] E) the WTRU may determine if it can support the latest activation request from the NW concurrently with other activated functionalities / models E1)-E2):

[0315] E1) if yes, WTRU completes latest activation request from network;

[0316] E2) if not, WTRU sends indication to network that indicates incompatibility with a currently supported functionality / model (e.g., indicating the functionalities / models that arecausing the conflict, the reason for the conflict, e.g., processing capacity limitation, power limitation, etc.,)

[0317] Handover: Dynamic Capability Indication: Detailed Operation

[0318] The following is a description of the detailed operation of WTRU-network node behavior related to dynamic capability indication, according to embodiments.

[0319] [WTRU receives configuration to assist WTRU in determining AI / ML functionality to support and associated reporting configuration]

[0320] The WTRU may receive (e.g., from NW / gNB / third party) configuration to assist the WTRU in determining the one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s) to support, which may include any one or more of the following A)-C):

[0321] A) priority of AI / ML functionality to support A1)-A4):

[0322] A1) e.g., Beam Management (BM) = priority #1, CSI = priority #2, Positioning = priority #3;

[0323] A2) e.g., BM spatial prediction = priority #1, CSI compression = priority #2, BM temporal prediction = priority #3, CSI prediction = priority #4, etc.);

[0324] A3) for example, the WTRU may receive a complete list of all AI / ML enabled (sub)functionalities and / or (sub)use cases as supported by the network and the corresponding priority to enable each (sub)functionality and / or (sub)use case;

[0325] A4) for example, the priority may be a function of radio conditions;

[0326] B) rules / conditions to determine the AI / ML functionality to support, which may be dependent on any one or more of the following B1)-B4):

[0327] B1) WTRU capabilities, e.g., if WTRU supports full duplex, activate AI / ML enabled spatial beam prediction as a first priority, otherwise, activate AI / ML enabled temporal beam prediction as a first priority;

[0328] B2) Model type, e.g., processing required for inference may be a function of the model type (e.g., DNN versus UNN versus CNN versus RNN etc.).

[0329] B3) WTRU traffic type;

[0330] B4) measurements. For example, a WTRU may be configured with resources on which to perform at least one measurement. The WTRU may compare the at least one measurement to at least one threshold. The at least one threshold may be configurable. If the at least one measurement is greater or less than the at least one threshold, the WTRU may determine to activate a certain AI / ML functionality. Activation of an AI / ML functionality may be associated with at least one measurement threshold. The measurement may include at least one of B4a)-B4m):

[0331] B4a) position, velocity, direction of mobility;

[0332] B4b) L1 or L3 measurement such as RSRP, RSSI, RSRQ, SINR, CO, RI, CQI, PMI, LI;

[0333] B4c) interference measurement;

[0334] B4d) Doppler, Doppler spread, delay spread, number of multipaths;

[0335] B4e) coherence time, coherence bandwidth;

[0336] B4f) beam direction, beamwidth, set of beams (e.g. elements in the set of the cardinality of the set);

[0337] B4g) rate of successful channel access attempts, e.g., the WTRU may keep track of the number / percentage of successful LBT attempts over a period of time. The period of time may be dynamically determined (e.g. sliding window). E.g., the number / percentage of successful LBT attempts falling below a threshold may determine the AI / ML (sub)functionality(ies) and / or (sub) use case(s) that the WTRU supports;

[0338] B4h) rate of NACKs. For example, a WTRU may maintain a measurement of the number or percentage of NACKs over a period of time. The period of time may be dynamically determined (e.g. sliding window);

[0339] B4i) path loss, e.g., if path loss > X, activate AI / ML enabled spatial beam prediction as a first priority, if X < path loss < Y, activate AI / ML enabled temporal beam prediction as a first priority;

[0340] B4j) whether the path is line of sight or non-line of sight;

[0341] B4k) throughput;

[0342] B4l) BLER;

[0343] B4m) latency.

[0344] C) comparison with legacy function, e.g., the WTRU may compare the performance of the AIML model / AIML enabled functionality with the expected performance of using a baseline (e.g. non-AIML) method to perform the function. A WTRU may determine a rate of error events from using the AIML model / AIML enabled functionality. An error event may be determined when the difference between the output of the AIML model and a baseline method is greater than or less than a threshold value. The WTRU may determine the priority of the AIML model / AIML enabled functionality if the rate of error events is greater than or less than a threshold. The WTRU may determine the priority / order of which AI / ML enabled functionality to activate if the difference between the output of the AIML model and the baseline model is greater than or less than a threshold.

[0345] The WTRU may receive (e.g., from NW / gNB / third party) configuration on when / if to perform assessment / ordering of priority of AI / ML (sub)functionality(ies) and / or (sub) use case(s).For example, the WTRU may be configured to perform the assessment on any one or more of the following basis:

[0346] periodically, with a configured periodicity;

[0347] semi-periodically;

[0348] aperiodically / Event-triggered;

[0349] The WTRU may receive (e.g., from NW / gNB / third party) configuration on when / if to report the result of the aforementioned assessment. For example, a WTRU may be configured to report the result of the assessment on any one or more of the following basis A)-E):

[0350] A) following every assessment;

[0351] B) periodically, with a configured periodicity;

[0352] C) at the expiry of a timer;

[0353] D) semi-periodically;

[0354] E) aperiodically / Event-triggered / Condition(s)-based:

[0355] E1) e.g., WTRU only reports to NW if it cannot activate first priority functionality as determined by network;

[0356] E2) e.g., WTRU only reports to NW if it cannot activate first N priority functionalities as determined by network, where N may be any integer number;

[0357] E3) e.g., WTRU only reports to NW if at cell edge;

[0358] E4) e.g., WTRU only reports to NW if it cannot activate first priority functionality as determined by network when at cell edge.

[0359] [WTRU determines (sub)functionality(ies) and / or (sub) use case(s) to support]

[0360] The WTRU may determine the one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s) to support based on one or more of A)-E):

[0361] A) Priority A1)-A2):

[0362] A1) As indicated by the NW;

[0363] A2) As determined by the WTRU based on rules / configuration received from the NW;

[0364] B) Applicable conditions B1)-B2):

[0365] B1) ‘Applicable conditions’ or ‘applicability conditions’ may refer to the fact that one AI / ML functionality / model ‘applicable’ under a certain set of configurations / scenarios / datasets may no longer be ‘applicable’ under another set of configurations / scenarios / datasets.

[0366] B2) Examples of applicable conditions may include:

[0367] B2a) applicable scenario, e.g., channel conditions, channel model, carrier frequencies, WTRU distribution within a cell, WTRU mobility levels, etc.;

[0368] B2b) applicable configuration, e.g., WTRU / gNB configuration, bandwidths, bandwidth parts, antenna configuration, antenna port layout, etc.;

[0369] B2c) applicable site, e.g., location, positioning, tracking area where the WTRU is in, attributes of the site where the model was trained, etc.;

[0370] B2c1) for e.g., if the model was trained in a rural area, deployment / use of the model for inference in an urban area may not be suitable;

[0371] B2c2) for e.g., at cell edge, to ensure a smoother transition with a neighbor cell, the WTRU may request for and receive reference signals (e.g., CSI-RS, PRS) from a neighbor cell prior to the handover procedure.

[0372] C) availability / status of WTRU internal condition (e.g., processing capability, storage, memory, battery, other hardware limitations), e.g., if processing capability < a configured threshold, WTRU may determine that it can support a certain set of (sub)functionality(ies) and / or (sub) use case(s) versus when processing capability > a configured threshold, where the WTRU may determine that it can support a different set of (sub)functionality(ies) and / or (sub) use case(s);

[0373] D) the WTRU may perform an assessment to determine the one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s) to support at the expiry of a timer (e.g., based on a configured periodicity), e.g., given the current computational resources and / or storage, WTRU determines whether it can update the currently supported AI / ML functionalities;

[0374] E) WTRU may deactivate AI / ML (sub)functionality(ies) and / or AI / ML (sub) use case(s) and / or AI / ML model(s) in decreasing priority level (stepwise degradation) until the WTRU may fallback to the legacy mechanism / operation.

[0375] E1) less accurate model; or

[0376] E2) less prioritized functionality.

[0377] [WTRU sends indication to NW]

[0378] According to an embodiment, the WTRU may send an indication to the NW, e.g., if it cannot activate the entire set of functionalities / models as requested by the NW. For example, the indication may include the following:

[0379] the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the WTRU;

[0380] the AI / ML (sub)functionality(ies) and / or (sub) use case(s) supported by the WTRU but will be activated at later time. Indication may also optionally include expected time when AI / ML (sub)functionality(ies) and / or (sub) use case(s) will be activated;

[0381] the AI / ML (sub)functionality(ies) and / or (sub) use case(s) currently not activated and / or supported by the WTRU for which the WTRU is using legacy mechanism as a substitute;

[0382] any of the aforementioned AI / ML (sub)functionality(ies) and / or (sub) use case(s) may be indicated, for e.g., in terms of AI / ML (sub)functionality(ies) IDs and / or (sub) use case(s) IDs;

[0383] associated criticality of being unable to activate the aforementioned list of AI / ML (sub)functionality(ies) and / or (sub) use case(s), for e.g., each (sub)functionality and / or (sub) use case could have a criticality number attached to it;

[0384] time delay when the WTRU expects to be able to activate any of the aforementioned list of AI / ML (sub)functionality(ies) and / or (sub) use case(s);

[0385] reason why it cannot support one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s), e.g., WTRU may send indication to network that indicates incompatibility with a currently supported functionality / model (e.g., indicating the functionalities / use cases / models that are causing the conflict, the reason for the conflict, e.g., processing capacity limitation, power limitation, storage limitation, etc.).

[0386] The WTRU may send such indication to the NW anytime it determines that it can or cannot support one or more AI / ML (sub)functionality(ies) and / or (sub) use case(s), on following an activation request from the NW to activate an AI / ML-based functionality / use case.

[0387] FIG.5 is a flow chart of a method 500 according to an embodiment.

[0388] The method may be implemented by a wireless transmit-receive unit, WTRU, in a network. The method comprises:

[0389] In 501, receiving, from the network, configuration information related to handover of the WTRU from a source network node to a target network node;

[0390] In 502, determining that artificial intelligence / machine learning, AI / ML, operation of the WTRU for at least one AI / ML functionality cannot be supported by the WTRU at the target network node;

[0391] In 503, configuring the WTRU for operating the WTRU at the target network node in a non-AI / ML operation mode; and

[0392] In 504, sending a handover complete message to the target network node, and indicating to the target network node that the WTRU is configured to operate in the non-AI / ML operation mode.

[0393] According to an embodiment of the method 500, the determining that AI / ML operation of the WTRU for at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node is based on AI / ML information related to the at least one AI / ML functionality that is comprised in the received configuration information related to handover of the WTRU from the source network node to the target network node.

[0394] According to an embodiment of the method, the determining that AI / ML operation of the WTRU for at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node is based on at least one of: a cell frequency of the target network node; a bandwidth part allocated to the target network node, reference signals received from the target network node.

[0395] According to an embodiment of the method, the indicating to the target network node that the WTRU is configured to operate in the non-AI / ML operation mode is done by comprising an indication that the WTRU is configured to operate in the non-AI / ML operation mode in the handover complete message.

[0396] According to an embodiment of the method, the indicating to the target network node that the WTRU is configured to operate in the non-AI / ML operation mode is done by comprising an indication that the WTRU is configured to operate in the non-AI / ML operation mode in a radio resource control, RRC, message sent subsequently to the sending of the handover complete message.

[0397] According to an embodiment of the method, the at least one AI / ML functionality is comprised in AI / ML related information that is comprised in the received configuration information related to handover of the WTRU from the source network node to the target network node.

[0398] There is also disclosed an embodiment of a wireless transmit-receive unit, WTRU, in a network, the WTRU comprising at least one processor, the at least one processor being configured to:

[0399] receive, from the network, configuration information related to handover of the WTRU from a source network node to a target network node;

[0400] determine that artificial intelligence / machine learning, AI / ML, operation of the WTRU for at least one AI / ML functionality cannot be supported by the WTRU at the target network node;

[0401] configure the WTRU for operating the WTRU at the target network node in a non-AI / ML operation mode; and

[0402] send a handover complete message to the target network node, and indicate to the target network node that the WTRU is configured to operate in the non-AI / ML operation mode.

[0403] According to an embodiment the at least one processor is configured to determine that AI / ML operation of the WTRU for at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node, based on AI / ML information related to the at least one AI / ML functionality that is included comprised in thereceived configuration information related to handover of the WTRU from the source network node to the target network node.

[0404] According to an embodiment, the at least one processor is configured to determine that AI / ML operation of the WTRU for at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node, based on at least one of: a cell frequency of the target network node; a bandwidth part allocated to the target network node, reference signals received from the target network node.

[0405] According to an embodiment, the at least one processor is configured to indicate to the target network node that the WTRU is configured to operate in the non-AI / ML operation mode by comprising in the handover complete message, an indication that the WTRU is configured to operate in the non-AI / ML operation mode.

[0406] According to an embodiment, the at least one processor is configured to indicate to the target network node that the WTRU is configured to operate in the non-AI / ML operation mode by comprising an indication that the WTRU is configured to operate in the non-AI / ML operation mode in a radio resource control, RRC, message sent subsequently to the send of the handover complete message.

[0407] According to an embodiment, the at least one AI / ML functionality is comprised in AI / ML related information that is comprised in the received configuration information related to handover of the WTRU from the source network node to the target network node.FIG. 6 is a flow chart of a method according to an embodiment.

[0408] FIG.6 is a flow chart of a method 600 according to an embodiment.

[0409] The method may be implemented by a wireless transmit-receive unit, WTRU, in a network, and may comprise:

[0410] In 601, receiving, from the network, configuration information related to handover of the WTRU from a source network node to a target network node;

[0411] In 602, determining that reference signal received power, RSRP, with the source network node is greater than a configured RSRP value / range;

[0412] In 603, determining that artificial intelligence / machine learning, AI / ML, operation of the WTRU for at least one AI / ML functionality cannot be supported by the WTRU at the target network node; and

[0413] In 604, sending an indication to the source network node indicating that the WTRU declines the handover to the target network node.

[0414] According to an embodiment of the method 600, the determining that AI / ML operation of the WTRU for at least one AI / ML functionality of the WTRU at the target network node cannotbe supported by the WTRU at the target network node is based on AI / ML information related to the at least one AI / ML functionality that is comprised in the received configuration information related to handover of the WTRU from the source network node to the target network node.

[0415] According to an embodiment of the method 600, the configuration information comprises information for accessing the target network node and the RSRP value / range.

[0416] According to an embodiment of the method 600, the configuration information comprises a time window for activation of the AI / ML operation of the WTRU at the target network node, the determining that AI / ML operation of the WTRU for the at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node comprising taking into account the time window for activation of the AI / ML operation of the WTRU at the target network node.

[0417] There is also disclosed an embodiment of a wireless transmit-receive unit, WTRU, in a network, the WTRU comprising at least one processor, the at least one processor being configured to:

[0418] receive, from the network, configuration information related to handover of the WTRU from a source network node to a target network node;

[0419] determine that reference signal received power, RSRP, with the source network node is greater than a configured RSRP value / range;

[0420] determine that artificial intelligence / machine learning, AI / ML, operation of the WTRU for at least one AI / ML functionality cannot be supported by the WTRU at the target network node; and

[0421] send an indication to the source network node indicating that the WTRU declines the handover to the target network node.

[0422] According to an embodiment, the at least one processor is configured to determine that AI / ML operation of the WTRU for at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node based on AI / ML information related to the at least one AI / ML functionality that is comprised in the received configuration information related to handover of the WTRU from the source network node to the target network node.

[0423] According to an embodiment, the configuration information comprises information for accessing the target network node and the RSRP value / range.

[0424] According to an embodiment, the at least one processor is configured to determine that AI / ML operation of the WTRU for the at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node, taking into accounta time window for activation of the AI / ML operation of the WTRU at the target network node, the configuration information comprising the time window.

[0425] FIG.7 is a flow chart of a method 700 according to an embodiment.

[0426] The method may be implemented by a wireless transmit-receive unit, WTRU, in a network. The method may comprise:

[0427] In 701, receiving, from the network, configuration information comprising information relative to at least one AI / ML functionality to support by the WTRU;

[0428] In 702, receiving activation indication from the network related to activation of at least one AI / ML functionality by the WTRU;

[0429] In 703, determining at least one AI / ML functionality for which the activation indication is received and that can be supported by the WTRU, and activating the at least one AI / ML functionality for which the activation indication is received and that can be supported by the WTRU; and

[0430] In 704, sending an indication to the network, the indication comprising information relative to the activated at least one AI / ML functionality.

[0431] According to an embodiment of the method 700, the configuration information comprises at least one of: priority of the at least one AI / ML functionality to support by the WTRU; minimum periodicity / duration of assessment of at least one AI / ML functionality supported by the WTRU; reporting configuration for sending the indication.

[0432] According to an embodiment of the method 700, the configuration information comprises priority of the at least one AI / ML functionality to support by the WTRU and reporting configuration, and wherein the WTRU reports to the network according to the reporting configuration when the WTRU cannot activate a first priority AI / ML functionality for which activation information is received.

[0433] According to an embodiment of the method 700, the configuration information comprises a minimum periodicity / duration of assessment of at least one functionality supported by the WTRU, the method comprising, according to the minimum periodicity / duration of the assessment:

[0434] performing assessment of supported AI / ML functionalities;

[0435] activation of at least one supported AI / ML functionality and deactivation of non- supported AI / ML functionalities;

[0436] sending the indication to the network, the indication comprising information relative to the activated at least one AI / ML functionality.

[0437] There is also disclosed a wireless transmit-receive unit, WTRU, in a network, the WTRU comprising at least one processor, the at least one processor being configured to:

[0438] receive, from the network, configuration information comprising information relative to at least one AI / ML functionality to support by the WTRU;

[0439] receive activation indication from the network related to activation of at least one AI / ML functionality by the WTRU;

[0440] determine at least one AI / ML functionality for which the activation indication is received and that can be supported by the WTRU, and activating the at least one AI / ML functionality for which the activation indication is received and that can be supported by the WTRU; and

[0441] send an indication to the network, the indication comprising information relative to the activated at least one AI / ML functionality.

[0442] According to an embodiment, the configuration information comprises at least one of: priority of the at least one AI / ML functionality to support by the WTRU; minimum periodicity / duration of assessment of at least one AI / ML functionality supported by the WTRU; reporting configuration for sending the indication.

[0443] According to an embodiment, the at least one processor is configured to report to the network according to reporting configuration when the WTRU cannot activate a first priority AI / ML functionality for which activation information is received, the configuration information comprising priority of the at least one AI / ML functionality to support by the WTRU and the reporting configuration.

[0444] According to an embodiment, the configuration information comprises a minimum periodicity / duration of assessment of at least one functionality supported by the WTRU, the at least one processor being configured to, according to the minimum periodicity / duration of the assessment:

[0445] perform assessment of supported AI / ML functionalities;

[0446] activate of at least one supported AI / ML functionality and deactivation of non- supported AI / ML functionalities;

[0447] send the indication to the network, the indication comprising information relative to the activated at least one AI / ML functionality.

[0448] Conclusion

[0449] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, orinstruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems.

[0450] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of wireless communication capable devices, (e.g., radio wave emitters and receivers). However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves.

[0451] It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, single image and / or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "WTRU", the term "remote" and / or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and / or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and / or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs.1A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0452] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, WTRU, terminal, base station, RNC, or any host computer.

[0453] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only, and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0454] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed."

[0455] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0456] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understoodthat the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0457] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0458] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and / or systems and / or other technologies described herein may be effected (e.g., hardware, software, and / or firmware), and the preferred vehicle may vary with the context in which the processes and / or systems and / or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and / or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and / or firmware.

[0459] The foregoing detailed description has set forth various embodiments of the devices and / or processes via the use of block diagrams, flowcharts, and / or examples. Insofar as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, it will be understood by those within the art that each function and / or operation within such block diagrams, flowcharts, or examples may be implemented, individually and / or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and / or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein may be distributed as a program productin a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and / or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0460] Those skilled in the art will recognize that it is common within the art to describe devices and / or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into data processing systems. That is, at least a portion of the devices and / or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and / or control systems including feedback loops and control motors (e.g., feedback for sensing position and / or velocity, control motors for moving and / or adjusting components and / or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing / communication and / or network computing / communication systems.

[0461] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and / orphysically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components.

[0462] With respect to the use of substantially any plural and / or singular terms herein, those having skill in the art can translate from the plural to the singular and / or from the singular to the plural as is appropriate to the context and / or application. The various singular / plural permutations may be expressly set forth herein for sake of clarity.

[0463] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and / or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A,B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Further, the terms "any of" followed by a listing of a plurality of items and / or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and / or "any combination of multiples of" the items and / or the categories of items, individually or in conjunction with other items and / or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

[0464] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0465] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0466] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, ¶ 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

Claims

CLAIMS What is claimed is:

1. A method, implemented by a wireless transmit-receive unit, WTRU, in a network, wherein the method comprises: receiving, from the network, configuration information related to handover of the WTRU from a source network node to a target network node; determining that reference signal received power, RSRP, with the source network node is greater than a configured RSRP value / range; determining that artificial intelligence / machine learning, AI / ML, operation of the WTRU for at least one AI / ML functionality cannot be supported by the WTRU at the target network node; and sending an indication to the source network node indicating that the WTRU declines the handover to the target network node.

2. The method of claim 1, wherein the determining that AI / ML operation of the WTRU for at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node is based on AI / ML information related to the at least one AI / ML functionality that is comprised in the received configuration information related to handover of the WTRU from the source network node to the target network node.

3. The method of claim 1, wherein the configuration information comprises information for accessing the target network node and the RSRP value / range.

4. The method of claim 1, wherein the configuration information comprises a time window for activation of the AI / ML operation of the WTRU at the target network node, the determining that AI / ML operation of the WTRU for the at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node comprising taking into account the time window for activation of the AI / ML operation of the WTRU at the target network node.

5. A wireless transmit-receive unit, WTRU, in a network, the WTRU comprising at least one processor, the at least one processor being configured to: receive, from the network, configuration information related to handover of the WTRU from a source network node to a target network node; determine that reference signal received power, RSRP, with the source network node is greater than a configured RSRP value / range; determine that artificial intelligence / machine learning, AI / ML, operation of the WTRU for at least one AI / ML functionality cannot be supported by the WTRU at the target network node; and send an indication to the source network node indicating that the WTRU declines the handover to the target network node.

6. The WTRU of claim 5, wherein the at least one processor is configured to determine that AI / ML operation of the WTRU for at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node based on AI / ML information related to the at least one AI / ML functionality that is comprised in the received configuration information related to handover of the WTRU from the source network node to the target network node.

7. The WTRU of claim 5, wherein the configuration information comprises information for accessing the target network node and the RSRP value / range.

8. The WTRU of claim 5, wherein the at least one processor is configured to determine that AI / ML operation of the WTRU for the at least one AI / ML functionality of the WTRU at the target network node cannot be supported by the WTRU at the target network node, taking into account a time window for activation of the AI / ML operation of the WTRU at the target network node, the configuration information comprising the time window.

Images