Methods for data collection for ai / ML life cycle management

Abstract

A wireless transmit / receive unit (WTRU) may receive configuration information. The configuration information may comprise one or more paging identities, one or more actions associated with each of the one or more paging identities, one or more configurations for performing the one or more actions, one or more conditions for starting the one or more actions, and / or one more conditions for stopping the one or more actions. The one or more actions may be associated with an AI / ML model. The WTRU may monitor the one or more conditions for starting the one or more actions. The WTRU may determine that the one or more conditions for starting the one or more actions are satisfied. The WTRU may start each of the one or more actions whose conditions for starting are satisfied. The WTRU may determine whether one or more conditions for stopping the one or more actions are satisfied.

Description

METHODS FOR DATA COLLECTION FOR AI / ML LIFE CYCLE MANAGEMENTCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 572,497, filed on April 1, 2024, the entire contents of which are incorporated herein by reference.BACKGROUND

[0002] The Third Generation partnership Project (3GPP) has been studying artificial intelligence or machine learning (AI / ML) related enhancements even before release (Rel)-18. However, the focus was mainly on enabling network automation and / or optimization (e.g., self-optimizing networks (SON), and / or mobility drive test (MDT), etc.) and / or associated data collection.

[0003] In Rel-17, a radio access network (RAN)3-led study on further enhanced data collection investigated the high-level principles of RAN intelligence enabled by Al. Based on this study, Rel-18 RAN3 work was undertaken. The work focused on enhancements to data collection and / or signaling to support AI / ML based network energy savings and / or load balancing and mobility optimizations.

[0004] In RAN1, a study on AI / ML for new radio (NR) air interface was undertaken in rel-18 (e.g., RP- 221348) and the outcome of the study is captured in the technical report. The following three main use cases were investigated in that study: channel state information (CSI) related enhancements: CSI compression (e.g., frequency domain), time-domain prediction, etc.; beam management (BM): temporal prediction (predicting of a beam’s quality based on earlier beam quality), spatial prediction (prediction of a certain beam’s quality based on the quality of other beams), etc.; and / or positioning: direct AI / ML positioning (e.g., fingerprinting) and / or AI / ML assisted positioning (e.g., the output of the AI / ML model inference is a new measurement and / or an enhancement of an existing measurement).

[0005] Of these three use cases, the BM and positioning have been standardized in Rel-19. The CSI use case is undergoing further study.

[0006] A Rel-19 RAN2 study item on AI / ML mobility enhancements has also been approved with the main objective of studying enhancements for network triggered L3-based handover (e.g., handover triggered by the network based on information received by the UE, such as measurement reports). Though not explicitly stated in the study item objective, one such valuable information may be user equipment (UE), also known as a wireless transmit / receive unit (WTRU), trajectory information. The network may use a WTRU’s trajectoryinformation to optimize the HO of the WTRU (e.g., reserve resources at target cells / nodes on time, and / or send the HO or CHO command to the WTRU on time, etc.).SUMMARY

[0007] A wireless transmit / receive unit (WTRU) may receive configuration information. The configuration information may comprise one or more paging identities, one or more actions associated with each of the one or more paging identities, one or more configurations for performing the one or more actions, one or more conditions for starting the one or more actions, and / or one more conditions for stopping the one or more actions. The one or more actions may be associated with an artificial intelligence or machine learning (AI / ML) model. The WTRU may monitor the one or more conditions for starting the one or more actions. The WTRU may determine that the one or more conditions for starting the one or more actions are satisfied. The WTRU may start each of the one or more actions whose conditions for starting are satisfied. The WTRU may monitor the one or more conditions for stopping the one or more actions. The WTRU may determine whether one or more conditions for stopping the one or more actions are satisfied. The WTRU may stop each of the one or more actions whose conditions for stopping are satisfied. The WTRU may send a report comprising the collected data associated with the performed one or more actions.

[0008] The one or more actions comprise performing measurements, logging measurements, monitoring performance of the AI / ML model, and / or training the AI / ML model. The measurements to be performed may comprise one or more of radio signal measurements, quality of service (QoS) related measurements, handover and / or cell reselection metrics, error conditions, power and battery levels, WTRU mobility state and path measurements, and / or AI / ML model performance.

[0009] The WTRU may log measurements based on a serving cell being above a threshold. The WTRU may stop logging measurements based on the serving cell being below a threshold. The one or more configurations for performing the one or more actions may comprise one or more of measurement configurations, AI / ML model monitoring configurations, or AI / ML model training configurations.

[0010] The one or more conditions for starting the one or more actions may comprise one or more of a paging message. The paging message may comprise a paging identity associated with starting the action, and / or fulfillment of a first condition of the one or more actions. The first condition may be associated with starting the action. The one or more conditions for starting the one or more actions may comprise one or more of validity conditions, a location of the WTRU, time of day, detected cells, radio signal levels of one ormore beams, a buffer level being above a threshold, WTRU speed, available WTRU power, available WTRU storage, and / or available WTRU processing.

[0011] The one or more conditions for stopping the one or more actions may comprise one or more of a paging message. The paging message may comprise a paging identity associated with stopping the action, and / or fulfillment of a second condition of the one or more conditions for stopping the one or more actions. The second condition may be associated with stopping the action. The one or more conditions for stopping the one or more actions may comprise one or more of a location of the WTRU, time of day, duration the action has been performed, amount of data collected, a range of values of key performance indicators, a buffer level being lower than a threshold, and / or AI / ML functionality and / or model training.

[0012] The WTRU may send AI / ML capability information. The AI / ML capability information may comprise one or more of supported AI / ML functionalities, supported AI / ML models, applicability or AI / ML training conditions, processing capability, and / or memory capability. The WTRU may receive a message indicating that the one or more configurations for performing the one or more actions can be activated or deactivated. The message may activate or deactivate the one or more configurations for performing the one or more actions based on the message.

[0013] The WTRU may send, after determining that the one or more conditions for starting the one or more actions are satisfied, an indication that the one or more conditions for performing the starting the one or more actions are satisfied. The WTRU may send, after determining that the one or more conditions for stopping the one or more actions are satisfied, an indication that the one or more conditions for stopping the one or more actions are satisfied.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0016] 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. 1 A according to an embodiment.

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

[0018] FIG. 2 depicts a diagram of a functional framework for artificial intelligence or machine learning (AI / ML) for new radio (NR) air interface.

[0019] FIG. 3 depicts an example realization of monitoring conditions to start and stop performing AI / ML related actions.DETAILED DESCRIPTION

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

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

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

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

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

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

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

[0027] I n 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).

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

[0029] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e, Wireless Fidelity (WiFi), IEEE 802.16 (i.e. Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0052] Although the WTRU is described in FIGS. 1 A-1 D 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.

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

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

[0055] When using the 802.11 ac 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.

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

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

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

[0059] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, 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.11 ah, 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.

[0060] In the United States, the available frequency bands, which may be used by 802.11 ah, 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.11 ah is 6 MHz to 26 MHz depending on the country code.

[0061] FIG. 1 D 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.

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

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

[0064] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such aseNode-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.

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

[0066] The CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part 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.

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

[0068] 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 oftraffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating WTRU IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

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

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

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

[0072] 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 more emulation 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.

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

[0074] Life cycle management (LCM) of artificial intelligence or machine learning (AI / ML) may refer to all the aspects of deploying and / or properly utilizing an AI / ML model in a given system. The following may be the main aspects and / or components of LCM: data collection, model training, functionality and / or model identification, model delivery and / or transfer, model inference operation, functionality and / or model selection, activation, deactivation, switching, fallback operation, functionality and / or model monitoring, model update, and / or wireless transmit / receive unit (WTRU) (also known as user equipment (UE)) capability reporting and / or identification.

[0075] Data collection may be performed for different purposes in LCM, (e.g., model training, model inference, model monitoring, model selection, and / or model update, etc.) Model training may be performed online or offline. In online training, a model currently being used for inference is trained in real time (e.g., continuously) with the arrival of new training samples / data sets. In offline training, data is collected, the model is trained using the collected data, and / or the trained model may be used later for inference.

[0076] Functionality and / or model identification may refer to a process and / or method of identifying an AI / ML functionality and / or model for the common understanding between the network and the WTRU. Identification of the functionality and / or model can be done offline without over-the-air signaling (e.g., implicitly via implementation where a model’s global ID indicates the functionality the model is to be used for, the training conditions, applicability conditions, etc.), or model identified explicitly via 3GPP based signaling (either initiated by the WTRU or the by the network). Once a model is identified, it may be assigned a local model ID that is used for further signaling in subsequent LCM operations.

[0077] Model delivery and / or transfer may refer to the delivery of an AI / ML model from one entity to another (e.g., from a network node and / or function such as a gNB, CN entity, etc. to the WTRU, etc.). The model being transferred may be already trained or untrained. A model may also be transferredtransparently to the 3GPP network. A WTRU vendor may train the models on an over-the-top (OTT) server and / or deliver the models to the WTRUs transparently to the 3GPP network (e. g . , like any other user plane (UP) traffic).

[0078] Model inference operation may refer to a process of using a trained AI / ML model to produce a set of outputs based on a set of inputs.

[0079] Additional LCM terms may include functionality and / or model selection, activation, deactivation, switching, and / or fallback operation. Selection may refer to choosing a given AI / ML model among multiple models for the same AI / ML function. Activation and / or deactivation may refer to the enabling or disabling of a certain AI / ML model for a specific AI / ML operation. Switching may refer to deactivating a currently active AI / ML model and / or activating another model. Fallback may refer to disabling a certain AI / ML function and / or using a legacy operation that does not employ AI / ML.

[0080] Functionality and / or model monitoring may refer to monitoring and / or observing the inference performance of a given AI / ML model or an AI / ML functionality.

[0081] Model update may refer to the updating of the AI / ML model parameters (e.g., after model (re)- training).

[0082] WTRU capability reporting and / or identification may refer to identifying what AI / ML related capabilities the WTRU has (e.g., supported functionalities, models for each supported functionality, training conditions of the models, and / or applicability conditions of the models, etc.). FIG. 2 depicts the functional framework 200 for AI / ML for NR air interface.

[0083] As described above, data collection may be needed for training of AI / ML models, for both network side models and / or WTRU side models (e.g., if the training is not done at the WTRU). Apart from model training, data collection may be used for other aspects of LTM such as model inference, performance monitoring, and / or model selection, etc.

[0084] Collecting data from CONNECTED WTRUs may be limiting. For example, a multitude of WTRUs may be in I DLE / INACTI VE that were at the right location and / or conditions for collecting data for the training, etc. Even for CONNECTED WTRUs, if the training is done outside the RAN within the mobile network operator (MNO), e.g., core network (CN) and / or operations, administration, and maintenance (OAM), or specially if done outside the MNO (e.g., OTT), the training entity may neither be aware of the WTRU and / or RAN conditions, nor know which WTRUs to collect data from.

[0085] Described herein are methods and / or examples of how to optimally identify WTRUs that have valid conditions (e.g. WTRU conditions and / or network conditions, etc.) to perform an AI / ML related action (e.g.,data collection for model training), instruct them to start performing the action, and / or receive information and / or associated report and / or data when the action has been completed.

[0086] Described herein are methods for monitoring conditions (e.g., validity conditions) to start and / or stop performing AI / ML related actions (e.g., data collection), indicating to the network when the starting conditions are fulfilled (or / and autonomously starting to perform the action), stopping the action when the ending conditions are fulfilled, and / or sending indication to the network (or autonomously sending information / report associated with the performed action).

[0087] A WTRU may perform: sending AI / ML related capability info to the network (e.g., supported functionalities, models, applicability / training condition, processing and / or memory capability, etc.).

[0088] The WTRU may receive a configuration containing one or more of the following: one or more identities (e.g., WTRU identities, paging identities, configuration identities, etc.); one or more actions associated with the identity (e.g., performing measurements, logging measurements, performance monitoring of an AI / ML model and / or functionality, and / or training of an AI / ML model, etc.); one or more configurations required for performing the action (e.g., measurement configurations, AI / ML model and / or functionality to be monitored and / or trained, etc.); one or more conditions (e.g., validity conditions) for starting the one or more actions (e.g., location of the WTRU, time of the day, detected cells, frequencies, and / or RATs, radio signal levels of certain cells and / or beams, WTRU speed, available WTRU power, available WTRU storage, and / or available WTRU processing, etc.) one or more conditions for stopping the one or more actions (e.g., location of the WTRU, time of the day, duration of time the action has been performed, amount / size of data gathered, value(s) or range of values of key performance indicator (KPI(s)) being monitored, training of model finalized / converged, etc.); and / or one or more (e.g., additional) trigger conditions for starting and / or stopping the action (e.g., autonomously when the starting and / or stopping conditions are fulfilled, upon the reception of an explicit indication to start and / or stop the action, etc.).

[0089] The WTRU may monitor the conditions for stopping the action. The WTRU may, upon determining the one or more conditions for stopping the action are fulfilled, perform the following: stop performing the action; send an indication to the network, and / or send a report and / or data associated with the performed action (e.g., autonomously and / or upon an explicit request from the network, etc.).

[0090] The WTRU may start monitoring the validity conditions for starting the action. This monitoring may occur: immediately after receiving the configuration, upon transitioning to a certain radio resource control (RRC) state (e.g., from CONNECTED to I DLE / I NACTI VE or vice versa, etc.); and / or upon an explicit indication from the network to start the action and / or start monitoring the starting conditions. Such anindication may be one or more of: a dedicated message, a broadcast message, and / or a paging message that includes the identity associated with the action / configuration, etc.

[0091] The WTRU may send the indication that the starting and / or stopping conditions are fulfilled to the network: if in CONNECTED mode, via a dedicated message (RRC, medium access control (MAC) control element (CE), and / or uplink control information (UCI), etc.). If in I DLE / I NACTIVE, the WTRU may send the indication via a connection setup and / or resume request message with an associated establishment and / or resume cause value. The indication may include: the condition that is fulfilled, and / or the metric and / or value thereof that fulfilled the condition.

[0092] The WTRU may start monitoring the conditions for stopping the action: immediately after starting the action, upon transitioning to a certain RRC state (e.g., from CONNECTED to I DLE / INACTIVE or vice versa, etc.) upon an explicit indication from the network to stop the action or start monitoring the stopping conditions. Such an indication may be one or more of: a dedicated message, a broadcast message, and / or a paging message that includes the identity associated with the action and / or configuration, etc.

[0093] Examples described herein may provide a flexible and / or enhanced framework to select and / or enable a multitude of WTRUs to participate in AI / ML related operation(s) (e.g., data collection related to an AI / ML model and / or functionality). Such AI / ML related operation(s) may fulfill the validity and / or requirements for performing the operation and collect and / or receive information related to the operation from the WTRUs when the WTRUs have finished performing the operation.

[0094] Described herein are the following terms: the terms AI / ML and AI / ML may be used interchangeably. The terms data, measurements, report, and results may be used interchangeably. The terms connection setup and connection establishment may be used interchangeably. The terms starting conditions and / or validity conditions may be used interchangeably. The terms indication, information, and message may be used interchangeably.

[0095] The term Ax may be used to refer to any of the events A1 , A2, A3, A4, A5, and / or A6. The events may be defined as: Event A1 (serving may become better than (e.g., larger than) a threshold); Event A2 (serving becomes worse than (e.g., smaller than) a threshold); Event A3 (neighbor may become offset better than a special cell (SpCell), where a SpCell may be the primary cell (PCell) or the primary secondary Cell (PSCell), in the case of dual connectivity); Event A4 (neighbor becomes better than threshold); Event A5 (SpCell may become worse than threshold 1 (e.g., a first threshold) and neighbor becomes better than threshold2 (e.g., a second threshold)); and / or Event A6 (neighbor may become offset better than a secondary cell (Scell), e.g., in the case of carrier aggregation).

[0096] The term Bx may be used to refer to any of the events B1 and / or B2, where the events may be defined as: Event B1 (Inter radio access technology (RAT) neighbor becomes better than threshold); and / or Event B2 (PCell becomes worse than threshol d 1 and / or inter RAT neighbor becomes better than threshold2).

[0097] The terms location and position may be used interchangeably. The terms information and report may be used interchangeably.

[0098] The focus of the solutions described herein has been mainly on data collection that can be used for model training, inference, and / or performance monitoring, etc. However, the mechanisms described herein, such as how the WTRU receives the configuration, how the WTRU monitors the conditions, and / or how the WTRU informs the network about outcome of the actions, etc., may apply equally to other functions as well. For example, similar mechanisms may initiate retraining and / or retuning of models at the WTRUs and / or initiate transfer of retrained models from the WTRU to the network. These mechanisms may occur when the training completes and / or some other condition(s) are fulfilled. Such conditions may include: start performance monitoring procedure for certain functionalities and / or models, report performance monitoring results and / or indicate availability of results when the performance monitoring is finished according to some specified conditions (e.g., for a given duration, for a given cell(s) or group of cell(s), and / or based on determined performance results according to some KPIs, etc.).

[0099] As used herein, the term network may refer to the RAN (e.g., gNB) or CN (e.g., an access and mobility function (AMF) and / or a location management function (LMF), etc.). However, the solutions may apply equally if the entity configuring the WTRU is outside the RAN (e.g., OTT server). For example, the OTT server may communicate to the RAN and / or CN regarding the required actions the WTRU may need to perform the starting and / or stopping conditions for the action (e.g., via a proprietary interface). The RAN and / or CN may translate this configuration into a message that can be sent to the WTRU via a 3GPP interface (e.g., RRC message and / or NAS message, etc.). Alternatively, the WTRU may receive the configuration from the OTT server directly (e.g., application layer protocol), and WTRU may need to send a request and / or indication to the RAN and / or CN that the WTRU has received the configuration from the OTT server. The WTRU may then have to receive a confirmation from the RAN and / or CN before it can start working according to the received configuration. A mixed scenario may include the WTRU receiving the configuration from the RAN and / or CN; however, the WTRU may send the data directly to an OTT server (e.g., transparently from the RAN via transparent containers and / or just like a UP data, etc.).

[0100] The solutions described herein may not require the WTRU to be AI / ML capable. For example, a WTRU that is not AI / ML capable may be configured to perform an action, such as data collection, used by the network and / or OTT to collect data for training the AI / ML models of the WTRUs.

[0101] If the WTRU is capable of AI / ML operation, and the action relates to an AI / ML related operation (e.g., performance monitoring and / or training, etc.), then the WTRU may use legacy operation in parallel. Moreover, the WTRU may not use the AI / ML model and / or functionality for inference purposes. For example, if the concerned AI / ML operation is the performance monitoring of beam, CSI, and / or cell measurement prediction, the WTRU may perform the measurements of beams, CSI-RSs, and / or cell level measurements as in legacy, using that to generate the CSI, beam, and / or cell level measurement reports (or perform other associated actions based on that such as beam failure recovery, conditional handover, etc.). The concerned AI / ML model, at the same time running the CSI, beam, and / or cell level measurement predictions may compare the predicted values with the actual values when the prediction time arrives, etc.

[0102] It should be noted that though the focus of the solution descriptions below is on AI / ML related operations such as data collection for training an AI / ML model, the proposed examples and / or frameworks are not limited to AI / ML based operations. Basically, all the solutions can be applied to scenarios where there are some WTRU actions that can be performed under certain conditions (i.e. , validity conditions) and there could be a definite requirements / KPIs that can be used to determine the action has been completed.

[0103] The solutions described herein may be agnostic to the kind of AI / ML model and / or technique used by the WTRU (e.g., the algorithm used, the mechanism such as neural network or what kind of neural network, e.g., depth, parameters, and / or weights of the network, etc.), the origins of the model (e.g., WTRU vendor, operator, and / or network vendor, etc.), or how / where the training of the model is done (e.g., the input data used for the training, where the training is performed, and / or if the training is performed offline or online, etc.). However, the model may be trained based on historical observation of the WTRU’s mobility (e.g., during certain time durations of the day, during which days of the week, and / or at which locations, etc.).

[0104] Furthermore, the following may be assumed: there is some WTRU capability communication between the WTRU and the network about AI / ML capability. Such communication may include, the WTRU indicating to the network the supported AI / ML models and / or functions, confidence level of predictions, and / or time horizon of predictions (e.g., how far along in the future are the prediction being made), etc.

[0105] The WTRU may support several AI / ML models for a certain functionality (e.g., with different prediction time horizons, prediction confidence levels, processing requirements, and / or trained under / for operation in different frequencies, cells, location, and / or times of day, etc.).

[0106] A given AI / ML model may operate in different modes (e.g., with different levels of prediction confidence levels at different prediction time horizons, etc.). The WTRU may choose the AI / ML model to use for a certain functionality. For example, the network may decide for which functionalities the WTRU may use AI / ML based operation. The WTRU may choose the AI / ML model to use. Also, the network may explicitly control the AI / ML model. In such case, the WTRU may provide details of AI / ML models and / or their capabilities and / or the network determines which model to activate for a particular functionality.

[0107] The AI / ML models may be available at the WTRU already trained, or the WTRU may be provided with an untrained AI / ML model and / or train itself.

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

[0109] The AI / ML model may be available at the WTRU but not trained at all or trained for certain WTRU and / or network conditions. The WTRU may train the model, e.g. for the conditions that the model is not trained for.

[0110] The WTRU may indicate capability. For example, if the WTRU is capable of AI / ML operation, it may inform the details of about its capability. This may include one or more of: supported AI / ML functionalities and / or models available for each functionality; capabilities and / or applicability conditions of the models or functionalities (e.g., conditions under which the models and / or functionalities have been trained to work, such as cells, frequencies, WTRU speeds, confidence levels of predictions, time horizons of predictions, and / or network configuration index, etc.); ability to do performance monitoring for the functionalities and / or models (e.g., including any previous recorded performance monitoring results for the functionality and / or model, etc.); and / or ability to do training / re-training of the models (e.g., additional information related to that such as expected time and training data required for the retraining, etc.)

[0111] The WTRU may receive the configuration while in CONNECTED state in a dedicated manner (e.g., RRC reconfiguration message, MAC CE, DCI, etc.).

[0112] The WTRU may receive the configuration in a dedicated manner upon transitioning from CONNECTED state to I DLE / I NACTIVE state (e.g., in the RRC Release message). The WTRU mayreceive the configuration in a broadcast manner (e.g., SIB signaling and / or paging, etc.) while in RRC CONNECTED, IDLE, or INACTIVE state. The WTRU may receive parts of the configuration via dedicated signaling and / or the other parts in a broadcast signaling. The WTRU may be provided with several configurations (e.g., each configuration associated with a configuration index) that it stores. The WTRU may receive a subsequent message from the network indicating which configuration(s) to activate and / or deactivate. For example, the configurations may be received in an RRC message. The activation and / or deactivation of the particular configuration may be signaled via another RRC message, a MAC CE, a DCI, broadcast signaling, and / or paging indication, etc.

[0113] Contents of the configurations and / or associated WTRU actions may include a configuration identity for each configuration or an identity for a group of associated configurations. The configuration and / or a group of configurations may be associated with a WTRU identity (e.g., paging identity). Each configuration and / or group of associated configurations may have one or more WTRU actions associated with the configuration(s).

[0114] The WTRU action may start to perform measurements. These measurements may be one or more of the following: radio signal measurements (e.g., cell level measurements and / or beam measurements, etc.); QoS related measurements (throughput, latency, and / or buffer occupancy, etc.). Handovers and / or cell reselections (number of handovers and / or related metrics such as handover latency, handover interruption time, and / or ping pong handovers, etc.); error conditions (radio link failures and / or handover failures, etc.); WTRU power and / or battery levels; WTRU mobility state / pattern (e.g., speed, direction, and / or location and / or trajectory, etc.); performance of certain AI / ML functionality and / or model (e.g., prediction accuracy, processing and / or memory requirements, etc.)

[0115] The WTRU action may start to log the measurements. The measurement logging could be configured to be raw measurement logging (e.g., log the measurements every time a measurement sample is taken) or based on events (e.g., log the measurements when the measurements fulfill certain conditions). For example, for the radio signal level related measurements, the logging conditions could be when the radio signal level of a certain cell becomes above / below a certain threshold (absolute threshold or relative threshold compared to another cell). In another example, for the QoS related measurements, the logging conditions could be when the UL / DL throughput is above / below a certain throughput threshold. For WTRU mobility related measurements, the logging conditions could be when the WTRU location has changed by a certain distance from previous logging instance or the speed and / or direction has changed by more than a certain threshold, etc.

[0116] The WTRU may log raw measured data. The WTRU may be configured to log filtered data (e.g., filtered data over a certain configured time window using filter coefficients provided in the configuration). The WTRU may log summarized and / or statistical data (e.g., average values, standard deviations, number / frequency of occurrences of certain events; and / pr average time interval between the occurrence of certain events, etc.).

[0117] The WTRU may be configured with contents and / or elements of the information it needs to log in addition to the data being measured. This could contain one or more of the following: time stamp (e.g., absolute time, relative time from a reference time known to both the WTRU and the network, relative time since the reception of the configuration, relative time since the start of performing the action, absolute time for the first measurement log entry and / or relative time for the rest of the measurement log entries, etc.); location (e.g., global navigation satellite system (GNSS) location, current serving cell, cells that the WTRU is currently under coverage where the WTRU considered to be under coverage of a cell if the signal level of the cell is above a certain threshold, etc.); WTRU mobility state (e.g., current speed in absolute terms and / or in ranges (e.g., low mobility and / or, high mobility, etc.), and / or direction ; RRC state; power level; buffer levels; and / or radio signal levels of serving and / or neighbor cells, etc.

[0118] The WTRU action may include the stopping of the performing of the measurements. The WTRU action may include the sending of an indication to the network that measurement logging has been finalized. The WTRU action may include the sending of an indication to the network that logged measurements are available. The WTRU action may include the sending of the logged measurements. The WTRU action may include the training of an AI / ML model (e.g., based on the data being collected). The WTRU action may include the sending of an indication to the network that the training of the model has been finalized (e.g., reached the desired and / or configured convergence level). The WTRU action may include the sending of an indication to the network that the training of the model was not successful (e.g., was not possible to reach the desired and / or configured convergence level).

[0119] Validity and / or applicability conditions for starting the WTRU actions may include configuring the WTRU with validity and / or additional conditions to be fulfilled before the WTRU starts performing the actions (e.g., separate validity conditions for each action, one set of validity conditions for multiple / all actions, certain validity conditions that are common to multiple / all actions and other validity conditions that are specific to each action, etc.).

[0120] The validity and / or additional conditions for starting a WTRU action may relate to the location of the WTRU. For example, this could include one or more of the following: WTRU location being at a certainGNSS coordinates or within a range of co-ordinates; current serving cell of the WTRU being one or more configured cells (e.g., physical cell identities (PCIs) and / or cell global identities (CGIs), etc.); and / or WTRU being under the coverage of one or more configured cells (e.g., PCIs and / or CGIs, etc.) (e.g., cells the WTRU can detect and / or cells that have signal levels above a configured threshold, etc.).

[0121] The validity and / or additional conditions for starting a WTRU action may include the current serving cell and / or the cells the WTRU may detect and / or is under the coverage of is within a configured list of frequencies and / or range of frequencies.

[0122] The validity and / or additional conditions for starting a WTRU action may include the current serving cell and / or the cells that the WTRU my detect and / or covers belongs to a certain RAT (e.g., long term evolution (LTE) and / or new radio (NR), etc.).

[0123] The validity and / or additional conditions for starting a WTRU action may be the current serving cell and / or the cells that the WTRU may detect and / or is under the coverage of may operate under certain conditions that the WTRU can detect. Such conditions may include: bandwidth, specification release, anything the WTRU may detect, (from the broadcast signaling of the cells, or any dedicated information that the WTRU may obtain, (e.g., on demand and / or a push manner from the network in the CONNECTED state, etc.)

[0124] The validity and / or additional conditions for starting a WTRU action may be the current serving cell and / or the cells that the WTRU may detect or is under the coverage of operate under certain network configuration (e.g., a configuration index / identity and / or a list of configuration indexes, etc.). For example, the WTRU may not have to know what this configuration entails, but the WTRU will know that two cells and / or nodes indicate that the configuration they are using (e.g., via broadcast signaling and / or dedicated signaling, etc.) are operating under similar configurations. The detection that the WTRU is being served by a cell or is under the coverage of a cell that indicates a configuration index equal to the configured network configuration index (or within the list of indexes, if more than one index value is configured), the WTRU may consider that the validity conditions for starting the WTRU action is fulfilled.

[0125] The validity and / or additional conditions for starting a WTRU action may include the WTRU battery level being above a certain configured threshold. The validity and / or additional conditions for starting a WTRU action may include the WTRU’s available memory, storage, and / or buffer being above a certain configured threshold (or the used memory, storage, and / or buffer being below a certain configured threshold).

[0126] The validity and / or additional conditions for starting a WTRU action may include the WTRU’s available processing capacity (e.g., percentage) being above a certain configured threshold (e.g., percentage threshold).

[0127] The validity and / or additional conditions for starting a WTRU action may relate to the mobility state of the WTRU. These validity and / or additional conditions may include one or more of the following: WTRU speed being above or below a certain threshold or within two thresholds (e.g., actual speed value, range of speed values, and / or relative change of WTRU speed, etc.); number of handovers (HOs) and / or cell reselections within a given time duration being above or below a certain threshold; and / or WTRU change of direction being above or below a certain configured rate, etc.

[0128] The validity and / or additional conditions for starting a WTRU action may relate to the current time being equal to a configured time instance or within a configured time duration. This may be a specific time instance (e.g., 8:30 am) or a specific time duration (e.g., between 8:30am and 10:30am). In case the time information is a time duration, the WTRU may consider the validity conditions related to the time to be fulfilled any time between the start and end of the time duration.

[0129] The validity and / or additional conditions for starting a WTRU action may relate to the current day being equal to a configured day or is within a configured range of days. This for example, could be a specific day (e.g., December 31st) or a range of days (e.g., between December 25th and 31st), weekdays, weekends, and / or specific days of the week (Mondays and T uesdays), etc.

[0130] The validity and / or additional conditions for starting a WTRU action may be the current RRC connection state of the WTRU being CONNECTED. The validity and / or additional conditions for starting a WTRU action may be the current RRC connection state of the WTRU being IDLE. The validity and / or additional conditions for starting a WTRU action may be the current RRC connection state of the WTRU being INACTIVE.

[0131] The validity and / or additional conditions for starting a WTRU action may be related to the radio signal level of current serving and / or neighbor cells being above a certain absolute or relative threshold (e.g., according to any of the Ax and / or Bx measurement event configuration).

[0132] If the WTRU has an AI / ML model and / or functionality and that model and / or functionality was trained under certain conditions (e.g., WTRU conditions and / or network conditions such as network configuration index, etc.), then the validity conditions for WTRU action may be the determination that the WTRU is under the same WTRU and / or network conditions that the model is trained. For example, a WTRU action that has such a validity condition may be the performance monitoring of the concerned AI / MLmodel and / or functionality. The WTRU may have communicated the information about the training conditions of the functionality and / or model to the network, (e.g., during capability exchange). The network may have received the information otherwise, (e.g., if the network was the entity that trained the model, or the network received the information from a third party, such as a WTRU vendor).

[0133] If the WTRU has an AI / ML model and / or functionality and that model and / or functionality was trained under certain conditions (e.g., WTRU conditions and / or network conditions such as network configuration index, etc.), then the validity conditions for WTRU action may be the determination that the WTRU is not under the same WTRU and / or network conditions that the model is trained. For example, a WTRU action that has such a validity condition may be the performance monitoring of the concerned AI / ML model and / or functionality (e.g., to determine if the model and / or functionality performs well in conditions that it was not trained for) or the WTRU action could be the retraining of the model for the new conditions.

[0134] In the above examples related to model performance monitoring, the WTRU action may just collect data for performance monitoring where the logged and / or collected data may later be used (e.g., for offline and / or online performance monitoring by the network). The WTRU may do the actual performance monitoring (e.g., WTRU doing the performance monitoring itself, and sending the results to the network later).

[0135] In the above examples related to model training, the WTRU action may just collect data for model training, where the logged and / or collected data may later be used (e.g., for offline training of the model by the network). The WTRU may do the actual training. The training may include the WTRU doing the training itself, and / or sending the results to the network later when the training is done, (e.g., according to training convergence criteria).

[0136] The WTRU may consider the validity conditions for starting the WTRU action are fulfilled if one of the validity conditions is fulfilled. For example, a WTRU may consider the validity conditions for starting the WTRU action are fulfilled if either the location related conditions or the time related conditions are fulfilled. For example, the WTRU may start the action if the time of the day is between the configured time duration, and / or the WTRU is served by one of the cells in the configured cell list.

[0137] The WTRU may consider the validity conditions for starting the WTRU action are fulfilled if more than one of the conditions (e.g., at least two) are fulfilled. The WTRU may consider the validity conditions for starting the WTRU action to be fulfilled if both the location and time related conditions are fulfilled. For example, the WTRU may start the action if the time of the day is between the configured time duration, and / or the WTRU is served by one of the cells in the configured cell list.

[0138] The WTRU may consider the validity conditions for starting the WTRU action to be fulfilled if one or more of the sub conditions have been fulfilled for a certain configured time to trigger (TTT). There may be one TTT applicable to all the sub conditions. For example, a TTT may equal 100 ms (milliseconds), and the WTRU is in RRC CONNECTED for at least 100 ms, being served by cell X by at least 100 ms, moving at a certain speed for at least 100 ms, before the WTRU may consider the validity conditions for staring the action to be fulfilled. Separate TTT values may be configured for each sub condition.

[0139] Evaluation of the validity and / or applicability conditions for starting the WTRU actions may include the WTRU starting to evaluate the validity and / or additional conditions immediately after receiving the configurations. The WTRU may start evaluating the validity and / or additional conditions a certain configured time duration after receiving the configurations. The WTRU may starts evaluating the validity and / or additional conditions upon receiving a first indication from the network (e.g., paging, broadcast indication, dedicated indication, etc.).

[0140] The WTRU, upon determining that the validity and / or additional conditions for an action has been fulfilled, may start performing the action immediately. The WTRU, upon determining that the validity and / or additional conditions for an action has been fulfilled, may inform the network.

[0141] The WTRU that has indicated to the network the validity and / or additional conditions have been fulfilled may start performing the actions upon a reception of a second indication from the network to start performing the action.

[0142] If there is a considerable time gap between the WTRU sending the information to the network and / or reception of the second indication (e.g., more than a certain configured time duration threshold), the WTRU may have to re-evaluate the validity conditions before starting to perform the actions. If the validity conditions are no more fulfilled, the WTRU may send an indication to the network. If the validity conditions are still fulfilled, the WTRU may start performing the action.

[0143] The WTRU may not be configured with any validity conditions associated with the start of an action. The WTRU may start the action upon receiving an explicit indication from the network to start the action.

[0144] The WTRU may be configured with validity conditions associated with the start of an action. However, the WTRU may start the action upon receiving an explicit indication from the network even if the validity conditions are not fulfilled. For example, the network indication to start the action may override the fulfillment of the validity conditions.

[0145] Conditions for stopping and / or pausing the WTRU actions may include configuring the WTRU with conditions to be fulfilled before stopping a WTRU action that started according to any of the solutions described above. Separate stopping conditions may exist for each action. One set of conditions for multiple / all actions and / or certain conditions common to multiple / al I actions and other conditions may be specific to each action, etc.).

[0146] The WTRU may consider the stopping conditions to be fulfilled if the validity conditions for starting the action are not fulfilled. The WTRU may be configured with a time duration value. This WTRU may consider the stopping conditions to be fulfilled if the validity conditions remain to be not fulfilled for more than the configured duration.

[0147] The WTRU may be configured with a counter value threshold. The WTRU may increment the counter value (which is set to 0 initially) every time the WTRU detects the validity conditions for starting the action were not fulfilled for more than a certain configured duration. For example, this duration may be less than the configured time duration for stopping the action. The WTRU may consider the stopping conditions to be fulfilled if the WTRU determines that the counter value has reached the configured counter threshold.

[0148] The WTRU may pause the performing of the action upon detecting the validity conditions are not fulfilled but while monitoring if the stopping conditions may be fulfilled according to the solutions above. For example, the WTRU may wait for the time duration conditions to be fulfilled while the validity conditions are not fulfilled. For example, if the validity conditions get fulfilled again before the time duration has elapsed, the WTRU may resume performing the action again.

[0149] If the WTRU action was performance monitoring of an AI / ML model and / or functionality or training of an AI / ML model and / or functionality, then the conditions for stopping the WTRU action may be the determination that the training conditions for the model and / or functionality are no more fulfilled (e.g., WTRU conditions, network conditions such as network configuration index, etc.)

[0150] If the WTRU action was performance monitoring of an AI / ML model and / or functionality or training of an AI / ML model and / or functionality, then the conditions for stopping the WTRU action may be the determination that the training conditions for the model and / or functionality are fulfilled.

[0151] If the WTRU action was the training of an AI / ML model and / or functionality, then the conditions for stopping the WTRU action may be the determination that the training has converged (e.g., according to training convergence criteria, etc.)

[0152] If the WTRU action was the performance monitoring of an AI / ML model and / or functionality, then the conditions for stopping the WTRU action may be the determination that one or more KPIs associatedwith the model and / or functionality has met some configured threshold(s) (e.g., for a given time duration, for a certain number of times, etc.)

[0153] If the WTRU has an AI / ML model and / or functionality and that model and / or functionality was trained under certain conditions (e.g., WTRU conditions, network conditions such as network configuration index, etc.), then the validity conditions for WTRU action may be the determination that the WTRU is under the same or similar WTRU and / or network conditions that the model is trained. For example, a WTRU action that has such a validity condition may be the performance monitoring of the concerned AI / ML model and / or functionality. The WTRU may have communicated the information about the training conditions of the functionality and / or model to the network (e.g., during capability exchange). The network may have the information otherwise, (e.g., if the network was the entity that trained the model), and / or the network may obtained got the information from a third party, such as a WTRU vendor).

[0154] If the WTRU has an AI / ML model and / or functionality and that model and / or functionality was trained under certain conditions (e.g., WTRU conditions, network conditions such as network configuration index, etc.), then the validity conditions for WTRU action may be the determination that the WTRU is not under the same WTRU and / or network conditions that the model is trained. For example, a WTRU action that has such a validity condition may be the performance monitoring of the concerned AI / ML model and / or functionality (e.g., to determine if the model and / or functionality performs well in conditions that it was not trained for) or the WTRU action could be the retraining of the model for the new conditions.

[0155] Relating to model performance monitoring, the WTRU action may just collect data for performance monitoring (where the logged and / or collected data can later be used, e.g., for offline / online performance monitoring by the network). The WTRU may be doing the actual performance monitoring (e.g., WTRU doing the performance monitoring itself and / or sending the results to the network later)

[0156] The WTRU may be configured with a time duration value. The WTRU may consider the stopping conditions to be fulfilled if the WTRU action has been performed for the configured time duration. In an example, the duration of the performance of the action may consider any pausing that might have happened according to the solution above. For example, if the WTRU was configured to perform the action for one hour, and the WTRU pause the performance for two occasions due to the validity conditions not being fulfilled an / or upon explicit pause indication from the network, each with two minute duration, the WTRU may stop the action one hour and four minutes after it has started performing the action. In another example, the WTRU may ignore any time durations during which the action was paused and / or justconsider the total time since the start of the action. Tor the example above, the WTRU may stop the action exactly 1 hour after the start despite the action being performed for 56 minutes.

[0157] The WTRU may be configured with a data size threshold (e.g., amount of data in megabytes (MB or Mbytes), amount of measurement / data records logged, etc.). The WTRU may consider the conditions for stopping the action to be fulfilled if the WTRU has collected more data than the configured data size threshold.

[0158] All the validity conditions for starting the action described above may also be configured as the conditions for stopping the action (e.g., with different values and / or thresholds).

[0159] Like the validity conditions for starting the action, the WTRU may perform one or more of the following: consider the stopping conditions fulfilled if one of the sub conditions are fulfilled; consider the stopping conditions fulfilled if a certain number of sub conditions are fulfilled; and / or consider the stopping conditions fulfilled if all the sub conditions are fulfilled, etc.

[0160] Also, like the validity conditions for starting the action, a TTT may be configured. The TTT may indicate to the WTRU the stopping conditions have to be fulfilled for the TTT duration before the WTRU may consider the conditions to be fulfilled.

[0161] Evaluation of the conditions for stopping / pausing the WTRU actions may include when the WTRU starts evaluating the stopping conditions immediately after starting the action. The WTRU may start evaluating the stopping conditions after performing the WTRU action for a given duration (e.g., the WTRU may be configured to do the action for a minimum time duration). The WTRU may start evaluating the stopping conditions upon receiving an indication from the network (e.g., paging, broadcast indication, and / or dedicated indication, etc.).

[0162] The WTRU, upon determining that the stopping conditions for an action have been fulfilled, may stop performing the action immediately. The WTRU, upon determining that the stopping conditions for an action have been fulfilled, may inform the network.

[0163] The WTRU that has indicated to the network the stopping conditions have been fulfilled, may stop performing the action upon a reception of a follow up indication from the network to stop performing the action. Alternatively, the WTRU may receive an indication from the network to keep performing the action. During the time of sending the indication and / or waiting for the response, the WTRU may keep performing the action or pause the performing of the action.

[0164] The WTRU may not be configured with any stopping conditions for an action. The WTRU may stop the action upon receiving an explicit indication from the network to stop the action.

[0165] The WTRU may be configured with stopping conditions for an action. However, upon receiving an explicit indication from the network, the WTRU may stop the action even if the stopping conditions are not fulfilled.

[0166] The WTRU may receive an indication from the network to pause the action and does so accordingly. The indication may include a time duration the WTRU should pause the action. The WTRU may receive an explicit indication from the network to resume a paused action.

[0167] A WTRU indicating interest and / or availability for performing an action. In examples, the WTRU may send an indication that its availability and / or interest to participate in an AI / ML related action (e.g., data collection). The WTRU may include further detailed information regarding its capability and / or availability to perform that action. This may include one or more of the following (for the case of data collection): time for collecting data (e.g., between two absolute time instances, time duration, and / or days of the week, etc.); locations where data can be collected (e.g, GNSS coordinates, cells, and / or regions, etc.); amount of data that can be logged (e.g, sample interest and / or total data size that can be logged, etc.); maximum time duration the collected data can be stored; current or anticipated WTRU conditions such as battery level, data activity level, and / or mobility pattern or trajectory, etc.); RRC state for collecting the data (e.g, in CONNECTED mode and / or in I DLE / I NACTI VE mode, etc.); and / or other limitations and / or preferences (e.g, if maximum data rate for sending collected data is below a certain threshold, etc.).

[0168] A WTRU that has previously indicated to the network about interest and / or availability to participate in an AI / ML related action may send a subsequent indication to the network that it is no longer interested and / or available. In this indication, the WTRU may further include reason for this, such as change of certain conditions at the WTRU our end user preferences.

[0169] A WTRU may send an indication to the network about interest and / or availability upon an explicit request / indication from the network. A WTRU may send an indication to the network about interest and / or availability even before it has received the configurations regarding WTRU actions, validity conditions, and / or stopping conditions, etc. The WTRU may receive the configuration after it has indicated its interest and / or availability to the network.

[0170] A WTRU may send an indication to the network about interest and / or availability after it has received the configurations regarding WTRU actions, validity conditions, stopping conditions, etc. For example, the WTRU may determine this based on its own implementation and / or based on end user preference.

[0171] The WTRU may receive indications and / or requests from the network and indications and / or responses from the WTRU while in I DLE / I NACTIVE. For example, a WTRU may receive with a configuration regarding an AI / ML related action to perform. The WTRU may further receive associated validity conditions for starting the action and / or conditions for stopping the action, according to any of the solutions described herein. The configuration may include one or more paging identities (e.g., one paging identity associated with starting the action, one paging identity associated with stopping the action, and / or one paging identity associated with sending the data, results, and / or measurements collected during performing the action, etc.).

[0172] A WTRU that may have received such a configuration may be sent by the network to an IDLE / I NACTIVE state. While in IDLE / I NACTIVE state, the WTRU may receive a paging message. Upon determining that the paging identity information includes a paging identity associated with the validity and / or starting conditions of the actions, the WTRU may evaluate the validity conditions for the actions. If the conditions are fulfilled, the WTRU may perform one or more of the following: start performing the action; send an indication that the WTRU has started to perform the action; and / or send an indication that the WTRU may start performing the action (e.g., WTRU may start the action if a subsequent response is received after this).

[0173] In examples, the indication sent by the WTRU is a connection establishment and / or setup request message if the WTRU was in IDLE state. The indication may be a connection resume message if the WTRU was in INACTIVE state. The WTRU may include a resume cause in the message (e.g., a new resume cause configured and / or specified for that purpose).

[0174] In response to that indication, the WTRU may receive a response from the network indicating to start or not start performing the action. The indication may be included in an RRC release message (e.g., if the WTRU is able to perform the action in IDLE / I NACTIVE state) and / or an RRC setup and / or resume message or a separate message after that (e.g., if the WTRU should transition to CONNECTED state to perform the action).

[0175] The WTRU may send the indication during the connection setup and / or resumption. For example, the WTRU may use a resume cause indicating mobile originated data (e.g., uplink (UL) data) is available. The network may send the WTRU a connection setup and / or resume message. The WTRU may include the indication that it has started the action and / or that the WTRU is ready to start the action in the setup and / or resume complete message. The WTRU may send an indication after the connection setup and / or resumption is completed (e.g., in a separate RRC message, MAC CE, and / or UCI, etc.)

[0176] The WTRU may evaluate the validity conditions to start performing the WTRU action. The WTRU may send the indication to the network (e.g., that the WTRU has started the action, or it is ready to start the action) autonomously without waiting to be paged by the network. Any solutions described above may be used for this case. A setup and / or resume may cause value in the setup and / or resume request message, indication in the complete message, and / or indication in a separate message after the connection is setup and / or resumed, etc.

[0177] A WTRU that may have started performing the WTRU action according to any of the solution above may be in an I DLE / INACTIVE state while performing the action. The WTRU may receive a paging message. Upon determining that the paging identity information includes a paging identity associated with the stopping conditions of the WTRU action, the WTRU may evaluate the stopping conditions for the actions. If the conditions are fulfilled, the WTRU may perform one or more of the following: stop performing the action; and / or send an indication indicating that it can stop the action.

[0178] The WTRU may also send an indication indicating that the conditions for stopping the action are not fulfilled yet.

[0179] As in the case of the starting conditions, the WTRU may send this indication in a connection setup and / or resume message (e.g., new resume cause value), in the connection setup and / or resume complete message, or after the connection has been setup or resumed in a separate message (e.g. RRC message, MAC CE, and / or UCI, etc.).

[0180] In response to that indication, the WTRU may receive a response from the network indicating to stop the action (e.g., in an RRC release message, in an RRC setup and / or resume message, and / or in a separate message after the connection establishment / resumption has completed).

[0181] The WTRU may evaluate the stopping conditions for the WTRU action without waiting to get a paging indication from the network. The WTRU may send the indication to the network that it has stopped the action and / or the stopping conditions are fulfilled. Any of the solutions described herein may be used for this case as well. A setup and / or resume may cause value in the setup and / or resume request message, indication in the complete message, and / or indication in a separate message after the connection is setup and / or resumed, etc.

[0182] The WTRU may stop performing the action upon the reception of the paging message without checking the stopping conditions for the action. A WTRU that may have stopped performing the WTRU action according to any of the solutions above may be in an IDLE / INACTIVE state. The WTRU may receive a paging message. Upon determining that the paging identity information includes a paging identityassociated with sending the data, results, and / or measurements collected during the performance of the action, the WTRU may send the collected data to the network (e.g., after transitioning to a CONNECTED state and / or using small data transmission (SDT) if the data to be transmitted is of small size, etc.).

[0183] The WTRU may send the collected data and / or measurements without waiting to be paged by the network. For example, the WTRU may initiate a connection setup and / or resume. The WTRU may then send the collected data after the connection is setup and / or resumed, or using SDT without transitioning into CONNECTED if the data to be transmitted is of small size.

[0184] The paging identities associated with starting the action, stopping the action, and / or sending the action may be the same. The paging message may include extra information indicating this is regarding the starting, stopping of the action, and / or sending of the data. In examples, the WTRU may implicitly determine whether the paging is regarding the starting, stopping of the action, and / or the sending of the data (e.g., related to starting, if the action has not started yet, stopping, if the WTRU has started performing the action, and / or sending of data if the action has been completed, etc.).

[0185] The paging identity or identities may be specific to a WTRU. The paging identity or identities may be common to multiple WTRUs. The paging related solutions may be realized using system information block (SIB) signaling instead. For instance a new SIB may be defined for AI / ML related actions and / or additional information elements (lEs) included in existing SIBs. The WTRUs may be monitoring the changes in the concerned SIB to determine the to start and / or stop the action and / or send the collected data.

[0186] In examples, the WTRUs in CONNECTED mode may be signaled to start and / or stop the WTRU action or send the collected results / data using a dedicated message (e.g., RRC message, MAC CE, and / or DCI, etc.) where the message may include an indication of the configuration (e.g., configuration index) associated with the WTRU action.

[0187] If the conditions for starting the action may be different from the conditions for resuming the action after it has been paused (e.g., different thresholds, etc.). The starting conditions may be common to more than one WTRU action. The stopping conditions may be common to more than one WTRU action.

[0188] Some of the conditions (including the thresholds) may be shared among many actions (for starting conditions and / or stopping conditions, etc.).

[0189] The WTRU may be configured with a nested set of conditions (for starting conditions and / or stopping conditions, etc.). The conditions at the top layer may be evaluated first. If those conditions are fulfilled, the WTRU may start evaluating the next layer of conditions. The WTRU may monitor first itsspeed. If the WTRU determines that speed meets the specified threshold, the WTRU may perform neighbor cell measurements at a certain frequency and / or checking if they meet the configured radio thresholds, etc.

[0190] The measurement configuration for the radio related information may be according to what the WTRU has already been configured for other legacy purposes and / or functionalities such as radio resource management (RRM), radio link monitoring (RLM), mobility drive test (MDT), etc. The WTRU may be provided with a measurement configuration explicitly for the concerned data collection activity.

[0191] A WTRU may be configured with the validity conditions for starting a certain action and / or without the configuration of the action itself. The WTRU may be provided with the configuration of the action and / or informed what action it must take after it has responded to the network that the configured validity conditions are fulfilled.

[0192] The WTRU may monitor the validity conditions for starting a certain action. When those conditions are fulfilled, the WTRU may request the network for assistance information that enables it to perform the action. For example, the validity condition may be a WTRU mobility state (e.g., speed) in certain areas (e.g., list of cells). The WTRU may then send an assistance information related to measurements once it has determined the mobility state conditions for starting the action have been fulfilled (e.g., request for additional measurements and / or reference signals, request for measurement gaps, request for additional information such as current network configuration information, such as configuration index that may be used to collect the right AI / ML model to use, etc.)

[0193] The solutions described herein may enable an entity that controls the LCM operation of an AI / ML functionality and / or model to indicate to all the WTRUs within the system (or within a selected subarea and / or subset of the system) that the WTRU may want some action taken. The AI / ML functionality may indicate that the WTRU may want to get a response from all the WTRUs that have the validity conditions fulfilled to start performing the operation. The AI / ML functionality may indicate that the WTRU may want to choose a subset of the WTRUs to perform the action (e.g., the WTRUs with the most favorable conditions, with the most capability such as processing / battery and possibility to finish the action the fastest, and / or WTRUs that do not already have heavy uplink (UL) traffic, etc. )

[0194] In case the operation is model training, the WTRU may send the trained model (or some parameters related to the trained model) upon the completion of the training (e.g., this can be used for federated learning).

[0195] Methods for monitoring conditions (e.g., validity conditions) to start and / or stop performing AI / ML related actions (e.g., data collection) may indicate to the network when the starting conditions are fulfilled (or / and autonomously starting to perform the action). These methods may further indicate the stopping action when the ending conditions are fulfilled, and / or a sending indication to the network (or autonomously sending information and / or report associated with the performed action).

[0196] A WTRU may perform the following: the WTRU may send AI / ML related capability info to the network (e.g., supported functionalities, models, applicability and / or training condition, processing, memory, and / or capability, etc.

[0197] The WTRU may receive a configuration containing one or more of the following: one or more identities (e.g., WTRU identities, paging Identities, and / or configuration identities, etc.); one or more actions associated with the identity (e.g., performing measurements, logging measurements, performance monitoring of an AI / ML model and / or functionality, training of an AI / ML model, etc.); one or more configurations required for performing the action (e.g., measurement configurations, AI / ML model and / or functionality to be monitored / trained, etc.); one or more conditions (e.g., validity conditions) for starting the one or more actions (e.g., location of the WTRU, time of the day, detected cells, frequencies, and / or RATs, radio signal levels of certain cells and / or beams, WTRU speed, available WTRU power, available WTRU storage, available WTRU processing, etc.); one or more conditions for stopping the one or more actions (e.g., location of the WTRU, time of the day, duration of time the action has been performed, amount and / or size of data gathered, value(s) or range of values of KPI(s) being monitored, and / or training of model finalized and / or converged, etc.); and / or one or more (additional) trigger conditions for starting and / or stopping the action (e.g., autonomously when the starting and / or stopping conditions are fulfilled, upon the reception of an explicit indication to start and / or stop the action, etc.).

[0198] The WTRU may monitor the validity conditions for starting to perform an action. The WTRU may, upon determining the one or more validity conditions for starting the action are fulfilled, send an indication to the network, and / or start performing the action (e.g., autonomously and / or upon getting an acknowledgement from the network, etc.)

[0199] The WTRU may monitor the conditions for stopping the action. The WTRU may, upon determining the one or more conditions for stopping the action are fulfilled, perform the following: stop performing the action; send an indication to the network, and / or send a report and / or data associated with the performed action (e.g., autonomously and / or upon an explicit request from the network, etc.).

[0200] The WTRU may start monitoring the validity conditions for starting the action: immediately after receiving the configuration, upon transitioning to a certain RRC state (e.g., from CONNECTED to IDLE / I NACTI VE or vice versa, etc.); and / or upon an explicit indication from the network to start the action or start monitoring the starting conditions, which could be one or more of: a dedicated message, a broadcast message, a paging message that includes the identity associated with the action / configuration, etc.).

[0201] The WTRU may send the indication that the starting and / or stopping conditions are fulfilled to the network. If in CONNECTED mode, the WTRU may send the indication via a dedicated message (RRC, MAC CE, and / or UCI, etc.). If in IDLE / I NACTIVE, the WTRU may send the indication via a connection setup and / or resume request message with an associated establishment and / or resume cause value. The indication may include the condition that is fulfilled, and / or the metric or value thereof that fulfilled the condition.

[0202] The WTRU may start monitoring the conditions for stopping the action: immediately after starting the action, upon transitioning to a certain RRC state (e.g., from CONNECTED to I DLE / INACTIVE or vice versa, etc.) upon an explicit indication from the network to stop the action or start monitoring the stopping conditions. The stopping conditions may include one or more of: a dedicated message, a broadcast message, and / or a paging message that includes the identity associated with the action / configuration, etc.

[0203] Examples described herein may provide a flexible and enhanced framework to select / enable a multitude of WTRUs to participate in an AI / ML related operation (e.g., data collection related to an AI / ML model and / or functionality). These examples may fulfill the validity and / or requirements for performing the operation and collect and / or receive information related to the operation from the WTRUs when they have finished performing the operation.

[0204] FIG. 3 depicts an example 300 realization of monitoring conditions to start and stop performing AI / ML related actions. At 304, the WTRU, while in CONNECTED state, may receive a configuration containing information about a WTRU action. The WTRU may further receive associated starting and / or stopping conditions and / or paging identities related to the starting and / or stopping of the action and / or the sending of the collected data during the performance of the action. At 308, the WTRU may store the configuration. At 312, the WTRU is transitioned to an IDLE / I NACTIVE state (e.g., due to user plane (UP) data inactivity). At 316, the WTRU may receive a paging message, with the paging identity associated with starting the WTRU action. At 320, the WTRU may check if the starting conditions are fulfilled. At 324, upon determining the conditions are fulfilled, the WTRU may start performing the action. At 328, the WTRU may send an indication to the network that the WTRU has started performing the action. The WTRU maysend, as part of the indication, a new resume and / or setup cause value in a resume and / or setup request message. At 332, the WTRU may receive an instruction to remain in the I DLE / I NACTIVE state (e.g., RRC release). At 336, the WTRU may check if the stopping conditions are fulfilled. At 340, upon determining the conditions are fulfilled, the WTRU may stop performing the action. At 344, the WTRU may receive a paging message. The paging identity may be associated with sending the collected data. At 348, the WTRU may send an indication to the network that the WTRU has finished performing the action and has data available (with a new resume and / or setup cause value in a resume and / or setup request message. At 352, the WTRU may receive an indication from the network to transition to CONNECTED state. At 356, the WTRU may indicate to the network the WTRU has successfully transitioned to CONNECTED state. At 360, the WTRU may send the collected data.

Claims

CLAIMSWhat is claimed is:1 . A wireless transmit / receive unit (WTRU), comprising a processor and a memory, the processor configured to: receive a configuration information, the configuration information comprises one or more paging identities, one or more actions associated with each of the one or more paging identities, one or more configurations for performing the one or more actions, one or more conditions for starting the one or more actions, and one more conditions for stopping the one or more actions, wherein the one or more actions are associated with an artificial intelligence or machine learning (AI / ML) model; monitor the one or more conditions for starting the one or more actions; determine that the one or more conditions for starting the one or more actions are satisfied; start each of the one or more actions whose conditions for starting are satisfied; monitor the one or more conditions for stopping the one or more actions; determine whether one or more conditions for stopping the one or more actions are satisfied; stop each of the one or more actions whose conditions for stopping are satisfied; and send a report comprising the collected data associated with the performed one or more actions.

2. The WTRU of claim 1 , wherein the one or more actions comprise performing measurements, logging measurements, monitoring performance of the AI / ML model, or training the AI / ML model.

3. The WTRU of claim 2, wherein measurements to be performed comprise one or more of radio signal measurements, quality of service (QoS) related measurements, handover and cell reselection metrics, error conditions, power and battery levels, WTRU mobility state and path measurements, or AI / ML model performance.

4. The WTRU of claim 2, wherein the processor is configured to: log measurements based on a serving cell being above a threshold, and stop logging measurements based on the serving cell being below a threshold.

5. The WTRU of claim 1 , wherein the one or more configurations for performing the one or more actions comprise one or more of measurement configurations, AI / ML model monitoring configurations, or AI / ML model training configurations.

6. The WTRU of claim 1 , wherein the one or more conditions for starting the one or more actions comprises one or more of a paging message, wherein the paging message comprises a paging identity associated with starting the action, or fulfillment of a first condition of the one or more actions, wherein the first condition is associated with starting the action, and wherein the one or more conditions for starting the one or more actions comprises one or more of validity conditions, a location of the WTRU, time of day, detected cells, radio signal levels of one or more beams, a buffer level being above a threshold, WTRU speed, available WTRU power, available WTRU storage, or available WTRU processing.

7. The WTRU of claim 1 , wherein the one or more conditions for stopping the one or more actions comprises one or more of a paging message, wherein the paging message comprises a paging identity associated with stopping the action, or fulfillment of a second condition of the one or more conditions for stopping the one or more actions, wherein the second condition is associated with stopping the action, and wherein the one or more conditions for stopping the one or more actions comprises one or more of a location of the WTRU, time of day, duration the action has been performed, amount of data collected, a range of values of key performance indicators, a buffer level being lower than a threshold, or AI / ML functionality and / or model training.

8. The WTRU of claim 1 , wherein the processor is further configured to: send AI / ML capability information, wherein the AI / ML capability information comprises one or more of supported AI / ML functionalities, supported AI / ML models, applicability or AI / ML training conditions, processing capability, or memory capability.

9. The WTRU of claim 1 , wherein the processor is further configured to: receive a message indicating that the one or more configurations for performing the one or more actions can be activated or deactivated; andactivate or deactivate the one or more configurations for performing the one or more actions based on the message.

10. The WTRU of claim 1 , wherein the processor is further configured to: send, after determining that the one or more conditions for starting the one or more actions are satisfied, an indication that the one or more conditions for performing the starting the one or more actions are satisfied; and send, after determining that the one or more conditions for stopping the one or more actions are satisfied, an indication that the one or more conditions for stopping the one or more actions are satisfied.

11. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: receiving a configuration information, the configuration information comprises one or more paging identities, one or more actions associated with each of the one or more paging identities, one or more configurations for performing the one or more actions, one or more conditions for starting the one or more actions, and one more conditions for stopping the one or more actions, wherein the one or more actions are associated with an artificial intelligence or machine learning (AI / ML) model; monitoring the one or more conditions for starting the one or more actions; determining that the one or more conditions for starting the one or more actions are satisfied; starting each of the one or more actions whose conditions for starting are satisfied; monitoring the one or more conditions for stopping the one or more actions; determining whether one or more conditions for stopping the one or more actions are satisfied; stopping each of the one or more actions whose conditions for stopping are satisfied; and sending a report comprising the collected data associated with the performed one or more actions.

12. The method of claim 11 , wherein the one or more actions comprise performing measurements, logging measurements, monitoring performance of the AI / ML model, or training the AI / ML model.

13. The method of claim 12, wherein measurements to be performed comprise one or more of radio signal measurements, quality of service (QoS) related measurements, handover and cell reselection metrics, error conditions, power and battery levels, WTRU mobility state and path measurements, or AI / ML model performance.

14. The method of claim 12, further comprising: logging measurements based on a serving cell being above a threshold, and stopping logging measurements based on the serving cell being below a threshold.

15. The method of claim 11 , wherein the one or more configurations for performing the one or more actions comprise one or more of measurement configurations, AI / ML model monitoring configurations, or AI / ML model training configurations.

16. The method of claim 11 , wherein the one or more conditions for performing the starting the one or more actions comprises one or more of a paging message, wherein the paging message comprises paging identity associated with starting the action, or a fulfillment of a first condition of the one or more actions, wherein the first condition is associated with starting the action, and wherein the one or more conditions for starting the one or more actions comprises one or more of validity conditions, a location of the WTRU, time of day, detected cells, radio signal levels of one or more beams, a buffer level being above a threshold, WTRU speed, available WTRU power, available WTRU storage, or available WTRU processing.

17. The method of claim 11 , wherein the one or more conditions for stopping the one or more actions comprises one or more of a paging message, wherein the paging message comprises a paging identity associated with stopping the action, or fulfillment of a second condition of the one or more conditions for stopping the one or more actions, wherein the second condition is associated with stopping the action, and wherein the one or more conditions for stopping the one or more actions comprises one or more of a location of the WTRU, time of day, duration the action has been performed, amount of data collected, a range of values of key performance indicators, a buffer level being lower than a threshold, or AI / ML functionality and / or model training.

18. The method of claim 11 , further comprising: sending AI / ML capability information, wherein the AI / ML capability information comprises one or more of supported AI / ML functionalities, supported AI / ML models, applicability or AI / ML training conditions, processing capability, or memory capability.

19. The method of claim 11 , further comprising: receiving a message indicating that the one or more configurations for performing the one or more actions can be activated or deactivated; and activating or deactivating the one or more configurations for performing the one or more actions based on the message.

20. The method of claim 11 , further comprising: sending, after determining that the one or more conditions for starting the one or more actions are satisfied, an indication that the one or more conditions for performing the starting the one or more actions are satisfied; and sending, after determining that the one or more conditions for stopping the one or more actions are satisfied, an indication that the one or more conditions for stopping the one or more actions are satisfied.

Images